1129 results found

1. Add ability to control local record access information in Primo

   Primo managed via Back Office has powerful functionality to control access information in Primo for all our local records.
   This includes the aligned features of availability statements and Get It / View It by Delivery & Scoping rules, Links rules for all harvested data sources, and the option to build custom mapping tables for references in various rules, all of which can be married with top level facets by Facet rules.

   These features provide necessary information in Primo as expected for a core discovery layer functionality of advising users how they can access and request our resources, and avoids wasting staff time by answering many queries and causing patron frustration, by setting clear expectations directly in Primo UI.

   This rich Primo Back Office environment lies in sharp contrast to Primo VE, where features such as availability statements and top level facets are hardcoded. This includes for discovery records in institutional repositories and archival management systems all marked as full text available, even when this actually isn’t true.

   It is unacceptable that our Primo environment would give false information, particularly with some of these Library resources being highly sensitive and restricted access by publication embargoes or cultural assessments marked as such by cultural advice icon and advisory statements for First Nations peoples.

   As a more detailed example, for our research output and special collections in our Institutional Repository and Archival Management System.
   Depending on the source information, these records can be assigned an availability statement of 'Access conditions apply', an ‘Access’ label in the Get It section, and an ‘Access conditions apply’ top level facet.
   They may have four different Link to Resource labels of 'Citation only (Embargoed)' with an Access label in Get It, ‘Citation only (Request access)’ with an Access label, 'View online for staff and students (Log in required)' with an Access label, and 'View online (Open Access)' with a View It label.
   Where records are ‘Citation only (Request access’), we also include a link to a custom request form in the Access (Get It) section.

   Further examples utilising this functionality include
   • adding a top level facet by the facets_toplevel rules for all Alma 'Physical Items' by Alma-P, instead of only the out-of-the-box facet value for available physical items
   • removal of 856 rules assigning online availability statement, delivery, and facet for Alma records, managed only by best practice Alma-E inventory
   • blending all Alma records with a local fields of lds50 of Peer-reviewed with CDI records for the Peer-Reviewed icon and facet
   • configuring relevant Alma and Institutional Repository records to blend with the Open Access CDI records for icon and facet
   In some few cases such as the Open Access icon for Alma records, Ex Libris have subsequently filled the gap to make available by default, but this took several years to do so on behalf of VE sites, rather than developing the configuration option so that VE sites can add themselves.

   This functionality includes overarching and granular aspects of
   • the ability to build and adjust rules for all local records (including for Alma MARC and Dublin Core) for Availability, Delivery & Scoping, Links, and Facets
   • the ability to build custom mapping tables and reference source data by normalization rules against these tables, to normalize from source data to target data and support clean presentation in UI regardless of source data variation

   This is an issue caused by Primo VE ongoing limited development in this area of local record management. Ex Libris should not force customers to move to Primo VE (either directly or indirectly) when sites using Back Office would have to sacrifice any of these features and functionality, simply because it is not yet developed in VE even after several years. Ex Libris as contracted vendor for our Library Services Platform is expected to provide a discovery environment with the ability to present our own records accurately with the same full functionality as Primo managed via Back Office for all records, including Alma records, discovery import profile records, and Remote Digital Repository records.

   Note: This submission is deliberately comprehensive of various parts of local record configuration, as all of the features are married together in UI. Also, Ex Libris only permits customers 25 votes in Primo Idea Exchange in which to try to advocate not to lose this aligned functionality in moving from BO to VE. Advocacy has also been attempted for several years via avenues such as the 2020 VE Survey and yearly enhancements cycles. The summary attached has also been provided to Ex Libris (with some latest updates included for more custom improvements in 2023, at the time of this idea submission). Ex Libris is welcomed and encouraged to engage with our site and our community on these alignment issues.

   Primo managed via Back Office has powerful functionality to control access information in Primo for all our local records.
   This includes the aligned features of availability statements and Get It / View It by Delivery & Scoping rules, Links rules for all harvested data sources, and the option to build custom mapping tables for references in various rules, all of which can be married with top level facets by Facet rules.

   These features provide necessary information in Primo as expected for a core discovery layer functionality of advising users how they can access and request our resources, and avoids wasting… more

   • 

   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

2. Sort Book Chapters in correct order when using PrimoVE in 'Everything' search

   When using the ‘Everything’ search in PrimoVE you can't consistently sort book chapters into the correct order. Even when using the facets to filter and sort results, it still returns chapters in a variety of orders.

   For example, searching for the following book and filtering by ‘Book Chapters’, refining the year to ‘2015’ and sorting by ‘Title’ still returned the chapters in the wrong order (see attached screenshot).

   “Meeting Health Information Needs Outside of Healthcare” Kreps, Gary L.; Neuhauser, Linda (2015)

   It may not be possible, due to the variety of way book chapters can be structured. However, if it is, we would like PrimoVE to be able to sort book chapters into the correct order (e.g. as it's published in the book) more consistently when using the ‘Everything’ search. This would greatly enhance the user experience.

   When using the ‘Everything’ search in PrimoVE you can't consistently sort book chapters into the correct order. Even when using the facets to filter and sort results, it still returns chapters in a variety of orders.

   For example, searching for the following book and filtering by ‘Book Chapters’, refining the year to ‘2015’ and sorting by ‘Title’ still returned the chapters in the wrong order (see attached screenshot).

   “Meeting Health Information Needs Outside of Healthcare” Kreps, Gary L.; Neuhauser, Linda (2015)

   It may not be possible, due to the variety of way book chapters can be structured. However, if it… 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…)
   3 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

3. Usage of the pre-filter options within Primo VE

   At the OU, we are interested in seeing the usage of the pre-filter options within Primo VE. While the 'basic search with pre-filter' option is counted, the individual pre-filter options are not. We need this data to better understand our user behaviour in order to make improvements to our service. We also want to see the usage of pre-filters to help us decide whether to go live with the new pre-filter options.

   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  ·  Analytics  ·  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. Preference of links from link resolver over link in record in brief results for merged records

   When one or more of the records in a merged group is coming from a collection using the link resolver, and other records are coming from collections using the link in the record, the link in record type of link is always displayed in the brief result list. It should be possible to choose to always display a link resolver type of link instead.

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

5. Show amount of records of a Discover Import Profile

   In Alma it's not possible to use the adv search bar/jobs/analytics to list records from external data sources. We can see the records loaded in the History option of each profile execution. But to have a total, we would need to open one by one.

   Could it be possible to have the amount of records and MMS IDs of each discovery import profile available to see?

   For example, in the same menu list where we see the History, Reload and Delete, etc, add an option called: Total and when we click on it Alma searches for all records of the data source and displays the MMS ID.

   In Alma it's not possible to use the adv search bar/jobs/analytics to list records from external data sources. We can see the records loaded in the History option of each profile execution. But to have a total, we would need to open one by one.

   Could it be possible to have the amount of records and MMS IDs of each discovery import profile available to see?

   For example, in the same menu list where we see the History, Reload and Delete, etc, add an option called: Total and when we click on it Alma searches for all records of the… 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  ·  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

6. Add editing functionality to labels/tags created in My Favorites

   Currently, there is no way to edit a label created in My Favorites to organize items you have saved/Pinned to My Favorites. It would be helpful to be able to edit typos or make adjustments to the label as needed, without have to reassign items.

   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

7. Consistent UX or labelling for Collection Discovery search box

   Ideal solution: The Collection Discovery search box should be persistent and always search at the item level within all collections (as it does in the lobby) in order to provide a logical, consistent user experience.

   Secondary solution: the label text should be editable for each search box separately to make it clear what is being searched on the page.

   Problem:

   • The lobby search box is for everything
   • The top-level collection search box is for the title of sub-collections in that area only
   • The sub-collection search box is for items in that sub-collection only.

   Yet, all three options say "search" and are defined by one singular label. This is an entirely mystifying experience to users.

   Ideal solution: The Collection Discovery search box should be persistent and always search at the item level within all collections (as it does in the lobby) in order to provide a logical, consistent user experience.

   Secondary solution: the label text should be editable for each search box separately to make it clear what is being searched on the page.

   Problem:

   • The lobby search box is for everything
   • The top-level collection search box is for the title of sub-collections in that area only
   • The sub-collection search box is for items in that sub-collection only.

   Yet, all three options say "search" and… more

   4 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

8. Quicklink display options on full record

   In Primo VE, any quicklinks associated with records show both at the top of the full record display and in the Links section of the record. CSS can be used to hide quicklinks from the Links section, but often results in a blank Links section on the record.

   It would be helpful to have options to show quicklink at the top of the full record display, but hide them from the Links section. This would help improve the usefulness of the Links section of the record.

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

9. Enhance DC XML normalization routines for external sources (PrimoVE)

   In Primo Back Office, there is 86 inbuilt transformational routines for MARC21 and Dublin Core data normalization (e.g. “Take first words”, “Get highest number and normalize last digit”, and “Remove HTML tags”). Most have been translated for MARC21 in PrimoVE by various people but, because of limited regex and Xpath functionality, few have been translated into Dublin Core XML normalization routines for PimoVE.

   We would like to see the implementation of full regex and/or XPath / XQuery functionality (or similar) to allow all Back Office normalization routines to be created for PrimoVE.

   55 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

10. Pipe setting improvement: allow to exclude specific OAI sets from a pipe

    We would like to have the possibility to exclude one or more specific sets when we harvest the data with OAI-PMH protocol in Primo.
    This option would have 2 results:
    - to reduce the number of imported records
    - we wouldn't have to set specific normalization rules in order to exclude the records we don't want to show in Primo

    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  ·  Integration with other systems  ·  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. Change handling of MARC fields 100 and 700 in citation styles in Primo VE

    Handling of MARC fields in citation styles should be changed as follows:
    1. If there are relator codes in $4, only $4 aut and cmp should be considered as author, relator codes $4 edt, ill, ivr, trl and drt should be treated as contributors. Entries with other $4 codes should be ignored for citation.
    2. If there are no relator codes $4 in the record, field 100 should be considered as author, field 700 as contributor.
    Benefits: Citiation styles get independent from cataloguing language as they are now by using $e. Also citation styles work independent from the fact, if the record is catalogued according to RDA or - as is the case with many records in many catalogues - by older rules like AACR2.

    Handling of MARC fields in citation styles should be changed as follows:
    1. If there are relator codes in $4, only $4 aut and cmp should be considered as author, relator codes $4 edt, ill, ivr, trl and drt should be treated as contributors. Entries with other $4 codes should be ignored for citation.
    2. If there are no relator codes $4 in the record, field 100 should be considered as author, field 700 as contributor.
    Benefits: Citiation styles get independent from cataloguing language as they are now by using $e. Also citation styles work independent from the fact, if… more

    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  ·  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. Automate SSL/TLS certificate management

    For hosted Primo sites that have custom domain names, the current process for deploying SSL certificates involves time-consuming manual steps and hand-offs, many of which must be repeated each time a certificate is renewed. [1]

    Several institutions will soon require SSL certificates to be renewed every 90 days, at which point the current manual process will become utterly unmanageable for both Ex Libris and its customers. [2]

    I propose that Ex Libris adopt an ACME-like service (such as Let's Encrypt) to fully automate SSL certificate management. The customer's responsibility would be to set up a DNS record (as they do today), but the SSL certificates would be completely managed by Ex Libris through automation. Some of our vendors are already doing this (e.g. Springshare, Elsevier), and it makes life much easier for both the customers and the vendors.

    [1] https://knowledge.exlibrisgroup.com/Cross-Product/Knowledge_Articles/Working_with_custom_domain_names_on_hosted_ExLibris_environments

    [2] https://sectigo.com/resource-library/google-announces-intentions-to-limit-tls-certificates-to-90-days-why-automated-clm-is-crucial

    For hosted Primo sites that have custom domain names, the current process for deploying SSL certificates involves time-consuming manual steps and hand-offs, many of which must be repeated each time a certificate is renewed. [1]

    Several institutions will soon require SSL certificates to be renewed every 90 days, at which point the current manual process will become utterly unmanageable for both Ex Libris and its customers. [2]

    I propose that Ex Libris adopt an ACME-like service (such as Let's Encrypt) to fully automate SSL certificate management. The customer's responsibility would be to set up a DNS record (as they do… more

    189 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…)
    8 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. CDI records: please provide us the ORCIDs in the PNX record in a usable form

    Unfortunately, we have received the following case response: "We have reviewed your request with our content operations team and determined that our system is currently not designed to provide the functionality you requested, so the next step is to pursue this as an enhancement."
    So we hope to get support for our proposal in the Alma community.

    We are currently working on making the ORCID more visible in our Primo (incl. linking to the ORCID entry of an author).

    We are glad to see that CDI records already contain the ORCIDs in the PNX record.
    Unfortunately, they cannot be used for normalization, because:
    - the XML fields <creator>/<creatorcontrib> list all authors of a record and the extra field <orcidid> lists the ORCIDs
    - however, the connection between these fields is missing

    It is not possible to find out which ORCID belongs to which author.
    Please provide us the ORCIDs in the PNX record in a usable form, so that we can create a link for those people who have an ORCID entry.

    Thank you in advance!

    Some PNX record examples:

    (1) TNcdiwebofscienceprimary000288028600012CitationCount
    Benefit of atrial septal defect closure in adults: Impact of age
    Humenberger, Michael ; Rosenhek, Raphael ; Gabriel, Harald ; Rader, Florian ; Heger, Maria ; Klaar, Ursula ; Binder, Thomas ; Probst, Peter ; Heinze, Georg ; Maurer, Gerald ; Baumgartner, Helmut
    OXFORD: Oxford Univ Press
    European heart journal, 2011, Vol.32 (5), p.553-560

    11 authors, 3 ORCIDs

    PNX record:
    <creator>Humenberger, Michael ; Rosenhek, Raphael ; Gabriel, Harald ; Rader, Florian ; Heger, Maria ; Klaar, Ursula ; Binder, Thomas ; Probst, Peter ; Heinze, Georg ; Maurer, Gerald ; Baumgartner, Helmut</creator>
    <creatorcontrib>Humenberger, Michael ; Rosenhek, Raphael ; Gabriel, Harald ; Rader, Florian ; Heger, Maria ; Klaar, Ursula ; Binder, Thomas ; Probst, Peter ; Heinze, Georg ; Maurer, Gerald ; Baumgartner, Helmut</creatorcontrib>
    (...)
    <orcidid>0000-0002-6902-126X ; 0000-0003-1147-8491 ; 0000-0002-9043-7657</orcidid>

    (2) TNcdicrossrefprimary101093eurheartj_ehq377
    Atrial septal defect: Waiting for symptoms remains an unsolved medical anachronism
    Berger, Felix ; Ewert, Peter
    OXFORD: Oxford Univ Press
    European heart journal, 2011, Vol.32 (5), p.531-534

    2 authors, 1 ORCID

    PNX record:
    <creator>Berger, Felix ; Ewert, Peter</creator>
    <creatorcontrib>Berger, Felix ; Ewert, Peter</creatorcontrib>
    (...)
    <orcidid>0000-0001-7881-1557</orcidid>

    (3) TNcdipubmedcentralprimaryoaipubmedcentralnihgov6194635
    Adherence to inhaled therapy and its impact on chronic obstructive pulmonary disease (COPD)
    Humenberger, Magdalena ; Horner, Andreas ; Labek, Anna ; Kaiser, Bernhard ; Frechinger, Rupert ; Brock, Constanze ; Lichtenberger, Petra ; Lamprecht, Bernd
    LONDON: Springer Nature
    BMC pulmonary medicine, 2018, Vol.18 (1), p.163-163

    8 authors, 2 ORCIDs

    PNX record:
    <creator>Humenberger, Magdalena ; Horner, Andreas ; Labek, Anna ; Kaiser, Bernhard ; Frechinger, Rupert ; Brock, Constanze ; Lichtenberger, Petra ; Lamprecht, Bernd</creator>
    <creatorcontrib>Humenberger, Magdalena ; Horner, Andreas ; Labek, Anna ; Kaiser, Bernhard ; Frechinger, Rupert ; Brock, Constanze ; Lichtenberger, Petra ; Lamprecht, Bernd</creatorcontrib>
    (...)
    <orcidid>0000-0003-3365-3449 ; 0000-0001-7746-3335</orcidid>

    Unfortunately, we have received the following case response: "We have reviewed your request with our content operations team and determined that our system is currently not designed to provide the functionality you requested, so the next step is to pursue this as an enhancement."
    So we hope to get support for our proposal in the Alma community.

    We are currently working on making the ORCID more visible in our Primo (incl. linking to the ORCID entry of an author).

    We are glad to see that CDI records already contain the ORCIDs in the PNX record.
    Unfortunately, they cannot be used… more

    53 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  ·  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

14. Add a job that can set the CDI option collectively

    We would like you to add a job to set "Activate for search in CDI" collectively for the electronic collection set of CZ.
    Also, please add a job to batch update the following CDI options for the electronic collection set of IZ.
    - CDI Search activation status
    - We subscribe to only some titles in this collection
    - CDI-only full text activation
    - Do not show as Full Text available in CDI even if active in Alma

    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…)
    2 comments  ·  Administrative Tools  ·  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. Give customers the option to have a custom multilingual file for synonyms and compound words.

    We are a multilingual network, catering to four languages. It is very important to us to ensure that customers find the same resources regardless of the UI language they use. As one of our UI languages does not have a synonyms file, it is currently not possible for us to incorporate synonyms beyond those included by default in our Primo, as this would lead to differing search results for this language. We would like this to be solved by allowing customers to use a dedicated multilingual file for synonyms, compound words etc. that they can customize to their needs.

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

16. Add option to filter out Global title index results without any offer

    When creating a scope that include CDI records non filtered per availability (Rapido-CDI expanded index), Global title index without any offer (no Get it section, no view online section and no item available in the Rapido tile) are retrieved (example). These records are owned by libraries participating in any POD (outside of ours) of Rapido.

    We would like to have an option to exclude the Global title index results without an offer.

    82 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…)
    3 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

17. Make both the label and the code from the controlled vocabulary registry searchable

    When adding a controlled vocabulary to the registry and afterwards connecting it to a certain MARC field in Primo VE, patrons now can only search using the code and not the label.

    As an example imagine a controlled vocabulary with the entry ECON (code) and Economy and Finance (label). If ECON (the code) is stored in the record and the patron searches for Economy and Finance in that field (in advanced filter), he or she will get no results. If you search for ECON however all relevant records will be returned.
    Of course the patrons are not supposed to know these codes, thus rendering the use of controlled vocabularies in search scopes practically useless.

    When adding a controlled vocabulary to the registry and afterwards connecting it to a certain MARC field in Primo VE, patrons now can only search using the code and not the label.

    As an example imagine a controlled vocabulary with the entry ECON (code) and Economy and Finance (label). If ECON (the code) is stored in the record and the patron searches for Economy and Finance in that field (in advanced filter), he or she will get no results. If you search for ECON however all relevant records will be returned.
    Of course the patrons are not supposed to know… 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  ·  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

18. Integrated with ChatGPT technology

    Good to integrate ChatGPT technology in Primo VE.

    4 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

19. Link search results for full text to the digital representation instead of the title

    One of the selling points of Primo VE is that full text from digital representations (Alma-D) is indexed automatically. When a user performs a search wherein full text is found, they can click on the brief result to go to the full display, then click on the digital representation to open the file in the viewer.

    This works well for titles with only one digital representation and file. If you search our catalog for the keywords feeder is also designed as a feeder, you will see an ESL Pamphlet about the Black River Canal as the first result. When you click through to the full display, it is obvious which digital version you want, because there is only one.

    However, this is confusing when a title has multiple digital representations, as in the case of a serial or multi-volume set. When a user performs a search wherein full text is found in a title with multiple representations or files, they can click on the brief result to go to the full display for the title, but it is impossible to determine which representation or file has the desired text.

    If you search our catalog for the keywords Roberton were appointed scrutineers, the results take you to the Transactions of the Mining and Geological Institute of India. But once you get to the full display, there is no way of knowing which volume or issue that text came from, unless you open each PDF and search within.

    Ideally, results of a search for full text in a digital representation would link directly to the file or files in which the text was found.

    Alternatively, when full text was searched and a brief result clicked, the resulting full display could only show digital versions in the View It section that included the desired text.

    It would also be helpful to be able to search within a title for text in representations or files. Using the above example, if you went to the full display for the Transactions of the Mining and Geological Institute of India, you could search its full text and see only those digital versions that included your desired text.

    One of the selling points of Primo VE is that full text from digital representations (Alma-D) is indexed automatically. When a user performs a search wherein full text is found, they can click on the brief result to go to the full display, then click on the digital representation to open the file in the viewer.

    This works well for titles with only one digital representation and file. If you search our catalog for the keywords feeder is also designed as a feeder, you will see an ESL Pamphlet about the Black River Canal as the first result. When you… more

    27 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  ·  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. Separate the Primo My Account Update Login Credentials form into two different forms for PIN code and Password

    As a user, I would like to have two different forms for Pincode update and Password update (Update Login Credentials in My Account > Personal Settings) so I am sure that I can also change only one of the two. With the current design (=one form for PIN and password update), it is suggested to me that I always have to update both.

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