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.
1773 results found
-
Include MARC leader in General Electronic Services Bib Fields Enrichment
The addition of bib fields enrichment for general electronic services has been helpful in creating service availability rules for GESes, but there is no way to configure enrichment based upon content in the MARC record leader. This is where primary resource aspects are noted, such as record type, bibliographic level, and whether a resource is under archival control. Being able to use this criteria when displaying or hiding a service would be much easier than the convoluted and imperfect workarounds we've resorted to.
3 votes -
Add "PO Line Owner" as an input parameter for Purchase/Invoice Review Rules
Adding "PO Line Owner" as a parameter for Purchase/Invoice Review Rules would allow differentiation by location. Our main library uses student workers for ordering, and I want to be able to have review rules in place to catch potential mistakes. Our satellite location has one staff person doing all the acquisitions. These same review rules will be cumbersome for their workflow. Having separate rules allows each location to operate most efficiently.
3 votes -
Ability to report on the source of a MARC record
It would be useful to be able to report on the source of a MARC record in Alma Analytics. This should be part of the 'Titles' Subject Area, providing information on whether the record was created using a record from a Z39.50 query or via a scheduled or manual import job.
If the record is imported via a Z39.50 query, the source bibliographic knowledgebase should be reportable (e.g. OCLC WorldCat, Jisc Library Hub etc.).
If the record was created via an import job, the name of the import profile should be reportable.
This would help libraries to better maintain statistics…
3 votes -
Add information regarding level URL clickthroughs to Analytics
Currently only clickthrough for portfolios are being captured in Analytics. It would be great if level URL clickthrough's in Electronic Collection could also be captured.
3 votes -
Adding a parameter to block the request queue for physical items at the title level
The request queue can be confusing for library users, as such requests are often canceled due to lack of copies. With title-level requests, the library should be able to decide whether or not to allow a queue for physical item requests. It should be possible to create a parameter for this to allow blocking the queue.
3 votes -
Preview PO line attachments in Alma
It currently is not possible to preview a PO line attachment in Alma; you have to download it to see what the document contains. This can result in downloading multiple documents before you find the one that you need. We would like to be able to preview those attachments in Alma to avoid that extra step of downloading each attachment just to view it.
3 votes -
Analytics recover the fields in the original configuration language in ALMA
ALMA is configured for Spanish-speaking countries in Spanish, so Analytics reports are required to generate data in the same language in which the original fields are configured.
3 votes -
Copyright Statuses within Digitization Fulfillment requests
In Alma's fulfillment area, processing a library/patron digitization request often requires multiple steps to get copyright approval. Currently, the copyright clearance process is a single step - a check against the Copyright Clearance Center (CCC), but if a publisher or rightsholder isn't part of CCC, the licensing process must be managed outside of Alma.
If the digitization request is a product of a citation (ie from Leganto or Alma COurse Reserves), then it would be helpful to include relevant course data and the number of students in the course as part of the request.
We propose adding a new state…
3 votes -
Add an option for annual token entry to track "Requests to publish" in multi-year transformative agreements
Currently there are only two options for tracking requests to publish for Transformative Agreements: Unlimited or Number of Tokens. However, for a multi-year agreement with a set number of tokens per calendar year, there is no great way to track this within the Agreement Definitions on an ongoing basis. If we could get the option to track the number of requests to publish for multiple time periods within the same agreement, that would be beneficial for those with multi-year TAs.
3 votes -
claims - serials - populate item description
It will be very helpull to include the item description in the list of claims.
3 votes -
Add option for Due Time to be after Midnight
Our library is sometimes open until 1:00am and when it is we want the due time of our items to be when we close and not at midnight. Currently to do this the due time needs to be overridden for each relevant item by our front desk. Adding this as an option in either calendar management or as a policy option would reduce manual effort by our staff, lower the risk of mistakes being made and patrons incorrectly being charged fines, and lessen confusion among our patrons.
3 votes -
AFN Loans on library loans webhooks
We manage home delivery requests. We need to print labels and generate a file of deliveries once a day with all loans.
Alma did not provide a list of home delivery transactions the same day, you need to wait the next day to generate a Analytics report.
We have developed a solution that makes a list using Loans Webhooks. Now we are using AFN (Automated Fulfillment Network) in our consortium and those transactions are not published on our Webhook, because books are from other institutions even though the loan was made in our system.
In order to have all home delivery transactions we need all loans made…6 votes -
Add a request cancellation code & reason in the Request webhook
The current Request webhook doesn't seem to include the Request Cancellation reason. Currently it just says:
'event' => {
'desc' => 'Request canceled',
'value' => 'REQUEST_CANCELED'
},The comment field refers to the request, but not the cancellation reason here:
'userrequest' => {
'requesttime' => '2022-05-11T23:42:26.191Z',
'managedbycirculationdeskcode' => 'EASTCIRC',
'mmsid' => '993815723607636',
'taskname' => 'Rejected',
'author' => 'Ferguson, J.',
'itemid' => '2365452260007636',
'issue' => '',
'pickuplocationlibrary' => 'ABC',
'dateofpublication' => '',
'managedbylibrary' => 'State Library',
'requesttype' => 'HOLD',
'requestid' => '1419991190007636',
'pickup…3 votes -
Add webhook event for Resource Sharing lending request
Actually we can intercept a RS borrowing request via webhooks in two ways, via a new request event or via a new item event (using a RS location filter), but there seems to be no events for lending request until the resource is located and the temporary RS location is applied. We need a specific webhook event that occur when a RS lending request is created.
3 votes -
Allow loans/requests APIs to override blocks and limits
When using the Alma UI staff are able to override user blocks and loan/request limits when loaning an item or creating a request. With the API this is not possible. It would be helpful if the APIs had a parameter to perform a staff override in the same manner. This would allow automated loans and requests to work in scenarios where staff would have overridden the block/limit, and where it is desirable that the loan/request always succeeds.
3 votes -
Option to remove Alma roles if staff not logged in for X days/months
Having an option to remove Alma roles if staff not logged in for X days/months will help automate the process of identifying and managing inactive accounts, saving administrative time.
We have a lot of staff that change job roles within the institution, but end up keeping their Alma roles unless someone tells us they are leaving the library department. Obviously this idea won't fix all the problems, but it would certainly help with reducing the risk of unauthorized access - particularly for any one that has an administrator role
3 votes -
Provide fulfillment configuration utility information in an API response
Currently, testing configurations requires manually pasting information into the Fulfillment Configuration Utility and then reviewing output.
It would be much more helpful if an API could accept a list of users and barcodes and return the output of the fulfillment configuration utility - names of the matched rules, or names + policy values. That would allow for much more robust and efficient testing of configuration.
3 votes -
Display Renewal Notes in the new Unified PO Line List
Along with the other notes that now appear in the new Unified PO Line (Vender, Activation, and Receiving) that was recently released, it would be great if Renewal notes also appeared in the Badges and Icons section when they were listed. Our staff currently use it to denote when they need to not renew an order, so having it displayed from the main list would be helpful for them to quickly parse out what needs to be handled.
3 votes -
Ability to queue borrowing requests for a temporarily inactive partner
Hi,
For resource sharing, we use Alma partners with the ISO profile type that are part of the Libraries Australia Document Delivery (LADD) network.When partner libraries suspend themselves from LADD services, their Status updates in Alma to Inactive.
However, sometimes a Library is the only possible lender of material. In these cases, we would prefer to wait until the Library becomes Active again, instead of trying to source a partner overseas (for us in Australia, time-consuming and much more expensive, plus challenges with postal delays). At present, we add a Note to the request that it is to be…
3 votes -
Option to NOT receive ticket updates 'Report to ExLibris'
Add a 'Report to ExLibris' option to NOT receive ticket updates.
Use case: I report that an ebook title in a huge Open Access collection is, in fact, not open access. I view this as a standard cleanup task. We've likely already suppressed the record from our catalog and don't need to track the ticket or receive updates. It generates many unnecessary emails.3 votes
- Don't see your idea?