647 results found

1. Adding Facets on Citation Trail in Primo VE

   Adding Facets on Citation Trail in order to filter results.

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Collection discovery - have an alert when using unsupported elements such as emoji

   Hello,
   In Alma Under Add New Collection Fields for Name and Description fields: "Non-text characters such as emojis are not supported."
   In fact, they cause a major side effect : the codes are then no longer translated into labels throughout Primo.
   I suggest:
   - either correcting this dysfunction
   - or, if emoji are prohibited (I'm personally not a fan of them for corporate communications), setting up an alert for the user when they attempt to include them in the relevant fields.
   Sincerely,

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Develop web browser bookmarking tool/extension for pre-populating Purchase Request

   With the recent development of the Order It tool, we have realised that for our purposes, we would like to have a similar toll available related to Purchase Requests.

   Quicker, easier more accurate.

   The form would help keep things accurate without giving access to order it to ordering librarians and help us utilise the requester information in the purchase request form (ours is behind a login and restricted to set user group)

   The tool would grab and place the metadata from websites such as amazon, waterstones, and our suppliers, place the information into the purchase request form (which for us requires login and grabs that person’s information) to help make purchase request easier and simpler for our librarians ordering in this way.

   As this is a tool which requires being added to browsers, I would expect it to be something that library controls giving out the link to install.

   Submitted to CERV 2025 - PENH-I-28305

   With the recent development of the Order It tool, we have realised that for our purposes, we would like to have a similar toll available related to Purchase Requests.

   Quicker, easier more accurate.

   The form would help keep things accurate without giving access to order it to ordering librarians and help us utilise the requester information in the purchase request form (ours is behind a login and restricted to set user group)

   The tool would grab and place the metadata from websites such as amazon, waterstones, and our suppliers, place the information into the purchase request form (which for us… more

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Allow conditionality/logic toggles for fields in Primo Forms

   Description: Currently the Resource Sharing Request form is fixed/non-customisable in the options available, e.g. format everything is available Digital or Print. However, for some circumstances we need to hide the options that don't apply to the request being made (see use case below) Given that conditionality/logic toggle is in the form for the chapter fields, this would is an additional application of the existing functionality in Primo forms, but that we could control.

   Use Cases: Where we can only provide a resource type in one way (print or electornic) we want the selection of resource limits the format type appearing ont he form AND give us the option ot make a default too. We currently cannot offer whole book Resource Sharing requests in electronic format, only print. If someone requested an entire book as an ebook, we have to contact them and give them other options, alter the request at that point. Extra confusion and frustration for user. Extra work for staff. We need the ability to customise what is available on the form based on selection. e.g. Book AND Chapter not ticked, only the print option appears. We also would like for conditionality to be available for other elements are well, e.g. should we be able to provide eBooks for resource sharing again, we would like to be able to alter the default format (digital or print) based on the resource type being requested (e.g. whole book = default print, article = default digital)
   Submitted to NERS 2024 and CERV 2025 (PENH-I-28351)

   Description: Currently the Resource Sharing Request form is fixed/non-customisable in the options available, e.g. format everything is available Digital or Print. However, for some circumstances we need to hide the options that don't apply to the request being made (see use case below) Given that conditionality/logic toggle is in the form for the chapter fields, this would is an additional application of the existing functionality in Primo forms, but that we could control.

   Use Cases: Where we can only provide a resource type in one way (print or electornic) we want the selection of resource limits the format type appearing… more

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Administrative Tools  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Recommendation system for learning and research resources

   Academic libraries increasingly act as an ecosystem for learning and research resources. Therefore, they need a platform that can serve as an ecosystem to guide academic users.

   Target: Incorporate into Primo VE a recommendation system that, based on users' searches, gives recommendations at the resource level (e.g., article, book, book chapter, case study, image, thesis, etc.).

   Output: After the user searches, Primo VE provides a list of prioritized learning or research resources, sorted by their thematic relevance or visualisation-based popularity.

   Parameters: The recommendation system should match the query with the users' profile (e.g., career, under|postgraduate level, etc.) after they log into the system.

   Academic libraries increasingly act as an ecosystem for learning and research resources. Therefore, they need a platform that can serve as an ecosystem to guide academic users.

   Target: Incorporate into Primo VE a recommendation system that, based on users' searches, gives recommendations at the resource level (e.g., article, book, book chapter, case study, image, thesis, etc.).

   Output: After the user searches, Primo VE provides a list of prioritized learning or research resources, sorted by their thematic relevance or visualisation-based popularity.

   Parameters: The recommendation system should match the query with the users' profile (e.g., career, under|postgraduate level, etc.) after they log… more

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Add a Collection title field for Collection Discovery, for full record display and search

   Adding records to a collection in Collection Discovery automatically adds them to the out-of-the-box Digital Collections facet in main Primo by the Collections title value.
   It would be a significant boost to discovery of these resources both individually and collectively in the main Primo environment if there was also a Collection title field available to be added to the full record display, which could be configured as a lateral hypertext link, and searchable by the collection title as keywords.
   This would marry together the main Primo environment with the Collection Discovery environment, with the ability to travel between each to find the related content, and taking advantage of options in main Primo such as saving the collection title query as a saved search alert, navigating by the next and previous result arrows through the collection content, filtering by facets such as author or subject, and exporting all the records.

   Use case: I am an academic looking to add works by Aboriginal and Torres Strait Islander authors to my teaching materials for my courses. I’d like to be able to search Primo by keywords for my course content as well as the terms like Aboriginal and Torres Strait Islander authors, find a record and open it to review the details, and click on the lateral hypertext link for the Aboriginal and Torres Strait Islander authors collection to find all the content available for review.
   Another use case is the same scenario but for academics looking for Open Educational Resources to add to their course content, for many libraries who use Collection Discovery to bring together OER content in their collections.

   Note: This is not currently possible to do by a local field as the Collection ID is not available as a bibliographic record data reference to map in the Collection Title to each record PNX. A local field can be used in a very manual way by adding rules for mapping the harvest point for a record and then adding the collection title, but this limits collection content to bibliographic data and does not leverage the ability to manage collections by logical sets using physical titles in location codes and all works with specific Authority IDs.

   Adding records to a collection in Collection Discovery automatically adds them to the out-of-the-box Digital Collections facet in main Primo by the Collections title value.
   It would be a significant boost to discovery of these resources both individually and collectively in the main Primo environment if there was also a Collection title field available to be added to the full record display, which could be configured as a lateral hypertext link, and searchable by the collection title as keywords.
   This would marry together the main Primo environment with the Collection Discovery environment, with the ability to travel between each to… more

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Functionality  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Add a uniqueness comparison check for local fields in a dedup record, and only display one instance of a non-unique field

   It became possible in November 2024 to display instances of a local field from all records in a Dedup record in Primo VE (Configuration > Discovery > Other > Local fields to display from all dedup members).
   The feature displays up to 10 instances of a field from records in the dedup group.
   This is a useful and welcome development to ensure patrons have access to all the metadata of the work.
   However, there is an issue that the data displays regardless if it is exactly the same in multiple records, despite that there is no usefulness for a patron to display the exact same data more than once, and it looks like an error to do so.
   Unfortunately Ex Libris has advised this is “expected” from the perspective that they have not developed this feature to do a comparison check to prevent multiple instances of display when the data in a field is exactly the same in multiple records dedup’d.
   Note: This is not an issue in Primo BO, where only one field displays when the content is not unique.
   This submission is for Primo VE to perform a uniqueness comparison check and only display one instance of the local field in a dedup record if the metadata is exactly the same.

   It became possible in November 2024 to display instances of a local field from all records in a Dedup record in Primo VE (Configuration > Discovery > Other > Local fields to display from all dedup members).
   The feature displays up to 10 instances of a field from records in the dedup group.
   This is a useful and welcome development to ensure patrons have access to all the metadata of the work.
   However, there is an issue that the data displays regardless if it is exactly the same in multiple records, despite that there is no usefulness for a patron… more

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Interface  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Consistent display of the "Search Inside" feature for Journal, Magazine, and Newspaper records

   Primo VE was developed in 2017 with a "Search Inside" feature, originally appearing only on Journal type records. In 2019 when CDI was developed Newspaper and Magazine types were added to the discovery environment.
   Unfortunately It appears that Ex Libris forgot to consider local records holistically, despite that Newspaper is an out-of-the-box configured type for Alma in Primo VE and many of their customers offer a blended search experience for their patrons.
   This is evidenced in an inconsistency that Search Inside displays on Newspaper records from CDI and fails to display on Newspaper records for local records. It will also not display on Magazine type local records, if a site chose to configure this.

   Ex Libris initially advised that they would consider correcting this, as part of a SalesForce case seeking to have the current functionality explained and documented. Finally after 10 months it was explained why the feature appearance was found to be inconsistent:
   “Local records—If the record has an ISSN (contains an addata/issn or addata/eissn field) and is a journal. To identify a journal, the display/type field must start with the word journal, or the record must contain an addata/jtitle field (not an addata/btitle or addata/atitle field).
   CDI records—If the record has an ISSN (contains an addata/issn or addata/eissn field) and is a periodical. To identify a periodical, the display/type field must start with the word journal, or the record must contain an addata/jtitle field (not an addata/btitle or addata/atitle field), or the addata/format and addata/genre fields must be set to journal. If the above criteria are met for CDI records, this section may also appear for magazines and newspapers.”

   These varying conditions mean that the feature does not display in Alma Newspapers, because the addata/jtitle field is not currently populated, as there is only as stitle not only for Newspaper type content, and there is no addata/format and addata/genre populated.
   Primo VE customers have no configuration options to fix this, with no access to addata PNX rules.
   And to add insult to injury, this inconsistent Search Inside feature also cannot be disabled by configuration, only by custom code application, for which Ex Libris explicitly does not provide support.

   Unfortunately Ex Libris ultimately advised after a year of the case being open that they would not fix this situation, documented the current inconsistency for Search Inside, and refused to engage further.

   This enhancement request is for the Search Inside development to be addressed holistically and simply, to display Search Inside consistently by the display type of Magazine, Newspaper or Journal regardless of data source, when the record contains an ISSN/EISSN.

   Primo VE was developed in 2017 with a "Search Inside" feature, originally appearing only on Journal type records. In 2019 when CDI was developed Newspaper and Magazine types were added to the discovery environment.
   Unfortunately It appears that Ex Libris forgot to consider local records holistically, despite that Newspaper is an out-of-the-box configured type for Alma in Primo VE and many of their customers offer a blended search experience for their patrons.
   This is evidenced in an inconsistency that Search Inside displays on Newspaper records from CDI and fails to display on Newspaper records for local records. It will also… more

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Interface  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. AI based tool for suggesting alternative search queries to users with saved searches and email alerts

   I was wondering if there could be an AI based tool for suggesting alternative search queries to users who have saved searches and have set email alerts. When they receive an email alert they could be suggested an AI generated search query (similar to what the AI Research Assistant could elaborate, with synonyms and boolean operators) to be checked for more results.

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Increase the maximum number of viewable records

    Currently the max number of viewable records is 2000. If the number of search results exceeds 2000, paging beyond the first 2000 records is prevented.

    If the limit is increased, users can continue to view search results beyond the first 2000 records without having to try and refine their search which may be difficult to do.

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  User Functionality  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Primo Research Assistant Recibir nuevos datos estadísticos

    Una de las recientes adquisiciones dentro del sistema ALMA tiene que ver con la integración del asistente de investigación, una inteligencia artificial que facilita la búsqueda de información por medio de consultas que el usuario hace, en la que la respuesta se sujeta con la documentación existente en el acervo electrónico del sistema bibliotecario.

    Al ser tan útil esta herramienta, en nuestra institución nos importa direccionar a los usuarios la información que más les puede resultar útil, y los resultados que ofrece el asistente de investigación pueden beneficiar a esta meta.

    Hemos explorado los reportes que Primo puede generar, en particular, “Primo Research Asistant”, sin embargo, esta información ofrece datos sobre las selecciones del usuario, si acceden o no al archivo.

    Nos interesa saber si podemos extraer otros datos dentro de la plataforma, como lo son:
    • Consultas dentro del asistente de investigación
    • Temática o documento que se muestra en los primeros resultados que muestra el asistente
    • Número de veces que el usuario hace copia de la información que el asistente de investigación genera
    • Número veces que se usa el asistente de investigación en un periodo específico de fechas
    • Datos del usuario que hace uso del asistente de investigación
    • Porcentaje de recursos institucionales y externos que muestra el asistente de investigación en la respuesta de un estudiante

    Una de las recientes adquisiciones dentro del sistema ALMA tiene que ver con la integración del asistente de investigación, una inteligencia artificial que facilita la búsqueda de información por medio de consultas que el usuario hace, en la que la respuesta se sujeta con la documentación existente en el acervo electrónico del sistema bibliotecario.

    Al ser tan útil esta herramienta, en nuestra institución nos importa direccionar a los usuarios la información que más les puede resultar útil, y los resultados que ofrece el asistente de investigación pueden beneficiar a esta meta.

    Hemos explorado los reportes que Primo puede generar, en… more

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Enable Full Support for Custom Meta Tags in the <head> of Primo VE Views to Improve SEO

    At present, Primo VE only allows institutions to configure the <meta name="description"> tag within the <head> of the HTML. Other essential metadata elements — such as <meta name="keywords">, <meta name="robots">, or custom meta tags for open graph and social media optimization — cannot be added or controlled through the platform’s configuration interface.

    While it is technically possible to include additional meta tags through the customization package, these elements are inserted into the <body> rather than the <head>, and therefore are not recognized by web crawlers. This limitation significantly reduces the ability of libraries and academic institutions to optimize their Primo VE discovery views for search engines and improve organic visibility.

    Enhancing SEO capabilities within Primo VE is particularly important for institutions that rely on open discovery to increase access to academic, research, and heritage resources. Allowing administrators to define comprehensive metadata in the <head> would make it possible for search engines to properly index and display discovery views, leading to broader discoverability and engagement.

    We propose that Ex Libris extend the SEO configuration options in Primo VE to include the ability to define and manage additional meta tags within the <head> section of the HTML. Ideally, these settings would be configurable per institution or per view, much like the current main.description field. Examples of useful additions include:

    <meta name="keywords" content="">

    <meta name="robots" content="">

    <meta property="og:title">, <meta property="og:description">, and other Open Graph tags

    This enhancement would bring multiple benefits:

    Improved organic ranking and visibility of library discovery portals in major search engines.

    Greater institutional autonomy to implement customized SEO strategies.

    Enhanced alignment with open access and digital scholarship initiatives that depend on online visibility.

    Better integration with current web standards and practices for discoverability and metadata management.

    Given the growing importance of digital visibility in higher education and research communication, this enhancement should be considered a high priority. It would empower libraries to position their Primo VE discovery environments as accessible, well-indexed, and SEO-optimized gateways to knowledge.

    At present, Primo VE only allows institutions to configure the <meta name="description"> tag within the <head> of the HTML. Other essential metadata elements — such as <meta name="keywords">, <meta name="robots">, or custom meta tags for open graph and social media optimization — cannot be added or controlled through the platform’s configuration interface.

    While it is technically possible to include additional meta tags through the customization package, these elements are inserted into the <body> rather than the <head>, and therefore are not recognized by web crawlers. This limitation significantly reduces the ability of libraries and academic institutions to optimize their Primo… more

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Integration with other systems  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Primo NDE change order of fields in request forms

    We would like to be able to change the order of the fields in the Request forms in Primo NDE

    For example: in the Request another Issue Digitization Request Form the 'Comment' field is in the middle of the form, and we would like it to be in a more consistent place, at the bottom of the form.

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  User Interface  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Primo VE Permalink Verification Process

    We would like a process to verify a file of Primo Permalinks are still valid for our institution.

    Our librarians and professors place Permalinks in online documents for our patrons. As the documents age and portfolio IDs change the links can fail. This is very frustrating for our patrons.

    The only link verification method today is to manually click on each permalink. This tedious and time consuming process is not cost effective when there are hundreds of links to check. Using standard web link checkers that operate in batch only establishes that a page does not result in an HTTP error.

    An Alma-specific verification process would help ensure the usability of web content that links to Primo. Ideally, a user could upload or paste a list of URLs into a tool, which would then check that each link resolves to a valid Alma or CDI record. As this relies on knowledge of both Alma and CDI record IDs, an external tool does not make as much sense as an ExLibris maintained solution.

    We would like a process to verify a file of Primo Permalinks are still valid for our institution.

    Our librarians and professors place Permalinks in online documents for our patrons. As the documents age and portfolio IDs change the links can fail. This is very frustrating for our patrons.

    The only link verification method today is to manually click on each permalink. This tedious and time consuming process is not cost effective when there are hundreds of links to check. Using standard web link checkers that operate in batch only establishes that a page does not result in an HTTP… more

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Administrative Tools  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Implementation of CDI rights at the article level and not just at the database and title levels

    CDI knows that a given article belongs to a given journal and knows that we have a subscription to it for this year (based on our SFX subscriptions). CDI therefore displays the article citation as part of the content to which we subscribe and creates an OpenURL link based on the citation metadata. If the citation in CDI is correct but this content does not exist on the platform, this generates errors in our catalogue and returns results that we do not have access to.

    ExLibris does not have rights at the article level (only at the database and title level), so Primo has no way of knowing that a particular article is not available on the platform.

    CDI knows that a given article belongs to a given journal and knows that we have a subscription to it for this year (based on our SFX subscriptions). CDI therefore displays the article citation as part of the content to which we subscribe and creates an OpenURL link based on the citation metadata. If the citation in CDI is correct but this content does not exist on the platform, this generates errors in our catalogue and returns results that we do not have access to.

    ExLibris does not have rights at the article level (only at the database and title… more

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Use all occurrences of a bibliographic field within GES Bib Field Enrichment

    Institutions can define which fields are extracted from the bibliographic record metadata to be used in General Electronic Services by adding fields to the GES Bib Fields Enrichment mapping table. However, if the bibliographic field occurs multiple times in the record, only the first occurrence of the field is used. This means that the GES is not calculated for any subsequent occurrences of the field. For example, if I want a GES to be displayed based on a particular value in a 590 local note, the GES will only display if that value occurs in the first of what may be many 590 local note fields. I request that all occurrences of the fields defined in the GES Bib fields enrichment mapping table be used in GES calculation for display in Primo records.

    Institutions can define which fields are extracted from the bibliographic record metadata to be used in General Electronic Services by adding fields to the GES Bib Fields Enrichment mapping table. However, if the bibliographic field occurs multiple times in the record, only the first occurrence of the field is used. This means that the GES is not calculated for any subsequent occurrences of the field. For example, if I want a GES to be displayed based on a particular value in a 590 local note, the GES will only display if that value occurs in the first of what may… more

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Allowing to opt out of loading OAI Repository records into Discovery Network

    Allowing to opt out of loading OAI Repository records into Discovery Network

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Allow hosted Back Office sites to use their own XSL transformation routines in data sources

    Primo documentation describes using XSL transformation routines to apply changes to records ingested to Primo from external sources (https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Primo/Back_Office_Guide/050Pipe_Configuration_Wizard/040Configuring_Data_Sources) but hosted sites are not able to see details of existing routine files or add their own.

    We would like to be able to add our own transformation file to handle a specific issue with harvested OAI metadata. Please make this possible or at least document the existing transformation routines so that we can see what they do.

    0 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  ·  Integration with other systems  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. customization package API

    Please add an API to deploy customization packages in Primo VE so that customers with many views can automate the cumbersome deployment process.

    0 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Administrative Tools  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Primo - "related titles sorted alphabetically by title" also for Primo direct / classic not VE

    In Primo VE one can have related titles sorted alphabetically by title
    This is particularly useful for multipart, journals, and in general complex record structure. Unfortunately, this is possible only in Primo VE, but not in classic Primo.
    It would be useful if the 2 versions of Primo were aligned also regarding this very useful feature.

    0 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  User Interface  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating