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.
2906 results found
-
Make reports in the ACTL of a network environment comprehensive
Working at an institution that is part of a network environment with one Network Zone and various Institution Zones, the Authority Control Task List, in its current form, is a tool that is of very limited use.
NZ-BIB-records are processed by the various jobs on the NZ level, while IZ-BIB-records are processed on the IZ level. On the IZ level, one is currently notified about IZ records, along with records linked to CZ - even if the latter are obviously not processed on the IZ level, but on the CZ level.
Records linked to NZ (which, in the framework mentioned…
67 votes -
Make ACTL reports dynamic
In a network environment usually the majority of Institution-Zone-BIB-records are linked to the Network Zone. Currently the ACTL reports are not comprehensive – see Ideas Exchange “Make reports in the ACTL of a network environment comprehensive”.
Once the IZ-ACTL comprehensively reports on the records representing all the resources available in a particular library, it would be of great help if the reports within a NZ environment were dynamic. Meaning that if one of the staff users of any of the Institution Zones has already corrected a NZ record it is linked to, and subsequently has deleted the item in their…
65 votes -
Job or tool for extraction of related bibliographic records
We would like the ability to get a hold of or extract the related bibliographic records in bulk based on a set of (other) bib-records.
Alma already now automatically displays related records in "other details". We understand that the links are built based on bibliographic data in the MARC linking fields: 773, 774, 777, 786, 800, 810, 811, and 830 (subfield w,x,z).
An example of a related record is a title within a monographic series. In this case, the bib record for the single monograph has a 830 $w with the MMS-ID/system number of the superordinate bib record.
We would…
117 votes -
Allow Alma to export preferred names to ILLiad when automatically creating ILLiad user records
When Alma automatically created an ILLiad user record for someone who has submitted a resource sharing request that must be exported to ILLiad, it always passes the First Name and Last Name fields to ILLiad even if the user's records contains a Preferred First Name and/or Preferred Last Name. It would be incredibly helpful if Alma could pass preferred names to ILLiad if the user's record contains any preferred names.
40 votes -
Add "General Notes" at the collection, service, and portfolio levels as indexable/searchable fields
Unfortunately, we have received the following case response: "Notes fields are not indexed for search as this is not within the current design/intended use for these fields."
So we hope to get support for our proposal in the Alma community.Our colleagues in the e-resources department use the "General notes" field at the collection, service, and portfolio levels.
However, it is not possible to search for theses notes:(1) In Alma itself you can search for:
Electronic Collection:
- Authentication note (Electronic Collection)
- Public note (Electronic Collection)
- Service Authentication note
Electronic Portfolio:
- Authentication note (Electronic Porfolio)
-…45 votes -
Add indication that the bib. record has a MDE note
It would be helpful to have an indication that there is a MDE note regarding this record posted by a cataloger.
One option to see this indication can be on the preview of a bibliographic record. It can appear the same way as when there is an order for the record (see photo attached), and if you click the number, it should take you to the note.
Additionally, it should be either reportable to Analytics or searchable in Alma, so that it will be possible to find all the records that have MDE note.42 votes -
Interested In Letter – improvement to the usability
When working on a purchase request, you can tick a box if you would like to notify the patron upon receiving/activation, and upon cancellation.
OTB the Interested In Letter sends the same message when the request is received or cancelled. The letter in use does not seem designed for the cancellation message.
This creates a discrepancy between what we choose to notify the patron of, and what we are actually able to communicate.
Since we neither have access to the message table used as an input to this letter, or the opportunity to differentiate by using labels, we are forced…
157 votes -
user - add option for dynamic purge date - e.g. 12 months after expiration date
Right now the purge date is a static value manually inserted when registering a new user. When the user renews registration, purge date must also be manually updated.
In our library regulations we'd like to purge users after a specific amount of time after expiry date. Keeping purge dates manually up to date is however quite an error prone procedure.
It would be great to have the chance to automatically update the value in purge date when saving according to specific a timespan (e.g. 10 months or 10 years after expiration date).80 votes -
PO line description should represent current bibliographical data
Alma provides insufficient data in PO lines for the task of pulling a list of subscriptions a library has of a specific publisher's titles:
The PO line description contains only bibliographical data from the bib record as it was at the time the PO line was created. Subsequent changes in the publisher data are not updated in the related PO lines.
Even in newly created PO lines, Alma introduces the content of MARC field 264 _1 instead of 264 31 if such a field exists, i.e. it copies the first, not the current publisher’s name into the PO line description.
…
61 votes -
Create a "sticky note" widget for individualized staff notes.
It would be helpful to have a "sticky note" type widget available on the Alma homepage so that staff could record personalized ideas/instructions/reminders to themselves about Alma-specific work.
The simplest version could just be a plain text box where staff could add/delete text as desired. A fancier version could allow for multiple notes to be created, storing them each with a title and create date and listing them all in the Widget.
If we get really crazy there could be a setting to enable the user to choose whether the note is a public note (for all other Alma users…
76 votes -
Add a tab "re-loan" to Patron Services to return and re-loan items in one step
An additional tab (e.g. "re-loan" or "Wiederausleihe" in German) would be a valuable improvement to the Patron Services page.
The goal of this tab is the returning and re-loaning of an item to the patron in one step, with a pop-up warning if there are requests present in the request queue.
The option of a re-loan tab would be a big help in cases where large amounts of items are reloaned to the same person when the items reach the maximum amount of renewals. The additional tab would make the process easier, less error-prone and especially faster.86 votes -
Add Storage Location ID to the list of customized fields on the Manage Item Returns screen
We have thousands of items in our collection that are primarily organized by the storage location ID, rather than call or accession number. For these materials, routing and reshelving activities would be more efficient if staff have the option to add the Storage Location ID to the list of customizable fields on the Manage Item Returns screen.
26 votes -
Bursar integration: Additional fee statuses in Alma & Allow fee status change with job Import from Bursar
Currently there exist in Alma only the fee statuses “open”, “transferred” and “closed”. Transferred means fee was exported to external Bursar system. When the fee is imported back to Alma, it is automatically Closed. For staff it is not possible to tell if the closed fee was paid, waived, unpaid etc. without consulting the 3rd party Bursar system.
To give the librarians and end users more transparency about the (invoice) status of a fee, we would need more differentiated fee statuses. Also, we need to be able to set this status when importing the fees back to Alma using the…94 votes -
Add option to close library for borrowing or lending requests based on format of request
A library can close for borrowing or lending requests and include dates when the library can't process borrowing or lending requests. It would be helpful and provide more efficient processing of borrowing and lending requests if requests could be deflected by format.
As a borrowing library, there are times when a patron's article requests could be processed and sent to a lending library, but a physical request can't be processed.
Borrowing physical requests may not be possible because the physical library building is closed, and the item can't be delivered to the location.
It would be helpful to have the…
44 votes -
PO Line: missing identifiers ISBN/ISSN/ISMN etc.
Please list all identifiers in the PO Line.
See the following examples:
Data in the bibliographic record --> data in the PO Line XML fileExample 1:
020 __ |a 9783702404727
024 2_ |a M008027376
--> PO Line - XML: only content of 020
<identifier>9783702404727</identifier>
<identifier_type>ISBN</identifier_type>Example 2:
024 3_ |a 730099129329
028 52 |a 8.551293
--> PO Line - XML: empty identifier
<identifier></identifier>
<identifier_type></identifier_type>Example 3:
020 __ |a 0415462444 (pbk.) |c £24.99
020 __ |a 9780415462440 (pbk.) |c £24.99
020 __ |a 0415462436 (hbk.) |c £70.00
020 __ |a 9780415462433 (hbk.) |c £70.00
--> PO Line - XML:…36 votes -
Add the option to custom harvest the entire institution's SUSHI accounts
We usually analyse the usage data of the whole previous year. In our "Monthly usage data" overview many reports failed. We have 100+ vendors with SUSHI accounts.
To manually go to each vendor and custom harvest the year's usage data takes a long time.
Please include the option to run a job that harvests ALL SUSHI data as a custom harvest.
33 votes -
Warn before regenerating the SFTP Service private key
There is a «Regenerate private key» button under Alma configuration » General » S/FTP definitions.
This button is too efficient. This idea is to make the button a little less efficient, but in doing so make it safer.
Clicking the «Regenerate private key» button immediately regenerates the private key for the Ex Libris Secure FTP Service. In the process it invalidates any previously generated private key and breaks all integrations with the SFTP Service. More so, the button in Alma (Premium) Sandbox does the same as in Alma Production, including breaking all production integrations.
All it can take is one…
32 votes -
Alma Withdrawal Option
Our library needs the Withdraw function in Alma. We request a Deposit when we lend particularly valuable items. After the reader returns the book, the Deposit should be refunded. And this option is not available in Alma. There is a Pay option, but there is no Withdraw/Refund function, and we would like to be able to settle all financial matters in Alma (and not use external fiscal programs / cash registers).
151 votes -
No request cancellation with change of item description
Actually it seems that Alma automatically cancels requests when there is a change of location (not the same FU rules anymore), of item policy (not the same TOU anymore) and a change of description (as this field is to be found in the request form).
For the latter, we would like to have a possibility to choose whether the request should be cancelled.67 votes -
PO Line: <series_statement> and <series_uniform_title> - missing 490/830 subfield v in the XML
Marc21 field 490, "series-statement", and Marc21 field 830, "series-uniform-title", are available on the Order List Letter (letter code: OrderListLetter).
However, the content is not complete :-(
Only 490|a goes to <series_statement>, 490|v - the Volume is missing.
Also 830 only provides |w as <series_uniform_title>, |v is missing.Please see example:
035 __ |a AC04654069
245 00 |a Keiner wird gewinnen |b populäre Musik im Wettbewerb |c Dietrich Helms ... (Hg.)
490 1_ |a Beiträge zur Popularmusikforschung |v 33
830 _0 |w (AT-OBV)AC00913498 |v 33 |9 O:1<series_statement>Beiträge zur Popularmusikforschung</series_statement>
<series_uniform_title>(AT-OBV)AC00913498</series_uniform_title>Please add 490 subfield v to the XML field <series_statement>,…
31 votes
- Don't see your idea?