37 results found

1. Make all PNX elements referable in Template URLs (of General E-Services) and Dynamic URLs

   In the Template URL of a General E-Service and in the Dynamic URL of a given collection of e-resources you can currently refer to any piece of metadata that Alma has included in the Context Object ("CTO"). The attributes of the Context Object are based on the OpenURL 1.0 standard but while this standard provides slots to convey any kind of locally scoped metadata (e.g. local identifiers) as well as globally scoped metadata (e.g. ISBN, ISSN, OCN, DOI) and descriptive metadata (e.g. author name, book title, journal title, article title) there is currently no way to let Alma include locally scoped metadata into the CTO.

   Unfortunately, this prevents you from using local identifiers in Template / Dynamic URLs in order to link to specific local services, for example. For former SFX customers, in particular, this is a very serious and painful feature loss.

   Extending the OpenURL standard to locally scoped metadata has made it very flexible and successful. Hence, extending the Alma CTO in a way that makes any PNX element referable will definitely boost the potential of General E-Services.

   In the Template URL of a General E-Service and in the Dynamic URL of a given collection of e-resources you can currently refer to any piece of metadata that Alma has included in the Context Object ("CTO"). The attributes of the Context Object are based on the OpenURL 1.0 standard but while this standard provides slots to convey any kind of locally scoped metadata (e.g. local identifiers) as well as globally scoped metadata (e.g. ISBN, ISSN, OCN, DOI) and descriptive metadata (e.g. author name, book title, journal title, article title) there is currently no way to let Alma include locally… more

   113 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Link Resolver  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. 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 a "link in record" it won't show any full text links for the same item in activated collections, which have the better URL if you are an OpenAthens library for the above reason.

   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… more

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Link Resolver  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Allow the general electronic services to create a service based on 856 from the bib record
   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Link Resolver  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. 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 Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Link Resolver  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. 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 and there is a CDI record with a link in record, TNcdisaetechnicalpapers2001010233

   So the Alma link resolver has no hope of finding that from the openurl from JSTOR, but if it could search the CDI by title and authors, that would lead to the full text.

   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… more

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Link Resolver  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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.

   37 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Link Resolver  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Two or more EBSCO plugins for Alma

   As we have two organizations that Alma is serving and therefore two EBSCO subscriptions it would be usefult to configure two EBSCO Integration Profiles as well. Now we have to choose which organization's EBSCO is configured to Alma and the other is not.

   We have two different API User ID's (in form custid.groupid.profileid) but now the other is ignored.

   15 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Link Resolver  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

   10 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Link Resolver  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

   •  

   25 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Link Resolver  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. 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 could be shorted by:

    1. Not sending duplicate parameters.
    2. Not sending empty parameters.

    Note: For our (UW-Madison's) locally developed discovery interface, we generate our own OpenURL links for things like "Request a copy" from article searching and the catalog records, so we can ensure proper length limits.

    ExLibris generates OpenURL links in their UResolver (Find it) and Primo Search API

    Alma/Primo OpenURLs

    For example, following a "Find it at UW-Madison" link from Google Scholar and then doing "Request a copy" (sending the OpenURL on to our ILLiad server):

    Starting in Google Sholar, and ending up here:
    https://uwi-primoalma-prod.hosted.exlibrisgroup.com/primo-explore/openurl?sid=google&auinit=PM&aulast=Vitousek&atitle=Beyond%20global%20warming:%20ecology%20and%20global%20change&id=doi:10.2307%2F1941591&title=Ecology.&volume=75&issue=7&date=1994&spage=1861&issn=0012-9658&vid=WISC&institution=WISC&url_ctx_val=&url_ctx_fmt=null&isSerivcesPage=true

    Provides an OpenURL link (request a copy) of:

    https://madison.hosts.atlas-sys.com/illiad/OpenURL?Action=10&Form=30&rft.genre=article&rft.title=Ecology.&rft.stitle=Ecology.&rft.atitle=Beyond+global+warming%3A+ecology+and+global+change&rft.jtitle=Ecology.&rft.au=&rft.date=1994&rft.month=&rft.volume=75&rft.issue=7&rft.number=&rft.spage=1861&rft.epage=&rft.edition=&rft.issn=0012-9658&rft.eissn=1939-9170&rft.aulast=Vitousek&rft.aufirst=&rft.auinit=PM&rft.pub=Brooklyn+Botanical+Garden&rft.pubdate=1920-&rft.pubyear=&rft.publisher=Brooklyn+Botanical+Garden&rft.place=Brooklyn%2C+NY+%3A&rft.doi=10.2307%2F1941591&rfe_dat=35698209&rfr_id=google

    Where the following parameters are included, yet blank:

    au, month, number, epage, edition, aufirst, pubyear

    Primo Search API

    In order to display electronic availability for articles we have to query the OpenURL resolver in alma to get data back. The string we use to query the resolver is provided to us by the Primo Search API

    Primo API Docs - Ex Libris Developer Network

    This one is by far the biggest offender, as that API returns the "GetIt1" URL we need to use. An example URL returned to us looks like:

    https://na02.alma.exlibrisgroup.com/view/uresolver/01UWI_MAD/openurl?svc_dat=CTO&ctx_enc=info:ofi/enc:UTF-8&ctx_id=10_1&ctx_tim=2020-02-07T10%3A04%3A19IST&ctx_ver=Z39.88-2004&url_ctx_fmt=info:ofifmt:kev:mtx:ctx&url_ver=Z39.88-2004&rfr_id=info:sidprimo.exlibrisgroup.com-proquest&req_id=&rft_val_fmt=info:ofifmt:kev:mtx:journal&rft.genre=article&rft.atitle=Telltale%20warming%20likely%20to%20hit%20poorer%20countries%20first&rft.jtitle=Nature&rft.btitle=&rft.aulast=Schiermeier&rft.auinit=&rft.auinit1=&rft.auinitm=&rft.ausuffix=&rft.au=Schiermeier,%20Quirin&rft.aucorp=&rft.date=2018-04-26&rft.volume=556&rft.issue=7702&rft.part=&rft.quarter=&rft.ssn=&rft.spage=415&rft.epage=416&rft.pages=415-416&rft.artnum=&rft.issn=00280836&rft.eissn=14764687&rft.isbn=&rft.sici=&rft.coden=&rft_id=info:doi/10.1038d41586-018-04854-2&rft.object_id=&rft.eisbn=&rft.edition=&rft.pub=Nature%20Publishing%20Group&rft.place=London&rft.series=&rft.stitle=&rft.bici=&rft_id=info:bibcode&rft_id=info:hdl&rft_id=info:lccn&rft_id=info:oclcnum&rft_id=info:pmid&rft_id=info:eric((addataeric}}&rft_dat=%3Cproquest%3E2056433252%3Cproquest%3E%3Curl%3Ehttp:search.proquest.com/docview/2056433252/%3C/url%3E,language=eng,view=MD&svc_dat=viewit&req.skin=MADskin&rft_pqid=2056433252&rft_galeid=572639507&rft_cupid=&rft_eruid=&rft_nurid=&rft_ingid=

    Previously we ran this URL through a parser to validate it and then remove empty parameters. There are three issues with this data - 1) sometimes keys are duplicated, which goes against best practices 2) Data is not properly url encoded 3) There are a lot of empty parameters.

    Removing those parameters for this example request would drop the length of the URL from 1328 to 1052 characters

    Note: We no longer parse this data as it was dropping the duplicated parameters causing lookup issues, so it's passed through to our OpenURL resolver as we receive it from the API (aside from prepending a parameter to return XML instead of HTML)

    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… more

    15 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Link Resolver  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. 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 suggested doing it through uResolver. But that puts it into ViewIt, and ViewIt only appears when we do have full-text.

    So eg https://library-lincoln-sb.hosted.exlibrisgroup.com/primo-explore/fulldisplay?docid=TN_cambridgeS0007485399000437&context=PC&vid=LU&lang=en_US&search_scope=All_resources&adaptor=primo_central_multiple_fe&tab=default_tab&query=any,contains,Mitochondrial%20COI%20and%20II%20provide%20useful%20markers%20for%20Wiseana&offset=0 we have the full-text so don’t need an OA version, but the Unpaywall link appears.

    Whereas https://library-lincoln-sb.hosted.exlibrisgroup.com/primo-explore/fulldisplay?docid=TN_medline22342531&context=PC&vid=LU&lang=en_US&search_scope=All_resources&adaptor=primo_central_multiple_fe&tab=default_tab&query=any,contains,drosophila%20genetics&offset=0&pcAvailability=true we don’t subscribe to the full-text, so we want to provide OA. But precisely because we don’t subscribe to the full-text, no ViewIt tab appears, so we don’t get the Unpaywall option!

    I think there’d be a number of different ways to tweak the functionality that has been created to make it work for our usecase. I would really like the opportunity to have some dialogue with how it gets developed from here so we can make sure it works the best way possible.

    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… more

    11 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Link Resolver  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    Under Review  ·  Dana Moshkovits responded

    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

12. 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 centrally. Our libraries have specific subscriptions to the EBSCO resources so we need to the ability to use a customer ID so that EBSCO knows the correct resources to apply the plug-in.
    1)Be able to set up specific libraries for the link resolver plug-in in the NZ.
    2) Be able to let limit the plug-in to the specific EBSCO resources for that library.
    
    More details can be found in case: 00570478

    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… more

    34 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Link Resolver  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. resolver proxy

    Provide the ability to use Azure AD as a resolver proxy

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Link Resolver  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. 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 ISSN, but that the NZ records are also looked at so a full text link will appear in the Primo record.

    Case# 00673680

    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… more

    24 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Link Resolver  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. 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 such cases, Alma's link resolver returns an error and no useful information for the user.

    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… more

    42 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Link Resolver  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

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

    8 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Link Resolver  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. 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 Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Link Resolver  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. 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 Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Link Resolver  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. 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 to resolve the record page - I can only see the ‘parent’ URL: https://nlnz-a.alma.exlibrisgroup.com/mng/action/home.do?mode=ajax#

    Alma ticket case #00668253 refers - closed as enhancement request:

    "Unfortunately, differently from Primo, Alma does not provide like a permanent link or direct link to a record. Users need to authenticate to Alma, then search MMS ID and etc."

    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… more

    5 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Link Resolver  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Link Resolver API Plugins

    While this would be helpful across the board, specifically with ProQuest's ownership of ExLibris it seems a logical step to add a link resolver API to increase the efficacy of the services page.

    Specifically request a Proquest Link Resolver API Plugin that would allow Alma to do a pre-check to ProQuest to see if full text is available. If the pre-check API query returns 0 matches, then the Full Text Service would be suppressed and the user would see 'No Full Text' on the Services Page. This would address certain linking issues where the services page recognizes full text is available but is unable to resolve the linking b/c of content provider metadata mismatch.

    While this would be helpful across the board, specifically with ProQuest's ownership of ExLibris it seems a logical step to add a link resolver API to increase the efficacy of the services page.

    Specifically request a Proquest Link Resolver API Plugin that would allow Alma to do a pre-check to ProQuest to see if full text is available. If the pre-check API query returns 0 matches, then the Full Text Service would be suppressed and the user would see 'No Full Text' on the Services Page. This would address certain linking issues where the services page recognizes full text is… more

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Link Resolver  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close