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
-
Mejorar realizar cambios globales en ejemplares físicos
Permitir realizar cambios globales sobre los campos de signatura de ejemplares físicos, para modificar una parte de la signatura sin cambiar el resto. Por ejemplo:
EPP3500(075)/ALV cambiar a PLP3500(075)/ALV
EPP3300/WES cambiar a PLP3300/WES
22 votes -
Receipt for waived fees
Customers sometimes want a receipt for waived fees. Currently that's not possible within ALMA.
20 votes -
Estimated price -field for following year on continuous POL
Estimated price -field is needed for databases and another continuous purchase orders for following year budget planning. There should be price fields for both current year and the following year (also possibility to split them to different funds). Estimated price -field should also to be selected on the analytics reports. Publishers may change database or journals prices a lot more than average rate.
42 votes -
Add usage statistics -field for other statistics than Counter
A need for a new Usage Statistics -field that could be used for usage statistics other than Counter. Smaller e-journal etc. publishers don't have Sushi statistics but libraries collect usage data another way. The new usage statistics field should be for every year. The Usage Statistics -field should work on the Analytics. Statistics notes -field is also required.
39 votes -
Option to define another set of records to be included in the Database search
The database search in Primo includes only electronic collections with collection type “database” or electronic collections with a collection level URL and an unsuppressed bibliographic record.
Even though you can change the electronic material type of a portfolio to “database” these titles can’t be searched through the database search. This means we have to add local database collections even though the title can be activated through the community zone.
An example is the electronic collection “De Gruyter Databases”. I should like to be able to include these in the database search.47 votes -
Sort booking requests by Start Time
When monitoring resource requests on Fulfillment > Monitor Requests & Item Processes, a "Sort by" button with an option to sort by Start Time would ease the handling of booking requests.
The booking requests are currently sorted by Request Date, which is not very useful, and can not be sorted by any other field.A "Sort by" button actually does appear on Fulfillment > Pick From Shelf.
Another option could be adding the Start Time on the drop down menu of the bar "Requests" on top of the page.
69 votes -
The "maximum renewal date" (max_renew_date) should be part of the fields that are provided by API
The max-renew_date is viewable in Primo, but if you use another Discovery it can't be displayed because it is not provided by API.
61 votes -
Allow staff to override auto return when a borrowing request is received after needed by date has passed or request has been cancelled
When a borrowing library receives a resource sharing item after the request's needed by date has passed, Alma automatically updates the request to returned without displaying any alert. This causes a substantial amount of confusion for staff. We would like Alma to display an alert when a resource sharing item is being automatically returned to the lender because it was received after the request's needed by date. We would also like the opportunity to override this automatic return so users can have the option of using the item.
Likewise, Alma automatically updates borrowing reqeusts to returned when they've been cancelled by the user after the lending library has already shipped the item. Alma does provide an alert when this happens, which is helpful. We would like the option to override this automatic return too.
When a borrowing library receives a resource sharing item after the request's needed by date has passed, Alma automatically updates the request to returned without displaying any alert. This causes a substantial amount of confusion for staff. We would like Alma to display an alert when a resource sharing item is being automatically returned to the lender because it was received after the request's needed by date. We would also like the opportunity to override this automatic return so users can have the option of using the item.
Likewise, Alma automatically updates borrowing reqeusts to returned when they've…
53 votes -
Please expand the volume of Internal note fields to the Physical Item Editor
Our library has more than three kinds of information need to be recorded in the internal note field, such as property number, new books statues notes, compensation books notes and so on.
Hope is could add more, or became expandable let staff to select numbers of fields they needed.122 votes -
Add "Streaming" Purchase Order Line (POL) Types
There are currently no POL line types for streaming content.
I'd like to see the following POL Line types added:
Streaming Video - Subscription
Streaming Video - One Time
Streaming Audio - Subscription
Streaming Audio - One Time81 votes -
Add institution address information to XML for Ful Transit Slip Letter
When an item is placed in transit to another institution in an AFN, the institution name is included in the XML of the Ful Transit Slip Letter. However, no address information for the institution in included in the XML, so it's not possilble to add that information to the Ful Transit Slip Letter. SUNY has added resource sharing partner address info to our resource sharing shipping and return letters, and that has proven to be very helpful. We would like the address of the library where the item is held to be added to the XML for the Ful Transit Slip Letter to we can display that information on the letter.
When an item is placed in transit to another institution in an AFN, the institution name is included in the XML of the Ful Transit Slip Letter. However, no address information for the institution in included in the XML, so it's not possilble to add that information to the Ful Transit Slip Letter. SUNY has added resource sharing partner address info to our resource sharing shipping and return letters, and that has proven to be very helpful. We would like the address of the library where the item is held to be added to the XML for the Ful Transit…
41 votes -
Allow harvesting of reports with the non-standard SN:Total_Chapter_Request metric
I noticed that some vendors - Taylor and Francis and Springer- are adding this non-standard metric - SN:TotalChapterRequest - to their TR Master Reports. These are 2 big vendors, and these TR master reports won't load into Alma with this nonstandard metric in them.. I was hoping there is a way to accommodate them and allow them to load.
21 votes -
Keep POL reclaim interval and grace period when changing vendor
We have an issue with acquisition when it comes to continuous orders. If we change a vendor for a given POL, the data previously entered for the grace period and the reclaim interval disappears. They are replaced by the default value from the vendor.
This can be quite a serious issue when changing vendors for many POLs at once, which happens from time to time.
It would be much more efficient to keep the grace period and the reclaim interval for the POL, as it's linked to the serial publication interval.Grace period and claim interval depends on title periodicity.
The advantage of adding this information at the POL level and not at the supplier level is to include periodicity information for reclamations. Even if a supplier changes, title periodicity generally remains the same.
Ex Libris should add a setting to allow customers to keep these information in some POL.
We have an issue with acquisition when it comes to continuous orders. If we change a vendor for a given POL, the data previously entered for the grace period and the reclaim interval disappears. They are replaced by the default value from the vendor.
This can be quite a serious issue when changing vendors for many POLs at once, which happens from time to time.
It would be much more efficient to keep the grace period and the reclaim interval for the POL, as it's linked to the serial publication interval.Grace period and claim interval depends on title periodicity.
The…
32 votes -
POLs are not closed when Proquest Ebook Central Electronic Ressource is activated by Autoload
We are using Autoload with Proquest Ebook Central. When we create a POL for a Proquest title and connect this POL with the portfolio which came per Autoload and pay the invoice, the POL remains in Status "Sent". It has the Activation status: Activated E-Ressource", but the warning "Electronic Resource was not activated". Now we have to go to the portfolio per the electronic portfolio search, select "Create E-activation task", then go to the electronic resources activation task list entry for this resource and select "Done" to make this alert disappear. This also closes the PO Line, but this workflow is very cumbersome. We'd like that a POL would be closed automatically when te invoice is paid and the Portfolio is activated by Autoload and that there will not be the assert "Electronic resource was not activated".
We are using Autoload with Proquest Ebook Central. When we create a POL for a Proquest title and connect this POL with the portfolio which came per Autoload and pay the invoice, the POL remains in Status "Sent". It has the Activation status: Activated E-Ressource", but the warning "Electronic Resource was not activated". Now we have to go to the portfolio per the electronic portfolio search, select "Create E-activation task", then go to the electronic resources activation task list entry for this resource and select "Done" to make this alert disappear. This also closes the PO Line, but this workflow…
39 votes -
Add warning for active title-level-requests when relinking or deleting holding records or items
When relinking holdings and items to new bib records or deleting holdings or items, requests can get lost. This is the case if they are on the titel level instead of on the item level.
(Cf. https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/Physical_Resource_Management/015_Managing_Physical_Resources#Relinking_Items_to_Another_Bibliographic_Record)Staff with the role Cataloger Extended or similar roles which allow for relinking and deleting of records, holdings, and items, would benefit from a warning that an active request is present on the title level (e.g. a pop-up) before a holding record or item is relinked or deleted.
81 votes -
Make Push Selected to MDE button available for Itemized Sets
'Push Selected to MDE' (pushing records in bulk to Metadata Editor) is not available for Itemized sets, but it is available for Logical sets in the current Alma implementation. While the option to Push Selected to MDE is plainly visible in the Logical Set Results view (please see the attached screenshots), it is replaced by the 'Remove Selected' button in the Itemized Sets Members’ view. We would be very interested in having the Push Selected to MDE available for both Logical and Itemized sets. Is it possible to add the 'Push Selected to MDE' to he Itemized view and keep the 'Remove Selected' button at the same time?
This issue was raised originally with ExLibris via incident #00954718 and we were advised this is not current functionality.
We appreciate your support for this idea!'Push Selected to MDE' (pushing records in bulk to Metadata Editor) is not available for Itemized sets, but it is available for Logical sets in the current Alma implementation. While the option to Push Selected to MDE is plainly visible in the Logical Set Results view (please see the attached screenshots), it is replaced by the 'Remove Selected' button in the Itemized Sets Members’ view. We would be very interested in having the Push Selected to MDE available for both Logical and Itemized sets. Is it possible to add the 'Push Selected to MDE' to he Itemized view and keep…
51 votes -
Mapping of Rialto invoice data in Alma
The freight charge in our Rialto invoices is being mapped to the "Overhead amount" field. We would like this to be mapped to the "Shipment amount" field which seems more accurate. Ex libris have advised that this is hard coded and requires support from the user community to proceed.
21 votes -
Make PO line Rollover Job work dependent on ledger and possibly fund codes.
User Story. Currently we our Acquisition team have a different set of ledgers to our Subscription team. When we do a Rollover of funds and ledgers this is not an issue. However, when we are trying to test the PO Rollover it is difficult to separate out the PO Lines that are for the Acquisitions Rollover and the Subscriptions Rollover.
Solution - It would be better if you could only roll over PO lines that were attach to a specific ledger (and possible set of fund codes). So that we could run the Acquisition rollover separately to the Subscriptions rollover.19 votes -
Enhance Display Logic Rules to incorporate the same full functionality options of General Electronic Services
Display Logic Rules options are limited in allowing only Hide options by User Group, ownership by campus or institution, or presence of another service. They also have hardcoded display depending on the service, such as displaying only when a user is logged in, and only in Get It or View It (some of which are understandable per service).
In contrast, General Electronic Services are extremely powerful with Show / Hide options by true or false default rule, choice of display in Get It and/or View It, allowing display when not logged in, as well as by ownership by campus or institution, along with many dozens of supported OpenURL elements such as genre and format in the Service Availability Rules.
This submission is to request that the same Service Details and Service Availability Rules interface and full options which exist for General Electronic Services are also made available for use in Display Logic Rules.
This would support use cases such as allowing Libraries to only show Purchase Request when the Library will conceivably fulfill the request by this pathway. This may be variable for each Library, but it is highly likely that this would rarely be offered for an ongoing subscription, a database, images etc.
Note: These are just two examples and this submission will not be met only by covering those.
Without such granularity, Alma (via Primo) either offers only an unnecessarily limited service, or gives users a false expectation of an available service leaving a negative impression when Library staff must then quash this expectation by rejecting the request.Display Logic Rules options are limited in allowing only Hide options by User Group, ownership by campus or institution, or presence of another service. They also have hardcoded display depending on the service, such as displaying only when a user is logged in, and only in Get It or View It (some of which are understandable per service).
In contrast, General Electronic Services are extremely powerful with Show / Hide options by true or false default rule, choice of display in Get It and/or View It, allowing display when not logged in, as well as by ownership by campus or…21 votes -
Analytics Reports for Deleted Purchase Requests
I would like to be able to run Analytics reports on deleted purchase requests. Currently, deleted purchase requests are not available in Analytics. Therefore, we don't want to delete any of our hundreds of purchase requests because we'd lose the ability to generate Analytics reports on them. Having hundreds of old purchase requests accumulate in Alma becomes unwieldy.
152 votes
- Don't see your idea?