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
-
Conversion job for any part of the record to any other part
Hello,
It would be nice if there was a job of conversion of every part of a record (bib, hol, item, portfolio) into another part, for example:
Bib records into Items
Bib records into Holdings
Bib records into Portfolios
Bib records into Orders
Items into Bib records
Items into Holdings
Orders into Bib records
Orders into items
Orders into Portfolios
Portfolios into Bib records
Portfolios into Orders
This way, we will not be limited by the search for any job.
For example, we would be able to search Bib records, convert the set into items and run a job for…13 votes -
More sophisticated functionality in the Duplicate Title Analysis function
The Duplicate Title Analysis functionality does not allow you to clear previous duplicates when you run a new job.
For example, you may run a job to find duplicate titles. You investigate those titles and decide that they are not problems for your library, so you wish to leave those titles in Alma, but you don't want them to come up on the next Duplicate Analysis title job.
3 votes -
Should be prevented from saving a bib or holdings record where a non-repeateable field/subfield is repeated.
One specific example which just came to light while testing something is the holdings 852 field, which (unlike the bib 852) is NOT repeateable. Alma does not generate an alert in the ME and will save the record with the repeated field (tracking ID E05-2906180135-S9VHD-GENERAL)
4 votes -
About the default inventory when view inventory in Metadata Editor
When I click "view inventory" in Metadata Editor, if there are print holdings and electronic portfolios connected with the bib, the default inventory show the electronic portfolios.
I think the deault inventory showed should be holdings. Because we seldom edit portfolios in metadata editory.
1 vote -
Open second search box when "Advanced" is selected from persistent search
The default persistent search box in Alma is one line. For a more complex search, I click on "Advanced". I then (always) have to click on the plus sign to get a second row for additional critieria. I would like for the system to automatically open that second search box when "Advanced" is chosen. Thank you.
0 votes -
Change the design or position of the search box on a set's Add Members screen
On the classic UI, when a staff member clicked on Add Members in a set they used to get a separate set of search boxes - with the "Find" box offering the choice of just one thing, e.g. Physical Items - into which to add the barcode or whatever else of the item they wanted. The persistent search box remained on screen, but had palpably nothing to do with the Set.
In comparison on the new UI, when a staff member clicks on Add Members they get a search facility which behaves the same way as its predecessor, but (i)…
2 votes -
Display edition statement in any brief results list
Results of an All Titles search include the edition statement in the brief display, but Physical Titles and Physical Items results do not. We often have multiple editions of a title, and while the date shows which is the most recent, if we have slight date variances that make the date useless we need to be able to see the edition statement in order to choose the right record to view.
4 votes -
Package level order info required in Repository Search > Other details
It would be helpful if, when clicking on the Other details link on a particular Repository Search result title which shows no order information, it would indicate whether there was a related order at package level.
If we want to know whether we are entitled to the access, it may look at first as if we aren't because there's no order attached. However, the order may be at package level.
We are relaxed about the wording and place of that indication within the Other details balloon - maybe something like "Package Level Order" underneath "Requests/Work orders"?
1 vote -
Include a DELETE Function for Patron Demand Driven Worflow
Currently Patron Driven workflow is managed by the PDA function under Acquisitions. The PDA function allows for Repository Import, where the corpus titles are uploaded for discovery. The PDA also enables order records to be uploaded, which will overlay the discovery record. However, what the PDA function needs is a DELETION function, where records of titles no longer carried by vendor for the PDA can be run through this function, and have it deleted from the PDA corpus set, bypassing the titles that have been paid for.
Currently, titles which have been marked for deletion by PDA vendors have to…1 vote -
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 -
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 -
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 -
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 -
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 -
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 -
exporting records retrieved in ALMA to (for example) the RIS-format for collection development purposes
Management of larger sets of bibliographic information is required for collection development purposes. Excel downloads are not (yet) compatible with regular reference management software (e.g. EndNote), and lack the options reference management software do offer (filtering, editing, managing, outputting). So exporting to for example the RIS-format of records retrieved in ALMA would make this data management possible.
7 votes -
Ability to create a Titles set from a logical physical item set
Currently it's not possible to create a Titles set from a logical Physical Items set. Instead, one must first create an itemized set from the logical set, then create a Titles set. We would love to see the option to create a Titles set from a logical physical items set.
2 votes -
Search package titles in "All titles"
We would like to search package titles in the index "All titles". This is not possible in the moment.
2 votes -
Flag required in Itemised Sets for adding other items at the same holding
The ability in the Itemised Set facility to add contents from a file to a Set is useful, but we feel it could be made more useful still.
We require something whereby, having read the contents of a list of item barcodes, Alma will find any other items based at the same holding as a given item on the list and add those to the Itemised Set as well.
There is a very definite need for this functionality for any Alma user tasked with working through Sets created from lists of item barcodes in order to identify items requiring withdrawal.…
1 vote -
Reminders for Sets
The Reminders for Bibliographic Records functionality premiered in the November Alma release is already proving most useful (in such instances as applying reminders to check things like eBook records when their portfolios expire X months or years in the future).
What would be at least as useful, however, is if this functionality were to be made available for Sets as well, e.g. when a Set reaches a specific number of months or years of age, a reminder can be set up requesting the owner to check whether it's still required and to consider deleting it.
Effective housekeeping of Sets (and…
1 vote
- Don't see your idea?