647 results found

1. NZ/IZ linking in consortia

   Background: MARC 776 is used to establish a link between related records (Also available in another form:). If a link cannot be established, a title search is started instead.

   In a consortial environment, there is an issue with this: Primo VE is only able to establish a link if both the linking and the linked-to title are available locally. This happens because Primo depends on Alma functionality for related records to establish a link and Alma is building them within institution scope only (Network is considered just another institution in this regard). This means that as soon as only the linking title is available in an IZ, a title search will be started.

   To give an example: We have a journal with the main title “Recht” (Law), which links to an electronic version of the same title. In IZ that do not have the electronic version, a title search for Recht/law will be started instead, leading to over 27’000 results – from a link that promised to lead to a different version of the same title. See also pdf below.

   This behaviour makes 776 largely unusable for consortia, where it would be important for that our patrons are able to find resources that are not available locally as well or where we’d at least want a system that can recognize if something is locally available and only displays the link in this case.

   Background: MARC 776 is used to establish a link between related records (Also available in another form:). If a link cannot be established, a title search is started instead.

   In a consortial environment, there is an issue with this: Primo VE is only able to establish a link if both the linking and the linked-to title are available locally. This happens because Primo depends on Alma functionality for related records to establish a link and Alma is building them within institution scope only (Network is considered just another institution in this regard). This means that as soon as only the… more

   • 

   144 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

   Submit Rating

2. Available online in Research assistant as default.

   It would be beneficial to be able to make what is under the refinement icon in the search box more visible. It would be even better if we could make the "Available online" button be checked by default.

   As it is now it is so hidden that users aren't aware that this is a possible feature. The fact that the user needs to select the refinement icon to see this possibility isn't optimal.

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

   Submit Rating

3. Open Access Indicator for Unimarc records

   Open Access Indication in Primo VE is currently supported for Marc21 and Dublin records : https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/030Primo_VE_User_Interface/Open_Access_Indication_in_Primo_VE
   Please support Unimarc record, too !

   134 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

   Submit Rating

4. Ability to Configure Multiple Journal Searches

   Currently, Primo VE supports only one Journal Search configuration for an institution. While this works well for many institutions, some institutions oversee multiple libraries or campuses with distinct journal holdings (e.g., different licensing agreements, consortia memberships, or campus-specific subscriptions).

   We would like to request the ability to configure and offer multiple, separate Journal Searches within Primo VE.

   Each Journal Search should:

   • Be scoped independently (e.g., by IZ, NZ, or a specific library/campus)

   • Have customizable display labels and help text to clearly indicate which journal collection the search covers

   • Support direct linking to each Journal Search from library platforms

   Use Case:
   At multi-campus institutions, users often need to know which journals are available specifically through their home campus. Currently, this is difficult to implement since only one centralized Journal Search can be offered.

   Multiple Journal Searches would:

   • Reduce user confusion when different campuses/libraries have different subscriptions

   • Support institutions that are part of consortia but also maintain unique, local journal collections

   • Improve the patron experience by allowing clear pathways to the correct set of journals

   Impact:

   We believe this enhancement would significantly improve discoverability, align search results with basic Primo searches, reduce access confusion, and allow libraries to better serve diverse user groups with distinct e-resource entitlements.

   Currently, Primo VE supports only one Journal Search configuration for an institution. While this works well for many institutions, some institutions oversee multiple libraries or campuses with distinct journal holdings (e.g., different licensing agreements, consortia memberships, or campus-specific subscriptions).

   We would like to request the ability to configure and offer multiple, separate Journal Searches within Primo VE.

   Each Journal Search should:

   • Be scoped independently (e.g., by IZ, NZ, or a specific library/campus)

   • Have customizable display labels and help text to clearly indicate which journal collection the search covers

   • Support direct linking to each Journal Search from library platforms

   Use Case: … more

   31 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

   Submit Rating

5. Allow view configuration to exclude retracted and withdrawn articles from results list

   The CDI Document Types labels and facets are valuable information. Now that we have that information, and the Document Types are also facets, can we please get the ability to set our discovery views to exclude these Retracted and Withdrawn articles (similarly to how we have the ability to set a view to exclude CDI ebook records)?

   I set up our custom primo search box widget on our library website to exclude these two resource types by default, and I locked those facets so they aren't lost on the next search. You can search the Combined Search box on our library site to try it out: https://www.normandale.edu/current-students/academic-resources/library/index.html

   But it's not a good work around. First, any time the user clicks on the New Search link in the menu, the facets are cleared. Second, when a user navigates from a CDI search to a local search (like our book search) or journal search the excluded facets are sticky in those searches too, even though they have no effect in those contexts. Also, by using the facet functionality to exclude these resource types, we are also in effect drawing extra attention to the existence of these unreliable sources in the library's collections.

   Although not a preferred solution because they would still be discoverable, I thought about possibly down boosting these two resource types. Currently, CDI document attributes are not boostable.

   The CDI Document Types labels and facets are valuable information. Now that we have that information, and the Document Types are also facets, can we please get the ability to set our discovery views to exclude these Retracted and Withdrawn articles (similarly to how we have the ability to set a view to exclude CDI ebook records)?

   I set up our custom primo search box widget on our library website to exclude these two resource types by default, and I locked those facets so they aren't lost on the next search. You can search the Combined Search box on our… more

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

   Submit Rating

6. Converting Greek letters in queries for local materials

   When queries include Greek letters with diacritics, the retrieval omits many local records, as there is no conversion in Primo VE between letters with or without diacritics, or with different diacritics.

   Example:
   Searching ἄγω or αγω gives different results. CDI records are retrieved regardless, while local records can only be retrieved in the exact manner they were cataloged.

   Using a blended search (local+CDI) can confuse patrons, as it may lead them to believe the library does not have certain materials. Using a local search scope, patrons sometimes receive zero results, so many records are hidden from them.

   Greek is not only a modern language. It is a fundamental ancient language used in classical studies in many academic institutions. Therefore, the omission of the libraries' collections/items must be corrected.

   We request the addition of a conversion between characters for Greek, so that results can be retrieved regardless of whether you search with or without diacritics, and whether a record came from a local catalog or CDI.

   The attached file is an offered conversion table. Each color represents one letter, so all characters in that color should retrieve the same results.

   When queries include Greek letters with diacritics, the retrieval omits many local records, as there is no conversion in Primo VE between letters with or without diacritics, or with different diacritics.

   Example:
   Searching ἄγω or αγω gives different results. CDI records are retrieved regardless, while local records can only be retrieved in the exact manner they were cataloged.

   Using a blended search (local+CDI) can confuse patrons, as it may lead them to believe the library does not have certain materials. Using a local search scope, patrons sometimes receive zero results, so many records are hidden from them.

   Greek is not… more

   • 

   38 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

   Submit Rating

7. Discovery collections per library and unfiltered view

   In our consortium we have some mixed IZs, which means different libraries, mostly in the same geographical area, that are part of the same IZ.
   Users accessing via the local library interface are interested mainly in that specific library Discovery collection. But at the same time they might be also interested to know if a resource is available in the near by libraries, as it could be easily accessible physically or to request it.
   We have activated the relevant configurations and Discovery collections displays correctly for the specific libraries only. But when the view is filtered and "Local copy unavailable" displayed, the user might overlook that there is the item near by and that it can be requested.
   We would like to have a configuration that keeps the get it section display as it is per default (with the "view _ to _ libraries _ for _ collection _ discovery" parameter turned to false), but at the same time displays the collections only for the relevant libraries (as we have when "view _ to _ libraries _ for _ collection _ discovery" parameter is set to true).

   In our consortium we have some mixed IZs, which means different libraries, mostly in the same geographical area, that are part of the same IZ.
   Users accessing via the local library interface are interested mainly in that specific library Discovery collection. But at the same time they might be also interested to know if a resource is available in the near by libraries, as it could be easily accessible physically or to request it.
   We have activated the relevant configurations and Discovery collections displays correctly for the specific libraries only. But when the view is filtered and "Local copy unavailable"… more

   28 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

   Submit Rating

8. Responsive label "item in place/not in place" for open shelf items

   Our available items in open rack cannot be requested for local pickup but this is confusing for patrons as there is a physical request button (only for a Transit request - the Owning Library is missing as pickup location). Only for items NOT in place and items in STACKS, the Owning Library is an additional Pickup location.

   As the option for local pickup for open shelf items depends on the availability and location (item in place/item not in place), we would like to change this label and add information about requestability and access to items (see image attached). But this status has to be mapped to the Holding Location (or item policy?), to distinguish between open shelf and stacks:

   • items in OPEN SHELF that are NOT available (on loan): requestable for local pickup and transit
   • items in OPEN SHELF that are available: only requestable for transit)
   • items in STACKS that are available/not available: requestable for local pickup and transit

   Is it possible to have a "responsive" status label, but only for items in open shelf?

   Our available items in open rack cannot be requested for local pickup but this is confusing for patrons as there is a physical request button (only for a Transit request - the Owning Library is missing as pickup location). Only for items NOT in place and items in STACKS, the Owning Library is an additional Pickup location.

   As the option for local pickup for open shelf items depends on the availability and location (item in place/item not in place), we would like to change this label and add information about requestability and access to items (see image attached). But this… more

   •  

   73 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

   Submit Rating

9. Primo VE : Alignment of Unimarc normalization rules with Marc21 normalization rules for the creation of the author facet

   The current OTB normalization rules for the creator/contributor facet in Primo VE differ between Marc21 and Unimarc records. Unimarc rules consider more elements than Marc21, leading to inconsistencies and duplicate facets for the same author.
   For example, from personal name fields (fields 70#), Exlibris uses the entry element, the part of name, the qualifier, Roman numerals and dates (a, b, c, d, f) for “Personal name” responsibility statements. In Marc 21, only the entry element is retained (a).

   Key Issues:

   1- Duplicate Facets: Two facets are created for the same author, one based on Unimarc and the other on Marc21.
   2- Search Inconsistencies: The facets do not filter search results uniformly, with Unimarc facets often limiting searches to printed documents and Marc21 facets refining searches for online resources.
   

   Proposed Solution:

   Align the Unimarc and Marc21 normalization rules to simplify the author facet. This pragmatic approach will improve search functionality until authority identifiers are widely adopted.

   Please refer to the attached document for more details and proposed modifications to the Unimarc standardization rules.
   Thank you in advance for any support you can give to this idea.

   Alexandre Faure
   Université de Bordeaux

   The current OTB normalization rules for the creator/contributor facet in Primo VE differ between Marc21 and Unimarc records. Unimarc rules consider more elements than Marc21, leading to inconsistencies and duplicate facets for the same author.
   For example, from personal name fields (fields 70#), Exlibris uses the entry element, the part of name, the qualifier, Roman numerals and dates (a, b, c, d, f) for “Personal name” responsibility statements. In Marc 21, only the entry element is retained (a).

   Key Issues:

   1- Duplicate Facets: Two facets are created for the same author, one based on Unimarc and the other on Marc21.

   … more

   • 

   73 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

   Submit Rating

10. Display ebook reading format (HTML, EPUB, PDF etc.) in Primo (VE) full display

    When displaying links to Ebook providers in Primo (VE) full display it would be suitable to have a notice of what ebook reading formats accessible for each provider. Instead of having to click further to the each provider to retrieve the information. Even information about online reading and/or download option would be suitable.

    44 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

    Submit Rating

11. Enable Custom Configuration of Primo Normalization Rules for Local Authority Search

    Current Situation: Local authority search records are currently displayed with hard-coded normalization rules (NRs).

    Proposed Change: Allow users to configure Primo normalization rules for local authority search. This flexibility will enable us to normalize authority records and display fields according to our specific needs.

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

    Submit Rating

12. ORCID iD Integration in Info Card for Contributor Page in Alma

    Background: In August, ExLibris implemented the Info Card feature for contributor pages in Alma, which appears under specific conditions related to linked authority records. This enhancement has significantly improved the visibility of contributor information.

    Current Conditions for Info Card Display:

    • A person is linked to an LC Names authority for a personal name.
    • A person is linked to a Name authority that exists in VIAF and can be linked to an LC Name authority for a personal name.
    • Information on the person exists in LC Names and Wikidata, with at least two fields containing information beyond the name of the person.
    • Wikidata cache is updated in Alma on a weekly basis.

    Enhancement Request: We propose an additional feature to further enrich the Info Card functionality. Specifically, we request that when an ORCID iD in the form of a URI is present in either the LC name authority record or Wikidata for the author, the following should occur:

    • Display the ORCID iD URI: The ORCID iD URI should be prominently displayed in the Info Card.
    • Make the ORCID iD URI Resolvable: The URI should be clickable and resolvable directly within the Info Card in both Alma and Primo.

    Benefits: Integrating ORCID iD URIs will enhance the discoverability of author contributions and facilitate seamless access to their research profiles, thereby improving the overall user experience.

    Thank you for considering this enhancement to the Info Card feature. We believe this addition will greatly benefit users and contribute to the ongoing development of Alma and Primo.

    Background: In August, ExLibris implemented the Info Card feature for contributor pages in Alma, which appears under specific conditions related to linked authority records. This enhancement has significantly improved the visibility of contributor information.

    Current Conditions for Info Card Display:

    • A person is linked to an LC Names authority for a personal name.
    • A person is linked to a Name authority that exists in VIAF and can be linked to an LC Name authority for a personal name.
    • Information on the person exists in LC Names and Wikidata, with at least two fields containing information beyond the name of the… more
    204 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  ·  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

    Submit Rating
    AdminAdina Marciano (Admin, Ex Libris) responded

    Thank you for the suggested idea. We see its value and will consider it in the future. This development requires integration with third-party providers, and we will need to investigate the possibility of this development.

13. Include subfield k from 245 in title index (important for manuscripts/archives)

    Subfield k of the 245 title field should always be indexed. Currently, it is only indexed when subfield a is absent. OCLC makes clear that both subfields may be used together: "Use subfield ǂk also to indicate "form" even if a formal title is given in subfields ǂa, ǂb, and ǂc." From: https://www.oclc.org/bibformats/en/2xx/245.html

    This subfield is important for manuscripts and archives. Examples from OCLC:

    245 ǂa Four years at Yale : ǂk diaries, ǂf 1903 September 16-1907 October 5

    245 ǂa The charity ball : ǂb a comedy in four acts : ǂk typescript, ǂf 1889 / ǂc by David Belasco and Henry C. DeMille

    Subfield k of the 245 title field should always be indexed. Currently, it is only indexed when subfield a is absent. OCLC makes clear that both subfields may be used together: "Use subfield ǂk also to indicate "form" even if a formal title is given in subfields ǂa, ǂb, and ǂc." From: https://www.oclc.org/bibformats/en/2xx/245.html

    This subfield is important for manuscripts and archives. Examples from OCLC:

    245 ǂa Four years at Yale : ǂk diaries, ǂf 1903 September 16-1907 October 5

    245 ǂa The charity ball : ǂb a comedy in four acts : ǂk typescript, ǂf 1889 / ǂc by David… more

    31 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

    Submit Rating

14. Disabling automatically generated links for related records if the associated NR is disabled.

    Primo VE is capable to automatically create links to related records via MARC 7xx fields.
    As these links where not working well for us, we were looking to turn them off with a NR, by setting “set pnx."display"."relation" to "N/A"” for 776 specifically.
    Unfortunately, this turned out not to work in all cases. As Ex Libris explained this is because
    - in the related records, they differentiate between child records and parent records
    - for child records, as the specific relation field is included, Display NR takes effect
    - for parent records, as the specific relation field is not included, and the opposite link is added automatically, Display NR cannot have any effect

    This means we can only disable links from child to parent records but not the other way around. What we would like to see is that, if a relation from a child to a parent record is supressed, the automatically added opposite link should also be supressed.

    Primo VE is capable to automatically create links to related records via MARC 7xx fields.
    As these links where not working well for us, we were looking to turn them off with a NR, by setting “set pnx."display"."relation" to "N/A"” for 776 specifically.
    Unfortunately, this turned out not to work in all cases. As Ex Libris explained this is because
    - in the related records, they differentiate between child records and parent records
    - for child records, as the specific relation field is included, Display NR takes effect
    - for parent records, as the specific relation field is not included,… 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…)
    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

    Submit Rating

15. Instant Insight into FRBR Versions in the Search Results

    We have received feedback from our users that they would like to get an initial overview of a FRBR group’s contents directly in the results list. When encountering the representative record of a FRBR group, they want to immediately see how many online resources and physical copies are included, along with other useful details such as publication dates or resource types.
    A straightforward implementation could be to enhance the link to the versions list so that it not only shows the total number of versions but also indicates how many available online (consortia: only online resources that are available in the respective IZ / no viewit_other) and print resources are included. More advanced solutions could go further by displaying additional information about each version.
    We believe this enhancement would improve both the generic and the preferred FRBR display, as it would reduce unnecessary clicks and help users assess relevant resources more efficiently and even prevent users from overlooking relevant resources.

    We have received feedback from our users that they would like to get an initial overview of a FRBR group’s contents directly in the results list. When encountering the representative record of a FRBR group, they want to immediately see how many online resources and physical copies are included, along with other useful details such as publication dates or resource types.
    A straightforward implementation could be to enhance the link to the versions list so that it not only shows the total number of versions but also indicates how many available online (consortia: only online resources that are available in… more

    30 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

    Submit Rating

16. Consortia environment: inheritance for open access collections

    Open access collections that are activated in the NZ are not inherited by the IZs.

    Given the number of open access collections and the possible number of IZs, it can be a tedious task to activate a large number of OA collections for each IZ.

    We would like to see that OA collections can be inherited just like regular subscription collections.

    PS - copied from https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/19695103-consortia-environment-provide-inheritance-for-ope, to open it for voting again.

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

    Submit Rating

17. Improve Primo VE searching in non-roman script so definite article prefixes are appropriately counted as non-filing characters

    Arabic and Hebrew print titles beginning with the definite article prefix (like English "the") cannot be retrieved in Primo VE unless that initial definite article is included in the search. This is true even when the linked 880 with non-roman script has the number of nonfiling characters coded correctly in the subfield indicator in the bibliographic record

    Example:

    245 13$6880-02 $aal-Mabānī al-Kanʻānīyah fī Filasṭīn / $cNimr Sirḥān.
    880 12$6245-02/(3/r $aالمباني الكنعانية في فلسطين / $cنمر سرحان.

    Without the initial definite article, the search comes up empty or retrieves only records from the CDI, but not the sought print materials present in our Alma IZ.

    Arabic and Hebrew print titles beginning with the definite article prefix (like English "the") cannot be retrieved in Primo VE unless that initial definite article is included in the search. This is true even when the linked 880 with non-roman script has the number of nonfiling characters coded correctly in the subfield indicator in the bibliographic record

    Example:

    245 13$6880-02 $aal-Mabānī al-Kanʻānīyah fī Filasṭīn / $cNimr Sirḥān.
    880 12$6245-02/(3/r $aالمباني الكنعانية في فلسطين / $cنمر سرحان.

    Without the initial definite article, the search comes up empty or retrieves only records from the CDI, but not the sought print materials present… more

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

    Submit Rating

18. Primo VE facet for collections regardless of inventory type

    I would like to propose an out of the box facet for collections that can include all 3 inventory types.

    We have users that need to be able to filter their search results by ‘collections’ or groupings that contain physical, electronic and digital resources. For example, our Original Materials ‘collection’ is made of physical items, digital items and electronic items that we have catalogued in local electronic collections.

    Currently, there are OOTB facets based on physical inventory (Library and Location) but none that combine all 3 inventory types.

    As a workaround, we have utilised the digital collection facet for this purpose. Although it is primarily used for digital records, it does support any type of record. However, this means that our Collection Discovery pages contain all of our collection items and some physical and electronic items without cover images or thumbnails. It also results in our Original Materials collection including 272,505 items instead of being used to showcase select resources as the functionality intended. We have to manually update these collections regularly as new items are catalogued.

    The creation of this facet type would improve collection discovery for uses by allowing libraries to create collections of resources regardless of inventory type.

    I would like to propose an out of the box facet for collections that can include all 3 inventory types.

    We have users that need to be able to filter their search results by ‘collections’ or groupings that contain physical, electronic and digital resources. For example, our Original Materials ‘collection’ is made of physical items, digital items and electronic items that we have catalogued in local electronic collections.

    Currently, there are OOTB facets based on physical inventory (Library and Location) but none that combine all 3 inventory types.

    As a workaround, we have utilised the digital collection facet for this… more

    38 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

    Submit Rating

19. Copy text from digital viewer

    When reading documents in the digital viewer, it would be nice to have the ability to copy text directly from the page. You can do this if you download the document. I was attempting to do this with a larger file that mentioned other reports I wanted copy the name of a report to view/search for in the catalogue; however, the digital viewer does not allow users to select text from the document.

    13 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

    Submit Rating

20. Author/Title Index in Browse Search

    Author/Title Index in Browse Search
    Please include an Author/Title index which searches headings combining author/creator name and uniform title. The index usually includes:
    * 100/240
    * 110/240
    * 111/240
    * 700 where $$t is present
    * 710 where $$t is present
    * 711 where $$t is present
    * 800 where $$t is present
    * 810 where $$t is present; and
    * 811 where $$t is present

    59 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

    Submit Rating