700 results found

1. 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 0 votes 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

2. 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 0 votes 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

3. 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 0 votes 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

   Submit Rating

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

5. 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 0 votes 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

6. 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 0 votes 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

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

8. 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 0 votes 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

9. 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 0 votes 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

10. 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 0 votes 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

11. Continue as Guest link on the authentication page

    To encourage more users to sign in to Primo, we would like to provide more links on our public website, in emails, and through signage that direct users to specific pages in Primo, such as the AI Research Assistant or My Library Account. These require authentication first. While this works for our current staff and students, such links may also be clicked by people who do not have an account.

    In this scenario, they are stuck on the authentication page with no option to opt out and get to the landing page. There is no top menu for them to choose from.

    An optional/configurable link that offers them a path to continue as a guest user and takes them to the landing page would be helpful.

    While this might also affect the sign-in window, it would not hurt to be there. It differs from the Cancel link, which simply closes the authentication pop-up – it does not take them to the landing page.

    In cases where we direct the user to a specific page via authentication, the same type of cancel link would not work. This enhancement would instead take them to the landing page, as they are not authorised to use these special areas of Primo.

    Example links:

    //DOMAIN/nde/login?vid={VID code}&toState=account/overview&toParams={"vid":"{VID code}","lang":"en"}

    //DOMAIN/nde/login?vid={VID code}&toState=researchAssistant&toParams={"vid":"{VID code}","lang":"en"}

    While these examples and screenshots are from NDE, this is something that we had previously wanted to do in Primo VE too.

    Related CERV enhancement request: https://enhancements.exlibrisusers.org/ideas/PENH-I-28464

    To encourage more users to sign in to Primo, we would like to provide more links on our public website, in emails, and through signage that direct users to specific pages in Primo, such as the AI Research Assistant or My Library Account. These require authentication first. While this works for our current staff and students, such links may also be clicked by people who do not have an account.

    In this scenario, they are stuck on the authentication page with no option to opt out and get to the landing page. There is no top menu for them to… more

    •  

    1 vote

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Add autocomplete to embedded searchbox

    Please add autocomplete to the embedded searchbox API for a consistent user experience.

    1 vote

    Vote 0 votes 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

13. Configuration for cubicle or space reservations

    Currently, the resource and space reservation functionality in Primo VE is very limited. It is necessary to enable configurations that make the reservation process faster and simpler. Among the required improvements are:

    • Adjusting the available reservation times according to the Library's opening hours, avoiding displaying time slots that are not relevant.
    • Allowing the Library team to configure only certain days, instead of automatically enabling all days.
    • Unifying the calendar system so that a single calendar is used to select the reservation date, instead of one for the start and another for the end.

    1 vote

    Vote 0 votes 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

14. Allow icons display in database search

    Allow display of images in database search results view for showing databases icons.
    It's the only menu in Primo where it's not possible. Makes no sense !

    1 vote

    Vote 0 votes 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

15. Add a field "Author Affiliation"

    Could you please add the field "Author Affiliation" for display? Currently, "Author Affiliation" is not displayable in Primo but only in search.

    1 vote

    Vote 0 votes 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

16. Dedup and FRBR Test Utility

    Could the Dedup and FRBR Test Utility (Configuration/discovery) have the ability to remember the last MMS ID numbers that were looked up? We seem to spend a lot of time going back and forth to the same records trying to get them to match and having to find and paste in the MMS of both, e.g. the print and the eBook records - usually from the Primo URL where I invariably pick up the preceding word, Alma. It would be great if it retained the last couple of MMS searched for to save a bit of time and effort.

    1 vote

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Support MARC field 857 (Web Archive Links) in Primo VE

    Please add support for MARC field 857 in Primo VE so that links stored in this field can be displayed in the Links section, similar to MARC field 856.

    Field 857 is increasingly used by libraries to store links to archived versions of web resources (e.g., web archive snapshots). Currently, these links are not displayed in Primo VE, even when the field is present in the MARC record.

    Supporting field 857 would allow libraries to expose web archive links and preserved web content directly to users and better support web archiving and digital preservation initiatives.

    Why this helps many institutions:

    • Web archiving is becoming more common in libraries and national libraries.

    • MARC field 857 is intended for archived web resources.

    • Displaying these links in Primo would improve access to preserved web content.

    Please add support for MARC field 857 in Primo VE so that links stored in this field can be displayed in the Links section, similar to MARC field 856.

    Field 857 is increasingly used by libraries to store links to archived versions of web resources (e.g., web archive snapshots). Currently, these links are not displayed in Primo VE, even when the field is present in the MARC record.

    Supporting field 857 would allow libraries to expose web archive links and preserved web content directly to users and better support web archiving and digital preservation initiatives.

    Why this helps many institutions:

    • … more

    1 vote

    Vote 0 votes 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. Display of Advanced Search Pre-filters in the “Searched for” section in the Advanced Search summary

    Currently, the “Searched for” section in the Advanced Search summary does not display complete pre-filter information. We believe it would be beneficial for users to see a complete summary of all search parameters, including any date range pre-filters applied in Advanced Search.

    For example, if a user searches with the following criteria:

    All Subjects contains exact phrase North Korea

    Resource Type: Books

    Date: 2016–2026

    the search results currently display only "Searched for: All Subjects contains exact phrase North Korea"

    We ask that the “Searched for” summary reflect the full set of applied filters, such as "Searched for: All Subjects contains exact phrase North Korea, Resource Type: Books, Date: 2016–2026"

    This would provide users with a clearer and more complete understanding of the search parameters they applied. Thank you.

    Currently, the “Searched for” section in the Advanced Search summary does not display complete pre-filter information. We believe it would be beneficial for users to see a complete summary of all search parameters, including any date range pre-filters applied in Advanced Search.

    For example, if a user searches with the following criteria:

    All Subjects contains exact phrase North Korea

    Resource Type: Books

    Date: 2016–2026

    the search results currently display only "Searched for: All Subjects contains exact phrase North Korea"

    We ask that the “Searched for” summary reflect the full set of applied filters, such as "Searched for: All Subjects contains… more

    1 vote

    Vote 0 votes 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

19. Add an "audiobook" indicator to CDI records

    We want to make it possible for our users to facet to and search more effectively for audiobooks.
    In CDI records, both non-musical and musical audio materials have the same resource type, audio, and there is no way to distinguish between non-musical and musical audio materials. Our researchers have identified this as an accessibility issue and barrier for use because they are not able to identify audiobooks in our Primo catalog. Locating audiobooks is important both for general research and to provide access for those needing audio formats.
    For local records, we can identify audiobooks by creating local/secondary resource types and assigning genre headings. These resource types and headings can then be used within pre-filters, facets, and field searching. We cannot enhance CDI records locally, so we would like the audiobook indicator to be added to and made available for faceting or other search features within CDI records.

    We want to make it possible for our users to facet to and search more effectively for audiobooks.
    In CDI records, both non-musical and musical audio materials have the same resource type, audio, and there is no way to distinguish between non-musical and musical audio materials. Our researchers have identified this as an accessibility issue and barrier for use because they are not able to identify audiobooks in our Primo catalog. Locating audiobooks is important both for general research and to provide access for those needing audio formats.
    For local records, we can identify audiobooks by creating local/secondary resource types… more

    1 vote

    Vote 0 votes 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

20. Enable exclusion of resource types in WorldCat 3rd party index scopes

    Many of our researchers prefer to search using a blended scope that includes WorldCat along with other Primo indexes. Despite the lack of facets for the WorldCat records and other caveats, this is a popular scope especially for advanced researchers. However, the inclusion of article records in the WorldCat index is unnecessary and confusing. Many of the WorldCat article records do not include sufficient metadata, although fuller metadata may be available in the records within WorldCat. The insufficiency of metadata results in the inability for accurate availability calculation and display of links to full text. Researchers may therefore place interlibrary loan requests for articles that are in fact available full text online with active links in better CDI records. This causes problems both for resource sharing and for researcher expectations. The WorldCat 3rd party index is not a good source for article searching for our institution, where CDI article records provide better discovery and access. We would like to be able to exclude article records from the WorldCat 3rd party index scope. We recognize that other institutions may want and use these records, so we would request the ability for institutions to select what resource types to include/exclude from a WorldCat scope, as is possible with CDI resource type selection in Central Index scopes.

    Many of our researchers prefer to search using a blended scope that includes WorldCat along with other Primo indexes. Despite the lack of facets for the WorldCat records and other caveats, this is a popular scope especially for advanced researchers. However, the inclusion of article records in the WorldCat index is unnecessary and confusing. Many of the WorldCat article records do not include sufficient metadata, although fuller metadata may be available in the records within WorldCat. The insufficiency of metadata results in the inability for accurate availability calculation and display of links to full text. Researchers may therefore place interlibrary… more

    1 vote

    Vote 0 votes 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