41 results found

1. Display item policy in item record

   It would be useful if item policy could be configured as a field to display in either the brief or full item display. Currently, the loanable indicator is defined by the fulfillment terms of use, which is dependent on users signing in in order for Primo to calculate the loan policy specifically for that user.

   Having the option to display the item policy from Alma as a field in Primo would be beneficial as this does not change dependent on the user type or fulfillment rules. It would also provide more information to users irrespective of whether they are able to sign into Primo (e.g. users not affiliated to the institution will be unable to sign in) and makes it clearer and easier for staff to explain to customers why a particular item can/cannot be borrowed.

   It would be useful if item policy could be configured as a field to display in either the brief or full item display. Currently, the loanable indicator is defined by the fulfillment terms of use, which is dependent on users signing in in order for Primo to calculate the loan policy specifically for that user.

   Having the option to display the item policy from Alma as a field in Primo would be beneficial as this does not change dependent on the user type or fulfillment rules. It would also provide more information to users irrespective of whether they are able… more

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

   Hi all,

   This enhancement is now available with the Primo VE August 2023 release.

   To learn more on this, see - 

   https://knowledge.exlibrisgroup.com/Primo/Release_Notes/002Primo_VE/2023/010Primo_VE_2023_Release_Notes?mon=202308BASE

   
   

   Best regards,

   Yael.

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

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

3. Ex Libris should allow customers to call or have an online chat with their support team

   We are disappointed with the technical support service provided by Ex Libris. We strongly believe that Ex Libris should provide customers with more effective, prompt and interactive service.

   There should be an option to call or chat online in real time with a support person who has a sound understanding of the product in question. This would be in line with all system vendors we have previously dealt with.

   We appreciate that there will be some issues that are designated as bugs or enhancements and will require more in depth investigation. However, a direct call/chat option with a properly trained support analyst would quickly and efficiently separate these issues from more general product queries. We are aware that there are many call-logging options used widely by other companies, such as FastCall, TenFold and RingDNA, which can be used to allow customer calls/chats to be registered directly in Salesforce. We believe that Ex Libris should implement this improvement as soon as possible.

   Please vote to show your support for this idea and feel free to add comments relating to your experience of this issue.

   We are disappointed with the technical support service provided by Ex Libris. We strongly believe that Ex Libris should provide customers with more effective, prompt and interactive service.

   There should be an option to call or chat online in real time with a support person who has a sound understanding of the product in question. This would be in line with all system vendors we have previously dealt with.

   We appreciate that there will be some issues that are designated as bugs or enhancements and will require more in depth investigation. However, a direct call/chat option with a properly trained… more

   347 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   8 comments  ·  Primo VE  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   Completed  ·  AdminNili Natan (Product Manager, Ex Libris) responded

   Ex Libris will start the phased rollout of online chat support for Primo VE in November 2020. Updates to the community will follow as we progress with the rollout.

4. Customizable Collection Discovery according to PrimoVE views

   It'll be great if, according to the view, you can see specific collections displayed in the Collection Discovery.
   Currently, Collection Discovery is the same regardless of the view, which goes in detriment of the user experience.

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

   This is now available in the August 2022 release

5. 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 →
   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
   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.

6. Utilize data from multiple fields (LDR and fixed fields 006,007,008) in Primo VE resource type configuration

   Related to a previous idea now marked as Completed
   (see: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/35488570-utilize-ldr-and-marc-fixed-fields-006-007-008-in)

   The functionality introduced in the April 2019 release only allows you to specify ONE field in the source MARC record that contains the resource type that you want to map to the local resource type.

   Primo VE should to be able to determine the resource type from combinations of data in MORE THAN ONE of the fields in the MARC record; i.e. fixed-field coding in the 006/007/008 field in conjunction with the LDR field.

   This is particularly crucial for complex resources not coded as language material (LDR pos. 06 = a) as changing LDR position 06 to m for computer file or p for mixed materials changes the definitions of positions 18-34 in the 008 field.

   Data in the LDR/006/007/008 fields cannot be assessed in isolation, but must be combined together in order to accurately determine the resource-type.

   Related to a previous idea now marked as Completed
   (see: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/35488570-utilize-ldr-and-marc-fixed-fields-006-007-008-in)

   The functionality introduced in the April 2019 release only allows you to specify ONE field in the source MARC record that contains the resource type that you want to map to the local resource type.

   Primo VE should to be able to determine the resource type from combinations of data in MORE THAN ONE of the fields in the MARC record; i.e. fixed-field coding in the 006/007/008 field in conjunction with the LDR field.

   This is particularly crucial for complex resources not coded as language material (LDR pos.… more

   281 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   8 comments  ·  Primo VE  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   Completed  ·  AdminNili Natan (Product Manager, Ex Libris) responded

   In Primo VE August 2020 we have added the option to add up to four conditions when defining custom resource type. With this we attempt to cover the need to define multiple conditions while keeping indexing performance time

   See in release notes of August 2020 https://knowledge.exlibrisgroup.com/Primo/Release_Notes/002Primo_VE/2020/010Primo_VE_2020_Release_Notes

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

8. 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…)
   25 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
   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

9. Primo VE: Need for new ‘Discovery Manager’ roles

   Create Discovery Manager roles and give customers the possibility to assign Discovery roles to colleagues who are in charge of specific content updates in the front end (notably Tag management, Resource Recommender management, Primo Central Index activations/deactivations) and who are not necessarily Primo administrators. For more flexibility and granularity, different roles (or parameters to add?) should be created. For example, a staff user in charge of Resource Recommender management should not necessarily have access to PCI activations.

   Subject and reference librarians could directly work in Alma in order to keep recommended resources, tags and PCI collections updated; tasks where traditional Primo administrator skills are not required. Currently, a single 'Discovery – Admin’ role concentrates too many responsibilities and functionalities.

   Create Discovery Manager roles and give customers the possibility to assign Discovery roles to colleagues who are in charge of specific content updates in the front end (notably Tag management, Resource Recommender management, Primo Central Index activations/deactivations) and who are not necessarily Primo administrators. For more flexibility and granularity, different roles (or parameters to add?) should be created. For example, a staff user in charge of Resource Recommender management should not necessarily have access to PCI activations.

   Subject and reference librarians could directly work in Alma in order to keep recommended resources, tags and PCI collections updated; tasks where traditional… more

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

   Thank you for posting this idea. with the new Primo VE August 2021 release , we have added two new Discovery roles – View Management Role and Discovery Operator Limited – to cover the needs raised in this idea. More details can be found in the Release notes

10. Barcode search in Primo

    It would be extremely helpful it we could search Primo VE by item barcode. We often want to quickly locate a bib record in Primo and scanning a barcode is the simplest and quickest search.

    172 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  ·  8 comments  ·  Primo VE  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Bib MARC field 505$t should be indexed in the Primo PNX file as a title entry

    The MARC 505$r is indexed in the PNX as Creator and contributor. The MARC 505$t is not similarly indexed in the PNX as an added or alternate title.

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

    Thank you for posting this idea. with the Primo VE June 2021 release Primo VE will index the 505 $t as well. This will be gradual rolled out pending the semi-annual indexing process planned to be completed by August.

12. Primo VE: add peer-reviwed and open access facet values to local records

    In Primo VE you can add an OpenAccess indicator to the records, but it should also be possible to add a value (bases on normalization routines) that includes these records into the OA facet value in the top-level facets, so they are included when using this filter. This option should apply to both Alma records and external data records.

    The same normalization option should be available for the Peer-reviewed indicator and facet value

    142 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    4 comments  ·  Primo VE  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    Completed  ·  AdminNili Natan (Product Manager, Ex Libris) responded

    Thank you for this suggestion. you can define Peer Reviewed and Open Access facet in local catalog more details can be found in Primo VE August and June release notes

13. 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 →
    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. Utilize LDR and MARC fixed fields (006,007,008) in Primo VE resource type configuration

    Currently it's not possible to utilize LDR and MARC fixed fields (006,007,008) in Primo VE resource type configuration. It would be helpful, if regular expressions could be used to utilize these fields. That way facets could be created for DVDs, Blu-Ray discs and streaming video etc. without workarounds, using standard cataloging.

    There is a similar idea already posted for Advanced Search, but we were advised by Ex Libris to list this separately.

    104 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
    Completed  ·  chaniy responded

    This functionality is now available in Primo VE April 2019 release.

15. 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 →
    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. 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 →
    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
    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.

17. Ability to select/set preferred record criteria for dedupe/FRBR in Primo VE

    We have instances where records for print materials in our holdings are combined with records for e-resources, to display a single record with multiple access points in our catalog. That is good and expected. However, often the source record is an e-resource record rather than the record for our physical holding, and we would prefer that the record for our physical resource be used so that important local notes are sure to be displayed. When the record for an e-resource is used instead, our local notes are not displayed, and that is a big problem.

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

    This is part of Primo VE June release.

18. 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 →
    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
    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.

19. 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 →
    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. Allow HTML in Collection Discovery description field

    It would be useful to allow HTML in the description field of an Alma Collection record. It would allow some formatting and links out to other pages. Currently any HTML displays as text.

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

    Hi,

    This is now supported on February 2024 release.

    
    

    Best regards,

    Yael.