[Erin Nettifee]

The Availability API documentation is incorrect, at least for Summon over Alma > the parameter is s.id and not id.

Also, it would help to specify that the id is the availability id, which appears at least in our case to be the Alma holdings ID. The availability id string is CATALOG_DB_ID + ” ” + Alma holdings id.

(I didn’t see another space to submit this feedback, but maybe if someone is confused and searching they’ll find this board post and save themselves some time.

[Alexandra Mackenzie]

Nice catch — for Summon over Alma the correct query parameter is s.id, not id. Also good to clarify that the availability id you see is CATALOG_DB_ID + ” ” + <Alma holdings id>. Recommend filing a docs issue or contacting Ex Libris support so they update the documentation — that’ll save others a headache.

[Alexandra Mackenzie]

In the Ex Libris Developer Network forum, users discuss an error in the Availability API documentation for Summon over Alma, where the parameter should be s.id instead of id. This distinction is crucial for accurately retrieving item availability, as id refers to a combination of catalog and holdings identifiers. Clear understanding of these parameters helps developers avoid confusion when working with the API. When sharing code snippets or configuration files during troubleshooting, using reliable online fax services ensures documents are transmitted securely and efficiently. These modern tools provide a better alternative to outdated communication methods that can cause delays and errors, improving collaboration and speeding up problem resolution within development teams.

• This reply was modified 1 month, 3 weeks ago by Alexandra Mackenzie.
• This reply was modified 1 month, 3 weeks ago by Alexandra Mackenzie.

[Author]

Posts