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.
1880 results found
-
Alma Purchase Request Facets - filter by fiscal year
It would be helpful to have facets in the Alma Purchasing requests to be able to filter out orders by fiscal year. The fund codes connected to the orders have fiscal years attached to them. It would be helpful to only be able to see the orders that are within the current fiscal year and not every order ever entered.
3 votes -
Indications rules for holding records
We are looking to filter sets with an indication rule to look in holding records to see if a 9XX field exists.
1 vote -
Improve the efficiency and accuracy of Check call no.
In the Aleph environment, when a cataloger presses F3 in the MARC tag of call number (050), they can see "all" similar call numbers. This helps them to decide the call number for the record they are working on. The system does not differentiate whether these are physical or electronic resources, or whether they have holdings. However, in the Alma environment, when in the same call number (050) MARC tag, it is not possible to see "all" call numbers of records in the system, especially not for electronic resources. This significantly increases the difficulty for catalogers in deciding the call…
3 votes -
Add Electronic Service Information Update Job
Electronic Portfolios and Electronic Collections each have an Information Update job in Alma. Electronic services need the same functionality because they are also affected in bulk by changes.
Job Name: Change Electronic service information
Job Description: Update Electronic service information for a set of Electronic services
Job Content Type: Electronic Service
Job Type: Information UpdateUse Case: ProQuest began requiring a value for the CLIENTID parameter in the Linking Parser Parameters section of all ProQuest electronic services. With over 50 ProQuest electronic collections activated, that meant that over 50 electronic services had to be manually edited one at a time…
3 votes -
Resource Sharing Loan Due Date
It would be ideal if a Loan Due Date could be a standardized length. Currently Loan Due Date= Due Date minus transit time and holdshelf. Often this results in an inconsistent length of time. This is most evident when loan periods are short. For example, if an item has a 14 day loan policy according to the Loan TOU, and the Lending Resource Sharing TOU Due Date is set at 21 days, the loan period could be 17 days.
We would prefer that Loan Due Dates follow the pattern:
If Loan TOU is shorter than {Due Date - Transit and…9 votes -
Selecting multiple sets of bibliographic records to export just in one go
At the moment the process to export multiple bib record sets is quite time-consuming since sets can only be selected one at a time. That means that if there are ten sets of bib records to export, the same procedure must be repeated ten times.
I wanted to suggest that from the Run a job screen it is possible just to select/tick in one go all the sets that need to be exported. It would be an enormous time-saver. I attach a screenshot for reference. Thanks3 votes -
Corollary suggestion to "Copy POL data to new POL with different order line type"
I would like to see Rollover of POLs receive a new rollover rules-build.
It would be extremely helpful if POL rollover could be done ledger-by-ledger if desired.
In addition, I (and maybe others? vote for this!) would like an option for firm orders to roll ONLY if they're still 'open', i.e. not 'closed', and not 'invoiced' (is rollover of firm orders ordered, received, AND PAID in one fiscal year into the next EVER useful? I doubt it myself...). Voyager did something like this with firm order rollover. I can't remember whether its rules just made sense, or if I adjusted…
2 votes -
Sort Option for Data Start Date or Data End Date in SUSHI Area/Vendor Details
It would be helpful to add a sort option for the 'Data Start Date and Data End Date" when analysing SUSHI reports that have been uploaded to the vendor details area/profile. When doing a custom harvest or uploading data it would make it so easy to see what date ranges have been uploaded and/or harvested. There is already sort functionality for the file name, uploaded date, SUSHI account and others, please see screen shot. I honestly think this is too important not to have been considered.
1 vote -
Merge records between IZ and NZ in batch
You cannot merge bibliographic records in batch from separate zones. We would like to encourage institutions to improve NZ bibliographic records by having users be able to do this within their own IZ instead of having to set up with the central office a separate external process for records to be updated in batch in the NZ.
1 vote -
rename "Draft" status during ledger rollover
When you run the "Rollover Ledgers" job, you can choose either "Draft" or "Active":
• If you choose "Draft," Alma creates a ledger with status "Inactive"
• If you choose "Active," Alma creates a ledger with status "Active""Draft" should be renamed "Inactive" in the ledger rollover menu because it creates an inactive ledger, not a draft ledger.
This is a problem because many staff mistakenly think choosing "Draft" will roll over the ledger in report mode. This is a reasonable assumption since report mode is available for PO line rollover.
1 vote -
Make physical item templates available in receiving workflow
The new physical item templates look super useful. However, the vast majority of our new items are added as part of our receiving workflow, so they do us little good currently. Can the physical item templates be made available as part of the receiving workflow?
38 votes -
Deleting Bib in NZ if record not Held by other IZs - Delete bib records job
When running the "Delete bibliographic records" job on a set of bib records in the IZ, check if the records being deleted are not held by any other members and if not - delete the bib on the NZ as well.
1 vote -
Bib Suppressed in NZ - Not showed suppressed in lZ
When a bib record is suppressed from Discovery at NZ level, it would be nice to have the Suppressed Icon when searching for the same bib record at the IZ level in the Network tab.
1 vote -
Improve "Select all" search results selection
When running a search within Alma, we have the option to "Select All", at which point we can accomplish various tasks like "Push selected to MDE" (for a Physical Titles search), "Add to Itemized Set" and "Create Itemized Set" (for a Physical Items search), etc.
However, when clicking "Select All", this only selects the results on that page of results, which is capped at 50. If you create a search with many pages of results, you would have to take action on each page individually. Clicking "Select All" should actually select all results, not just the results on that page--or…
25 votes -
mergent market atlas
Mergent has a new product that is replacing Mergent Online, which will be sunsetting in 2025. The replacement product is Market Atlas.
https://marketatlas.mergent.com. Are there plans to add this new collection?0 votes -
Implement Upload Electronic Holdings (Autoholdings) integration for Emerald
Implement Upload Electronic Holdings (Autoholdings) integration for Emerald, as is already available for ProQuest, Elsevier, Ovid, Springer, Project MUSE, JSTOR.
3 votes -
Add "equal" option to the title search "Authority id" index
When searching for titles by authority ID, currently the search supports searching with: Contains keywords, contains phrase, is empty, not contains keywords, not contains phrase, is not empty.
Add the option to also search by "equals".0 votes -
"Show linked bibliographic records" action in Authorities search.
Add a new action in the Authorities search, that will allow navigating to the bibliographic records in the institution's catalog that have bib headings linked to that authority record.
0 votes -
Delete Bibliographic Records Job should be able to be restricted to the different Related Record Types
The "Delete Bibliographic Records" job can be executed with "Do not delete if related to other records", but the parameter takes into account any Related Record Type to other bib records. We think it would be a great improvement if "Do not delete if related to other records" could be used to optionally select the exact Related Record Types that should be used for running the job. This selection would be very similar to the functionality for consortia "Restrict Deletion of Network Zone Bibliographic Records with Related Records " with Configuration > Resources > Collection Retention > Bibliographic Record Deletion…
7 votes -
Provide DOI agency integrations for Alma Digital
There is now a handle integration for Alma Digital as well as Esploro - great.
There are Crossref and DataCite DOI integrations for Esploro (https://knowledge.exlibrisgroup.com/Esploro/Product_Documentation/Esploro_Online_Help_(English)/Esploro_Integration/Configuring_External_Systems_in_Esploro), but not for Alma D.
Please consider adapting these for Alma Digital resources. This would support institutions who might be hosting student theses and other scholarly comms in Alma D, and complement the handle integration.
10 votes
- Don't see your idea?