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.
261 results found
-
1-Click Button to View Shelf List in Primo FROM ALMA
Since the shelf list in the metadata editor is very difficult to use and see in the tiny quarter screen of space allotted to it, it would be helpful if there was simply a button one could press to view the call number shelf list in Primo (the primo 'Browse by LC call number" page) while one was cataloging in Alma.
Ideally, the record searched for would not display as the very first result, but instead a few lines down from the top, so that it would be very easy to compare the call number to both the records before…
1 vote -
make OCLC delimiter (double dagger (ǂ)) invalid in Alma
Please make the OCLC delimiter (double dagger (ǂ)) an invalid character in Alma. We all copy and paste information from Connexion. Often, people forget to change the double dagger to the double $$. Please make the double dagger invalid, and require the cataloger to replace with the proper character ($$) before they save the record. Other systems like Voyager make the cataloger replace the double dagger delimiter before they can save the record.
2 votes -
Ability to edit records during import when manual handling required
During the import of records, we sometimes get the "Manual Handling Required" notice, from which we can view the record in question as well as its error.
On that screen you can view the record and we have often found that only a small fix is needed to correct the error, and would be best done at this point in the process rather than getting the original file, making a change, and either reloading the whole thing or extracting the one file to fix and reload it alone.
It would be nice if, along with the ability to simply view…
12 votes -
We should be able to add an 856 to a bib record and that link show up in Primo.
856 fields have always held links to electronic versions of titles or just to another resource. We need this put back in ALMA so that in PRIMO we can see that url when the title is searched for as part of the physical item record.
7 votes -
Zone tab colors
Make the current zone tab you clicked easier to see by having the tab color change (or become darker) when the user clicks on it. This way you know what zone you are working in. Currently it is hard to see the little triangle pointer under the tab.
3 votes -
Shorter turn around time needed...
In Cataloging/ Metadata Editor: We need a shorter than 6 hour turn around time when we make changes. An example would be adding an 856 URL link, wanting to look in PRIMO to see if the link looks correct and test it.
3 votes -
Allow sorting of itemized set members similarly to logical set results.
In Manage Sets, enable sorting the members of itemized record sets by title, creator, and publication date, similar to the criteria available for sorting results of logical sets. Currently our only option for sorting the members of an itemized set is by exporting to Excel and manipulating the resulting spreadsheet, which doesn't allow for clean sorting by the same criteria.
95 votes -
Change color of "suppress from discovery" and other checkmarks
It is difficult to tell at a glance based just on the color of the check mark whether a holding or bib you're working with has been successfully suppressed or unsuppressed when you click on it. Going from faded yellow to bright yellow is not very obvious, especially for those who are already struggling with font size.
Could it not be a completely different color? Maybe yellow/black?
This would be easier than having to go back and look to see if the eye is present or not.
6 votes -
Display all work orders when binding items
When I want to bind two items together, there is a screen which allows me to pick a work order type. But in this screen, only work orders that have been defined on the institution level are displayed. Work orders on library level are not displayed and therefore can't be chosen.
Solution: Display all work order types when binding items.
We want to create a work order type on library level for our binding workflow.
5 votes -
Editing multiple collections from a set in bulk
We have a lot of historic collection records left over from our migration which we would like to update in bulk, for example, there collections have no portfolios so I would like to be able to add services to them all at once rather than individually. I'd also like to be able to update the "Library" field etc.
I can create a set of all these collections however, I can't make bulk updates to it. It would be great if there was an ability to run a job to add services and download a spreadsheet of all the fields in…
19 votes -
Ability to browse all call numbers in a single search
We would like the ability to browse all call numbers, regardless of call number type. In Alma, many of our local Library of Congress, Dewey, and SuDocs call numbers are retrievable only by the call number type Other Scheme. An “all call number” browse would allow us to retrieve a complete shelf list of our call numbers and would be especially helpful when assigning new call numbers.
20 votes -
[Alma] - export items job - csv format - always add / embed in double quotes as text qualifiers / delimiters
Right now in Alma, when running a job to export a set of Items in csv format, double quotes are added only to values containing commas (see attached example).
Which is not wrong at all, but it would be much better (e.g. for postprocessing the file in a text editor or using regex) if the double quotes were always added by default in the .csv format.
For example, right now is.
03149898,Machine à lettres,MeMo,Book,"Magnani, Julien",AM 22800
but it would be much easier to process if it were:
"03149898","Machine à lettres","MeMo","Book","Magnani, Julien","AM 22800".2 votes -
Add title column to Receive new material > Received items list
When receiving titles for a membership/package we need to see the titles displayed in an extra column on the Received items list in order to distinguish between titles in such a membership/package. See screen prints.
4 votes -
Allow for work orders to be placed against MMS IDs
It would be helpful if we could apply a work order against ALL the items attached to an MMS ID in a single go, rather than go through Actions against each item. I know it's possible to create a set and do it that way but it would be much easier to be able to click on a work order option and have that applied to a whole list of items.
3 votes -
Index 049 field.
We tie the OCLC holding library in the 049 closely to our Alma holding locations. Searching the text in the 049 field as keyword is quicker than an advanced search. If the idea below to allow free text searching of all MARC fields and subfields is implemented it would cover this request.
0 votes -
Community Zone records: subfield t missing in 780 and 785 MARC tags
In the CZ please add $t (Title of the related resource) to tags 780 (Continues) and 785 (Continued by).
The lack of $t causes issues in discovery where 780 and 785 tags are set to be displayed, linked and searchable. With no $t this is not possible.
31 votes -
Retain preferences in manage sets screen
When you select either private or public sets, retain the preference for the duration of the session and do not routinely default back to private. Having to re-select public repeatedly is just more repetitive clicking.
6 votes -
Different authority icon
In authority control instead of having the looking glass icon, an icon that indicated the heading was Full or not would be better.
14 votes -
Unclutter index for F3 lookup from field 830 (Series Added Entry - Uniform Title)
F3 lookup from field 830 is used to verify if a series title has been entered into the database in a standardized form, and, if so, to link the bib record to that title . At present, the index searched by F3 contains a mixture of headings from fields 830 and 490 (where the non-standardized series title is entered) and headings with volume numbers (which refer to a part of a series, not the series as a whole). To best serve its purpose, the index looked up from 830 with F3 should contain and display only the fields $a, $p,…
20 votes -
View It in Alma for physical resources
In Aleph we were able to CTRL + O and see the physical item's record in the OPAC immediately. Now our metadata staff have to wait until the Alma pipe to Primo has run to view their record in Primo. Would it be possible to add a View It, like in the case for e-resources, for physical resources also.
2 votes
2.png){kind=link}
1.JPG){kind=link}
- Don't see your idea?