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.
87 results found
-
Change Financial Year dates after they have been set
It doesn't look as if it is possible to change the start and finish dates of any financial year in Acquisitions Configuration > Fund And Ledger Fiscal Period table mapping tables once the year has been created, unless it is deleted completely.
Can it be made possible for the start and (in particular) the end dates to be edited having already been set and saved, if so required?
Being able to do this would be of particular benefit around the time of a financial year rollover, especially if an institution cannot be certain that all financial transactions for the outgoing…
17 votes -
Ability to link to single interface records from vendor record
At the moment, when you link to an interface from a vendor record in Alma the interface record cannot be linked to one that has already been set up. For example, if you have Vendor A and link it to Interface X you cannot also link Vendor B to Interface X. You are also unable to have two interfaces with the same name. This is required in situations where we have multiple vendors for the one interface. For example, SAGE journals are acquired directly through SAGE but the ebooks are acquired through iGroup. In this case we would like to…
94 votes
Anonymous
responded
Submitted by Ex Libris PM on behalf of our customers
-
need more search criteria in acq such as operator id or create/update date
It would be useful to have some additional search criteria, such as operator id, and facets, such as a last update date range and status, available to monitor staff productivity. Not just in purchasing but in all areas of acquisitions the site reports the need for functionality that will allow a combination of attributes of the records to generate results. For example, an operator should be able to search using their user name, some category of task (po lines in review, invoice lines in review, invoices pending approval, etc.) and a date or date range, or status (sent/ waiting auto…
60 votesAnonymous
responded
Submitted by Ex Libris PM on behalf of our customers
-
The default receiving status in manage items of receiving workbench is all and it should be not received or should be configurable
As part of the new prediction pattern development it is possible in the receiving workbench to receive new items and filter the 'manage items' section by "all" "received" or "not received".
Currently it defaults to "all" which is not what would be desired because
A. it would show too much
B. they would need to manually search for what they want to receive.It should default to "not received" because then they can choose the issue they have in hand and receive it. Another option would be to have it always remember the previous filter of the user and use…
34 votesAnonymous
responded
Submitted by Ex Libris PM on behalf of our customers
-
EDI check in for print journals
Alma documentation states that Alma supports the following Edifact message types – INVOIC, ORDERS, OSTENQ, ORDRSP, ORDCHG. However our old LMS Aleph supported an additional Edifact message type called DESADV.
This allowed our serials agent, Ebsco, to check in our journals in on the LMS remotely via EDI once our monthly consolidated deliveries of print journals were despatched from the warehouse.
Provided our prediction patterns matched the PIA line this worked efficiently. An example of EDI text is as below:-
LIN+1'
PIA+5+0001-4788(2012)42?:1;1-9:SI::28'
IMD+L+050+:::ACCOUNTING AND BUSINESS RESEARCH'
QTY+12:1'
RFF+SNL:52280023'
RFF+SNA:52280023'The above essentially means that for order no 52280023 (linking to…
24 votes -
Automatically Associate Certain Payment Methods (e.g., Credit, JV, Deposit) with Prepaid Functionality when Creating Invoices
We would like the ability to automatically associate certain Payment Methods (Credit Card, JV (Correction), Deposit Account, etc.) with Prepaid functionality when creating Invoices. 1) This would save time. 2) Most institutions do not want certain payment methods going to their ERP, but occasionally forget to check the Prepaid box. Setting this up systematically would serve as a fail-safe for such situations.
14 votes -
Add a new privilege to the "Purchasing Operator" role which will prevent users with this role from being able to delete items
This Idea was submitted by ExLibris to check the community support for the following enhancemnet:
Currently, users with "Purchasing Operator" role can delete items, the existing logic behind this is, when a PO line is created (even before it is received), there is a need for the Purchasing Operator to be able to delete the item in case of an error on the order.This Idea suggest to add a new privilege to the Purchasing Operator role which will prevent this user from being able to delete items - the new privilege should be enabled by default to maintain existing…
0 votes
- Don't see your idea?