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 ~
1745 results found
-
self checkout
Self checkout over sip2 to have Alerts/fulfillment notes on checkout , not checkin only.
Patrons need to be alerted to how many pieces SHOULD be in the item when they checkout so they can alert staff if pieces are missing on checkout
26 votes -
Tie the Non-Renewal Notice Period or Cancellation Restriction fields in licenses to the PO Line
Create a linkage between the renewal notice period and cancellation restriction fields in a PO Line, if it is linked to a license agreement that references either a non-renewal notice or termination notice period, ask if this information should sync. Perhaps this is an area where DARA could operate?
1 vote -
Indication rule that checks if subfields are in the same field
Currently it is not possible to write an indication rule which checks the subfield a and b of a field only when both subfields are in the same field and not in repeated fields of the same record. Both of the following records are treated the same when looking for a subfield a "mercury" and subfield b "venus" in the 690 field:
Record 1:
690 $$a mercury $$b venusRecord 2:
690 $$a mercury $$b mars
690 $$a earth $$b venusI'd appreciate an option to distinguish if I'm looking for subfields in different fields or in the same field. We need this quite often for our local fields, as our data reflects different classifications via subfield 2.
Currently it is not possible to write an indication rule which checks the subfield a and b of a field only when both subfields are in the same field and not in repeated fields of the same record. Both of the following records are treated the same when looking for a subfield a "mercury" and subfield b "venus" in the 690 field:
Record 1:
690 $$a mercury $$b venusRecord 2:
690 $$a mercury $$b mars
690 $$a earth $$b venusI'd appreciate an option to distinguish if I'm looking for subfields in different fields or in the same field.…
63 votesI recommend applying XSL normalization rules with the required logic and integrating them into the Upon Save normalization process.
-
A "kill switch" for General System Administrators to immediately disconnect individual Alma users
Use case: A library employee (student or staff) responds to a phishing text message by providing their Single Sign-On (SSO) credentials; SSO is used on our campus for Alma authentication. I want to (1) disable all the roles on the library employee's account except for Patron; (2) disconnect the employee if he/she/they/* has an active session in Alma; and (3) be notified with the IP address of the originating computer if he/she/they/* attempts to log in again. I would like to accomplish both #1 and #2 by checking a box ("Disable roles") and moving a slider ("Disconnect user"), WITHOUT having to save the user record. A notification email with the IP address would be useful for #3, because it could be passed on to campus IT and we wouldn't have to worry about taking screen shots.
If #1-#3 are too much together, I'd take #2 alone -- I can get the roles disabled myself, but I want to be able to disconnect a user immediately, much the way I occasionally needed to go onto the Voyager server and kill sessions by process number.
This is functionality that I never needed in seven years on Alma, until the use case happened to us yesterday, at which time I REALLY NEEDED IT!
Use case: A library employee (student or staff) responds to a phishing text message by providing their Single Sign-On (SSO) credentials; SSO is used on our campus for Alma authentication. I want to (1) disable all the roles on the library employee's account except for Patron; (2) disconnect the employee if he/she/they/* has an active session in Alma; and (3) be notified with the IP address of the originating computer if he/she/they/* attempts to log in again. I would like to accomplish both #1 and #2 by checking a box ("Disable roles") and moving a slider ("Disconnect user"), WITHOUT having…
64 votes -
Item Policy Code Table issues
After adding an Alma Item policy in the Configuration->Fulfillment->Physical Fulfillment->Item Policy, the Item Policy Code Table allows you to edit the Code. Existing items records linked to the item policy code are not updated in such an edit. Such items retain the now “orphaned” original item policy code as can be queried in analytics.
To compound this, leading and trailing spaces within an item policy code are considered significant, so an edit to remove a trailing space leaves (invisible to the user) distinct item policies, one of which is broken.
We propose the following three changes:
1.) The Item Policy code table be changed to not allow editing of the item policy code to bring it in-line with other code tables in Alma to avoid “orphaning” item policies. This enforces consistency within the system.
2.) When saving an item policy, the system performs a trim of prefixed and postfixed spaces to the item policy code. This enforces data cleanliness.
3.) Since you can no longer edit the item policy code going forward per #1 above, the removal of an existing item policy should not be allowed until all items associated with item policy have had their item policy changed or removed. This enforces data consistency relating to existing items and ensures removal of unused item policies from items.
After adding an Alma Item policy in the Configuration->Fulfillment->Physical Fulfillment->Item Policy, the Item Policy Code Table allows you to edit the Code. Existing items records linked to the item policy code are not updated in such an edit. Such items retain the now “orphaned” original item policy code as can be queried in analytics.
To compound this, leading and trailing spaces within an item policy code are considered significant, so an edit to remove a trailing space leaves (invisible to the user) distinct item policies, one of which is broken.
We propose the following three changes:
1.) The Item Policy…
5 votes -
Alma “scan-in” API: Marc21 field 852 - call number prefix and suffix
We are using the Alma “scan-in” API
/almaws/v1/items?itembarcode={itembarcode}
which redirects to
/almaws/v1/bibs/{mmsid}/holdings/{holdingid}/items/{item_pid}
to print book labels.Some sublibraries also use call number prefixes or suffixes in some cases.
Please see the following example record:
- Marc21 field 852 in the Holding record
- XML output(1) Example: Call number with prefix 852 $$k
852 8_ |b XHOG |c XGRY |h G-1234567 |k PräfixXML output:
item/holdingdata/permanentcallnumber: Präfix G-1234567
item/holdingdata/callnumber: Präfix G-1234567
item/holdingdata/accession_number: G-1234567item/itemdata/parsedcallnumber:
<parsedcallnumber>
<callno/>
<call_no>Präfix</call_no>
<call_no>G-1234567</call_no>
</parsed_call_number>(2) Example: Call number with suffix 852 $$m
852 8_ |b XHOG |c XGRY |h G-1234567 |m SuffixXML output:
item/holdingdata/permanentcallnumber: G-1234567 Suffix
item/holdingdata/callnumber: G-1234567 Suffix
item/holdingdata/accession_number: G-1234567item/itemdata/parsedcallnumber:
<parsedcallnumber>
<callno>G-1234567</call_no>
<call_no/>
<call_no>Suffix</call_no>
</parsed_call_number>(3) Example: Call number with prefix 852 $$k and suffix 852 $$m
852 8_ |b XHOG |c XGRY |h G-1234567 |k Präfix |m SuffixXML output:
item/holdingdata/permanentcallnumber: Präfix G-1234567 Suffix
item/holdingdata/callnumber: Präfix G-1234567 Suffix
item/holdingdata/accession_number: G-1234567item/itemdata/parsedcallnumber:
<parsedcallnumber>
<callno/>
<call_no>Präfix</call_no>
<call_no>G-1234567</call_no>
<call_no/>
<call_no>Suffix</call_no>
</parsed_call_number>and after some tests the <parsed_call_number> section looks like this:
<parsed_call_number>
<call_no/>
<call_no>Präfix</call_no>
<call_no>G-1234567</call_no>
<call_no/>
<call_no>Suffix</call_no>
</parsed_call_number>Conclusion:
- Marc21 subfields 852 $$k and $$m are not listed sperately in the XML :-(
- In <parsed_call_number> section the content of <permanent_call_number> or <call_number> is splitted up into the content of 852 $$k, $$h and $$m. The order of the <call_no> tags is correct (call number prefix / call number / call number suffix) but there are also empty <call_no/> tags.Please provide us a XML output with Marc21 852 content in seperate fields. The important call number fields for us are:
- 852 $$k ... call number prefix
- 852 $$h ... call number (classification part)
- 852 $$m ... call number suffix
- <accession_number> includes 852 $$h only if the call number has been generated via a call number (accession number) counter.Other libraries may be interested also in other subfields of Marc21 852:
https://www.loc.gov/marc/holdings/concise/hd852.html
$h - Classification part (NR)
$i - Item part (R)
$j - Shelving control number (NR)
$k - Call number prefix (R)
$l - Shelving form of title (NR)
$m - Call number suffix (R)Having the content of 852 $$k, $$h and $$m in separate XML fields gives us the possiblity to handle the call number parts in a different way on the book label (if desired).
Having two <call_no> tags in the <parsed_call_number> section is not clear enough. It could mean that you have:
- 852 $$k ... call number prefix / 852 $$h ... call number (classification part)
- or 852 $$h ... call number (classification part) / 852 $$m ... call number suffixThank you in advance!
We are using the Alma “scan-in” API
/almaws/v1/items?itembarcode={itembarcode}
which redirects to
/almaws/v1/bibs/{mmsid}/holdings/{holdingid}/items/{item_pid}
to print book labels.Some sublibraries also use call number prefixes or suffixes in some cases.
Please see the following example record:
- Marc21 field 852 in the Holding record
- XML output(1) Example: Call number with prefix 852 $$k
852 8_ |b XHOG |c XGRY |h G-1234567 |k PräfixXML output:
item/holdingdata/permanentcallnumber: Präfix G-1234567
item/holdingdata/callnumber: Präfix G-1234567
item/holdingdata/accession_number: G-1234567item/itemdata/parsedcallnumber:
<parsedcallnumber>
<callno/>
<call_no>Präfix</call_no>
<call_no>G-1234567</call_no>
</parsed_call_number>(2) Example: Call number with…
20 votes -
Add Electronic Collection Information to the Bib Record Enrichment Fields in the OAI Publishing Profile
Problem - Database type electronic collections are not getting published to Blacklight in the OAI publishing job. So bibliographic records that have database type electronic collection inventory attached, display as records without inventory in the catalog.
Situation as described by Ex Libris - The OAI publishing profile is designed to publish the BIB record plus the enrichment fields. The Collection enrichment in the profile is for the Digital Collection, not the Electronic collection. The descriptive BIB record does not have Electronic collection as its inventory, the inventory is only Physical/Electronic/Digital. Adding Electronic Collection to the descriptive BIBs would be an enhancement request.
Please add electronic collection to the collection enrichment in the OAI publishing Profile.
Problem - Database type electronic collections are not getting published to Blacklight in the OAI publishing job. So bibliographic records that have database type electronic collection inventory attached, display as records without inventory in the catalog.
Situation as described by Ex Libris - The OAI publishing profile is designed to publish the BIB record plus the enrichment fields. The Collection enrichment in the profile is for the Digital Collection, not the Electronic collection. The descriptive BIB record does not have Electronic collection as its inventory, the inventory is only Physical/Electronic/Digital. Adding Electronic Collection to the descriptive BIBs would be an…
49 votes -
Do not create activation task if portfolios are activated on import and do move POL into waiting for invoice status
When using GOBI API for e-book ordering and loading local stand alone MARC records, we don't want the activation task to be created because the portfolios are already activated on import, and the activation task is hampering the order from moving to Waiting for Invoice.
We want to be able to configure a Do not create electronic activation task setting in Update inventory import profile type
Yes40 votes -
Alma Withdrawal Option
Our library needs the Withdraw function in Alma. We request a Deposit when we lend particularly valuable items. After the reader returns the book, the Deposit should be refunded. And this option is not available in Alma. There is a Pay option, but there is no Withdraw/Refund function, and we would like to be able to settle all financial matters in Alma (and not use external fiscal programs / cash registers).
157 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',
'pickuplocation' => 'Redmond Barry Reading Room',
'materialtype' => {
'desc' => 'Book',
'value' => 'BOOK'
},
'requestsubtype' => {
'desc' => 'Patron physical item request',
'value' => 'PATRONPHYSICAL'
},
'volume' => '',
'managedbylibrarycode' => 'ABC',
'part' => '',
'barcode' => '30328504468884',
'expirydate' => '2022-05-19Z',
'description' => undef,
'pickuplocationtype' => 'CIRCULATIONDESK',
'comment' => undef,
'userprimaryid' => '12345678',
'pickuplocationcirculationdesk' => 'DEFAULTCIRCDESK',
'managedbycirculationdesk' => 'East Retrieval',
'requeststatus' => 'HISTORY',
'title' => 'Life.',
'requestdate' => '2022-05-12Z',
'additional_id' => '141-999-119'
}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 -
Allow the rollover of a set of POLs or the results of an Alma Analytics query
It would be nice to be able to roll just a set of of orders, not individual POLs, or specific types of POLs. In our case, we have two libraries that prefer to have their orders rolled over on encumbrance, and the remainder on expenditure plus an FPC factor. We tried doing this this year by separately rolling the specific library's ledger and then associated POLs, but it took days. I think the issue is that it is trying and failing to roll every other active POL, and then just failing on those that do not yet have active funds.
Being able to roll this set of POLs over first would be much more effective.It would be nice to be able to roll just a set of of orders, not individual POLs, or specific types of POLs. In our case, we have two libraries that prefer to have their orders rolled over on encumbrance, and the remainder on expenditure plus an FPC factor. We tried doing this this year by separately rolling the specific library's ledger and then associated POLs, but it took days. I think the issue is that it is trying and failing to roll every other active POL, and then just failing on those that do not yet have active funds.…
3 votes -
Filtering a report based on a user set
Right now if you want to filter a report on a user set...
- Run a search in Alma and save to a set
- Export the list, using Excel.
- Manipulate the needed field (e.g. of barcodes), to be stored in one row, with semicolon separating them (e.g. 365704-340;365704-350).
- Copy this list as a row to be used as a filter in Analytics
I would like Alma smart enough, when I click on filter to simply supply the user set I created.
5 votes -
Generate PIN as an option in the Update/Notify user job.
Please add "generate PIN" as an option in the "Update/Notify user job".
6 votes -
Prevent placing different request types on the same item
Currently in Alma there is no cross check and no way to prevent a patron from placing both a Physical Item Request and the Digitization Request on a single item. The Ex Libris expectation is that requests will be reconciled through the request queues. However this adds additional time to the request process as it requires contacting the requester to confirm which type of request they need. I encountered the lack of a preventive configuration created a concrete clash as it came to our attention when a patron placed both types of requests on an item. This impacted 3 locations and resulted in an unnecessary and wasteful transit and confusion for staff and the patron. The Physical Item request transited from one holding location to a second location for pick-up. The Digitization request was received at another holding location.
By adding a configuration that allows institutions to limit types of requests on an item it would maintain a consistent and efficient workflow for staff and timely delivery for patrons.Currently in Alma there is no cross check and no way to prevent a patron from placing both a Physical Item Request and the Digitization Request on a single item. The Ex Libris expectation is that requests will be reconciled through the request queues. However this adds additional time to the request process as it requires contacting the requester to confirm which type of request they need. I encountered the lack of a preventive configuration created a concrete clash as it came to our attention when a patron placed both types of requests on an item. This impacted 3 locations…
1 vote -
Extend or allow one to be able to extend the time it takes to time-out when on the Manage Patron Services screen.
Please extend or allow one to customise their own time-out settings for the Manage Patron Services screen.
Gets on my nerves when I'm in the middle of composing an email to a Patron about their loans and I have to keep bringing up their account because it goes back to the search screen.
I need more time if I'm dealing with: fines, loan history, and making notes on an account, whilst trying to communicate what I'm doing.
3 votes -
Add portolios from CZ Updates Task List to associated collection in bulk
The Community Zone Updates Task List displays portfolios that were added to a non auto-active collection. But you can only handle these portfolios one by one. It would be helpful to select the desired portfolios and to add them in bulk to the associated collection.
The planned solution from ExLibris to manage collections as auto-active collections is not wanted because not all portfolios that are automatically activated are interesting to the library (e. g. when the library has a specific book stock and does not provide its readers with all scientific disciplines).1 vote -
Customize the Register/Update User (Quick User Management) screen/window
Watching a Primo demo complete with a discussion on how the view was customized, made me wonder if certain areas in Fulfillment could be customized. Is it possible to customized/configure the Register/Update User (Quick User Management) screen/window depending upon the role of the user? For instance a Circulation Assistant or Student Assistant would see only a limited number of fields (of course all the mandatory ones) whereas an Admin would see all the fields?
2 votes -
1 vote
-
Automatically disable a loan rule
During the holidays, we set up exceptional loan rules for a specific period (e.g. summer holidays).
But these rules must be deactivated manually, at a given date, in order to return to the normal rules used during the academic period.
It would be very interesting if these rules could be deactivated automatically by Alma, by entering, for example, an expiry date.
31 votes -
Transit Time Rules for Work Order Departments
We have work order departments in a central location providing services to multiple libraries across our state. When the department has completed their task and is ready to send the item to the distant library, Alma sets the delivery date to 24 hours when the transit time between libraries could take 72 hours. This confuses patrons who believe the item is available when it is in transit.
The Transit Time Rule set between libraries are not configured to include Work Order Departments and only the library level is available for configuration. We would like the Transit Time Rules to include the option to use Work Order Departments.
We have work order departments in a central location providing services to multiple libraries across our state. When the department has completed their task and is ready to send the item to the distant library, Alma sets the delivery date to 24 hours when the transit time between libraries could take 72 hours. This confuses patrons who believe the item is available when it is in transit.
The Transit Time Rule set between libraries are not configured to include Work Order Departments and only the library level is available for configuration. We would like the Transit Time Rules to include…
5 votes
- Don't see your idea?