NERS

NERS #8126: Ability to do a bulk export of search results (VE/BO)

Total Votes: 6469

Request:

In a recent user survey, students provided feedback they would like the ability to export all or a large number of their search results. Currently, they are limited to a maximum of 50 results at a time. Users reported they had worked to create a search strategy and were disappointed they could not obtain a full list of their search results, and were forced to move to searching individual databases instead. Please add an option to export all or a larger number of search results such as 1000 results at a time. Users have an expectation that this is 'standard' functionality for a search interface. 

High Level Solution:

• New option will be available in the user interface to support the bulk export of search results. We may offer the users to export: current selection, current page or entire results - limited to X results (X will be determine in implementation phase).

• Users can select to export search results in the following formats: CSV/Excel, RIS or BIBTEX.

• The new export option will be available only for signed-in users (we can add notification for guests users to sign-in to use this option).

• Users will be requested to fill in the target email to send the exported file to (we may also add the from address using the signed-in main address).

• File will be sent by email as attachment once the bulk export process will be completed. As mentioned, this action will be invoked in the background and will allow the users to continue to work in Primo while export process is running. As for the time to expect the exported search results - this will be determined in the implementation phase. 

• The exported file will not display the search results in the same order as displayed in the user interface. Justification for that: users will use this exported file to import the search results in citation managers.  We plan to invoke light-weight search APIs in both CDI and Local to support the mass export (In blended search we may show results sorted by date - all of this will be determined in implementation phase).

• There is also performance impact of which fields will be exported in the bulk upload and we will also take this in consideration while implementation (for example exporting abstracts from CDI). We will also not include fields that require to invoke delivery call (Library location for example).

Status: Design phase.

NERS #8210: Prevent search results expansion by use of exact phrase (VE/BO)

Total Votes: 5654

Request:

There is no ability to prevent search results expansion term inflection by use of exact phrase, either in Advanced Search by exact phrase or by quotation marks, or with Boolean operators, with associated loss of ability to do targeted specialized searches. Testing and cases have shown that the ‘Verbatim match boost’ and higher ranking for direct term match over variations such as spelling and synonyms are not succeeding in ensuring that all results are meaningful and targeted to match user queries. Negative impact: Makes it more challenging to perform specialized searches. Proposed solution: Using quotation marks and Boolean operators should generate more precise search results See additional information: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/41092123-remove-cdi-constant-expansion-of-results. 

High Level Solution:

Today in CDI, we apply language-specific text analyzers to both indexed terms and search terms. For example, the term “students” appearing a record will be indexed as “student”. The current payload mechanism as discussed, is used to support the current verbatim match boosting feature meaning boosts the relevance scores of verbatim matches between search terms and indexed terms, without excluding non-verbatim matches.  

The proposed enhancement is to modify CDI’s search algorithm to use the same payload mechanism to limit the matches to verbatim matches only when double quotes are used. meaning in this cases we will ignore other variations.

• As mentioned this solution will be limited to searches on metadata fields -> it will not include full text searches (as we don't save the original terms to exclude in case of "")

• Differences in diacritics and other character variations will be considered to be non-verbatim matches. They will not be cross-searchable with double quotes. Examples:  

  • fiancé vs. fiance

  • 大學 vs. 大学

Status: Design phase.

NERS #8134: Allow HTML coding in labels, public notes and collection description (VE/BO)

Total Votes: 5284

Request:

Allow HTML coding in labels, public notes and collection discovery description, including a href for links.

High Level Solution:

We will allow HTML coding in the following specific labels list, which was provided by the community:

Phase 1:
c.uresolver.availableOnline.service_is_temporary_unavailable
nui.search.error.ui.server.error.header
nui.search.error.ui.server.error
nui.mypref.label.errorSavingSettings
specificChapterPages
brief.results.tabs.Get_it_from_other_locations_no_services
email.note
nui.ngrs.no.offer.message.termsAndConditions.first
almaResourceSharing.header
almaResourceSharing.formDescription
almaResourceSharing.article / almaResourceSharing.book
almaResourceSharing.formatPhysical / almaResourceSharing.formatNoneReturnable / almaResourceSharing.formatDigital

In addition we added HTML support in the following:
Citation Disclaimer - citation.labels.disclaimer

Public notes in GES in how to get it section
Collection discovery label - nui.colldiscovery.lobby.description
Collection discovery description coming from Alma (coming from Alma response for each collection)

Phase 2: We will receive an additional list from the community and will add support for those labels as well.

Status: Phase 1 is available with the Primo and Primo VE February 2024 Releases; Phase 2 will be available with their November 2024 releases.

NERS #8157: Preserve the formatting of citations copied from Primo (VE/BO)

Total Votes: 3503

Request:

Primo's citation tool copies citations to the clipboard in plain text format, causing all formatting to be lost. In order to preserve citations in the correct formatting, this tool should be modified to allow citations to be copied in rich text format. 

High Level Solution:

Previously, the Citation export action copied citations to the clipboard in plain text format, but the citation's formatting (such as italics) was lost when copying it to a document (such as Word). The Citation export action will now save the citation to the clipboard in Rich Text Format (RTF) and will retain the citation's formatting when copied to Word documents. When using a text editor such as Notepad, the text will be copied without formatting.

Status: Available as of Primo VE November 2023 Release.

NERS #8141: Add ability to configure the display at the item level and the location level in the Get It section (VE)

Total Votes: 1102

Request:

In Primo, 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. If there are items in more than one location, the first display is at the location level. In large 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 whether the first display in the GetIt section is at the item or the location level when only one library is visible. 

High Level Solution:

Today when there is only one location, we automatically display the item's level under Get It.
The new configuration will allow you to choose whether to display the Get It at the location level or item level when there is only one location available.

Status: Available with the Primo VE February 2024 Release.

• Article last edited: 25-December-2023