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.
1771 results found
-
Support local portfolio record creation using parser parameter linking
Alma electronic collections offer ‘parser parameter’ linking as an alternative to static URLs. Community Zone electronic collections generally use parser parameter linking. Currently there is no way of creating local bibliographic and portfolio records and at the point of record creation setting them to use parser parameter linking, and populating the portfolio record parser parameters field with the relevant bkey value for that title. If we want to use local bibliographic and portfolio records and use parser parameter linking, our only option is to create the records using static URLs and then subsequently edit the records to use parser parameters.
Potential…
69 votes -
make "test access" work when direct linking is enabled
The "test access" button in Alma does not work when direct linking is enabled in Primo. When trying to test access for an electronic portfolio, Alma loads a blank page forcing staff to click "display in a new window" in order to proceed. We recommend that this behavior be changed so that test access works the same regardless of whether direct linking is enabled.
69 votes -
Fulfillment Overrides without separate login
When an override by a manager is needed at a circulation workstation, there should be a way for the manager to override either remotely or at the workstation without the operator logging out.
69 votes -
Adding a field in the Excel Example of Creating Invoice from File.
Adding a field in the Excel file under batch process that allows for inputting custom exchange rates. The reason for this is because the invoice creation date may not always be on the same day as payment, resulting in outdated rates.
68 votes -
Wikidata URIs
We request that Wikidata be maintained within Alma as an authority vocabulary source. This functionality should include the ability to search against Wikidata as part of the Metadata Editor F3 linked data enrichment function. Cataloguers should be able to enrich bibliographic records by manually selecting the authority to apply the corresponding Wikidata URI to a name heading. This is useful for non-Library of Congress cataloguers and for those with Special Collections and archiving cataloguing responsibilities to use a more agile and international authority source in our cataloguing.
68 votes -
New Metadata Editor templates: editing template v. creating new record
Previously, when opening a template in the classic Metadata Editor (MDE), a click on the template name from the list of templates would give a list of options, including creating a new record: there was no doubt as to whether you were creating a new record from the template, or editing the template itself.
However, with the new MDE, clicking on the template name takes you straight into editing the template itself. Creating a new record from the template now requires a right click first to get to the options menu, but this is not at all obvious. It is…
68 votes -
Enhance Convert to Resource Sharing function on Pick From Shelf List
When you don't find a requested item at your institution, it is great to be able to 'convert it to a resource sharing request' -- however that function should mark the item missing from our institution. Since pick from shelf does NOT display barcode and once we select the item to be converted to resource sharing request, it disappears from the pick from shelf list, so it is very difficult and time consuming to find the item and toggle it to missing. Also, the resource sharing request might be canceled because the item at our institution shows up as 'item…
67 votes -
Prioritising Digitisation requests over hold requests for processing
Is it possible to have digitisation requests automatically prioritised to the top of a request queue over the physical item requests. Currently all physical item and digitisation requests go by the date they are placed by the patron. We find that patrons are waiting months sometimes just to get a copy of a chapter, where as if all digitisations were automatically at the top of the list they could all be processed and then items loaned to patrons.
67 votes -
Visibility of extension packs and possibility of selecting them one by one for editing and/or deleting
Extension packs once added to a local MARC-based profile are not visible and cannot be retrieved in any way. It would be much better if each extension pack loaded to a bibliographic profile could be visible to system admnistrators in order to be downloaded from bibliographic profile for purposes of editing and reloading, should the need arise. This feature was part of the tentative future developments proposed by Ex libris back in 2017 (see: internal: 2017 Q1 URM-45100)
67 votes -
Establish system to ensure complete coverage of LC classifications
Alma Analytics includes LC Classification code data, but frequently valid classification codes come up as "Unknown." Ex Libris currently has no reliable way of keeping up with changes in LC classification. They rely upon the "Library of Congress Classification Outline", which is not complete. They will add classifications upon customer request, though this process takes months or years and puts significant burden upon institutions. Ex Libris should develop a system to reliably update its LC classification coverage. This could take the form of e.g. establishing its own access to Classification Web, subscribing to LC updates, and/or setting up some alternative…
67 votes -
Add General Electronic Services information to Analytics
In General Electronic Services, we have four different services for article requests, four different services for book requests, and five different services for book chapter requests, all developed over the years to address provider idiosyncrasies. Each group of services provides the same link to the user, e.g. the article request links all display "Get this PDF".
Our Interlibrary Services unit has the product delivery statistics, but I would really find it helpful to know how many clicks each of our General Electronic Services gets. It would help with service and link maintenance and I expect with troubleshooting, since it would…
67 votes -
Mechanism to validate binary MARC record structure
There is currently no mechanism within Alma to ensure that exported or published binary MARC records have valid record structures. Even though Alma uses MARCXML and is not impacted internally by invalid binary MARC, libraries must still provide binary MARC records to external entities in the course of regular business (vendors, outsourcers, agencies, other stakeholders).
Structurally invalid binary MARC records significantly hamper data sharing for libraries. A third party application, MarcEdit, can be used to validate MARC record structure, but since our data is stored in Alma, there should be a mechanism native to Alma that validates binary MARC structure…
67 votes -
Brief Record - Quick Cataloging Template
Boston College would like to see the contents of the linking tab of Electronic Portfolio Editor added to the Brief Record, Quick Cataloging template for electronic articles.
This will enable us to edit the URL and enable the proxy as we catalog and would save us the step of going in later to edit the linking information. It would also enable us to test the link before posting it, rather than using the "view it" function afterwards.
66 votes -
Ampersand symbol (&) in Repository search
It's found that the repository searches using the ampersand (&) symbol and the word 'and' produce different results. Our request is to make the ampersand symbol and the word ‘and’ interchangeable when Alma does repository searches.
SF case # 00646924
66 votes -
Alma User Role for Editing/Deleting only Quick-Cataloged Records
Scenario:
Library staff frequently need to create records for resources using the Quick Cataloging feature. Often, those records need to be edited after creation, due to mismatching resource types, updated information, operator input errors, etc. Most of the staff using the Quick Cataloging feature are not trained as catalogers, and do not have cataloging roles in Alma.Problem:
Quick-Cataloged records are not editable by staff without cataloging roles in Alma - who are frequently the creators/managers of these records. This has led to several different workarounds at various institutions:Some institutions have given their non-cataloging staff full cataloging permissions to…
66 votes -
Limit fine/fee payment to specific library
One of our satellite libraries would like restrict payment of fines/fees for their materials to them -- we have separate accounting and budgets.
66 votes -
Add 245 subfield n to the letter XML node for title
Many letters display the name of the title using the node notificationdata / physitem_display / title. This field contains a subset of subfields from the MARC field 245 to display the title of the work.
We receive complains from our users regarding missing book title number in mostly textbooks. The missing number is available in the MARC field 245 subfield n and is an important part of the title. For example:
245 10 |a Prisma Physik |n 1
245 10 |a Deutsch |n Drei
245 00 |a Prisma |n 1
245 10 |a <<Die>> Sprachstarken |n 2 |b…66 votes -
Add warning to "Scan In Items" and "Shipping Items" for certain item policies
We would like to suggest the implementation of a pop-up for "Scan In Items" and "Shipping Items" to alert staff when they are about to process an item with a restrictive item policy (e.g. 63, 67, 68, etc.).
For example, when a request is placed at the title level and there are multiple items with differing item policies, this pop-up would be helpful to avoid processing the wrong item.
66 votes -
Indication rule that checks if subfields are in the same field
Currently it is not possible to write an indication rule which checks the subfield a and b of a field only when both subfields are in the same field and not in repeated fields of the same record. Both of the following records are treated the same when looking for a subfield a "mercury" and subfield b "venus" in the 690 field:
Record 1:
690 $$a mercury $$b venusRecord 2:
690 $$a mercury $$b mars
690 $$a earth $$b venusI'd appreciate an option to distinguish if I'm looking for subfields in different fields or in the same field.…
66 votesI recommend applying XSL normalization rules with the required logic and integrating them into the Upon Save normalization process.
-
We would like the ability to manage course reserves reading lists and courses in bulk. Currently, it appears that we can only delete them o
This is about allowing Course Reserves course and reading lists to be able to be managed in sets and deleted in bulk.
We would like the ability to manage course reserves reading lists and courses in bulk. Currently, it appears that we can only delete them one at a time and have thousands of old outdated ones. This could either be done in the Mange Fulfillment Sets or just Manage Sets and then we would want a way to delete them too with a job.
65 votes
- Don't see your idea?