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
-
Improving Physical Item Editor management
I would like to suggest two ideas which can improve the whole management of working with physical item editor:
1. Enable all tabs and fields to be editable without clicking on 'save and edit' button – Currently after you click on 'Add item' and being navigated to the 'Physical Item Editor' form, not all the fields and tabs (General, ENUM/CHRON, Notes, and History) are enabled for editing, the barcode no. is not populated automatically, and the dropdown list of process type is disabled as well. Only after clicking on 'save and edit' button, the complete form, including the tabs are…492 votes -
Improve Alma Job Reports for Failed Record
It would be extremely helpful if more details were given when there are failed records or records with exceptions on the jobs we run in Alma. Many of the job reports only report the number of failed records. It would be great if the report would provide MMSID information so the we know what records failed.
482 votes -
Better management of serial prediction when publication frequency changes
Sometimes providers change a journal’s publication frequency throughout the year. So, the prediction’s pattern selected / elaborated at the beginning of the year doesn’t work anymore in Alma. One part of predictions (date of receipt) will be ok until the change but all other predicted items will be false. Now, we can revise the prediction during the year but we must erase the items already received. We can also leave the prediction defined at the beginning of the year and edit manually the false items from the time of the prediction change.
It would save a lot of time if…
355 votes -
Reset PO and POL number every year
Dear colleagues,
Currently, the POs and POLs numbers are generated automatically and the turn of the calendar year has no effect on it.We would find very convenient that, at the start of each year, the sequence starts again.
The first PO of 2023 of would be PO-2023-1, same with the POLs POL-2023-1.
The numbers would gain in clarity.Thank your for considering this.
Kind regards,
Maxime317 votesDear community, thanks for sharing this idea. To clarify, from the description of the idea, it looks like the need os to have the sequence restart in the beginning of the calendar year and not have any relation to the institution FY.
The suggested solution will be applied as described in this idea; At the start of each year, the sequence of the previous year will stop and starts again with indication of the new year.
The first PO of 2023 of would be PO-2023-1, same with the POLs POL-2023-1.
Important note:
- This functionality is activated by a customer parameter controlled by the institutions (Acquisitions) - by default the CP should be false
- The new numbering will begin when ever the Customer Parameter was enabled, even if it is in the middle of the calendar year.
- Any existing PO/PO line numbers will not be changed, when the functionality is enabled…
-
Subdivided LCSH headings should be flipped by Preferred Term Correction
Preferred Term Correction is not flipping all LCSH headings when the authority record changes. If there is an authority record that has a subdivision, it is only flipped by PTC if the heading in the bib has no additional subdivisions. This means there is a significant gap in the PTC process that requires manual attention and handling, which is unsustainable. The PTC process needs to be more thorough.
For example, this LCSH:
$a Germany $x Politics and government $y 19th century
was updated by LC to be:
$a Germany $x Politics and government $y 1789-1900
When the authority record changed,…
305 votes -
Update URL in porfolio when attached bib record's 856 is updated
When the URL in a bib record attached to a portfolio is updated (individually edited, or batch load/overlay of records), there should be a setting to the action so that the URL in an attached portfolio would also be updated and we don't have to remember to manually do this. We have had 2 recent instances, one where we used APIs to update bib records using our old PURL manager to use our new one, only to find that the portfolio URLs also needed to be changed separately, and one where we have a batch of vendor records with changed…
295 votes -
Metadata editor: Enable moving up and down within a field using arrow keys
It would be nice to be able to move up and down within a field using arrow keys in MDE. For example, when a lengthy 505 or 520 MARC field has many lines, the cataloger must now move to the desired line using either mouse or left/right arrow keys, since pressing up/down arrow causes the pointer to move to the previous/next field.
My suggestion is that the pointer should be able to move within the field using up/down arrows and move only to the previous/next field when the pointer is on the first/last line of the field.
Using up/down arrow…
279 votes -
In "Purchase Requests": Permit re-linking request to a Portfolio.
Purchase requesters are permitted to both 'Use existing record' AND choose 'Requested format' = 'Electronic'.
Please add the possibility of re-linking to an E-Portfolio--not just to a bibliographic record.
Beginning an e-purchase with a bib rather than a portfolio requires a lot of fiddling around after the fact to correct the record so the bib is not suppressed, or mis-indexed. And who knows what's happening under the hood.
279 votes -
Serials: Editing of Description Needed
When opening predicted items, the Description-Field is populated by the data provided in “Next Predicted Item´s information” and displays these data in a certain punctuation-logic. Unfortunately, this logic is not equal to the description- (and punctuation-) logic used in German speaking countries (which is following ZETA-Standard) – and there is no possibility to edit this. Since there has to be a correct description (for sorting etc.), the only way is to open and edit every single item once it is created by prediction pattern. This is causing a lot of unnecessary work to be done manually - we need the…
270 votes -
"Save and dismiss" button in "Manage EDI Tasks"
In the "Manage EDI Tasks", when using the "Update Expected Receipt Date" action, updating the date and clicking on "Save", it would be great the concerned line would automatically be removed from the list without having additionally to click on "Dismiss". A new function button like "Save and dismiss" would be helpful.
265 votes -
Invalid email address list or failed to be sent notifications
We would like Alma to indicate somewhere (in a report, in the user account or else) if an email was not delivered to a patron or a vendor due to an invalid address. This would help to locate them faster and correct this data.
Otherwise, we would like to have a list by Alma institution of users / vendor accounts with invalid email addresses.Thank you!
261 votes -
Re-sequence MARC fields by each tag when running a normalization rule
Currently, after running a normalization rule on a set of bib records, the bib records display the 5XX fields out of order, e.g. 500, 546, 506 etc. This occurs even after running the CnmarcBibReSequenceTask as fields between 500 and 899 are not sorted, or sorted only by hundreds (this was the information given to us by a member of staff when we reported the issue on the ExLibris Customer Portal).
Having all fields in the correct order would ease any future cataloguing needed on these records, or when staff members view the record for work purposes.
I've attached an example…
256 votes -
Improve the e-book purchase request workflow
The purchase request workflow needs to be improved for acqusition of electronic resources.
Currently, you can either approve or reject a purchase request. An approval automatically creates a POL and a standalone portfolio based in the Purchase Request BIB record. Both outcomes are unfortunate when working with e-books. An e-book will usually be ordered on the vendor site (e.g., the ProQuest portal) rather than through an Alma POL. It should be possible to select whether a POL is created. More importantly, we'd like the option, upon approval, to select and activeate a title from among CZ collections instead of having…248 votes -
Allow Linking PO Lines to Electronic Inventory Regardless of Order Record Type
We keep running into road blocks with not being able to hotlink POLines into the POLine fields of either Electronic Collection Records or Portfolio records.
Is there a way that Alma can allow us to add POLines to Electronic inventory no matter what the order type is? This would save us so much time and allow us to use existing order lines for renewals. Right now we are doing a work around to connect order lines with electronic inventory by entering order information in the Portfolio Internal Description field.
241 votes -
Add “next year” as an option in serials subscription date range drop down menu for invoice lines.
Many of the invoices we process are for serials subscriptions for the following calendar year. Having “next year” as an option, for invoice line subscription ranges would be quite helpful.
234 votes -
Allow Reinstatement of Fines/Fees
Fines are occasionally processed in error or you might need to reinstate a fine payment taken on someone's account. We would like the ability to reinstate fines that have previously been paid or waived.
223 votes -
Batch deleting PO's
There is currently no system job to delete PO's. These have to be done manually using the Acquisitions>Purchase Order>Delete PO function individually in ALMA.
We have 1000's of old orders migrated from our legacy system that are no longer required. We also now only keep 7 years worth of orders in line with current financial practice and so would like to be able to set a job to batch delete at rollover into the new fiscal period.
219 votes -
Overriding and/or deleting a continuous POL at the item level
As a cataloger at a large research library, we frequently receive gap-fill purchases of periodical issues from third-party vendors or as gifts from donors—including for subscriptions that are still open.
We know that we can associate a POL at the holding level, but this is undesirable for these situations where we need to trace the POL/method-of-acquisition to an individual item. Also, if you change a continuous POL at the item level, Alma changes the POL for every item attached to that same holding.
Often we have many items purchased with different (or no) POLs—subscription, firm order, gift—together on one holding,…
210 votes -
Suggestions for Normalization Rules (NR) functions
Hello,
Please see the attached file.
We would appreciate it if the suggested Normalization Rules functions would be developed in Alma.Thanks
203 votes -
Prevent change of due-date when the item is under the recalled status.
Or have an alert message of some kind when the due date is being changed.
Because when the due date is changed, the recalled item reverts back to its initial status making it difficult to determine if there are requests placed on the item.203 votes
.png){kind=link}
.png){kind=link}
- Don't see your idea?