162 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. "Give Us Feedback" tool / "Report a problem": separate e-mail addresses

   We have been waiting for this enhancement for a long time:

   Give Us Feedback Tool (NERS "Report a problem for records in Primo") / Primo May 2022 release:
   https://knowledge.exlibrisgroup.com/Primo/Release_Notes/Primo/2022/001Primo_2022_Release_Notes

   Since full-text links in Primo are displayed in different places and come from different sources (Alma "View it" section, CDI - "Link in record", Primo Link section), the "Report a Broken Link" option is of course difficult to implement. The "Report a Broken Link" feature as it was available in SFX (an option directly at each full-text link) would of course be more intuitive for the users, but unfortunately it is not implementable that way in Primo.

   The e-mail that is sent now contains "only" the link of the current Primo search or full display page and everything else (e.g. which link does not work) must be specified by the users in the "Description" field.

   Since the Feedback tool is not displayed directly with the links, the tool can also be used for other feedback options, such as the predefined "Report a Search Issue" and two other options.
   This is nice, but unfortunately the implementation here is not optimal.

   Only one feedback e-mail address can be defined. But different problems are handled by different departments, e.g.:
   Broken links --> e-resources department.
   Search Problems --> Helpdesk team
   etc.

   It would be fine to be able to define separate e-mail addresses for each option. This should be easy to implement with the new mapping table "Report a Problem".

   Thank you in advance!

   We have been waiting for this enhancement for a long time:

   Give Us Feedback Tool (NERS "Report a problem for records in Primo") / Primo May 2022 release:
   https://knowledge.exlibrisgroup.com/Primo/Release_Notes/Primo/2022/001Primo_2022_Release_Notes

   Since full-text links in Primo are displayed in different places and come from different sources (Alma "View it" section, CDI - "Link in record", Primo Link section), the "Report a Broken Link" option is of course difficult to implement. The "Report a Broken Link" feature as it was available in SFX (an option directly at each full-text link) would of course be more intuitive for the users, but unfortunately it is… more

   24 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  ·  User Functionality  ·  Delete…  ·  Admin →
   Completed  ·  AdminYael (yael.shahar@clarivate.com, Ex Libris) responded

   This is to update that in November we've added the option to set different email address per category.

   
   

   Best regards,

   Yael.

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

5. A new type of search - Authority Search

   Add Authority Search as a new type of search in Primo. The new feature will enable both patrons and librarians to search the authors and topical subjects from their authority records and link to the related records in their local catalog(s) and preferably also CDI.
   The search will be based on alma's authority files and Linked Open Data.

   This development was part of the Primo roadmap for 2021 and was removed.

   A similar search option was implemented at the University of Haifa using local customizations and a dedicated search scope + view.
   It enables to search a term only on authority records and displays double-sided links: from the term's authority record to its occurrences as authors or subjects in the bibliographic records, and from a bibliographic record (in the regular Primo search) to the authority terms in the authority scope.

   A short video for a demonstration: https://shellyaridor-haifauniv-lib.tinytake.com/msc/Njg0MTgwNl8xOTQ5NzQ5MA

   (*) To support this feature also in Primo via Back Office, Alma APIs should publish authority information as XML records Primo can use.

   Add Authority Search as a new type of search in Primo. The new feature will enable both patrons and librarians to search the authors and topical subjects from their authority records and link to the related records in their local catalog(s) and preferably also CDI.
   The search will be based on alma's authority files and Linked Open Data.

   This development was part of the Primo roadmap for 2021 and was removed.

   A similar search option was implemented at the University of Haifa using local customizations and a dedicated search scope + view.
   It enables to search a term only on… more

   48 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  ·  User Functionality  ·  Delete…  ·  Admin →
   Completed  ·  AdminYael (yael.shahar@clarivate.com, Ex Libris) responded

   This was delivered as part of the May 2024 release - you may find more details about this feature in the release notes under "Support Discovery of Local Authority Records" -

   https://knowledge.exlibrisgroup.com/Primo/Release_Notes/002Primo_VE/2024/010Primo_VE_2024_Release_Notes?mon=202405BASE

   
   

   
   

   
   

   Regards,

   Yael.

6. Add 'Search in full text' toggle parameter to the URL so that it is retained

   Ex Libris introduced a new 'Search in full text' toggle in the Primo May 2022 Release, with the option for a site to set a default while also empowering users with the autonomy to change the setting to meet their needs.
   This was an excellent range of configuration options for both sites and users, but unfortunately there is a significant flaw.
   If a user does choose to change this setting from the default, and then uses other Primo features such as sharing the search with colleagues by QR Code link, or saving the search for their own re-use by setting a Save Search Alert, or if they need to communicate an issue with their library via the Report a Problem tool, then this key information is not included. The user's current search is also disrupted to lose this choice, if the user needs to refresh the browser for some reason, which is quite common for factors such as needing to clear cache for link navigation.
   This lack of URL element is in stark contrast to the existing expanded search toggle to include results not available in full text, which adds &pcAvailability=true / false to the URL, and has none of the UI problems detailed above.
   From a user perspective, it is completely hidden that this particular choice is not retained, and there is no indication or explanation why one expansion setting is saved but not the other.
   When this was raised, Ex Libris has responded that: "After discussions with product management, they have clarified that not having the URL parameter is intentional and by their design. They have stated the following: When the Primo FE UI page is refreshed, the option will go back to the default. This is because the parameter is not part of the URL, because changing it is costly and more risky."
   It is unfortunate that the price of saving development time is negative impact on the usefulness and consistent behaviour of a new feature for users, with basic usability factors not considered before rolling out a feature, and leading to this idea exchange submission.

   Ex Libris introduced a new 'Search in full text' toggle in the Primo May 2022 Release, with the option for a site to set a default while also empowering users with the autonomy to change the setting to meet their needs.
   This was an excellent range of configuration options for both sites and users, but unfortunately there is a significant flaw.
   If a user does choose to change this setting from the default, and then uses other Primo features such as sharing the search with colleagues by QR Code link, or saving the search for their own re-use by setting… more

   •  

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

   This was done in February 2023 release.

   
   

   Best regards,

   Yael.

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

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

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

10. Add Resource type `Questionnaires` to CDI

    One of the central CDI collections in Israel is the Szold Research Tools collection.

    This collection specializes in questionnaires used in dissertations and theses. However, the resource type is shown as Other, as there is no Questionnaires resource type currently in CDI.

    This resource type is important to the academic community in several fields of study, and is searched widely by our patrons in Primo.

    Libraries are also continuously cataloging questionnaires, created and translated by researchers within the institutions.

    Since there is no common ground between CDI and local questionnaires, using advanced search or filtering the facet for questionnaires prevents users from getting all relevant records.

    Adding this resource type to CDI will help make display and search\filtering better and more coherent for users.

    One of the central CDI collections in Israel is the Szold Research Tools collection.

    This collection specializes in questionnaires used in dissertations and theses. However, the resource type is shown as Other, as there is no Questionnaires resource type currently in CDI.

    This resource type is important to the academic community in several fields of study, and is searched widely by our patrons in Primo.

    Libraries are also continuously cataloging questionnaires, created and translated by researchers within the institutions.

    Since there is no common ground between CDI and local questionnaires, using advanced search or filtering the facet for questionnaires… more

    105 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  ·  3 comments  ·  Other  ·  Delete…  ·  Admin →

11. Enable creation of Carousel widgets for collections

    We would love to be able to create scrolling carousels to highlight collections, and embed them in other platforms (LibGuides, webpages, etc.) We see examples of this kind of carousel within Primo VE records, for materials that are in Collection Discovery (aka Digital Collections); at the bottom of the record there is a feature labeled "More from the same collection" with a link to the full collection in Collection Discovery as well as a scrolling carousel of images with the book jacket images and links to the other titles. We would like to be able to embed this kind of feature in other resources.
    It would be great if it were possible to establish and share code for these kind of carousels, to enable highlight of and link to Alma/Primo materials. Digital Collections is one example of a use case, but carousel widget creation for other selected sets might also be a boon.
    Different institutions may be taking different local development approaches to create these sorts of tools, so it would be great if Ex Libris could help develop something everyone could share.

    We would love to be able to create scrolling carousels to highlight collections, and embed them in other platforms (LibGuides, webpages, etc.) We see examples of this kind of carousel within Primo VE records, for materials that are in Collection Discovery (aka Digital Collections); at the bottom of the record there is a feature labeled "More from the same collection" with a link to the full collection in Collection Discovery as well as a scrolling carousel of images with the book jacket images and links to the other titles. We would like to be able to embed this kind of… more

    •  

    97 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  ·  Integration with other systems  ·  Delete…  ·  Admin →
    Completed  ·  AdminYael (yael.shahar@clarivate.com, Ex Libris) responded

    Hi,

    This is to update that the Primo showcase widget was released in February 2024 release.

    For more details see:

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

    Best regards,

    Yael.

12. Display pagination navigation on top of resultpage

    Following the new pagination experience (May 2021 release), our users would like to see the pagination navigation also at the top of their resultpage.

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

    This functionality is available since February 2023 release.

    
    

    Best regards,

    Yael.

13. Ability to set the default value for Results Per Page

    With the improved pagination experience (May 2021 release), it would be great if we could have the ability to set the default number of results per page. Instead of the default value of 10, we would like the ability to set the default value to 25.

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

    This is available from February 2023 release.

    
    

    Best regards,

    Yael.

14. Make persistent search history a user customizable option

    Would like to have this option be at the user level instead of the system level: https://knowledge.exlibrisgroup.com/Primo/Knowledge_Articles/How_to_disable_the_option_to_save_authenticated_user's_search_history

    I realize users can delete individual searches at anytime, but if they don't want any searches saved there is no way for them to do this. Since this can't be controlled at the individual user level, for privacy concerns we have to disable it at the system level and therefore users who might not have privacy concerns do not get to benefit from the feature.

    65 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  ·  User Functionality  ·  Delete…  ·  Admin →
    Completed  ·  AdminYael (yael.shahar@clarivate.com, Ex Libris) responded

    This feature is now available in the August 2022 release

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

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

17. Number and sort the volumes in multi-volume works

    With the March 2021 release we got "Related Link for Series Added Fields 80X-83X", which is a big improvement.

    But in the list of volumes, the volumes are not sorted and they are missing their volume number.

    How this looks:
    https://basel.swisscovery.org/permalink/41SLSP_UBS/mmbbsj/alma993707790105504 (see also screenshot 1)

    How it should be looking: see screenshot 2

    Ex Libris considers this a feature enhancement request.

    (SF00934664, SF00930520)

    329 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…)
    17 comments  ·  User Interface  ·  Delete…  ·  Admin →
    Completed  ·  AdminNili Natan (Product Manager, Ex Libris) responded

    With the Primo VE March 2022  the related titles will be grouped by the relation type (such as Contains)  and within each group relations will be sorted alphabetically by title

18. Improve webhook availability/links display for Newsbank/Access World News

    Ex Libris has collaborated with Newsbank/Access World News to enable the use of a search webhook to enable content discovery within the Primo/Primo VE platform -- which is great! However, we are finding the current display of availability and links within the Newsbank webhook largely unusable, preventing us from implementing within our public production environment. The problem is that no online availability statement is displayed in results list nor brief record display, and no View Online area appears in the record. The results and records appear exactly the same as content outside of our full text results -- EXCEPT for a small link labelled "Read document" within the Links area at the bottom of the record. This makes it very confusing for our users, and very difficult for us -- since the labels, links, and other display elements are the opposite of what we teach users to look for in identifying and accessing full text resources.
    
    Documentation at https://knowledge.exlibrisgroup.com/Primo/Product_Materials/Discover_Primo_Feature_Overviews/Primo_Search_Webhook includes an example webhook for Project Gutenberg in which the results list does display "Online Access" and links to Gutenberg are included within the "View Online" area. Can this improved display/functionality be incorporated into the Newsbank webhook?

    Ex Libris has collaborated with Newsbank/Access World News to enable the use of a search webhook to enable content discovery within the Primo/Primo VE platform -- which is great! However, we are finding the current display of availability and links within the Newsbank webhook largely unusable, preventing us from implementing within our public production environment. The problem is that no online availability statement is displayed in results list nor brief record display, and no View Online area appears in the record. The results and records appear exactly the same as content outside of our full text results -- EXCEPT for… more

    13 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Integration with other systems  ·  Delete…  ·  Admin →
    Completed  ·  AdminNili Natan (Product Manager, Ex Libris) responded

    Thank you for posting this idea. with Primo VE August 2021 release , the Read Document link will be accessible also from the "How to Get It " section to improve user navigation.

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

20. Collection Discovery usage in Primo Analytics

    Currently, Analytics possibilities for "Collection Discovery" are rather limited. With action “Display a Collection”, you can for example see how many times your collections (all together) have been displayed, added to favorites... in a period of time, but you cannot see which collections are the most and the less successful, what materials should maybe be more promoted, which collection should maybe be removed because its content is maybe of too little interest, which collections are added to favorites, etc.

    Therefore, we would like Collection IDs and Collection Names to be transferred to Primo Analytics. Additionally, if this could also be done for collection items (MMS ID and Title), this would be very useful too!

    Currently, Analytics possibilities for "Collection Discovery" are rather limited. With action “Display a Collection”, you can for example see how many times your collections (all together) have been displayed, added to favorites... in a period of time, but you cannot see which collections are the most and the less successful, what materials should maybe be more promoted, which collection should maybe be removed because its content is maybe of too little interest, which collections are added to favorites, etc.

    Therefore, we would like Collection IDs and Collection Names to be transferred to Primo Analytics. Additionally, if this could also be… more

    •  

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

    Hi all,

    This option it now available with the August 2023 release, via the new Analytics subject area - Primo Customized Values Usage

    
    

    Best regards,

    Yael.