42 results found

1. New Book List in Primo VE

   I would love to have in-built Primo VE functionality to showcase the new book list in Primo VE, like Trinity College (https://ctw-tc.primo.exlibrisgroup.com/discovery/search?vid=01CTW_TC:CTWTC&lang=en) did using this alternatively, but not everyone is that techy, so please consider adding this in upcoming releases.

   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 →
   Completed  ·  AdminNili Natan (Product Manager, Ex Libris) responded

   This can be achieved embedding the Primo Showcase

   https://developers.exlibrisgroup.com/blog/primo-showcase-how-to-embed/

   
   

2. Add ability to configure the display at the item level and the location level in the GetIt section

   In Primo VE, the display of the GetIt section works currently as following:
   If there are only items in one location, the first display after opening the full view is at the item level (example: https://eth.swisscovery.slsp.ch/permalink/41SLSP_ETH/lshl64/alma99118073204005503).
   If there are items in more than one location, the first display is at the location level (example: https://eth.swisscovery.slsp.ch/permalink/41SLSP_ETH/lshl64/alma990104195490205503).
   Because our libraries are part of a huge consortium, our users always have to check first in which library an item is available before checking the item information. Furthermore, we believe that the user experience would be better, if the GetIt section looked always the same at first glance. We therefore wish that libraries can configure in Primo VE whether the first display in the GetIt section is at the item or the location level.

   In Primo VE, the display of the GetIt section works currently as following:
   If there are only items in one location, the first display after opening the full view is at the item level (example: https://eth.swisscovery.slsp.ch/permalink/41SLSP_ETH/lshl64/alma99118073204005503).
   If there are items in more than one location, the first display is at the location level (example: https://eth.swisscovery.slsp.ch/permalink/41SLSP_ETH/lshl64/alma990104195490205503).
   Because our libraries are part of a huge consortium, our users always have to check first in which library an item is available before checking the item information. Furthermore, we believe that the user experience would be better, if the GetIt section looked… more

   •  

   •  

   9 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Primo VE  ·  Delete…  ·  Admin →
   Completed  ·  AdminYael (yael.shahar@clarivate.com, Ex Libris) responded

   Hi,

   This is to update that this was developed for February 2024 release.

   
   

   Best regards,

   Yael.

3. Remove field 655 from the subject facet

   In Primo VE the 655 are shown in the Subject facet. As the 655 relate to form and not to content, they should not be shown as subjects. Furthermore, the 655 are correctly shown in the “Genre” facet.

   The 655 should be excluded from the Topic facet in the Facets Section Mapping:
   https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/120Other_Configurations/Mapping_to_the_Display%2C_Facets%2C_and_Search_Sections_in_the_Primo_VE_Record#Facets_Section_Mapping

   54 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…)
   Completed  ·  7 comments  ·  Primo VE  ·  Delete…  ·  Admin →

4. New Tool-Give Us Feedback

   The Give Us Feedback Tool should perform a validity check of the email address. Currently it is possible to enter anything in the field 'Enter your email'. The email address validation is commonly used by default within forms.

   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…)
   2 comments  ·  Primo VE  ·  Delete…  ·  Admin →
   Completed  ·  AdminYael (yael.shahar@clarivate.com, Ex Libris) responded

   Hello,

   This is completed and was released in November release.

   
   

   Best regards,

   Yael.

5. Relevancy sorting in FRBR version list display should use terms searched

   FRBR groups and the display of versions within them does not consider the relevancy of the terms searched. Often a user is searching for a specific version within the FRBR group (ex: Homer's Iliad translated by Richmond Lattimore) but there is no way to focus in on this version within the list of FRBR versions. Even when users search specifically for terms: Iliad Lattimore, Lattimore is hidden within search results. Within the list of FRBR versions, sorting by Relevancy should use the terms searched by the user -- this should enable the works of a single translator (like Lattimore) to rise to the top of the list of results when that translator's name is explicitly included in the search, greatly improving discoverability and access.

   FRBR groups and the display of versions within them does not consider the relevancy of the terms searched. Often a user is searching for a specific version within the FRBR group (ex: Homer's Iliad translated by Richmond Lattimore) but there is no way to focus in on this version within the list of FRBR versions. Even when users search specifically for terms: Iliad Lattimore, Lattimore is hidden within search results. Within the list of FRBR versions, sorting by Relevancy should use the terms searched by the user -- this should enable the works of a single translator (like Lattimore) to… more

   209 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…)
   28 comments  ·  Primo VE  ·  Delete…  ·  Admin →
   Completed  ·  AdminYael (yael.shahar@clarivate.com, Ex Libris) responded

   In this enhancement, Primo VE will highlight the selected record on top of the list of  FRBR versions, only for the preferred record mode.

   We understand from the comments here that there is also a request to add this option for Generic mode, however in the generic mode we only show a link to the list of versions and not pointing for a specific record. In Generic mode we don't show any actions or availability status, and there is no option to open a full mode as this is not a specific representation of the record.

   This is why we have chosen to implement this only for preferred mode.

   Please provide some more clarifications for the generic mode request in a dedicated idea.

   
   

   Best regards

6. ShareDigitalResources parameter to allow individual settings

   When the customer parameter shareDigitalResources is enabled, which is useful to allow freely available digital representations (for digital objects stored in Alma or in a remote digital repository) to be available to all institutions, records loaded from external data sources via discovery import profiles are also impacted by this. According to Ex Libris, this is by design as these records from external sources are considered as digital objects. This leads to the following problem in Primo:

   As soon an IZ enables this parameter, its records from external data sources are included in the search results of local search scopes made in other IZs local views. Generally all external data sources which are shared with the network, should be part of the results for searches within the Discovery-Network-scope and not be part of the My-Institution-scope of an IZ which has no corresponding import profiles configured in their IZ Alma. (see details in SF 00992268).

   An enhancement should allow the flexibility to define which resources are impacted by the customer parameter shareDigitalResources and which are not, such as the resources from external data sources.

   When the customer parameter shareDigitalResources is enabled, which is useful to allow freely available digital representations (for digital objects stored in Alma or in a remote digital repository) to be available to all institutions, records loaded from external data sources via discovery import profiles are also impacted by this. According to Ex Libris, this is by design as these records from external sources are considered as digital objects. This leads to the following problem in Primo:

   As soon an IZ enables this parameter, its records from external data sources are included in the search results of local search scopes made… more

   132 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…)
   Completed  ·  1 comment  ·  Primo VE  ·  Delete…  ·  Admin →

7. Make it possible to add or exclude records from the OTB resource display types based on locally-defined conditions

   We would like to have more flexibility with Primo VE resource types and the related facet and prefilter values. There are situations in which we would like to be able to add records to an OTB resource display type that don't meet the OTB conditions. For example, for certain textual integrating resources that users are likely to think of as books, we use conditions based on the presence of form/genre headings to add them to the OTB ""book"" display type in Primo BO (e.g., open textbooks that are periodically updated: https://searchit.libraries.wsu.edu/permalink/f/j5jme3/CP71251613210001451). Conversely, we would sometimes like to be able to exclude records from a particular OTB display type.
   Here are two possible ways to accomplish this request:
   1) Make the OTB resource display type rules locally editable.
   2) Use a local field to override the OTB resource display type rule. For example, 999 $a could be defined as the local override field for resource types. Each OTB resource type could be associated with a code that could be added to 999 $a to force that record to have that OTB resource type.
   
   Conditions could be added to the OTB rules as follows in this example for conference proceedings:
   --If 999 is null, then execute the standard OTB rule for conference proceedings
   --If 999 is not null, then check if 999 = ""conferenceproceeding""
   -----If 999 = ""conferenceproceeding"" then mark record as conference proceeding #force include
   -----If 999 != ""conference_proceeding"" then do nothing #force exclude

   We would like to have more flexibility with Primo VE resource types and the related facet and prefilter values. There are situations in which we would like to be able to add records to an OTB resource display type that don't meet the OTB conditions. For example, for certain textual integrating resources that users are likely to think of as books, we use conditions based on the presence of form/genre headings to add them to the OTB ""book"" display type in Primo BO (e.g., open textbooks that are periodically updated: https://searchit.libraries.wsu.edu/permalink/f/j5jme3/CP71251613210001451). Conversely, we would sometimes like to be able… more

   299 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 →
   Completed  ·  AdminYael (yael.shahar@clarivate.com, Ex Libris) responded

   The option to customize the mapping for OTB resource types will be available in May 2023 release.

   
   

   Best regards,

   Yael.

8. Add more options to configure facets by prefilter and resource type

   The configuration options for facets in Primo VE are currently very limited, and not at parity with Primo on Back Office. It is not currently possible in Primo VE for a single record to have multiple facets or prefilter resource type values, to better align with CDI in a blended search, it is not possible to configure the facet and prefilter resource type values separately and independently of the display resource type values, and these facets cannot be configured with sufficient granularity. As examples of this configuration issue to be made possible with this request: Example 1: Our display types are mostly based on physical format: print books, ebooks, microforms, audio CDs and so on. However, because we are able to apply multiple facet values to a record, those items above might also be able to facet as a dissertation or conference proceeding, etc. Our users are accustomed to being able to facet or limit by those multiple values. This difference in behavior can be seen in a search for "conference" in Primo Back Office (https://tinyurl.com/1ouvijhn) vs. our test instance of VE (https://tinyurl.com/16j67u7t). In the Primo Back Office version, more records are identified as conference proceedings because we use more strategies to identify them as such. Also, if one limits to conference proceedings, they can then further limit by format, such as print book or audio CD. For prefilter, we also incorporate multiple resource types together into a single category (e.g., audio or video). This enables us to help users who are only interested in a specific format, such as streaming video, as well as users who wish to search for audio or video more generally. Example 2: As an example, we treat the audio and video resource types differently for facets and prefilter within Primo Back Office. For facets, we identify the specific resource type: e-audio/streaming audio, audio CD, audio cassette or LP. However, for prefilter, we incorporate these resource types together into a single audio category. Example 3: Applying the Local Resource Type “Microform” would replace the primary original resource type “Book,” “Journal,” “Map,” etc. – but in fact both the physical format “Microform” and the original resource type “Book” or “Journal” or “Map” would be needed.

   The configuration options for facets in Primo VE are currently very limited, and not at parity with Primo on Back Office. It is not currently possible in Primo VE for a single record to have multiple facets or prefilter resource type values, to better align with CDI in a blended search, it is not possible to configure the facet and prefilter resource type values separately and independently of the display resource type values, and these facets cannot be configured with sufficient granularity. As examples of this configuration issue to be made possible with this request: Example 1: Our display types… more

   417 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 →
   Completed  ·  AdminYael (yael.shahar@clarivate.com, Ex Libris) responded

   This is to update that this is now supported in August 2022 release

9. Correct citations for local Articles and Book chapters

   Articles and Book Chapters from local sources (externals sources as well as Alma) don't have complete citations because data are missing in the mapping. Volume, issue and pages are not mapped.
   Our request is to provide a mapping for these data elements so that they can be added to the Addata section of te record, or to allow sites to normalise the data in this section so that we can provide correct citations and export functionality.

   96 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…)
   Completed  ·  1 comment  ·  Primo VE  ·  Delete…  ·  Admin →

10. Enhance the database search to include keyword searching

    Currently the Database Search in Primo VE is limited to searching for words from the title. This is unsatisfactory as many databases have vague and uninformative titles. We need broader search capabilities and would like the search to also include categories, subjects and descriptions.

    91 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 →
    Completed  ·  AdminNili Natan (Product Manager, Ex Libris) responded

    Primo expands the Database Search to include all search fields, such as subject and description. Previously, searches performed in Database Search matched only on the title. In addition, if configured the expanded DB search functionality will also allow users to search by category name.

11. Campus level settings for CDI Link in Record

    Discovery Customer Settings are only configurable at the institution level.

    It makes CDI Link in Records broken for multi-campus environments with separate subscriptions to vendors like Gale, Infobase, and Kanopy.

    Please make customizable using Inventory Management Groups or Discovery Views.

    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…)
    3 comments  ·  Primo VE  ·  Delete…  ·  Admin →
    Completed  ·  AdminNili Natan (Product Manager, Ex Libris) responded

    Thank you for this idea, In Primo VE December 2020 release we introduce a new mapping table for managing the Central Index linking templates with your institutional linking parameters where you can also manage multiple linking templates per campus code.

12. Work with additional batches of 50 records after the first set of 50

    It's now possible to select and act upon a set of 50 records in Primo VE. However, once the first set of 50 records has been selected and saved to Favorites (or otherwise acted upon), all actions on additional records must be done manually, one at a time. After the first 50, the user gets the message, "Please edit your selection to include no more than 50 records." and then it is no longer possible to work with records in batch.
    For example, often a user will perform a search in Primo VE and find a set of 150 or more records of interest to their research. Currently, the user can Choose the Top 50 results and save to Favorites; then Load More Results, page by page (10 results per page); then Deselect the original 50 selected; then begin with record 51 and individually select each record to select records 51-100, and add to Favorites; then repeat the deselect, load more results, individually select records process to add records 101-150 to Favorites; and so on. Acting upon the first set of 50 records is easy, but the manual work to capture and work with records 51-150 (etc.) is both cumbersome and challenging.
    It would be great if it were possible to Choose the Next Top 50 Results to work with them in batch, as well.

    It's now possible to select and act upon a set of 50 records in Primo VE. However, once the first set of 50 records has been selected and saved to Favorites (or otherwise acted upon), all actions on additional records must be done manually, one at a time. After the first 50, the user gets the message, "Please edit your selection to include no more than 50 records." and then it is no longer possible to work with records in batch.
    For example, often a user will perform a search in Primo VE and find a set of 150 or… 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…)
    4 comments  ·  Primo VE  ·  Delete…  ·  Admin →
    Completed  ·  AdminNili Natan (Product Manager, Ex Libris) responded

    Thank you for this suggestions. The new pagination method will allow to select additional set of records and not only first top 50 records.
    This is coming with Primo May 2021 release and Primo VE June release.

13. Put the FRBR Dedup Test Utility where cataloguers can use it

    The FRBR Dedup Test utility is currently hidden in Discovery configuration (Primo VE). The team members who need to use this functionality are cataloguers so they can see what edits might be needed to troubleshoot issues preventing or causing unexpected FRBR/deduplication.

    Adding it to the Resources menu in Alma is an option, another might be for cataloguers to be able to trigger it when comparing records in the metadata editor.

    34 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    6 comments  ·  Primo VE  ·  Delete…  ·  Admin →
    Completed  ·  AdminNili Natan (Product Manager, Ex Libris) responded

    New discovery role is now available : Discovery Operator – Limited " so more library staff can get access to the FRBR Dedup Test Utility
    Check for more details in Primo VE release notes – under Allow Task-Oriented Discovery Roles for Staff

14. Boost Institutional Search Results in Primo VE

    We'd like the ability to boost our institutional results in a search profile slot that includes consortial records.

    46 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 →
    Completed  ·  AdminNili Natan (Product Manager, Ex Libris) responded

    Thank you for this idea. We added to Primo VE the Boost My Institution option to allow an institution in a consortium to boost its search results, over results from other member institutions.

15. Primo VE: allow translations in OTB Display Fields

    We 'd like the possibility to use translations in OTB Display fields, not only in local fields.
    Use case: we want to use a code for contributors & creators ($4), rather than tag Relator term ($e) and use the translation functionality to display this role in the language of the interface.

    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 →
    Completed  ·  AdminNili Natan (Product Manager, Ex Libris) responded

    Thank you for this suggestion. Primo VE now allows you to translate metadata in all or specific subfields from the Creator and Contributor display fields.

16. location displayed for resources sharing

    Do not display the resource sharing link for item that do not circulate. This is super confusing for our students. The request link does not display in the other scopes, but cannot seem to be turned off for resources sharing. Our students are requesting items from our sister college that do not circulate.

    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 →
    Completed  ·  AdminNili Natan (Product Manager, Ex Libris) responded

    Thank you for posting this idea. Please refer to Primo VE release note – January 2021 for more details on Central Definition for Hiding Resource Sharing Button – Based on Institutions Location List

17. Customizable RIS mapping table for Primo VE

    In Primo, customers could customize the RIS export table, to determine what PNX fields should be used for RIS fields. In Primo VE this is not possible:

    The mapping of the RIS fields to PNX fields is as follows:
    IS addata/issue
    TY addata/ristype
    N2 addata/abstract
    N1 addata/notes
    PB addata/publisher
    A2 display/contributor
    ET addata/edition
    KW display/subject
    EP addata/epage
    DO addata/doi
    PY addata/date ; display/creationdate
    JA addata/stitle
    VL addata/volume
    CY addata/cop
    AU display/creator
    T3 addata/seriestitle
    T2 addata/addtitle
    T1 display/title
    SP Addata/spage
    JF Addata/jtitle
    ID Alma MMS ID
    SN Addata/issn; addata/isbn; addata/eissn; addata/eisbn

    As most reference managers will read A2 as Series Editor, it would be helpful if the display/contributor could be conditioned to map to AU instead. This is just one example - and why the mapping should be customizable.

    In Primo, customers could customize the RIS export table, to determine what PNX fields should be used for RIS fields. In Primo VE this is not possible:

    The mapping of the RIS fields to PNX fields is as follows:
    IS addata/issue
    TY addata/ristype
    N2 addata/abstract
    N1 addata/notes
    PB addata/publisher
    A2 display/contributor
    ET addata/edition
    KW display/subject
    EP addata/epage
    DO addata/doi
    PY addata/date ; display/creationdate
    JA addata/stitle
    VL addata/volume
    CY addata/cop
    AU display/creator
    T3 addata/seriestitle
    T2 addata/addtitle
    T1 display/title
    SP Addata/spage
    JF Addata/jtitle
    ID Alma MMS ID
    SN Addata/issn; addata/isbn; addata/eissn; addata/eisbn

    As most reference managers will read A2 as Series Editor,… more

    58 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    3 comments  ·  Primo VE  ·  Delete…  ·  Admin →
    Completed  ·  AdminNili Natan (Product Manager, Ex Libris) responded

    Thank you for this idea . With the April 2022 release Primo VE allows you to customize the default mapping used to export records to RIS format.

18. Add Mandatory choices for all Request forms in Primo VE

    For the Digitization Request, Hold and Booking Request, and Purchase Request forms, the Alma mapping tables (under GetIt Configuration) define the fields that are displayed to users (Yes = viewable to users, No = not viewable to users).

    We would like to have the possibility to configure mandatory fields if we want the user to specify a field in the form (as it is already the case with a check box in the Resource Sharing Request form).

    223 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…)
    14 comments  ·  Primo VE  ·  Delete…  ·  Admin →
    Completed  ·  AdminNili Natan (Product Manager, Ex Libris) responded

    Thank you for posting this suggestion. Starting of VE July 2021 release you will have more options to improve requests forms: adding mandatory choices , adding forms’ description including links and add generic checkbox. more details can be found in Primo VE release notes

19. Improve new sort in collection discovery

    As of Nov 2019, we can sort a collection in collection discovery by "relevance" which seems to be arbitrarily applied and title.

    1. There should be the same sort options (as the main Primo results):
    2. Date (newest)
    3. Date (oldest)

    4. Author

    5. Institutions should be able to apply a default of choice

    6. Institutions should be able to remove a sort option

    22 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    6 comments  ·  Primo VE  ·  Delete…  ·  Admin →
    Completed  ·  AdminNili Natan (Product Manager, Ex Libris) responded

    Thank you for this suggestion. you can find now with Primo August release notes and Primo VE July release notes more details on the new sort options with also an option to set per collection the default sort.

20. Option to allow patrons to opt-in/ opt-out of sms from Primo VE my account tab.

    Currently there is no option to enable the sms opt-in option from PRIMO VE. This will allow patrons to enable/disable sms notification if they wish to from My Personal Details on PRIMO VE.

    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…)
    2 comments  ·  Primo VE  ·  Delete…  ·  Admin →
    Completed  ·  AdminYael (yael.shahar@clarivate.com, Ex Libris) responded

    Hi,

    This is to update that this functionality is now supported in Primo VE from February 2024 release.

    
    

    Best regards,

    Yael.