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
-
Library level patron limits configuration
It should be possible to configure the Patron Limits table at the library level. Only Max Cash, Max Overdue and Max overdue recalls should be configurable, so that each library will be able to control when it starts blocking patrons independently of one another.
13 votes -
Further filtering in Authority control task list
We are regularly getting old bib records in the Authority control task list and they make it hard for us to spot new bib headings that we need to add to our local authority file. It would be very helpful if it would be possible to filter the list by creation date to limit the list to new bib records.
34 votes -
Creating expected items in status acquisition without using prediction pattern
In the current workflow for periodicals, when using predicted items, there is no easy way to add just one predicted item. This means that if we make a mistake or there is a change in the publication pattern, for example we receive the wrong item/delete the wrong item, or that a periodical is published as a combined issue (ex: issue 2 and 3 together, as number 2/3 2023), there is no easy way to fix it. We must then create predicted items for that whole year again which involves editing “next predicted item information” in the metadata editor, opening and…
32 votes -
Analytics: Add the country to subject Area digital usage details
The country of download and the organization are key information about the digital usage details as they add value and context to the statistics. This information is very important to our institution. Would it be possible to add the country, country code and organization to the digital usage details the same way as in Esploro subject area Asset usage details
17 votes -
Have AFN/FN loan/fine information available in IZ
Similar idea to https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/44761048-user-purge-should-be-made-afn-aware-and-not-allow
BUT there should be information in the IZ analytics so that an IZ can determine if a local patron has an AFN (or FN) loan or fine.
This doesn't need to be the full loan/fine information, but could be as simple as a flag that says "active AFN/FN loan", "active AFN/FN fine".
At this time, there is no way in the IZ (without opening each patron account within Alma) to see if someone has an active loan or fine outside of the IZ.
This is required at a number of our institutions for when patrons leave…
10 votes -
Combining "Request Type", "Work Order Type" & "Process Type" in a single analytics report
We'd like to retrieve a full list (with breakdown of all Work Order Type, including withdrawn, display, missing, not for circulation items…etc) of physical records by Material Type, Word Order Type & Process Type via Analytics. However, only part of records can be retrieved currently after combining Process Type & Work Order Type together. After consulting Salesforce, it is confirmed Analytics do not support to combine these fields together in a single report. It's crucial to enable combining these fields in a report as library always need to review the figures of each Work Order Type & Process Type, not…
12 votes -
Ability to report on inventory for citations
We would like to analyse print and electronic inventory for citations for a single or multiple reading lists. We're interested to look at reading lists with high or low print/electronic inventory so that we could engage with reading list owners e.g. for lists with high amounts of print we may want to look at the addition of e-book versions of the titles.
Currently it is not possible to report on print and electronic inventory for citations due to the fact that the 'locate' process links the citation to a particular bibliographic record and it's consequently not possible to connect from…22 votes -
Lending Ship item physically check item barcode matches title
When staff use "Ship Item Physically" from an individual request, there is no check that the item barcode entered into the Ship form matches the item barcode for the title. Staff can accidentally scan a barcode for a different request.
Because the item barcode is already in use, the other request can't be Shipped.
Adding a General setting to check that the item barcode matches the located title would help prevent workflow errors.
24 votes -
"Plugin Thresholds" for General E-Services
For SFX a "plugin threshold" is known as an almost arbitrary complex condition (evaluated by any sort of locally developed script code returning 1=true or 0=false) on the contextual relevancy of a certain service. The Alma link resolver should not stand behind and be able to employ any third party web service for the evaluation of conditions too complex to be stated by means of its out-of-the-box types of thresholds.
8 votes -
Add all Enumeration and Chronology fields to the Inventory Information tab of an Import Profile
Currently, only Enumeration A - C and Chronology I - K are listed in the Inventory Information tab of our Import Profiles. Our consortia uses Enumeration A-D; Enumeration D specifically is used for free-text phrases that do not conveniently fit into the category of volume, number or issue; so "index", "part", "box", etc. are all written in EnumD. This is why it is frustrating that this enumeration field cannot be imported via an import profile.
It would be immensely helpful for us if all enumeration fields were listed in the import profile. There is no point in having so many…
55 votes -
Enhance the comprehensiveness of Analytics of usage analysis
For some vendors, it may have sub-databases in the subscriptions and collect usage for a particular database and the titles within seems not possible currently by Analytics. Though there’s a “Platform” field in Analytics, it did not separate the figures between different databases for a single vendor. It's strongly recommended to enhance the comprehensiveness of Analytics and enhance the functionality of usage analysis.
21 votes -
Finished claiming job does not give the library the option to check which vendors received a claim letter
When a claiming job is finished running in Alma you can view “events” from the finished job. This gives a line for each claim processed in the job, and lists three different identifiers: JOBID, POLINEID and VENDORID. None of these identifiers are searchable for the library, and the library then have no option to control what letters were sent in that specific job. If the identifiers listed in the job events were changed to the PO line reference and the vendor code the library would have the option to find the relevant POL and vendor and…
28 votes -
Add read-only parameter to Users > Role
In the Users subject area, you can report on roles, but not if a role is read-only. This means that reporting on who has administrator roles is very confusing and implies more access than may actually exist. That value needs to be added to this subject area.
4 votes -
Free text box in request forms
In the same way that there is a generic tick box built into all of the request forms, it would be useful to have a generic input box where we can request additional information about the request without having to contact them afterwards (such as purpose of loan).
9 votes -
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 -
Filter OUT cancelled PO Lines
Provide a facet to filter OUT cancelled PO Lines in the PO Line view. We have a lot of cancelled PO Lines with the same title as existing PO Lines, and it is confusing and time consuming to find the 'active' PO Lines. It would help us tremendously if we could filter OUT cancelled PO Lines, perhaps even by default.
14 votes -
Authority data: first indicator in the bibliographic record
Now we have many mistakes in our bibliographic records in the settings of the first indicator by connecting with authority data (GND, IdRef, ..). It would be great to have an automatic process, which takes over the first indicator of the authority data to the bibliographic record when you select the authority heading.
What you have then is the following: First indicator, preferred term and authority identifier are taken over from the authority record to the bibliographic record by using “select” in the index view of the authority record.
It would be great, if this is implemented for 1XX/6XX/7XX in…31 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 -
Ability to Set "Current Year" Embargoes
In Alma, coverage settings for embargoes assume a "moving wall" style of embargo where new content is available every month. However, some periodicals operate on the basis of a "current year" style of embargo where coverage is fixed throughout the year, and only rolls over in January.
Currently, our only solutions to manage a "current year" embargo are to either set a shorter embargo, meaning unlicensed content would be discoverable in Primo or to set a longer embargo, meaning not all licensed content would be discoverable in Primo.
We'd like to see functionality that would allow us to set fixed…
9 votes -
No relation "Replaces/Replaced by" between records due to entry of invalid ISBN (020 $z)
If there are two records in Alma, one that has 020 $a u and another that has 020 $a v and 020 $z u, the both records will be related by the system with the relation: Replaces/Replaced by. The 020 $z is understood as a "cancelled" ISBN and therefore included in the job that calculates the relations.
In the vast majority of cases we know 020 $z is a false/invalid ISBN: a publisher mistakenly(!) uses the same ISBN in two different resources that have nothing to do with each other. However, according to the international rules for describing resources, the…
4 votes
- Don't see your idea?