Alma
Your feedback matters to us. Help us improve Alma by telling us what you’d like to see using the message areas below. You can also can support something already posted.
We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.
For more information please review our FAQ and guidelines. Thank you.
9 results found
-
Add API call to fetch all holdings and items associated with one bib record (MMSid)
It would be great to have a single API call to fetch all holdings and items related to an MMS id, which would return all this data in one big XML file. The way it works now, if you want to get, say, all of the barcodes for all items associated with a single MMS id, you have to do an api call for every holding record. So if you have a bib that has one item in 6 different locations, you have to do 6 API calls.
66 votes -
Patron Self Registration
Make Patron Self Registration possible via Primo. This feature would need to be configurable by libraries and able to be turned off altogether by the library. Configuration options could include: what data elements are required, whether new accounts need to be reviewed before they are active.
56 votesThanks for the idea. This is already supported and can be defined as part of the Social and Email Login setup. For more information please refer to https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/090Integrations_with_External_Systems/060Authentication/060Social_and_Email_Login
-
api isbn
I would love to see the API suit expanded to allow retrieval of bibliographic MARCXML and JSON based on other standard identifiers, such as ISBN/ISSN or OCLC number.
13 votes -
Create combined IZ and NZ file for Google Scholar
We would like to be able to publish our IZ electronic portfolios and NZ electronic portfolios available for us in one file to Google Scholar. Google Scholar publishing is very problematic for consortia with electronic inventory set up at both the IZ and NZ level. Right now, even though most of our electronic holdings info is set up in the NZ, only our IZ holdings file gets published to GS. In Salesforce, we've been told that (unlike in the SFX days) there is no way to combine the two files for all e-resources available at an institution. As a result,…
12 votesPlease see comment by Asaf Kline about existing functionality.
-
API query to retrieve only those user accounts where active fines/fees exist
We want to export user fine/fee data to our SIS (PeopleSoft) while retaining the ability to manage patron fine/fees in Alma. The Alma bursar export does not meet our needs because it closes out the fine/fees in Alma. The user API only allows for checking accounts individually to determine whether a fine/fee exists. The 'users' query does not provide a filter for whether a fine/fee is on the retrieved user's account.
11 votesThe Export User Blocks action in the Users Integration Profile ? This action is used to export users that should be blocked due to unpaid fines. It can be used to routinely export a list of users that owe more than a given amount.
-
API for fetching datetime for Alma Analytics data
Add an API call to fetch the value of the two datetime objects that can be seen in Alma GUI:
- Data available as of
- Data updated as of
This will make it much easier for jobs that run daily and that is dependent on Alma Analytics data and that needs to be run as early as possible.
6 votes -
Fines/Fees API needs a PUT option to allow us to change the status of the loan
We have several fines/fees that have been paid or waived that are still in ACTIVE status. We would like to be able to change the status, either in Alma (one at a time) or with the API so that we could change multiple transactions.
3 votesThe Pay/waive/dispute/restore user fine/fee API can be used to pay fines (see https://developers.exlibrisgroup.com/alma/apis/docs/users/UE9TVCAvYWxtYXdzL3YxL3VzZXJzL3t1c2VyX2lkfS9mZWVzL3tmZWVfaWR9/).
-
API support for monitoring Alma publishing and Primo updating data flow
Currently, the monitoring of Alma-side import and publishing jobs, and Primo-side pipes and indexing processes must be performed manually. Job status information should be accessible via API, so institutions could make this manual monitoring work much more automated.
1 vote -
Allow for format de-duplicating in YBP Real Time Ordering
When we were testing the Real-Time Integration between YBP and Alma, we found that if we own either the print or electronic format, but we receive a request for the other format, the order attaches to the existing bib, even if it is in the wrong format. In these cases, if the format is different, what should happen is that the system should create a new brief MMS record for the order's format. I've been told that adding additional matchpoints to prevent this would have to be an enhancement request. As YBP has told me that three other libraries also…
0 votes
- Don't see your idea?