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.
- or
No existing idea results
- ~ No ideas found ~
1692 results found
-
Add filter to Vendor Invoices tab
I would like to be able to limit the invoices I see on the Invoice tab in the vendor records to a specific time frame or add a filter to have the ability to select the fiscal year of the invoices in the list.
This will allow me to only see truly historic invoices when and if I need to.24 votes -
Generate accession number by typing directly in field 852
Generation an accession number in 852$$h or $$j can only be done by using the menu (Tools -> MARC21 holdings -> generate accession number), or by keyboard shortcut (ctrl+schift+A) in the new MDE.
Even though the keyboard shortcut saves some clicks, we would like to type the prefix directly in field 852, followed by a character like # for example, that would indicate to Alma to generate the sequence number after saving the holding record.Example : 852 $$b library $$c location $$h RIA #
-> after saving the record :
852 $$b library $$c location $$h RIA 6785If the prefix doesn't exist in the accession number code table, there should be a warning upon saving.
Also, it would be helpful if the accession number does not need to be connected to a specific location. We should be able to choose to connect it to all locations of a library, or only one location like currently.
Best regards.
Generation an accession number in 852$$h or $$j can only be done by using the menu (Tools -> MARC21 holdings -> generate accession number), or by keyboard shortcut (ctrl+schift+A) in the new MDE.
Even though the keyboard shortcut saves some clicks, we would like to type the prefix directly in field 852, followed by a character like # for example, that would indicate to Alma to generate the sequence number after saving the holding record.Example : 852 $$b library $$c location $$h RIA #
-> after saving the record :
852 $$b library $$c location $$h RIA 6785If…
39 votes -
Accession number available by API
Hello,
To be able to develop several external tools (relabelling, cataloging, ...) we need to access the "Accession number" table by API (read and write).
This would probably give many other clients oportunities in developing external tools for managing physical collections.
Best regards.19 votes -
Open Predicted Items feature in MDE should bring in the Item Policy value from the previous item
The feature of Open Predicted Items in MDE cannot bring in the Item Policy as it does for the Material Type, which is inherited well from the previous item.
25 votes -
Provide a solution to use POLs in context of Auto Holdings collections
The Auto Holdings collections are a big help for activating electronic resources. However, if you want combine them with manage your orders for the resources in Alma, you run into problems.
Use case 1: A library orders several thematic e-book packages on a yearly basis from Springer. They activate SpringerLink Books - AutoHoldings. All e-books are activated there. If, however, the library wants to retrace, wich thematic packages they bought in which year, they are confronted with n POLs attached to SpringerLink Books - AutoHoldings with no chance to sort out quickly, which order pertains to which collection and which e-books contained therein.
Use case 2: A library orders some e-books hosted by Wiley over several years. The activation is done via Wiley Online Library - AutoHoldings Books. Where should the library attach the POLs, so that they will know in future, which e-book they ordered when?The Auto Holdings collections are a big help for activating electronic resources. However, if you want combine them with manage your orders for the resources in Alma, you run into problems.
Use case 1: A library orders several thematic e-book packages on a yearly basis from Springer. They activate SpringerLink Books - AutoHoldings. All e-books are activated there. If, however, the library wants to retrace, wich thematic packages they bought in which year, they are confronted with n POLs attached to SpringerLink Books - AutoHoldings with no chance to sort out quickly, which order pertains to which collection and which…30 votes -
'Undo Last Action' option for Resource Sharing requests
Many times, our library staff accidentally choose an unintended Resource Sharing status or scan the wrong barcode when shipping material. They either realize the error too late, or they instantly regret the results of the status change.
Currently, there is no good way to undo this type of unintended error for both partners. Manually changing the status only changes it on your end, not the partner's end, which throws off the entire workflow. This usually forces the partners to create brand new requests in order to finish circulating the material. This is more work for everyone involved and throws off stats.
We would love an 'Undo Last Action' option in the More Actions menu. This would allow for easier and faster workflow correction of Resource Sharing requests for both partners.
Many times, our library staff accidentally choose an unintended Resource Sharing status or scan the wrong barcode when shipping material. They either realize the error too late, or they instantly regret the results of the status change.
Currently, there is no good way to undo this type of unintended error for both partners. Manually changing the status only changes it on your end, not the partner's end, which throws off the entire workflow. This usually forces the partners to create brand new requests in order to finish circulating the material. This is more work for everyone involved and throws…
31 votes -
Add indications to Electronic Service & Portfolios showing when portfolios use MARC metadata instead of parser parameters for linking
There are some electronic services and portfolios in the Alma CZ that do not use parser parameters. Instead, they use ISSN or some other element drawn from the MARC metadata to construct their links. However, there is no indication in Alma when a service or portfolio behaves this way. To the Alma user, it looks as if the portfolios must be misconfigured, as they have no parser parameters and no apparent way to link at the title level. This makes troubleshooting linking problems very difficult, and it conceals the actual linking functionality from Alma customers.
To be fully transparent with customers and to enable customers to better troubleshoot linking problems, Ex Libris should add an indication at the service level linking tab (inherited by portfolios) 1) showing when MARC metadata is used instead; and, when this field is selected, 2) either the Parser parameters field or a new field should show which MARC fields are used to construct the links. I will attach an image showing where I think these new indications should appear in the service linking tab (they should also be inherited by portfolios).
An example collection that behaves this way is Akademiai Kiado, CZ Collection ID 611000000000000691
There are some electronic services and portfolios in the Alma CZ that do not use parser parameters. Instead, they use ISSN or some other element drawn from the MARC metadata to construct their links. However, there is no indication in Alma when a service or portfolio behaves this way. To the Alma user, it looks as if the portfolios must be misconfigured, as they have no parser parameters and no apparent way to link at the title level. This makes troubleshooting linking problems very difficult, and it conceals the actual linking functionality from Alma customers.
To be fully transparent with…
69 votes -
Add fund name to communication letter and po line claim letter
When starting a communication with a vendor the body field is pre-populated. Unfortunately, the fund name is missing. We would like to have to option to add the fund name in the communication letter (via letters configuration).
75 votes -
add modification date to "Monitor Requests & Item Processes"
It would be helpful to have the modification date, not just the request date as filter on the "Monitor Requests & Item Processes" page. Now it's almost not possible to find items which are e.g. stuck in hold shelf processing.
The request date does not allow to filter for items/requests which have been processed recently.8 votes -
Alma RS - Lending - Ship item digitally - email address to be viewable & editable
When Lending requests are shipped via ‘Ship item digitally’ staff cannot see the Borrowing library’s email address.
Below is a specific case with a VDX borrowing library. However the case can be applied to other scenarioes such as when a borrowing library asks to have the request shipped to a different email address.
Case:
When a VDX Borrowing library has the VDX proprietary DocStore enabled and sends a Lending request to an Alma library, the DocStore email address is output in the email request field in Alma RS (docdellibrariesaustralia@vdxhost.com).• Non VDX libraries cannot send digital content to this email address.
• The display of the DocStore address in the Alma email address field and the VDX inability to receive content from non VDX libraries is a VDX shortcoming.
If Lending staff have not seen and replaced the DocStore email address in the request’s General Information tab and use ‘Ship item digitally’ they are unaware that they are shipping to an invalid email address.
Lending staff are only alerted to the error when the Borrowing library responds that the digital content has not been received.
Please can the ‘Ship item digitally’ form be enhanced to include the Lending Library’s email address and the ability for the Borrowing library to update the email address on the ‘Ship item digitally’ form?
Please see the attached document for screen shot information.
When Lending requests are shipped via ‘Ship item digitally’ staff cannot see the Borrowing library’s email address.
Below is a specific case with a VDX borrowing library. However the case can be applied to other scenarioes such as when a borrowing library asks to have the request shipped to a different email address.
Case:
When a VDX Borrowing library has the VDX proprietary DocStore enabled and sends a Lending request to an Alma library, the DocStore email address is output in the email request field in Alma RS (docdellibrariesaustralia@vdxhost.com).• Non VDX libraries cannot send digital content…
24 votes -
Ability to remove default suppressed filter from resource locate
When using resource locate within reading lists to link a citation to a title the default search filters out suppressed title records.
This could be changed by adding mms_tagSuppressed to the Locate Citation By Fields table (Fulfillment Configuration > Courses > Locate Citation By Fields). Allowing it to be disabled.
This would be useful for us as we regularly use suppressed records where the physical item is not held but a representation of a chapter or article is and the representation will not be discoverable by primo. This prevents a title with no holdings appearing.
44 votes -
Analytics - make History tab in User Records indexed & searchable
We have been informed by Ex Libris that when a User Record is updated, either with an API or via the Alma interface, then those fields updated will not be updated with the daily SIS feed. They are considered "manual" changes and are therefore, locked. Now, in the history tab of User Records, you can see the changes made and by whom, but we have been told this information is not available in Analytics and the only way to know who has these locked fields is as we come across them. There is no way currently to systematically pull these records. This is a problem for us - a rather significant problem.
We have been informed by Ex Libris that when a User Record is updated, either with an API or via the Alma interface, then those fields updated will not be updated with the daily SIS feed. They are considered "manual" changes and are therefore, locked. Now, in the history tab of User Records, you can see the changes made and by whom, but we have been told this information is not available in Analytics and the only way to know who has these locked fields is as we come across them. There is no way currently to systematically pull these…
19 votes -
Trial : request of a Trial viewer role
There are 3 roles about Trials : administrator, operator and participant.
But none gives access to the Trials and all information with only option to view (and not delete neither modify datas).
A license viewer role exists in ALMA ; we request a similar Trial viewer role.28 votes -
Set Linking Parser Parameters at the Interface level
It would be more efficient to set the Linking Parser Parameters at the interface level, with an option to override the parameter at the Service Link level.
For example, I want to set our university's ProQuest clientid at the ProQuest interface level rather than have to open each of our 20+ ProQuest collections to edit the Service Link Parameters.
40 votes -
Analytics: Transit end time NOT registered
Hello,
Please see our public ticket 00903860.
If you make a query containing the field "Physical item historical events->Event end date->event end date and time" with the conditional "event type description=physical item went into transit" on this field is NOT registered the end of transit process, but the start of the following process (if any). Please correct this behaviour.40 votes -
Visibility of extension packs and possibility of selecting them one by one for editing and/or deleting
Extension packs once added to a local MARC-based profile are not visible and cannot be retrieved in any way. It would be much better if each extension pack loaded to a bibliographic profile could be visible to system admnistrators in order to be downloaded from bibliographic profile for purposes of editing and reloading, should the need arise. This feature was part of the tentative future developments proposed by Ex libris back in 2017 (see: internal: 2017 Q1 URM-45100)
67 votes -
Block the patron (several days) if they do not pick up a physical item that was requested and that they have reserved on the hold-shelf
Create a new TOU request type Policy type to sanction the not pick up of the item from the hold-shelf
31 votes -
On-shelf requests for specific user groups
We have limited human resource for picking up the items for on-shelf requests. Therefore, we hope this service is only available for patrons in need, for example, disabled patrons or distinguished professors/researchers.
Therefore, we need Alma to support “specific user groups’ to “request for on-shelf items”, and “pick up in different library/campus only”. It would also be nice if we can limit the number of on-shelf requests in a period of time.
This will definitely help librarians to provide precise service efficiently!
144 votes -
Enable Auto Refresh on the Monitor Jobs Page
At University of Tennessee we have found we are often waiting on lengthy system jobs to process before manually ran jobs are completed. It would be nice if this page had a built in auto-refresh to reload job percentage completion. It is rather tedious to repetitively click the refresh button to see if a job has began or made any substantial progress. If possible the button should be able to be clicked for instant refreshes but it should also refresh automatically in a timely matter. I believe increments of thirty seconds would be favorable or up to a minute. Thank you for considering this idea!
At University of Tennessee we have found we are often waiting on lengthy system jobs to process before manually ran jobs are completed. It would be nice if this page had a built in auto-refresh to reload job percentage completion. It is rather tedious to repetitively click the refresh button to see if a job has began or made any substantial progress. If possible the button should be able to be clicked for instant refreshes but it should also refresh automatically in a timely matter. I believe increments of thirty seconds would be favorable or up to a minute. Thank…
43 votes -
Show "Open for Update" override enabled
This is about the protection of data for external user records. I have copied the below text from the Alma Documentation page: https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/050Administration/030User_Management/010Managing_Users#UserDetails
To enable editing other fields of external users, select Open for Update, and select Yes. Edit the relevant fields and select Save. Note that changes you make to most fields will be lost after the next SIS synchronization job. However, Alma prompts you to determine whether the following fields will be overridden with the next SIS synchronization job: Title, PIN number, Job category, User group, Campus, Preferred language, Resource sharing libraries, Cataloger level, Selected patron letters. (Note that this determination is kept internal and is not externalized in the user record in any way.)
If I open an external user account and want to protect the mentioned data fields and click "yes" to protect these fields, we need a way to tell that I have enabled these fields to be protected.
So if I have User 1 and User 2 and I open User 1 and then open for update and protect those fields and then I open User 2 and open for update but DO NOT protect those fields, we need a way by looking at User 1 and User 2 records that one has these fields protected and one does not have these fields protected.
My idea is to allow this to be visible when these fields are protected.
(I had a salesforce case for this, for reference it was 00918286).
This is about the protection of data for external user records. I have copied the below text from the Alma Documentation page: https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/050Administration/030User_Management/010Managing_Users#UserDetails
To enable editing other fields of external users, select Open for Update, and select Yes. Edit the relevant fields and select Save. Note that changes you make to most fields will be lost after the next SIS synchronization job. However, Alma prompts you to determine whether the following fields will be overridden with the next SIS synchronization job: Title, PIN number, Job category, User group, Campus, Preferred language, Resource sharing libraries, Cataloger level, Selected patron letters. (Note…
44 votes
- Don't see your idea?