Skip to content

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

20 results found

  1. 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.

    134 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Display logic rules should work on Primo users NOT logged in

    Display logic rules currently only work if a user logs in Primo. Also, the rules only work to hide a service (not show a service). Also, Primo New UI does not allow forcing users to log in.

    So, we have a scenario where we want CCC Get It Now articles to display only for our Faculty user group. However, the article links are displaying to everyone (guest) - until the user logs in and then the links are hidden for everyone except our faculty. Because everyone starts out in Primo as guest, this defeats the purpose of the rule.

    Another…

    64 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Enable journal coverage date ranges to be shown whilst still allowing direct linking.

    Our students want Direct Linking enabled, because they expect to go straight to the full text of an item when they click on the search result. Our academics want to be able to see the range of dates for which we have access the journal title they've searched for, like they could when we were using SFX as our Journal search.

    We have Direct linking enabled which means that journals we get from a single supplier go straight through to the journal without showing the coverage date range, causing numerous complaints from academics. We tried the solution suggested by the…

    59 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Accepted  ·  10 comments  ·  Link Resolver  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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

    54 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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…

    44 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Set Linking Parser Parameters at the Interface level

    It would be more efficient to set the Linking Parser Parameters at the interface level, with an option to override the parameter at the Service Link level.

    For example, I want to set our university's ProQuest clientid at the ProQuest interface level rather than have to open each of our 20+ ProQuest collections to edit the Service Link Parameters.

    35 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  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…

    33 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Enable the customization of the label of Unpaywall API link.

    The unpaywall link displays with the label of "Unpaywall" in the ViewIt window of Primo. This may not be an intuitive description for some users.

    We would like the option to change the service label as we do for other services in Alma.

    26 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  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…

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. For general electronic services links at the item level, allow the item id to be used in the URL

    When a General Electronic Service is added as an item-level service, the URL template may be configured to make use of the a bunch of Holdings and item-level information, for exampe, the barcode. But the item id is not included as a possibility. Please add this as an option.

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Provide complete Factiva full text service

    The Factiva full text service is incomplete. When searching with Primo, a complete set of results from Factiva is not retrieved. it is explained that the Factiva collection does not provide full coverage from the provider, but the alternative coverage mechanism also does not work. This was not an issue when we used Summon. It will be good for users to get a complete set of results from Factiva.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Please, let us use the full power of rft_dat / pid again!

    rftdat (OpenURL 1.0) and pid (OpenURL 0.1), respectively, is one of if not the most powerful OpenURL field(s) and SFX allowed the customer to make full use of this power. It's such a shame for the Alma link resolver not even being able to parse a local identifier from rftdat / pid in cases when these parameters contain anything else than just the identifier (like in rftdat=<GVI>BV012345678</GVI>). So please allow regular expressions to define a pattern for a substring to extract from the value passed in rftdat / pid.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Allow multiple levels of nesting for functions in Dynamic URLs

    I am requesting the ability to nest the same or different functions multiple times (at least five, but preferably many more).

    Use Case: Sometimes it is necessary to replace multiple strings in a dynamic URL.

    For example, I need to replace three different characters for Nexis Uni:
    1) Replace + with a space
    2) Replace & with an empty string (effectively removing &s)
    3) Replace : with an empty string (effectively removing :s)

    This is what the dynamic URL would look like:
    IF(rft.atitle)
    https://advance.lexis.com/search?pdsearchterms=TITLE%28%22REPLACE(REPLACE(REPLACE({rft.atitle},%3A,""),%26,""),+,"%20")%22%29&pdtypeofsearch=urlapi&pdstartin=snapshot&pdsearchtype=bool&pdmfid=1516831&pdisurlapi=true
    IF(rft.stitle)
    https://advance.lexis.com/search?pdsearchterms=PUBLICATION%28%22REPLACE(REPLACE(REPLACE({rft.atitle},%3A,""),%26,""),+,"%20")%22%29&pdtypeofsearch=urlapi&pdstartin=snapshot&pdsearchtype=bool&pdmfid=1516831&pdisurlapi=true
    IF()
    https://www.nexisuni.com

    Currently, if that dynamic URL is entered in Alma, Alma returns an…

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. "Plugin Thresholds" for General E-Services

    For SFX a "plugin threshold" is known as an almost arbitrary complex condition (evaluated by any sort of locally developed script code returning 1=true or 0=false) on the contextual relevancy of a certain service. The Alma link resolver should not stand behind and be able to employ any third party web service for the evaluation of conditions too complex to be stated by means of its out-of-the-box types of thresholds.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Openurl resolver to search CDI when no full text services found in Alma

    Sometimes the Alma openurl resolver can't locate an item, but you can find it in the CDI, so could the openurl resolver search the CDI by title + authors for possible matches? Perhaps present any results as suggestions, a bit like bX recommendations, so as not to raise expectations that the correct document has been found.

    Here's an example. JSTOR has a record for a paper that was published in print in SAE Transactions, ISSN 0096-736X, 2001, Vol.110, p.86-92
    https://www.jstor.org/stable/44724287

    But the paper is published online as SAE Technical Paper 2001-01-0233, ISSN 0148-7191
    https://www.sae.org/publications/technical-papers/content/2001-01-0233/

    It is available in SAE Mobilus…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Link Resolver  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Link Resolver  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Check coverage dates on physical holdings by link resolver

    When there is no full-text match for an electronic title, the link resolver can bring back a bib record for physical holdings. However, since the coverage in the 866 field is not being checked, this shows records which do not match the dates desired sent by the the open URL.

    Please consider implementing a check on the coverage dates of physical holdings to make things less confusing for patrons.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Display logic rules: always allow use of "OPEN_ACCESS" criteria

    Currently, if Alma's enableopenaccessservicesfromunpaywallapi Fulfillment setting = true, then in Display Logic Rules we gain the ability to write rule criteria that considers the presence of open access service links. If the fulfillment setting = false, that DLR option disappears.
    We assume this connection was made at a time when the Unpaywall API setting was the only way that OA services might get into Primo, so there was no need for OA services to be a criteria in DLRs when the Unpaywall API was turned off.
    However, we've found that the new Unpaywall CZ…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. More linking parameters for links in CDI records

    I meant to submit this as an enhancement request but missed the deadline. We need the ability to do more than say Proxy Yes/No to links in CDI records. If you are an OpenAthens library, some vendors use the Proxy and others don't and Proquest in particular doesn't. In OpenAthens Proquest URLs get no redirector and instead have a ?accountid=*** with the customer ID. We need to be able to customize CDI links depending on vendor and to put a customer ID to build the correct URL, at least for Proquest CDI URLs. Also, it seems like if there is…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base