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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Make Alma link resolver compatible with EndNote's "Find Full Text" feature

    EndNote offers a "Find Full Text" feature that allows users to locate full text for citations saved to their library. The feature can be configured to work with your institution's link resolver. However, according to EndNote customer support, the Alma link resolver is not currently compatible with this feature. This enhancement would allow Alma customers to locate full text for EndNote citations via openURL.

    192 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Improve Alma Link Resolver’s performance with Pubmed IDs (PMIDs)

    Improve Alma Link Resolver’s performance with Pubmed IDs (PMIDs) such that it is as good or better than Serials Solutions’ 360 Link performance with Pubmed IDs. Areas where this is currently a problem include translation of OpenURL data from Pubmed over to Illiad through Alma Linker and Primo, item level linking between Pubmed, Alma Linker and Cochrane Library, and probably many other areas.

    112 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Improve Display Logic in Alma Uresolver to show all variant coverage statements in a collapsed menu

    Ideally, Alma should be able to display ALL unique variant coverage statements when showing a collapsed menu.

    If a library uses the Display Logic rules to for example show Proquest as an option only once in a services menu, this works very well where a journal may be in 12 Proquest databases with the same coverage.

    However, when the coverage varies significantly between these databases, Alma uresolver will still just show one of the coverage statements and a user will only see a subset of holdings and believe this is all the library has. (eg Nursing standard in Proquest is…

    85 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. portfolio link checker

    Develop a built-in link checker that generates a regular report of all active portfolios in Alma with broken links. Display broken links on a task list for staff to investigate and update.

    79 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. Failsafe links to databases if/when Direct Linking fails

    When we were a Serials Solutions customer and we used Summon discovery, we also used Direct Linking. What was great about Summon was that it would provide a pane at the top of the screen after linking to full-text content that would provide a way to see all the database targets on the 360 Link page. See attached image.

    This same feature would be highly desirable in Primo and is one of the main reasons why we do not currently use Direct Linking. Currently, if the full-text fails to load for the default target, there is no way to see…

    64 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. Make Alma resolver better at locating books and book chapters without ISBN

    Alma resolver incorrectly matches to other books with the same title if the open URL does not contain an ISBN.

    Alma is not fit for purpose as an open url resolver for Books when an ISBN is not available.

    Other resolvers such as SFX and 360 link use all the information in the openurl eg author and publisher and date. Alma resolver only uses the Book title which causes numerous false matches.

    See example in attached file

    43 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. NZ EBSCO Link Resolver Plug-in

    Currently in the NZ, if you use the EBSCO Link Resolver Plug-in, it is applied all of the libraries using the NZ. We are not able to activate the plug-in for specific libraries in the NZ. Not all of the libraries want to use the link resolver plug-in. Also, along with being able to activate the plug-in for specific libraries, the plug-in will also need to be set up for the specific customer ID. Currently, when we have the link resolver plug-in activated in the NZ, all libraries are being filtered by all of the available EBSCO resources paid for…

    37 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Link to next higher level when Alma can't match to article or chapter

    When Alma cannot successfully link to an article because of no exact match is found, it would be helpful for Alma to use alternative metadata, such as the page number, to target. It would also be useful to users to be taken to the next higher level of the publication, e.g., the journal issue page. If there is uncertainty about the issue, then users should be taken to the journal page.
    This problem frequently arises for short pieces and book reviews. For example, some journals publish book reviews in a section entitled, "Book Reviews", rather than as separate articles. In…

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Use NZ records for full text links in Primo search results

    There is an issue with full text links not appearing in the Primo record when the incorrect ISSN is in the 022$y field. If the incorrect ISSN is in an IZ record, the search stops there and there is no full text link in Primo when in actuality there is full text available from the NZ. Can the NZ records be used in this case, not just end at the "bad" IZ record?
    My end goal would be that when looking for full text, the search doesn’t end with an IZ record that may or may not have the correct…

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. OADOI/Unpaywall link doesn't display where needed

    I originally posted the idea https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/16880380-add-oadoi-org-as-an-option-in-uresolver which was implemented in the Alma November release.

    It looks like it's implemented the feature exactly as I suggested – unfortunately the method I suggested turns out to be exactly wrong for the use case as I (admitted briefly) described it! :-{

    Our use case, more specifically, is that when we don’t have full text for an item but an OA version is available through Unpaywall, we want that Unpaywall option to appear very visibly for users. (Being a bit fuzzy on the relationship between uResolver, GetIt, ViewIt, and when these all appear) I…

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thank you for your feedback.
    Today Primo does present viewit services for resources that do not have full text indications.
    We will check with Primo if this can be changed as the Unpaywall service can appear also when there is no full text service.

    Note that this issue is not relevant to PrimoVE

  11. Show Service temporarily unavailable message even if Direct linking is enabled

    The Service temporarily unavailable message is only visible if direct linking is not enabled.

    It would be useful if activating the message, would automatically disable Direct linking for that particular service

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Improve OpenURL generation to remove blanks and duplicates

    Openurls generated could by Alma/Primo be shorted by:


    1. Not sending duplicate parameters.

    2. Not sending empty parameters.

    Background:

    We have noticed that OpenURLs produced by Alma/Primo (which are then sent on to our ILLiad server, which can require redirection to get the patron authenticated) can be VERY long. So long in fact, that they can produce errors for our ILLiad web server. The ILLiad server will end up reporting "Request header is too large", and the user is left with a HTTP Status 400 Bad request error.

    We believe the responsibility here is on the Alma/PRimo side as the urls generated…

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Merge electronic services from the same vendor/interface in the viewit

    When there are multiple services in the viewit from the same vendor/interface, Alma should merge them instead of showing of the same vendor name multiple times which just confuses patrons.
    In the end the link goes to the same place - just coming from different packages from the same vendor we got

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Customize / brand resolver window

    We have Direct Linking turned on for articles, but there are always some cases where the article can't be found and the link takes the user to the resolver window. Our users are mystified by this window because there is no Tufts branding and they aren't at all sure where they have landed or what they are supposed to do there. Our previous resolver allowed us to fully customize this window. I asked Support about it and they said it isn't customizable. We need to be able to brand it.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Link resolver should use ISSN and title from external resource

    When the link resolver receives a URL from an external resource, it should use the ISSN and the journal title from the incoming URL to create links for Interlibrary loans and ignore any related links if related links are activated (Fulfillment > Fulfillment Configuration > Configuration Menu > Discovery Interface Display Logic > Related Records). Currently, the link resolver will change the incoming ISSN and journal title to that of the related link when creating ILL requests, which makes the ILL article information incorrect.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Use all of the author fields when creating a display record from an Alma resolver call.

    Right now, if you pass an openurl call to the resolver with fields of rft.au fields and rft.aufirst or rft.aulast the record created does not include the main author represented in the rft.aufirst and the rft.aulast.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Show item title in browser tab name (title) for uresolver landing page

    At present if users follow a link from one of our website or our VLE to an item with more than one content provider or a Public Note it takes them to an Alma landing page for the uresolver, which opens in a new window or tab.
    The <title> of the Alma uresolver tab or window shows as 'Home'. If the user has several tabs open the word 'Home' is not likely to help them identify the one that contains the links to the item they were trying to access. It would be much more helpful if the browser tab…

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Use a link shortener for the permalink on Alma Services pages

    Alma Services pages offer permalinks, but these links can be very long. Primo and Summon permalinks are shortened.

    Primo example: https://primo.csu.edu.au/permalink/61CSU_INST/1hkg98a/alma990009296670402357

    Summon example: http://tinyurl.com/ybkajbbe

    Alma Services pages should offer short permalinks using TinyURL or possibly a simple link using a unique identifier like Portfolio ID or MMS ID.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Link Resolver  ·  Admin →
  20. Resolvable URL that links to the ALMA record

    From doing a search outside of ALMA, I have an MMS_id for a record I want to look at. (E.g. 9913920213502836 )

    I want to be able to share this record page with a colleague, or store a pointer to the record in a document or spreadsheet.

    The most useful approach would be to use a URL, where I could display the MMSid as the text, while pointing to the record as the URL ( e.g. www.myalmadomain/mng/action/showrecord.do?mms_id=9913920213502836 )

    Because of how the page is built, there doesn’t appear to be a single url I can use…

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base