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.
1727 results found
-
Allowing the relink of a holding from a bib record to another maintaining the call number even if the location is the same.
Now in Alma if you try to relink a holding with the same location (ex.: ABC) and call number 123 (1) from a record to another that have already a holding with the same location (ABC) and call number 123 (2), the holding with location ABC and call number 123 (1) disappear and everything is under the location ABC and call number 123 (2),.
This happens with a relink of a POL or an item.
We want to maintain the call number 123 (1).
If it is not possible to do it automatically at least a pop up message that…81 votes -
Producing the shipping forms by supplier
Each time a request has been marked "Ship" or "Return", the request details will be collected on a "Shipping Form" (by supplier).
When ready to ship a package -with returned/requested books- to another library, "print form" will:
1. Produce a full detailed form to include with the box
2. Will start a new form for future package.80 votes -
Improve Shelf Report functionality and responsiveness
Alma’s “Shelf Report” tool is a cumbersome, involved “inventory” process that requires users to populate a spreadsheet with barcode values, feed it to Alma, and then track down and manually identify any items that come back as an error (without Alma providing a timely or clear explanation for where a problem item might have been found if it was detected, or not detected). We’re aware of Dean Lingley’s API for “shelf inventory” and the WRLC “AlmaInventory” tool that attempt to cover some of these gaps, but neither of these replicate the same mass-scan-immediate-feedback-fix-it-and-move-on utility (without involving spreadsheets, macros, etc.) that…
80 votes -
Improvements for the MDEs left pane
The left pane in the MDE is a very helpful tool for navigation in daily business. With the following improvements it could be even more helpful:
- Customization of the display of the different databases in all the tabs (records/templates/rules): it would be very helpful if one could select only the databases that are necessary for the daily work for display (example: I have in the record tab 14 different databases of which I only need 4, and one that I need is only accessible through the drop down menu); if a selection is not possible it would be helpful…80 votes -
Create a Set of Inventory from a Title Set
It would be very useful to be able to take a set of titles, and convert it into a set of inventory attached to those titles. Specifically, I would like to create a Portfolio set from a set of Electronic Titles. I have regular need to move groups of portfolios from one local e-collection to another. I have only a list of ISBNs to start with, which I use to create an itemized Electronic Titles set. However, moving portfolios requires a Portfolio set, which can only be created with Portfolio IDs. It is very cumbersome to arrive at the appropriate…
79 votes -
Delete interested users job - independent of Interested In Letter
Ex Libris says the Delete interested users job "Runs weekly to delete interested users that are linked to closed or canceled PO lines. The job checks that an interestedin letter was sent to the interested users before removing it from the PO Line. Interested users will not be removed from a closed or canceled PO line if a letter was not sent to them."
Due to privacy regulations, we would like the job to run regardless of a letter being sent or not. The closed or cancelled PO line should be sufficient to run the job.
We do not use…
79 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:…79 votes -
Add Material Type Mapping to Physical Inventory Import Profile
As a Copy-Cataloger I receive batch files of bibliographic records with physical inventory from a variety of vendors and some of these vendors send a variety of formats in the same file. These files contain bibliographic records with a material type of Book, Map, DVD-ROM, Issue, etc. With our current Import Profile that we use, the Library field, Location field, Barcode field, and Item policy field can be mapped with MARC21 local field. But this is not possible for Material type. So when we import this large file with multiple material types they are being imported with the Material type…
78 votes -
Modifying a partner after recieving a borrowing request should be possible
In the SNLP workflow the partner changes from the own partner code to the partner who ships the request automatically. Therefore most of the requests have the correct partner when the item arrives at the library.
So most of the time there is no need to modify a partner and the staff's attention to this attribute is not as high as it is to other attributes of the request. If we observe this AFTER receiving the item, there is no possibility to do so.
Because we don't know to which partner we have to send back the item after it…78 votes -
Add Collection related subject area/dimensions/parameters in Analytics
Please elaborate Collection in Analytics. We suggest three ideas for that;
Idea 1)
Collection can be a separate dimension, with the existing/new parameters below;
- Collection ID (existing)
- Collection Name (existing)
- Collection External System
- Collection External ID
- Collection MMS ID (of the collection's BIB itself)
- ★★★ The PIDs of the collection's direct sub-collections (in different rows, not combined with semicolons; should be repeatable so that the created report can show the hierarchical structure of whole collections)
- Collection level (the depth)
- Collection Path (from the collection's top level collection to itself)
- Collection Description…78 votes -
Store information about request history
It is currently not possible to see whether an item has previously been requested, only that it's checked out. I want (often) to be able to tell: how many times throughout the history of this item has it been requested and in what way (page from shelf, recall, something else). It's super weird to me that this isn't present in the fulfillment history at least, and probably in analytics.
78 votes -
Make the effect of exclude process from publishing on holdings configurable
The current implementation of exclude process types from publishing has the side-effect, that a holdings record gets automatically suppressed as well if it only contains items which get suppressed based on the exclude from process types configuration.
E.g. if you have process type=acquisition, material type=issue, exclude=true all holdings which happen to only have items with material type issue in process type acquisition are suppressed no matter what. This is bad in itself, since it precludes the possibility of offering additional information to our users via the 866 field.
What makes things worse is that the bib record gets suppressed as…77 votes -
Allow user preferred pick up location while retaining other options
Currently in the TOU you can allow pick-up at "Any pick-up location" or at" User affiliated Campus Pick-up locations". If the latter is set, only pick-up locations of the user's campus are available. We need an extension to the former rule, that lets the user's preferred pick-up location (a new parameter in the user profile) be selected as default option, while still allowing the user to select a different location when placing the request.
Obviously, the "User preferred pick-up library" needs to be added to the user profile.77 votes -
Make citation information mandatory in digitization requests
The patron form for digitization does not make page numbers, or any citation information mandatory. This would be helpful for patrons who do not provide complete information.
76 votes -
Field to add "Charges" in the price.
We need a field that allows us to add "Charges" in vendor record or in the POL, now these only allow discounts.
Nowadays we have to assign this charge manually in the POL's list price.
76 votes -
E-Collections: Read-only access to Alma for other institutions
We wish to provide read-only access to our Alma instance to other institutions in our consortium and vice versa so that we can compare setup more efficiently. The permissions need to be quite restrictive and prohibit access to financial, patron data, etc. but allow us to view E-Collection, Service and Portfolio level screens.
When comparing set-up of our e-collections we are spending a lot of time discussing via email and sharing screen shots, which is not as efficient as being able to go in with a view privilege and compare in real-time.
76 votes -
Ability for fulfillment staff to renew patron loans from other institutions under network activity in Alma
Our consortium would like circulation desk staff to have the ability within Alma to renew items on loan from other institutions from under a user's network activity tab (renew all and renew selected, though renew all being more helpful if both are not possible).
Currently, only the user has access to a renewal option via their Primo VE My Library Card.
76 votes -
Show 'chapter/article title' and 'chapter/article author' in completed digitization requests and in Analytics
For copyright reasons, we need to track whether users have requested an article from an issue or a chapter from a book from which they have already received a scan.
Completed digitisation requests in Alma do not show the chapter/article title or chapter/article author, only the overall title requested. The data is not available in Analytics either.
This means that we are reliant on a local spreadsheet to track what users have already requested.
We would like to see the data available on the completed requests and in Analytics.
76 votes -
Alma MDE: Filter by Marc21 field and subfield
As a cataloger I would like to have the possibility in MDE to filter the Marc21 data by field and subfield
value to have a better overview over the current part of the data which is to be checked/edited.
Further I would like to have the possibility to quick access filters which i use often.Proposal:
Add a possibility to filter by field and subfield, e.g. by having an input form for the Marc21
field (rows filtered by "Begins with {value}") and for the Marc21 subfield (rows filtered by
"Contains {value}"). The filtering should by done by "AND" condition. (See…76 votes -
Create a set from records held in the Metadata Editor
It would be useful to be able to save all of the records that you are working on in the metadata editor as a set to come back to later.
For example, this would be helpful when working on a bound with where you need to work on several records at the same time and need to add links across the records. At the moment, if this work is not completed and we need to return to it later, we would then need to create an itemised set by searching for and adding each record individually. Instead, it would be…
76 votes
- Don't see your idea?