Versions Compared

Old Version 5

changes.mady.by.user Maureen Elizabeth Driscoll

Saved on

compared with

New Version 6

changes.mady.by.user Kara Young

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Acquisitions/Finance

Resolved

Course Reserves/Leganto

  • Enhancements

    • New “No List expected” list option indicator (NERS 7744) to indicate that course does not have a reading list (visible in Course Information tab). The “No List expected” option sticks upon course rollover or duplication.The No list expected indication will be added to Analytics in the February release.
    • Now when selecting the Reset X after searching for items within a list, the search term clears and the results are reset (Ideas Exchange).
    • To describe the attribute more accurately and match the analytics term, the Publication Status attribute was changed to Publication List Visibility. 

  • Resolved

    • In some cases, completed citations appeared in the Ready for Processing task list. This was fixed.
    • Previously, the Leganto UI language did not update until the page was refreshed. This was fixed.

Resource Management

Resolved

  • An error resulted when 'Push Selected to MDE' button was pressed when adding a title to a collection. This was fixed and the 'Push Selected to MDE' button was removed from adding titles to collections.
  • Japanese: The U+202F NARROW NO-BREAK SPACE character was not converted to a normal space character (as was already done for U+3000 IDEOGRAPHIC SPACE (also known as double-width space)). It has now been added to the list of character conversions done when the customer parameter solr_searching_language = jp.
  • Display of Additional Staff Search Fields does not support special characters. This was fixed and the fields now support special characters.
  • In some cases, sorting search results by a field other than the default 'Rank' led to zero results. This has been fixed by introducing a new customer parameter - 'temp_apply_schema_template_for_non_rank_sort'. Its default value is 'false'. When it is set to 'true', changing the sorting field does not change the results in such cases.
  • Creating a set using an Excel file with empty lines caused an error. This was fixed and these lines are now skipped.
  • New Metadata Editor: Clicking CMD + click for rows multi-selection in the editor in macOS does not work. This was fixed.
  • When testing a normalization rule, changes made without saving in the bib record are not considered in the preview. This was fixed. 
  • New Metadata Editor: When the CP 'font_for_special_characters' is enabled, the font size is smaller. This was fixed.
  • There were some values of the KORMARC control-field 008 that were missing for the rare book record type. This was fixed and all values were added.
  • New Metadata Editor: The 'expand from template' menu action was incorrectly enabled for Community Zone records. This was fixed and the menu action is now disabled in such cases.
  • New Metadata Editor: When a user with the correct role tries to duplicate a template, the new template can’t be saved or edited. This was fixed. 
  • MARC21 > "7xx authority" records containing subfield $$e. The subfield is duplicated when linking it to the bib record. This was fixed.
  • Analytics is lacking the labels for 2 values in the Authorities Heading Subject details (Chronological Subdivision, General Subdivision). This was fixed. The labels have now been added.
  • Linked 880 fields were using punctuation rules for 8XX fields instead of from the linked field. This has been fixed.
  • Metadata configuration list - Authority vocabularies list was not displayed when there was a local authority of type 'DCMI'. This was fixed and now the authority vocabularies list is displayed.
  • For some users, opening the 'Monitor and View Imports' page took a long time. This was fixed. The loading time for this page was enhanced and the performance was improved. 
  • Sequence number Maintain job: When running on a set that includes more than one record, the sequence number was not updated in the database. This was fixed. Saving sequences that already existed in the DB (compare based on prefix and sequence number), will 'skip' over all the existing sequences instead of creating duplications. In addition, the Job report will reflect all the skipped sequences. 
  • Records marked for merge are sometimes not merged correctly in Alma. This was fixed. Two new counters were added to the job report for the SBN alignment jobs: 'Record not merged - non-preferred record doesn't exist in Alma' and 'Record not merged - preferred record doesn't exist in Alma'. This should reduce the number of records that are included in the 'Failed to merge records' without explanation.
  • SBN Alignment job - Adding a new schedule option was added (everyday at 20:00).