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.
176 results found
-
Improve the management of license terms in config
Currently to manage the order and organization of license terms in Alma, we have to number each term we wish to use in order. If we want to add or reorder, we need to carefully renumber the existing terms so we don't accidentally use the same number twice and risk overwriting existing terms. While we've all learned work-arounds for this, given the amount of work it takes to maintain our hundreds of licenses, it seems risky to have this form of ordering. It would be much better to have the functionality that appears elsewhere in Alma that allows for lines…
56 votes -
Improve Alma's Licence „Controlled Vocabulary“ functionality
Background (as it works now):
Under „Manage License Terms“ a field can be defined as „Controlled Vocabulary“ and the defined CV values can be selected within a License. However, these CV values are only some kind of text module / boilerplate text which are copied into a specific license field. This means: when a CV value is changed or deleted, the content of this specific field in all licenses did not change. The change must be made in each license itself. A deleted CV value is displayed in the license field as: „<CV value> (not listed)“. The CV values functionality…
25 votes -
Add electronic collection details to the Alma publishing
Currently both physical and digital collections are published to Primo. Because of this these data elements can be added to the display sections of the Primo UI including the collections facets (courtesy of the Primo back office rules).
Similarly the collection name is published to Primo Central and therefore can be included in the collections facet and full display Details section.
Note: The publishing should also include details showing whether the resource is a Community Zone resource or not. (It may be desirable to only include non-Community Zone collections in the Primo displays as the PCI collections is already displayed).
…
21 votes -
Improve 'Synchronize from CZ' job reports
Sometimes, the information in the reports bears no resemblance to what’s in the CZ Updates Task List. For example, the 'portfolio linked to different bibliographic record' information isn't included in the CZ Updates Task List at all so you have to submit a SF case each time if you want to find out which portfolios were moved and which records are involved.
It would be useful to have clickable counters in the 'Synchronize jobs from CZ’ job reports that take you through to the corresponding changes in the CZ Updates Task List.
24 votes -
make "test access" work when direct linking is enabled
The "test access" button in Alma does not work when direct linking is enabled in Primo. When trying to test access for an electronic portfolio, Alma loads a blank page forcing staff to click "display in a new window" in order to proceed. We recommend that this behavior be changed so that test access works the same regardless of whether direct linking is enabled.
76 votes -
"Electronic material type originating from Bib" vs "Electronic material type" : a display issue in the Portfolio service editor's list
In an electronic portfolio, there is a field called "Electronic material type originating from Bib" which can be overloaded by another field called "Electronic material type".
The Job "Change electronic portfolio information" allows to update the material type of portfolios into the field "Electronic material type" into a set of portfolios.
If we do so, the material type is not updated into the Portfolio service editor's list... which is confusing.our request : when the material type of a portfolio has been updated in the field "Electronic material type", ALMA should only considare this material type and display it in…
18 votes -
E-Collections: Read-only access to Alma for other institutions
We wish to provide read-only access to our Alma instance to other institutions in our consortium and vice versa so that we can compare setup more efficiently. The permissions need to be quite restrictive and prohibit access to financial, patron data, etc. but allow us to view E-Collection, Service and Portfolio level screens.
When comparing set-up of our e-collections we are spending a lot of time discussing via email and sharing screen shots, which is not as efficient as being able to go in with a view privilege and compare in real-time.
79 votes -
43 votes
-
Implement auto holdings for IEEE
Implement auto holdings (autoholding, auto load, autoload) for IEEE, as is already available for ProQuest, Elsevier, Ovid, and Springer.
118 votes -
Display perpetual coverage dates where no other coverage provided
We now have the ability to log current access dates and perpetual access dates on a portfolio. However there is no way to display the perpetual access dates in Alma or Primo unless looking at the coverage tab of the portfolio.
It would be good if there was an option to use the perpetual coverage dates as our display dates either by having an additional option for the local, global, local and global section, or just displaying those dates if local only is selected and there is nothing in the local section.
We have titles that we had current and…
98 votes -
Using load portfolios in a collection to update POL link
We currently use the Load Portfolios tool in the Electronic service to update portfolio information. We have found this won't update the PO Line information in the Acquisition tab of the Portfolio. It is included in the data in an extended export of portfolio information, but does any changes/additions made to this field in the spreadsheet are not reflected in Alma when it is loaded.
We would like to be able to add/change this information using the Load portfolios tool.
A recent example of where this would be useful was a number of portfolios were incorrectly deleted from a collection.…
41 votes -
Portfolio Bulk Load file limit too small
The file limit of 10MB is too small. If we're using the Bulk Load, it means we're dealing with very large amounts of portfolios. Having to split those files is cumbersome.
12 votes -
Electronic Resource Activation Task List: do not revert to "Assigned to Me" tab after deleting a task
When you're working in the "Unassigned" tab of the Electronic Resource Activation Task List, it always reverts to the "Assigned to Me" tab after you delete a task. I want it to stay in the "Unassigned" tab.
21 votes -
Add Access type in the portfolio information update job
Since Ex Libris has added Access type for individual portfolio, there has to be a job to run to add access type to the portfolios in a collection. Currently, either we have to specify it in each portfolio manually, or we load a spreadsheet matching on portfolio ID. Unfortunately, as of today 1/23/2019, when loading a spreadsheet without the local coverage, e.g. only the access type, the local coverage is overwritten.
32 votes -
Job and/or API to unlink a set of bib records from the CZ
We would like the ability to run a job or use an API that would unlink a set of bib records from the CZ. There are currently both a job and an API that will unlink records from the NZ, but not the CZ.
Use case: ebook portfolio records provided from vendors can be extremely brief, missing many points of discovery (e.g., no subjects, tables of contents, etc.). When portfolio bibs are linked to the CZ, we are forced to update each of these portfolios one at a time, which is painstaking and inefficient. We already have scripts that use…
27 votes -
KBART export from Alma to include title level URL
As we from time to time need to interface with software and services outside the ExLibris suite, it would be great if the KBART Schema for export would include a proper title level URL as specified in the KBART Recommended Practice:
"[Title level URL] Indicate the URL of the title’s homepage.
For journals, this page should be a listing of the available volumes and issues. "39 votes -
Electronic Portfolios - can we have a new coverage line where free access can be added ?
At present in the coverage tab, there are the global dates, local, and perpetual (if the collection has been identified as having some perpetual access) Some of these titles have free access, which is not technically perpetual but is also not part of a subscription. Could a new line be added to include these free years/volumes, with the option to display these dates (or not) ? It would allow us to reduce the number of Free collections we have which all take users to the same place, and identify why we have access to journal years outside of our subscription…
11 votes -
Add " Additional e-mails " fields to " Report to ex libris " form in Alma
In Salesforce the customers can use "Additional e-mails" feature to let colleagues know that they have (already) opened a case for a specific issue. This makes teamwork easier.
For SF cases opened using the "Report to ex libris" feature, this is not possible. Plase add 5 "E-mail 1" - "E-mail 5" as in SalesForce.
16 votes -
Update import profiles, so portfolios are listed in ALMA & Primo in the same order as the 856 fields in the bibliographic record
Currently electronic portfolios are generated from the 856 fields in the bibliographic record, but they appear in reverse order in ALMA and Primo. Vendors often have 856 for multiple volumes in their records and they often list URLs in the order of their importance. In my attached example, the vendor includes a link to browse the particle resource first, then links to search the collections which contains the resource. The links are listed in order of importance. It is confusing to the user to list v.2 before v.1 and less important searching options before the most direct way of access…
57 votes -
In import profiles, ability to specify which 856 $u url is used to create electronic portfolios
Scenario: We manage some electronic collections in Worldshare Collection Manager. OCLC provides bibliographic records with the resource's url in the 856 $u. Sometimes the bib records will include multiple url's but we only want to select a specific one to create our portfolios in Alma.
For example, the Worldcat master record for OCLC 957128084 has 11 856 fields. (See attached screenshot.) Some are institution specific and others belong to different access providers. In such a situation, we want to be able to select the 856 $u url that begins with "http://www.jstor.org/stable" or "https://proquest.safaribooksonline.com".
In import profiles,…
16 votes
- Don't see your idea?