403 results found

1. Primo VE webhook search blending

   In terms of usability, it would be good if Primo VE webhook search results could be blended to the combined search results (local resources and articles). Blended results feature should be able to select on a search-by-search basis e.g. if you apply search for AI-based article search portals or whether to apply search for printed resources from the repository libraries.

   32 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. Enable user personalization for their default "Expand my results" and "Search in full text" options

   Currently, institutions set a default for "Expand my results" and "Search in full text." Users can toggle these settings, but unlike other filters, these toggles are not "sticky" and it does not seem possible to "lock" them. When the session is reset or the user selects "New Search", the institutional default is re-applied. The user who prefers other settings must therefore constantly re-toggle their desired options.
   
   We find vastly different needs between our faculty, graduate students, professional practitioners, and undergraduates in their search behaviors and preferences. Currently, we have default settings designed for the least sophisticated searchers (undergraduates), but many of our more advanced users are expressing frustration with these settings. They would be much happier if they could use other settings by default. It would be a great help to them if "Expand My Results" and "Search in Full Text" could be added to Primo VE's personalization options for signed in users, like Results Per Page. The ability to set a preference in Personal Details and Settings, "lock" the toggles like the filters/facets, and/or have the system remember and retain the user's last selection could all be big improvements to the user experience and satisfaction.

   Currently, institutions set a default for "Expand my results" and "Search in full text." Users can toggle these settings, but unlike other filters, these toggles are not "sticky" and it does not seem possible to "lock" them. When the session is reset or the user selects "New Search", the institutional default is re-applied. The user who prefers other settings must therefore constantly re-toggle their desired options.
   
   We find vastly different needs between our faculty, graduate students, professional practitioners, and undergraduates in their search behaviors and preferences. Currently, we have default settings designed for the least sophisticated searchers (undergraduates), but many… 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  ·  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. Option to bulk export normalization rules Primo VE

   We would like to make a bulk export for backup of the normalization rules that we have set up in Primo VE.

   At the moment this functionality does not exist but would be very helpful for us. At the moment if we make changes to the normalization rules it is easy to accidentally delete the entire set of rules for one field. It is also not possible to easily roll back a change that we made.

   Therefore it would be useful to have the export option, to have an extra copy of all the normalization rules as a backup.

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

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

5. Allow suppression of GES based on Primo View

   Currently a GES (General Electronic Service) link can be suppressed or shown based on certain characteristics of the record or though Alma Display Logic Rule, through characteristics of the logged in user or presence / absence of other GES links. We would like the ability to control the display of GES links based on the current Primo view. This would allow us to show or suppress links in certain Primo views before asking the user to login.

   6 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

6. Display the item "process type" label in Get It

   In get-It, we would like to display some of the "Process type" labels from our local item processes.
   For example, we think that the information "In the process of scanning" would be interresting for the users, instead of the general label "In process".
   This would highlight projects in progress that are eagerly awaited by users.

   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

7. Quotation marks: align the behavior of Alma and CDI records

   When using quotation marks in a search, Alma and CDI records behave differently:

   CDI records:
   « » → not considered for the search
   „ “ → considered for the search only for some languages
   “ ” → considered for the search only for some languages
   " " → considered for the search

   For local records:
   « » → not considered for the search
   „ “ → not considered for the search
   “ ” → not considered for the search
   " " → considered for the search

   With this idea exchange we propose to align the behavior of Alma and CDI records towards the different quotation marks.
   This should uniform and make more coherent the search results obtained by patron users.

   When using quotation marks in a search, Alma and CDI records behave differently:

   CDI records:
   « » → not considered for the search
   „ “ → considered for the search only for some languages
   “ ” → considered for the search only for some languages
   " " → considered for the search

   For local records:
   « » → not considered for the search
   „ “ → not considered for the search
   “ ” → not considered for the search
   " " → considered for the search

   With this idea exchange we propose to align the behavior of Alma and CDI… more

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

8. Do not display private fields in “display source record” or full record in Primo VE.

   Marc 21 coding is used to identify some marc record fields/subfields as private. As an example, the indicators in the 541 tag are used to indicate that data in the field is ‘private’ to the organisation. Primo VE should automatically hide these fields from the source record and full details display in Primo VE. If an organisation wishes for the field to be made public they can adjust the record coding as appropriate. Alternatively organisations should be able to select to suppress private fields (as identified in marc 21) from public display.

   68 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

9. Banner - start and end date

   We're using the banner to promote different library related events/workshops etc that run throughout the year. Currently we would have to manually enable and disable banners.

   If there was something that allows us to determine how long the banner would display then it would make it easier, and not having to make sure a member of staff is available on certain days of the year just to switch on/off a banner.

   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

10. Ability to place restrictions on Display Source Record link

    When enabling the ‘display source record’ link in Primo VE it would be useful to be able to specify which types of records the link displays or doesn’t display for. In our case we would prefer to restrict the option to our records for published resources so the private notes more typically associated with unpublished material such as manuscripts would not be publicly viewable.

    5 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    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

11. Allow end users to toggle "Resource Type" sorting - alpha or size

    Hello

    We have had a query about whether it is possible to add a second Resource Type section to Primo VE in order to allow for an alphabetical searching option (our default sort is size of search results). I was sure this wasn't possible, but offered to create an idea here requesting to allow end users to choose how they sort the list of Resource Types.

    This would enable them to toggle between the two sort types, e.g. to see Newspaper Articles near Newspapers, but then to change back to 'size' sorting to see the largest number of results, etc.

    Thanks!

    Hello

    We have had a query about whether it is possible to add a second Resource Type section to Primo VE in order to allow for an alphabetical searching option (our default sort is size of search results). I was sure this wasn't possible, but offered to create an idea here requesting to allow end users to choose how they sort the list of Resource Types.

    This would enable them to toggle between the two sort types, e.g. to see Newspaper Articles near Newspapers, but then to change back to 'size' sorting to see the largest number of results, etc.

    … 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

12. Enable logo image used in Primo to be resized without perfoming CSS customizations.

    Enable logo image used in Primo to be resized without perfoming CSS customizations.

    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

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

14. Make collection and subcollection names discoverable in the Collections lobby.

    Make collection and subcollection names discoverable in the Collections lobby. Currently, collection names and subcollection names are discoverable in Primo VE, but not discoverable in the Collections lobby.

    Example:

    We have a collection called: "Daher Folk Tales". It is discoverable in Primo VE:

    https://librarysearch.centennialcollege.ca/discovery/search?query=any,contains,daher%20folk%20tales&tab=Everything&search_scope=MyInst_and_CI&vid=01OCLS_CENTENN:CENTENN&lang=en&offset=0

    but not in the Collections lobby:

    https://librarysearch.centennialcollege.ca/discovery/collectionDiscovery?vid=01OCLS_CENTENN:CENTENN&query=any,contains,daher%20folk%20tales

    We would like all collections and subcollections to be discoverable by name in the Collections lobby, because we will soon have a long list of collections on the lobby page, and many, many levels of subcollections. This enchancement would nake it easier for users to find the right subcollection, without having to click through the entire hierarchy.

    Make collection and subcollection names discoverable in the Collections lobby. Currently, collection names and subcollection names are discoverable in Primo VE, but not discoverable in the Collections lobby.

    Example:

    We have a collection called: "Daher Folk Tales". It is discoverable in Primo VE:

    https://librarysearch.centennialcollege.ca/discovery/search?query=any,contains,daher%20folk%20tales&tab=Everything&search_scope=MyInst_and_CI&vid=01OCLS_CENTENN:CENTENN&lang=en&offset=0

    but not in the Collections lobby:

    https://librarysearch.centennialcollege.ca/discovery/collectionDiscovery?vid=01OCLS_CENTENN:CENTENN&query=any,contains,daher%20folk%20tales

    We would like all collections and subcollections to be discoverable by name in the Collections lobby, because we will soon have a long list of collections on the lobby page, and many, many levels of subcollections. This enchancement would nake it easier for users to find the right subcollection,… 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…)
    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. Enhance possibility to show information out of linked authority records

    Introduce new Authority Info Card based on Linked Data URI. Utilize Linked Data URIs to present new Information Card in various displays (search results list, brief & full display). Enrich the display with more information on linked entities and related resources made available thanks to the URI. This functionality should be provided for all authority sources available in the Community Zone that offer linked data URIs such as GND, Rameau, etc.

    6 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. Expandable facets beyond the number we set

    Recently it has become possible in VE to display up to 50 facets. 50 tries the patience of the average user but may be what it takes to help those with more specific needs. In some cases CDI limits the number anyway. It would be better if more facets are available this could be noted at the bottom by a "more" link which would then display more than the default number. This would be more consistent with other ways Primo displays complexity.

    35 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

17. add a link to the location section

    We would like to be able to create an embedded link to the location section in PRIMO VE (please see image attached)

    This embedded link would then be added to a libguide to provide real time information on the location of the item

    •  

    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

18. Make the Resource Recommender Banner fit the length of the resource description

    The banner description text is truncated in the first line, making the display of the description dependent on its length and even shorter when viewed on mobile devices. It would be great if the height of the banner would auto-adjust to show all the text.

    I attach images showing this (banner.png) and how we would like it to be displayed (banner_modified.png).

    Thanks

    •  

    •  

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

19. Additional Function:Excludes unnecessary resource types in Specialized Search Scopes for CDI

    ■Idea
    When configuring "Specialized Search Scopes for CDI"　https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/040Search_Configurations/010Configuring_Search_Profiles_for_Primo_VE
    in Primo VE, currently only 5 CDI resource types can be selected, so we want to change the system that unnecessary resource types can be excluded.

    ■Context
    Regarding "Exclude eBooks from CDI Results - Phase 2 (NERS #6702)", In Phase 1, all books were excluded from search, but after Phase 2, some books remain in the search results.

    To exclude books for this reasons,we would like to set the "Specialized Search Scopes for CDI" with limited number of CDI resource types.
    But the maximum number of resource types that can be selected is too few, so we would like the system to be changed so that unnecessary resource types can be excluded.

    This function allows scopes to be more limited to specific resource types.

    ■Idea
    When configuring "Specialized Search Scopes for CDI"　https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/040Search_Configurations/010Configuring_Search_Profiles_for_Primo_VE
    in Primo VE, currently only 5 CDI resource types can be selected, so we want to change the system that unnecessary resource types can be excluded.

    ■Context
    Regarding "Exclude eBooks from CDI Results - Phase 2 (NERS #6702)", In Phase 1, all books were excluded from search, but after Phase 2, some books remain in the search results.

    To exclude books for this reasons,we would like to set the "Specialized Search Scopes for CDI" with limited number of CDI resource types.
    But the maximum number of resource types that can be… more

    16 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

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