adding wisdm v2.5.0

[spearmangillman]

Important not for PR reviewers

Before merging the PR, please rebuild the package index using the rebuild-metadata.ps1 script

Summary by CodeRabbit

• New Features
  • wisdm 2.5.0 now includes two new online example libraries with dedicated resources and imagery: a Sparrow distribution modeling library and a Maxent example library for reference and learning.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds new metadata.xml manifest file for wisdm 2.5.0 package, defining package metadata including name, version, description, URL, and release location. Introduces two online library entries: wisdm-example and wisdm-maxent-example, each with associated storage and image URLs.

Changes

Cohort / File(s)	Summary
Package Manifest wisdm-2.5.0/metadata.xml	New manifest file defining wisdm 2.5.0 package metadata with two onlineLibrary entries (wisdm-example, wisdm-maxent-example), each with storage and image URLs

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• adding wisdm v2.4.1 #32 — Adds wisdm metadata.xml manifest for a different package version with the same two onlineLibrary entries

Suggested reviewers

• afilazzola
• christopher-givelas
• katieb1

Poem

🐰 Two libraries bloom in metadata's spring,
wisdm-example and maxent take wing,
URLs pointing to storage so bright,
A manifest manifest of pure delight! 📚✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'adding wisdm v2.5.0' clearly and specifically describes the main change in the pull request: adding a new version of the wisdm package.
Description check	✅ Passed	The pull request description matches the required template and includes the important instruction for maintainers to rebuild the package index before merging.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@wisdm-2.5.0/metadata.xml`:
- Around line 1-7: The package location URL in the <package> element (attributes
name="wisdm" version="2.5.0" location="...") is returning 404; update the
location attribute to a valid, reachable release asset URL (or re-upload the
wisdm-2-5-0.ssimpkg to that GitHub release) so the file at the URL resolves with
HTTP 200, then verify the URL and version (version="2.5.0") match the actual
release asset name and encoding; alternatively replace the location with a
working hosted URL (e.g., the correct GitHub release asset path or an S3 URL)
and confirm the package installs.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8ae8c94 and 9faf07a.

📒 Files selected for processing (1)

• wisdm-2.5.0/metadata.xml

🔇 Additional comments (2)

wisdm-2.5.0/metadata.xml (2)

17-23: The wisdm-maxent-example library entry is correctly structured and consistent with the first entry.

Both onlineLibrary entries follow the same XML structure and naming conventions. The S3 resources are accessible and properly configured for v2.5.0.

---

9-15: First online library entry is properly structured with accessible S3 resources.

The wisdm-example library entry has all required attributes with consistent S3 URL paths using v2.5.0. Both the library package (wisdm-example.ssimbak) and image (wisdm-example.png) are accessible.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

# First, let's locate and read the actual metadata.xml file
find . -name "metadata.xml" -type f 2>/dev/null | head -20

Repository: syncrosim/packages.v3

Length of output: 774

---

🏁 Script executed:

# Verify the GitHub release URL
curl -sI "https://github.com/ApexRMS/wisdm/releases/download/2.5.0/wisdm-2-5-0.ssimpkg" 2>&1 | head -20

Repository: syncrosim/packages.v3

Length of output: 760

---

🏁 Script executed:

# Also check for the file path mentioned in the review
if [ -f "wisdm-2.5.0/metadata.xml" ]; then
  cat "wisdm-2.5.0/metadata.xml"
else
  echo "File not found at wisdm-2.5.0/metadata.xml"
fi

Repository: syncrosim/packages.v3

Length of output: 1291

---

Package location URL is inaccessible (404 Not Found).

The GitHub release URL returns an HTTP 404 error, indicating the package file does not exist at the specified location. This must be resolved before the metadata can be used. The URL points to: https://github.com/ApexRMS/wisdm/releases/download/2.5.0/wisdm-2-5-0.ssimpkg

The XML structure itself is well-formed with consistent version numbering (2.5.0), and the onlineLibrary references are properly configured with S3 URLs. However, the broken package location URL prevents installation.

🤖 Prompt for AI Agents

In `@wisdm-2.5.0/metadata.xml` around lines 1 - 7, The package location URL in the
<package> element (attributes name="wisdm" version="2.5.0" location="...") is
returning 404; update the location attribute to a valid, reachable release asset
URL (or re-upload the wisdm-2-5-0.ssimpkg to that GitHub release) so the file at
the URL resolves with HTTP 200, then verify the URL and version
(version="2.5.0") match the actual release asset name and encoding;
alternatively replace the location with a working hosted URL (e.g., the correct
GitHub release asset path or an S3 URL) and confirm the package installs.

[christopher-givelas]

@spearmangillman is this PR still valid?