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 ~
1693 results found
-
Improve 'Synchronize from CZ' job reports
Sometimes, the information in the reports bears no resemblance to what’s in the CZ Updates Task List. For example, the 'portfolio linked to different bibliographic record' information isn't included in the CZ Updates Task List at all so you have to submit a SF case each time if you want to find out which portfolios were moved and which records are involved.
It would be useful to have clickable counters in the 'Synchronize jobs from CZ’ job reports that take you through to the corresponding changes in the CZ Updates Task List.
29 votes -
Add Storage Location ID to Physical Items Search brief results
We'd like to start using the Storage ID field to track inventory shelved in storage locations. It would be very helpful if this field would display in the Physical Items brief results list, so that operators know right away that the item is in a storage location. Unfortunately, it does not appear to be a field that has been added yet. Please can you add this field to the Physical Items brief results list.
36 votes -
Analytics: Add item changed permanent location to events that are recorded (and timestamped) Physical Items Historical Events subject area
Usage case: University of Wisconsin would like to create reports that inventory items that change permanent locations by date. Currently, a report that can inventory all items that were added to a permanent location from various other locations by fiscal year isn't possible. With the addition of item changed permanent location as an event that is timestamped such a report would be possible. For example, a report of all items relocated to off-site storage during the past fiscal year is a desired report.
27 votes -
Generate Feedback Message with Link to E-Resource Activation Task
When creating an e-activation task for an electronic inventory item directly from the portfolio or collection, the feedback message contains only an informational message that the task was completed but does not contain a link to the task on the E-Resource Activation Task List. We would like to see a feedback message that would include a direct link to the task so that the user can then handle the task (for example, assign the task to themselves or to others.)
We would also like to see a feedback message containing a link to the newly created task when submitting an order for an e-resource if a task is created.
When creating an e-activation task for an electronic inventory item directly from the portfolio or collection, the feedback message contains only an informational message that the task was completed but does not contain a link to the task on the E-Resource Activation Task List. We would like to see a feedback message that would include a direct link to the task so that the user can then handle the task (for example, assign the task to themselves or to others.)
We would also like to see a feedback message containing a link to the newly created task when submitting an…
30 votes -
make "test access" work when direct linking is enabled
The "test access" button in Alma does not work when direct linking is enabled in Primo. When trying to test access for an electronic portfolio, Alma loads a blank page forcing staff to click "display in a new window" in order to proceed. We recommend that this behavior be changed so that test access works the same regardless of whether direct linking is enabled.
69 votes -
Metadata Editor should add the year automatically to the 866 field
Currently the Metadata editor does not add automatically the year to the 866 field. If we want the year to be in our 866 we have to add it manually. Actually this is the only way our patrons can see the year in Primo.
69 votes -
Permanent collections
Colecciones permanentes:
Si un título tienen todos sus ítems asignados a una colección permanente de documentos perdidos, extraviados, descartados, etc. , el sistema Alma debe evitar que el registro se recupere y visualice a través de Primo, esto a fin de que los usuarios no visualicen un recurso que no tiene la biblioteca y a fin de evitar de realizar otro proceso de cambio.Permanent collections:
If a title has all its items assigned to a permanent collection of lost, missing, discarded documents, etc. , the Alma system must prevent the registry from being recovered and viewed through Primo, so that users do not visualize a resource that the library does not have and in order to avoid carrying out another process of change.Colecciones permanentes:
Si un título tienen todos sus ítems asignados a una colección permanente de documentos perdidos, extraviados, descartados, etc. , el sistema Alma debe evitar que el registro se recupere y visualice a través de Primo, esto a fin de que los usuarios no visualicen un recurso que no tiene la biblioteca y a fin de evitar de realizar otro proceso de cambio.Permanent collections:
If a title has all its items assigned to a permanent collection of lost, missing, discarded documents, etc. , the Alma system must prevent the registry from being recovered and viewed through Primo, so…93 votes -
Trials : when a participant reopens a survey form, the replys already submitted should display
At the moment, when a participant reopens a survey form he already submitted, all the answers are empty.
If he fills in again the survey form, at the end, when submitting his answers the second time, a warning message displays (do you want to submit again ?)
We consider that this warning is too late in the workflow.So our request is : when a trial participant has filled in a survey form, if he reopens the same survey form later, this one should display the answers already submitted.
19 votes -
Add preferred address to Resource Sharing Shipping Slip Letter
I suggest that preferred shipping information be added to notificationdata/partnershippinginfolist/partnershippinginfo in the xml of this letter. Currently all registered partner addresses are added to the XML with no indication of which is the preferred address.
As a result the true shipping address cannot be deduced from the XML, which leads to a manual address lookup before shipping.
21 votes -
Accrual Accounting>Add Ability to Manually Edit Accrual Amounts
Alma calculates accrual percentages based on days, while we have always calculated the percentages/amounts based on months. That creates problems when we manually calculate an invoice outside of Alma, and then try to re-create it in Alma. We have had instances in which we have different amounts in Alma and with our business office as we could not enter the amounts manually in Alma. It would be really helpful to be able to manually edit amount fields for both fiscal years.
As another example, a 50/50 split of an odd number, e.g. 49.87 requires one year to be 24.93 and one to be 24.94. Currently, we have no control over which fiscal year gets billed more.
Alma calculates accrual percentages based on days, while we have always calculated the percentages/amounts based on months. That creates problems when we manually calculate an invoice outside of Alma, and then try to re-create it in Alma. We have had instances in which we have different amounts in Alma and with our business office as we could not enter the amounts manually in Alma. It would be really helpful to be able to manually edit amount fields for both fiscal years.
As another example, a 50/50 split of an odd number, e.g. 49.87 requires one year to be 24.93 and…
32 votes -
Use NZ records for full text links in Primo search results
There is an issue with full text links not appearing in the Primo record when the incorrect ISSN is in the 022$y field. If the incorrect ISSN is in an IZ record, the search stops there and there is no full text link in Primo when in actuality there is full text available from the NZ. Can the NZ records be used in this case, not just end at the "bad" IZ record?
My end goal would be that when looking for full text, the search doesn’t end with an IZ record that may or may not have the correct ISSN, but that the NZ records are also looked at so a full text link will appear in the Primo record.Case# 00673680
There is an issue with full text links not appearing in the Primo record when the incorrect ISSN is in the 022$y field. If the incorrect ISSN is in an IZ record, the search stops there and there is no full text link in Primo when in actuality there is full text available from the NZ. Can the NZ records be used in this case, not just end at the "bad" IZ record?
My end goal would be that when looking for full text, the search doesn’t end with an IZ record that may or may not have the correct…26 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 -
Allow each items’ request policy with specific parameters (location, keyword etc.) to be excluded from the title-level request policy
I believe this is an expansion on this idea https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/31119715-title-level-request-and-item-level-request
But we are dealing with ASRS in our case so I thought it might be a little more elaborate.
We would like to have the option to allow each items’ request policy with specific parameters (location, keyword etc.) to be excluded from the title-level request policy.
Currently we have "No requesting" as our general policy that's applied to all of our items except for the ones in ASRS. The problem is that when items with multiple copies and identical call number exist both at open-stack library and ASRS, the No requesting policy takes precedence over everything else even if ASRS items are set as requestable.
It would be beneficial if the patrons are able to choose freely where they want to request from based on the items’ availability instead of having No requesting applied across all locations, especially when the item is actually "requestable" in ASRS.
I believe this is an expansion on this idea https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/31119715-title-level-request-and-item-level-request
But we are dealing with ASRS in our case so I thought it might be a little more elaborate.
We would like to have the option to allow each items’ request policy with specific parameters (location, keyword etc.) to be excluded from the title-level request policy.
Currently we have "No requesting" as our general policy that's applied to all of our items except for the ones in ASRS. The problem is that when items with multiple copies and identical call number exist both at open-stack library…
83 votes -
NZ EBSCO Link Resolver Plug-in
Currently in the NZ, if you use the EBSCO Link Resolver Plug-in, it is applied all of the libraries using the NZ. We are not able to activate the plug-in for specific libraries in the NZ. Not all of the libraries want to use the link resolver plug-in. Also, along with being able to activate the plug-in for specific libraries, the plug-in will also need to be set up for the specific customer ID. Currently, when we have the link resolver plug-in activated in the NZ, all libraries are being filtered by all of the available EBSCO resources paid for centrally. Our libraries have specific subscriptions to the EBSCO resources so we need to the ability to use a customer ID so that EBSCO knows the correct resources to apply the plug-in.
1)Be able to set up specific libraries for the link resolver plug-in in the NZ.
2) Be able to let limit the plug-in to the specific EBSCO resources for that library.
More details can be found in case: 00570478Currently in the NZ, if you use the EBSCO Link Resolver Plug-in, it is applied all of the libraries using the NZ. We are not able to activate the plug-in for specific libraries in the NZ. Not all of the libraries want to use the link resolver plug-in. Also, along with being able to activate the plug-in for specific libraries, the plug-in will also need to be set up for the specific customer ID. Currently, when we have the link resolver plug-in activated in the NZ, all libraries are being filtered by all of the available EBSCO resources paid for…
33 votes -
Location Priority
We need Location Priority function in Alma-Primo too. IP, temp/remote, and alphabetical ordering options are not enough to show locations in the way we want to display them.
37 votes -
Make the email that is generated when an ILLiad resource sharing partner exports a request to a third party customizable
Unfortunately, ILLiad's email import feature does not always import emails generated by Alma properly. This happens mainly when there is a copyright symbol in the requested item's publication date. Giving us the ability to remove the publication date field from the email generated by Alma would help us manage this issue until OCLC and Atlas Systems can find a proper fix.
19 votes -
Allow customization of close_paid_lost_loans parameter
When the closepaidlostloans parameter to false and lost loans are closed (either manually or through the Close Lost Loans job), refunds/credits are not automatically given to patrons if the item is subsequently found and returned. When setting the closepaidlostloans parameter to true and the lost loan is closed (automatically setting the Lost and Paid status), a refund/credit IS applied to the patron’s account if the item is subsequently found and returned, providing the Lost Loan Refund Ratio is greater than 0.
For libraries that wish to take advantage of this new Process Type, but do not wish to issue credits automatically for Lost and Paid items, this can cause some problems. Staff must monitor and waive these credits as they often negate other fines on the patron’s account. In addition, the credit can cause problems with automated financial processes (i.e. Bursar integration) as credits transmitted to the financial system can act on non-library fees owed, or create automatic refunds that may or may not be due depending on the refund policies in place.
Proposed solution: When setting the closepaidlost_loans parameter to true, we’d like an additional option to allow or block the automatic refund/credit when a lost and paid item is found and returned. In other words, we’d like the option to keep the new Lost and Paid Process type, but also the ability to actually close the loan completely as is done with regular Lost Loans.
When the closepaidlostloans parameter to false and lost loans are closed (either manually or through the Close Lost Loans job), refunds/credits are not automatically given to patrons if the item is subsequently found and returned. When setting the closepaidlostloans parameter to true and the lost loan is closed (automatically setting the Lost and Paid status), a refund/credit IS applied to the patron’s account if the item is subsequently found and returned, providing the Lost Loan Refund Ratio is greater than 0.
For libraries that wish to take advantage of this new Process Type, but…
82 votes -
Mechanism to validate binary MARC record structure
There is currently no mechanism within Alma to ensure that exported or published binary MARC records have valid record structures. Even though Alma uses MARCXML and is not impacted internally by invalid binary MARC, libraries must still provide binary MARC records to external entities in the course of regular business (vendors, outsourcers, agencies, other stakeholders).
Structurally invalid binary MARC records significantly hamper data sharing for libraries. A third party application, MarcEdit, can be used to validate MARC record structure, but since our data is stored in Alma, there should be a mechanism native to Alma that validates binary MARC structure prior to export or publishing.
An internal job or process to validate the structure of single or files of binary MARC records should be added so that customers are not reliant on a third party application for this.
There is currently no mechanism within Alma to ensure that exported or published binary MARC records have valid record structures. Even though Alma uses MARCXML and is not impacted internally by invalid binary MARC, libraries must still provide binary MARC records to external entities in the course of regular business (vendors, outsourcers, agencies, other stakeholders).
Structurally invalid binary MARC records significantly hamper data sharing for libraries. A third party application, MarcEdit, can be used to validate MARC record structure, but since our data is stored in Alma, there should be a mechanism native to Alma that validates binary MARC structure…
64 votes -
Email notification to ISO Partners about Overdue Items
We would like for the Borrowing Library to receive an email notification (in addition to the patron) when an item is Overdue.
Since Dec. 2018 this option is available for NCIP Partners, but not for ISO Partners13 votes -
Displaying the "Requester Notes" from Purchase Requests in the list of Purchase Requests
In the Purchase Request List you can't see the "Requester Note" for a Purchase Request. In many cases there are very helpful information for managing the Requests. So it would be great if you can see the information immediately.
If the Note is very long, a mouse over with the text could be a solution.21 votes
- Don't see your idea?