37 results found

1. 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 a good example in some it is 1998-2013 and others is 2015 +, )

   The most obvious case is when using the A-Z list or a general Primo search to find a journal title.

   In SFX it is possible to add a year or source parameter to the display logic rule so that the collapse display logic only applies when the user specifies a date or when the open url does not come from the A-Z list. This means that a user wanting to use Primo or the A-Z to see ALL date holdings of a given serial title could see all possible links with their coverage statements, not just one statement per provider.

   It would be better if the collapsed menu could be preserved and all the unique holding statements were shown, however, the SFX logic of conditionally showing all links is preferable to the current Alma behaviour.

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

   143 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…)
   5 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. 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.

   131 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…)
   4 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

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

4. 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 the other full-text options that would have appeared if Direct Linking were not enabled.

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

   •  

   61 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…)
   5 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  ·  AdminItai Veltzman (Product Manager, Ex Libris) responded

   Currently we have some technological barriers we are looking how to overcome. We will update on the solution

5. 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 scenario is that a college that we are in a consortium with wants to hide EBSCO links if Gale links exist. They can create a display logic rule to do this, but the rule will not work for guest, only for logged in users.

   Another fix for this issue would be to allow a display logic rule that will basically only SHOW a service if it is a certain user group. This would allow us to show the CCC Get It Now interface if the user group is faculty. However the display logic rules do not allow this type of logic.

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

   58 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…)
   4 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

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

   • 

   49 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

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

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

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

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

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

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

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

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

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

16. Allow rft.source as input for GES availability rules

    Right now, when constructing the service availability rules for a GES, the dropdown menu for the input parameters includes rft.SOURCE and rfe.SOURCE. However, when I attempted to use this, it didn't behave as expected. I did further testing and found this is not currently functional: I set rules to show a link when the rft.SOURCE is empty, and it always showed up. The same happened with rfe.SOURCE.

    This would be helpful, as it would allow us to configure links to only show up for PCI records, or only for Alma records. Especially in environments where you'd like to route users only to resource sharing or only to ILL as appropriate, this would be very useful.

    Right now, when constructing the service availability rules for a GES, the dropdown menu for the input parameters includes rft.SOURCE and rfe.SOURCE. However, when I attempted to use this, it didn't behave as expected. I did further testing and found this is not currently functional: I set rules to show a link when the rft.SOURCE is empty, and it always showed up. The same happened with rfe.SOURCE.

    This would be helpful, as it would allow us to configure links to only show up for PCI records, or only for Alma records. Especially in environments where you'd like to route users… more

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

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

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

20. Allow same URL functions/rules possible for Dynamic URL in General Electronic Service URL Template

    When constructing Dynamic URLs for electronic portfolios, Alma can parse URL functions such as SUBSTR, REPLACE, and URLENCODE to create working links.

    General Electronic Services often require or would be improved by use of these URL functions for the same reasons as the Dynamic URLs, when the OpenURL attributes alone are not enough to create the best possible link.

    It would seem that Alma already has the potential to parse these functions since they are used in Dynamic URLs, so allowing them in GES URLs should be possible.

    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