1129 results found

1. Collection discovery - sub collection searches

   We welcome the enhanced searching on the top level of collection discovery however we have found we also need full searching over our nested sub collections. This is not only useful for users of PrimoVE but also for local data scopes as we require them to accurately include sub collections in search profiles.

   36 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  ·  Primo VE  ·  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. Support of CRediT - the Contributors Role Taxonomy within the article and local indexes

   120 journals are now fully supporting this NISO standard (NISO Z39.104-2022) for authorship and roles (https://www.niso.org/standards-committees/credit). We believe this emerging standard will allow additional search functionality for authors who have played different roles within the construction of the scholarly article. Over 50 publishers have adopted this taxonomy across their publications (Elsevier, etc.)

   2 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  ·  Other  ·  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

3. Improved Support of multilingual elements for external data sources in Primo VE

   For Dublin Core and Generic XML records that contain multilingual content, Primo VE should display the values of the associated fields according to the user's language when the language code is available as an attribute in the Dublin Core elements.

   For instance:
   <dc:subject xml:lang="fre">Phonotèque/dc:subject <dc:subject xml:lang="ita">Fonoteca/dc:subject

   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  ·  Primo VE  ·  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. Primo does not work with some date formats used for old material and rare books.

   Primo does not work with some date formats used for old material and rare books. The biggest problem is that Primo only recognises 4-digit dates and does not accommodate date searches for pre-1000 dates that have 3 digits or less. This issue greatly inhibits searches for a significant number of users of archives and rare material collections.

   Primo also does not work well with dates in square brackets that include text and unknown dates that have a question mark or dash instead of the wildcard character ‘u’ - e.g. [i.e. 1973], [between 1772 and 1802?], 195? or 195-. These are all valid date formats that follow international bibliographic standards and are frequently found in bibliographic records. It would be beneficial to our users if these issues could be addressed and fixed.

   Primo does not work with some date formats used for old material and rare books. The biggest problem is that Primo only recognises 4-digit dates and does not accommodate date searches for pre-1000 dates that have 3 digits or less. This issue greatly inhibits searches for a significant number of users of archives and rare material collections.

   Primo also does not work well with dates in square brackets that include text and unknown dates that have a question mark or dash instead of the wildcard character ‘u’ - e.g. [i.e. 1973], [between 1772 and 1802?], 195? or 195-. These are… more

   50 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  ·  User Functionality  ·  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. Calculated availability for non-full text records in digital imports from repositories

   In Primo VE, institution repositories are limited to one label. For example, a link to the full online resource or a link to the physical resource are both labelled as ‘Full Text Available’.

   This is a problem, as not all repositories are the full text, some repositories may just be an abstract.

   Primo's label options are better, it is clearer to the user by the various different labels, for example ‘Full text available’ or ‘No full text’.

   We would like Primo VE to have the various different labels, like Primo.

   Please vote for our NERS request.

   NERS Request ID: 7842

   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…)
   1 comment  ·  Primo VE  ·  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. Extend the limit on the Summary Holdings Display to more than 10 holdings.

   If a title is held at more than 10 locations, its holdings summary will not appear on the Locations page—however, the more locations, the higher demand for checking the range of the coverage. Therefore, please display all summary holdings regardless of the number of holdings.

   48 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  ·  Primo VE  ·  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. Increase security for option to delete a view in Primo VE

   Right now it is all too easy to delete a Primo VE view. If the option to delete a view is accidentally clicked on the drop down menu, a confirmation message appears with the "confirm" option highlighted. A confused user might click enter to get rid of the message without reading the message. This happened to us recently. A user who selects the delete option should have to type in the view code to confirm deletion. This extra step would help to prevent accidental deletion.

   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…)
   1 comment  ·  Primo VE  ·  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. Provide a link to a help page for Unpaywall links in Primo VE

   We are using the Unpaywall Quicklink to display open access links in our search results in Primo VE. The links themselves show that they are provided by the Unpaywall API, but we think that most users are not familiar with this service's name and functionality, so we would like to be able to provide more information to them. For example we would like to provide a link to a help page explaining what Unpaywall is and how it works.
   Using JS customization, we have tried to add a link to a under the Unpaywall link, but the scope in which the Unpaywall link is provided does not give enough context for us to display the help page only for Unpaywall links. For example, we cannot use "$ctrl.isUnpaywallLinksAvailable" because its value is always true when the integration is activated. The help page's link ends up being displayed for all View It links.
   We would like to request either that a "link to a help page about Unpaywall" function would be added to the integration, or that the Angular scope would provide enough context for us to add this link via customization.

   We are using the Unpaywall Quicklink to display open access links in our search results in Primo VE. The links themselves show that they are provided by the Unpaywall API, but we think that most users are not familiar with this service's name and functionality, so we would like to be able to provide more information to them. For example we would like to provide a link to a help page explaining what Unpaywall is and how it works.
   Using JS customization, we have tried to add a link to a under the Unpaywall link, but the scope in which… 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  ·  Primo VE  ·  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. The possibility to change the order of values in the top-level facet

   Several institutions of the eLABa consortium (https://www.elaba.lt/elaba-portal/en) would like to change the order of values in the top-level facet "Availability" (facet_tlevel) as they please. For example:
   1. Available in the Library
   2. Full Text Online
   3. Peer-reviewed Journals
   4. Open Access
   5. Cited Articles
   This idea is related to Case 06220252.

   9 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  ·  User Interface  ·  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. Allow patrons to order a specific item in a fulfillment network

    Hi

    We are in a consortium with a fulfillment network.

    Which in many cases means that the patrons can not pick which copy of a book they want to order.

    While this may make sense as the default (1), it is frustrating for many patrons, myself included.

    • When more than one copy is available, I want to be able to decide which one to get
      
    • When a book is on loan I may prefer to wait for the copy of my favorite library to come back instead of getting the book from somewhere else

    This is especially relevant when I'm in a setting where getting a copy from another library costs me money.

    ---

    The option 'choose specific item' should be available in the full title display (when logged in). If this is not possible, it could be an option in the patron settings.

    ---

    (1) Although it leads to an inconsistent display in Primo VE: sometimes the links for ordering are above the call number, sometimes next to it.

    Hi

    We are in a consortium with a fulfillment network.

    Which in many cases means that the patrons can not pick which copy of a book they want to order.

    While this may make sense as the default (1), it is frustrating for many patrons, myself included.

    • When more than one copy is available, I want to be able to decide which one to get
      
    • When a book is on loan I may prefer to wait for the copy of my favorite library to come back instead of getting the book from somewhere else

    This is especially relevant when I'm… more

    155 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  ·  User Functionality  ·  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. Filter collections (in Primo) to show 'online' or 'physical' items

    Currently, when you click into a collection on Primo, there are a few sorting options (relevance, date, title, author), but it would be useful to let users see only 'online' items or only 'physical' items (libraries with more than one site may want to let users see physical items at particular sites).

    2 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  ·  Primo VE  ·  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. TOU should be hidden when users Not logged in.

    In Primo VE, when a user is logged in, the TOU according to the user's category is displayed. However, when the user is not logged in, the TOU could be displayed as "Loanable" even if the book is loanable only to faculty members. When the user is not logged in, the TOU should be hidden.

    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  ·  Primo VE  ·  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. Ability to collapse elements in full title display per view and per search scope slot

    Please add the ability to collapse elements in full title display
    - per view
    - per search scope slot

    We are in a consortium, and some information in the full title display is confusing for our patrons and we have no way to hide it.

    We would like a setting to collapse each element of the full title display separately. This setting needs to be configurable per view and within the view per search scope slot.

    Example:

    We have the search scope slots
    - our IZ
    - NZ & CDI

    Section 'Other loan and request options' should be collapsed in "our IZ", but not in "NZ & CDI".

    Please add the ability to collapse elements in full title display
    - per view
    - per search scope slot

    We are in a consortium, and some information in the full title display is confusing for our patrons and we have no way to hide it.

    We would like a setting to collapse each element of the full title display separately. This setting needs to be configurable per view and within the view per search scope slot.

    Example:

    We have the search scope slots
    - our IZ
    - NZ & CDI

    Section 'Other loan and request options' should be collapsed in… more

    0 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  ·  User Interface  ·  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. It would be helpful if Ex Libris can automate fetching our metadata for new ADFS signing certificate to update our Primo VE SAML profile, th
    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  ·  Primo VE  ·  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. It would be helpful if Ex Libris can automate fetching our metadata for new ADFS signing certificate to update our Primo VE SAML profile, th
    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  ·  Primo VE  ·  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. Add support for the following HTML tags : <ul>, <li>, <sub>, <sub>.

    So that they can be embedded into records to improve the frontend display.

    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  ·  User Interface  ·  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

17. blockchain

    Please consider adding blockchain technology to Primo for tracking the provenance/use/download of research content.

    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  ·  Integration with other systems  ·  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

18. Allow the available figure for Physical items to be configured

    The available figure in Primo for Physical items includes all items which are not on loan. We want to be able to exclude items with certain item policies or item locations from this figure.
    These items will still be displayed within Primo but will not be included in the available count.

    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  ·  Primo VE  ·  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

19. Add target_url to DisplayCTO output

    There is a feature in Primo VE to debug OpenURLs. You add to the OpenURL the parameter &displayCTO=true, e.g. https://uzb.swisscovery.slsp.ch/discovery/openurl?institution=41SLSP_UZB&vid=41SLSP_UZB:UZB&id=pmid:24881163&sid=Entrez:PubMed&displayCTO=true

    Now you find between the metadata and the inventory a button "DISPLAY CTO". If you click there, you get an XML file with the metadata details that are available to Primo VE at the moment as well as data for the online services Primo VE will offer the user. However, one important information is missing: The target URL the service will link to is not displayed.

    If you, however, use the debug URL of the Alma Link Resolver: https://slsp-uzb.alma.exlibrisgroup.com/view/uresolver/41SLSP_UZB/openurl?svc_dat=CTO&debug=true&debug=true&id=pmid:24881163&sid=Entrez:PubMed

    You get in every service record a field <target_url>. There you find the exact URL that will be called, when the service is chosen.

    This is crucial and should be added to the displayCTO feature in Primo VE.

    There is a feature in Primo VE to debug OpenURLs. You add to the OpenURL the parameter &displayCTO=true, e.g. https://uzb.swisscovery.slsp.ch/discovery/openurl?institution=41SLSP_UZB&vid=41SLSP_UZB:UZB&id=pmid:24881163&sid=Entrez:PubMed&displayCTO=true

    Now you find between the metadata and the inventory a button "DISPLAY CTO". If you click there, you get an XML file with the metadata details that are available to Primo VE at the moment as well as data for the online services Primo VE will offer the user. However, one important information is missing: The target URL the service will link to is not displayed.

    If you, however, use the debug URL of the Alma Link Resolver: https://slsp-uzb.alma.exlibrisgroup.com/view/uresolver/41SLSP_UZB/openurl?svc_dat=CTO&debug=true&debug=true&id=pmid:24881163&sid=Entrez:PubMed

    You… more

    88 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  ·  Primo VE  ·  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. Publish synonym list for hosted non-VE customers in Primo documentation

    It was announced in the Primo mailing lists during August 2021 that the list of synonyms for Primo VE had now been added to the documentation page.

    The equivalent documentation for non-VE Primo customers such as us is at:

    https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Primo/Technical_Guide/120Linguistic_Features/040Synonyms#ww1052488

    As hosted customers, however, we still can't see the contents of the synonym files as described, as we don't have that sort of server level access. Therefore we are unable to determine:

    (i) whether the non-VE synonym list bears direct comparison to the VE list,

    (ii) if it does not, where the differences lie.

    Significant staff time is taken up raising synonym-related cases that turn out to be fools' errands and could be made more focussed, or even not need raising at all, were the non-VE list made visible.

    The absolute ideal would be for the ranking power - from Very High to Very Low - for each synonym to be published as well.

    It was announced in the Primo mailing lists during August 2021 that the list of synonyms for Primo VE had now been added to the documentation page.

    The equivalent documentation for non-VE Primo customers such as us is at:

    https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Primo/Technical_Guide/120Linguistic_Features/040Synonyms#ww1052488

    As hosted customers, however, we still can't see the contents of the synonym files as described, as we don't have that sort of server level access. Therefore we are unable to determine:

    (i) whether the non-VE synonym list bears direct comparison to the VE list,

    (ii) if it does not, where the differences lie.

    Significant staff time is taken up… 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  ·  Other  ·  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