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.
3212 results found
-
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 -
Role for adding normalizations processes
Cataloging staff often need to create normalization or indication rules to edit groups of records. They can create these in the Medatdata Editor but they cannot use them on sets of records until they are added as a process/task in the resources metadata configuration area.
The ability to add processes is limited to the highest role of cataloger administrator which also allows configuration permissions.
Include the ability to add normalization and indication rule processes to the cataloger manager role to allow more flexibility to do global changes on Marc records.
Catalog managers need to add their own rules without giving…
6 votes -
Allow for Gift Acknowledgement Letters
The Legal Deposit method of acquisition allows for letters of acknowledgment to be sent to the vendor by automatic email from Alma after the item is received on Alma.
This functionality is lacking for the 'Gift' method of acquisition. As standard we like to send an acknowledgement to all of our donors and it would be ideal if Alma could automate this process as it does for Legal Deposit acknowledgements. The functionality to send an 'order' letter for a gift is there - but not for acknowledgement of receipt, which is actually the wrong way around for our requirements.
4 votes -
Resource Sharing Preferred Email Address
We have multiple libraries set up as Resource Sharing Libraries. However as we can only have one preferred email address the Borrowing Resource Sharing Requests are coming from the default email address for the library (usually the information email address), and not the dedicated email address for resource sharing at that library.
It would be really useful to have an email address type in a library record that is used to send Resource Sharing requests.3 votes -
Add ability to see name associated with user ID in MD Editor
User IDs are visible in MD Editor for "Created by" and "Modified by", but unlike other pages, there is no way to quickly see the name associated with that ID. Currently, one must leave the record and search the Users index for that number to get the person's name.
There should be a clickable icon like you see on the Monitor Jobs screen that shows you the name associated with the ID.
2 votes -
Add a confirmation warning when creating a Course without Instructors
When creating Courses for Reserves, Alma allows you to save a course without entering an instructor. This is a good thing -- it allows for "general reserves" cases.
However, because Instructors are entered on a separate tab from the main Course info, it's extremely easy for a user to neglect to add an instructor, leading to retrieval problems later.
Could an alert be raised when a staff member saves a Course record without selecting at least one instructor, confirming that the omission was intentional?
2 votes -
Conversion job for any part of the record to any other part
Hello,
It would be nice if there was a job of conversion of every part of a record (bib, hol, item, portfolio) into another part, for example:
Bib records into Items
Bib records into Holdings
Bib records into Portfolios
Bib records into Orders
Items into Bib records
Items into Holdings
Orders into Bib records
Orders into items
Orders into Portfolios
Portfolios into Bib records
Portfolios into Orders
This way, we will not be limited by the search for any job.
For example, we would be able to search Bib records, convert the set into items and run a job for…13 votes -
View closed fines- order by transaction date
When answering fines queries it would be useful to be able to arrange the 'closed' fines in the order in which they were resolved, in order to provide a chronological explanation.
2 votes -
Request option via List of Items screen
It is possible to place a Work Order on an item from the List of Items screen, but not a Request. Could this function be added?
3 votes -
Creating sub lines in a manual invoice
The ability to add servicing charges to an invoice manually as separate invoice lines that are linked to the regular lines.
13 votes -
Ability to set individual item records to not publish
Would like the ability to set individual item records to not be published.
Historically, we did not create item records for individual serial issues, but created a fake item record to get usage which migrated over to Alma. These item records display to the user in Primo.
Our options to fix this would be to give them all a process type, and set that process type to not publish but many of our staff find work orders confusing and we would not like to complicate it further. Alternatively, we could move each one to a suppressed holdings record, which would…
3 votes -
When adding invocie line, Secondary Reporting Code and Tertiary Reporting Code which is empty in POL will be set to a default value from the
For ‘add invoice line’ operation after typing the POL number the system will bring the POL’s information such as total price, reporting code, Secondary Reporting Code and Tertiary Reporting Code, which is good. But we want the information for Secondary Reporting Code and Tertiary Reporting Code to override the information from configuration > acquisitions > purchase order > Secondary Reporting Code/Tertiary Reporting Code. Even if the POL’s Secondary Reporting Code and Tertiary Reporting Code are empty, which currently will be set to a default value from the configuration.
1 vote -
Index Statistical category fields for use in reports
Our library uses customer Statistical Categories to track usage by external students. We need to be able to filter reports on statistical categories to certain time periods but the Creation Date field isn't currently indexed.
The Alma User Details > Statistics tab displays the following columns, see attached statistics screenshot 1: - Statistical Category - Category Type - Note - Created By - Creation Date - External Data You can also export an individual users statistics log with these fields. However in Alma analytics not all of these fields are available for reporting, see attached statistics screenshot 2. The missing…
1 vote -
Enable drag and drop of recent pages so we can use that as virtual bookmarks
If you can allow drag and drop of recent pages so we can use that as virtual bookmarks and not have to see rarely used pages that happen to be recently used.
1 vote -
More sophisticated functionality in the Duplicate Title Analysis function
The Duplicate Title Analysis functionality does not allow you to clear previous duplicates when you run a new job.
For example, you may run a job to find duplicate titles. You investigate those titles and decide that they are not problems for your library, so you wish to leave those titles in Alma, but you don't want them to come up on the next Duplicate Analysis title job.
3 votes -
Add all information to excel downloads with the option to filter if decided (e.g barcodes on Picklist)
Add all information to excel downloads with the option to filter if decided (e.g barcodes on Picklist).
3 votes -
Ajout de l'adresse de la Bibliothèque propriétaire de la demande annulée
Concernant la lettre d'Annulation d'une demande "FulCancelRequestLetter", au lieu d'avoir l'adresse de l'Institution, nous aimerions voir apparaître les coordonnées de la bibliothèque dont dépend le document demandé.
Cela permet à l'usager d'avoir la possibilité de contacter la bibliothèque en cas d'annulation de demande de celle-ci.
Bien cordialement1 vote -
Consolidate items onto one Overdue or Lost Loan Letter
Alma Overdue or Lost Loan Letters currently send an e-mail for EACH item lost or overdue. This bombards patrons' e-mail accounts and contributes to their disregard of correspondence from the library due to the high volume.
An improvement would be to consolidate items onto one Overdue or Lost Loan Letter to each patron. This would also lessen the amount of "Attachments" in each patron's record for staff to consult when interacting with patron questions or concerns.
5 votes -
How can we know which ISBN identifier be used to perform the "linking local portfolios to CZ" processing
We have 2 local portfolios https://onlinelibrary.wiley.com/doi/book/10.1002/9781118558133 (v.1) & https://onlinelibrary.wiley.com/doi/book/10.1002/9781118558126 (v.2) which those 2 portfolios are linked to MMSID 9940441503411. See attached spreadsheet.
As those 2 local portfolios with the 3 same set of ISBNs be involved (9781848211124, 9781848211117, 9781848211100), we have tried to link them to CZ by ISBN identifier. Only 1 local portfolios be linked to CZ successfully (see linking to community by ISBN identifiers_2.png). We have performed the linking process again and found that it is linked to the same CZ portfolio (bkey=10.1002/9781118558126). We are wondering which ISBN identifier be used for the linking processing if we have…6 votes -
Make Faceting in "Manage Purchase Requests" sticky
It would be very helpful if the faceting that can be done in Manage Purchase Requests can be made "sticky" for each user account; some who use that area/workflow are orderers, some managers, and some selectors. All may have different areas they only want to see (e.g. request type, location, or those with queries, etc.), and it would be nice if the faceting we do can be made sticky, so we don't see unwanted entries.
12 votes
- Don't see your idea?