Primo February 2021 Release Notes
Features
Show Loading Indicator for Alma Get It and View It
February 2021 
NERS Enhancement (ID #6440) PRM-44007
Because View It and Get It require additional processing to fetch and load information, they may not load as quickly as other sections on the page. With this enhancement, an indication has been added to each section to let users know that information is still loading.
Configuration Options
This functionality requires no new configuration, but you can customize the indicator by modifying the following CSS in your customization package:
prm-alma-mashup{
iframe{
background-image: url("../img/diamonds-loading.gif");
background-repeat: no-repeat;
background-position: center;
}
}
Recent Search Suggestions
February 2021 PRM-43977
Previously when users typed their query, Primo displayed autocomplete suggestions based on the metadata index only. With this enhancement, autocomplete suggestions for Primo simple searches are extended to include suggestions based on simple searches stored in My Favorites > Search History.
When users select a recent search suggestion, Primo performs the search using the same search terms, tab, and scope of the matching search in Search History. Only the matching search and tab display for the recent suggestion.
-
Suggestions will start to appear after a user types at least two characters.
-
For all users, Primo will display only one recent suggestion, which is based on the most recent simple search in Search History.
-
For signed-in users, Primo will now retain the last 100 searches (including Advanced Search queries) in Search History. For more information, see Persistent Search History for Signed-In Users.
Configuration Options
This functionality is enabled by default at the institution level. If you would like to disable it, clear the Show Recent Search check box in the Institution Wizard (Primo Home > Ongoing Configuration Wizards > Institution Wizard).
Support Translation of Link in Record Label for CDI
February 2021 PRM-43449
Previously, CDI returned only the $$E subfield in the links/linktorsrc PNX field, which did not allow the link's label from being translated separately from the provider name. For example:
<links>
<linktorsrc>$$Uhttps://www.jstor.org/stable/resrep02650?pq-origsite=summon$$EAccess_content_in_JSTOR</linktorsrc>
</links>
With this enhancement, CDI will continue to support the existing $$E subfield but will add the $$F (label) and $$G (provider) subfields to allow the label to be translated. For example:
<links>
<linktorsrc>>$$Uhttps://www.jstor.org/stable/resrep02650?pq-origsite=summon$$EAccess_content_in_JSTOR$$FAccess_content_in$$GJSTOR</linktorsrc>
</links>
If the CDI record does not contain both the $$F (label) and $$G (provider) subfields, Primo will use $$E for the link in the Link section of the record's full display.
In addition, if CDI does not return provider-specific information but returns the default text without the provider in $$E, you may translate this default text.
<links>
<linktorsrc>$$Uhttp://hdl.handle.net/10256.1/2568$$EView_full_text_in_collection</linktorsrc>
</links>
Configuration Options
To support the customization and translation of the $$F and $$E subfields, you can now customize the following codes in the Full Display Labels code table, respectively:
-
default.fulldisplay.Access_content_in: Access content in {{provider}}
-
default.fulldisplay.View_full_text_in_collection: View full text in collection
Persistent Search History for Signed-In Users
February 2021 PRM-43977
Previously, search history was tracked per session and was not saved between sessions in My Favorites. For signed-in users, Primo will now store the last 100 searches in My Favorites > Search History so that they are retained for suggestions in future sessions. Selecting a search's Pin icon will copy the item to Saved Searches and remove it from Search History. Although the same search can appear in Search History more than once, you will not be able add the same search to Saved Searches more than once.
-
Under Search History, the row containing the date no longer includes the time at which the search was performed.
-
During a session, searches performed prior to sign-in are not retained after sign-in. After sign-in, Search History will include searches from previous sessions and new searches performed after sign-in.
Under Search History, users can easily remove searches from their history by selecting them either individually or in bulk and then selecting the Delete icon.
For information on how to disable this functionality, see How to disable the option to save authenticated user's Persistent search history.
UX Improvements to My Favorites
February 2021 PRM-41651
With this release the following usability improvements have been made to My Favorites:
-
When removing a record or group of records from My Favorites, users will now receive a prompt to confirm the deletion of the saved records:
Row Action to Remove a Single Item -
When adding or removing labels, the page no longer refreshes and focus stays on the current page.
-
After removing a record or records, the page will refresh and retain focus on the last item marked for deletion.
Configuration Options
This behavior does not require any configuration unless you want to customize or translate any of the following display labels in the Favorites Labels code table.
| Code | Description |
|---|---|
| default.nui.favorites.removeSingleItem | Remove this item? |
| default.nui.favorites.removeSelected | Remove selected items? |
| default.nui.favorites.remove.no | NO |
| default.nui.favorites.remove.ok | REMOVE IT |
| default.nui.favorites.removeSelected.no | NO |
| default.nui.favorites.removeSelected.ok | Remove selected |
Additional Enhancements
- February 2021 CDI-1840 SF: 866616
The following terms have been added to the English stemmer exception list:-
atlas -> atlas
-
cosmos -> cosmos
-
bias -> bias
-
andes -> andes
-
- February 2021 PRM-44598
Primo has been upgraded to JDK 11. For more details, see Upcoming Issues to Note. - February 2021 PRM-43901 SF: 503579
For Hebrew searches, cancelling the distance limitation between words solved issues raised when searching by Subject for the following examples: פרשנות ביאליק or צבא ופוליטיקה. Note that this change, which was as requested by the community, could affect the ranking in other cases. - February 2021 PRM-44149
Primo is now translated out of the box for Welsh. - February 2021 PRM-43223
The Basic search with pre-filter action under the Action Usage subject area is now sent to Primo Analytics with the search scope type. - February 2021 PRM-39579
Mixed directional text (including Hebrew) in brief display and details in full display is now ordered correctly. For more details, see Handling Bidirectional Text in Display Fields. - February 2021 PRM-41942
If a PNX record includes URIs. For example:<uri>$$Asubject$$VLongwall mining--Australia$$U(uri) http://id.loc.gov/authorities/subjects/sh85078310</uri>
<uri>$$Asubject$$VCoal mines and mining--Australia$$U(uri) http://id.loc.gov/authorities/subjects/sh93008548</uri>
Primo will now use JSON-LD to implement Schema.org. For example:
"about": [
{ "@type": "Thing", "name": "Longwall mining--Australia", "sameAs": [ "(uri) http://id.loc.gov/authorities/subjects/sh85078310" ] }
,
{
"@type": "Thing",
"name": "Coal mines and mining--Australia",
"sameAs": [
"(uri) http://id.loc.gov/authorities/subjects/sh93008548"
]To learn more about Schema.org in Primo, you can inspect the element of Schema.org within the record's Full Display.
Resolved Issues
- February 2021 PRM-41567 SF: 621134, 739249
The First Page Results columns in the Primo Action Usage subject area were not adding up to 100%. This has been fixed. - February 2021 PRM-44648 SF: 903120, 912412
Static date for OAI pipes was being overwritten. This has been fixed. - February 2021 PRM-44770 SF: 901731
Pre-filter options (md-focused class) were not cleared after simple search. This has been fixed. - February 2021 PRM-44611
Removed redundant online_PC_TN filter and will continue to use the online_resources filter. - February 2021 PRM-43974 SF: 870555, 880737, 886277, 886917, 890125, 890455, 898173, 904736
Citation trail is displayed inconsistently for Full and Brief results. This has been fixed. - February 2021 CDI-1409 SF: 866418
ISBN precedence in CDI search algorithm. This has been fixed. - February 2021 CDI-1248 SF: 892429
Searches failed for generic searches such as science. This has been fixed. - February 2021 CDI-994 SF: 809739, 873891, 899266
Added and removed Hebrew synonyms in CDI. This has been fixed. - February 2021 CDI-324 SF: 878144, 429850
For CDI, added terms to the British American synonym files. - February 2021 CDI-318 SF: 591805, 100810
Searches in which a number contains a comma or period returned a different number of results. This has been fixed. - February 2021 PRM-44627 SF: 794705
Increased the timeout of scheduled reports to 10 minutes in Primo Analytics. - February 2021 PRM-44622 SF: 911766
The security vulnerability with bundle.js.map has been fixed. - February 2021 PRM-44602 SF: 911386
There was a Cross-site Scripting (XSS) vulnerability issue under basket.do. This has been fixed. - February 2021 PRM-44403 SF: 891007
The Forgot Password link was not accessible with the TAB key. This has been fixed. - February 2021 PRM-44329 SF: 890819
If one of the pairs was missing from addata (aulast-aufirst), initials were missing from APA citation. This has been fixed. - February 2021 PRM-44326 SF: 648000
For Primo Analytics, the word undefined incorrectly displayed on a monthly basis in the Popular Searches report. This has been fixed. - February 2021 PRM-44290 SF: 899786
For drop-down lists, no indication was given to the focused value when using keyboard arrows. This has been fixed. - February 2021 PRM-44267 SF: 653863, 647187, 727645, 743285, 835300, 859333
Summary holdings and Notes were truncated with ellipses. This has been fixed. - February 2021 PRM-43974 SF: 870555, 880737, 886277, 886917, 890125, 890455, 898173, 904736
The Citation trail was displayed inconsistently for Full and Brief results. This has been fixed. - February 2021 PRM-43971 SF: 868699, 874929, 875813, 876820
Newspaper Search results for filtered searches contained 'No full text' records for customers enabled with CDI. This has been fixed. - February 2021 PRM-43875 SF: 849320
Snippet calls occasionally returned no information. This has been fixed. - February 2021 PRM-43656 SF: 852529
Changed the type of the Mendeley entity types mapping table so that it will not be overwritten after SP. - February 2021 PRM-43421 SF: 689325
The OTB Alma MARC - Template contained superfluous rules 4-6 for control/almaid. This has been fixed. - February 2021 PRM-43275 SF: 827943
The MMS ID was missing from the Alma UNIMARC template. This has been fixed. - February 2021 PRM-43099 SF: 823551
No aria label was provided for the See all versions link. This has been fixed. - February 2021 PRM-43046 SF: 792371
In Safari, the alternative text for Sign Out button was signOut instead of Sign Out. This has been fixed. - February 2021 PRM-43045 SF: 819555
item filters were not applied after selecting Show more items. This has been fixed. - February 2021 PRM-42951 SF: 817479
The DYM suggestion ID was displayed without original diacritics. This has been fixed. - February 2021 PRM-42846 SF: 807200
For the Alma Dublin Core - Template, collection records had an incorrect control/colldiscovery. This has been fixed. - February 2021 PRM-42691 SF: 792387, 792469
For accessibility no skip links were provided to go from facets to the Apply Filters button. This has been fixed. - February 2021 PRM-42212 SF: 739817
In the Full Record Display, many aria labels were either unhelpful or could not be customized. This has been fixed. - February 2021 PRM-40797 SF: 661298, 794787
The Boost down functionality on the stem part of a query was not working. This has been fixed. - February 2021 PRM-39660 SF: 574295, 628026
The Alma Dublin Core Template was using a non-existing mapping table. This has been fixed. - February 2021 PRM-36906 SF: 459472
An issue with the normalization rules created a duplicate entry when the source was PNX and the action was MERGE. This has been fixed.