Versions Compared

Version Old Version 53 New Version 54
Changes made by

Jennifer Eustis

Charlotte Whitt

Saved on

Key

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

Week of April 4 Highlights

...

  • UIIN-1962 - Bugfest. Instance, holdings, item - edit view. Many data elements are misaligned (e.g. Identifiers, contributors, notes) Awaiting deployment
    • When viewing Instance, identifier pair values are misaligned. See also UIIN-1962 - Bugfest. Instance, holdings, item - edit view. Many data elements are misaligned (e.g. Identifiers, contributors, notes) Awaiting deployment
  • UIDEXP-270 - The search box is reset after updating filter in the Select transformations Open
    • Data Export: The search box do not contain searching value when User filtering result list by Record type in the Select Transformations
  • MODINV-550 - Bound-with-parts gets an empty collection Open
    • Bound-with parts get empty collection
  • UIIN-1927 - Bugfest. Inventory. Item selector box in the top of the instance record cause great confusion In progress
    • For Lotus R1 2022. Fix the box to select which holdings to move to another instance to make sure it is more visible.
  • MODDATAIMP-649 - Data Import job creates duplicate marc records for a few records in the import file In progress
    • For Lotus R1 2022. Sometimes in the first import of the day for a small number of the records in the import duplicates are created.
    Image RemovedUIIN-1927 - Bugfest. Inventory. Item selector box in the top of the instance record cause great confusion In progress
    • Lotus R1 2022. The checkbox to select a holdings record when moving a holdings record is confusing. This is to move the checkbox in line with the holdings title.
  • Lotus R1 Release Highlights:
    • Invalid Statistical Code Ids and Migration issues: Items with invalid statistical code ids (non-existing or non-UUID) are rejected with an error. The migration neither fails or cleans up the invalid statistical code id. Workaround: Manually cleanup invalid statistical code ids or add statistical codes in Settings/Inventory. This is related to the two following issues on handling invalid statistical code ids on migration (830) and deleting statistical codes (829).
      • MODINVSTOR-829 - Handle delete of statistical code associated with instance, holdings, or item properly.. In Review
      • MODINVSTOR-830 - Automated migration to cleanup non-existing statistical code ids or document SysOps process to manual cleanup Open
  • UXPROD-3463 - NFR: Data Import R1 2022 Lotus Support Bug Work In progress
    • Data Import Lotus R1 support bug features. Follow this issue and associated issues to follow work on bugs and support for Data Import. One issue is that when using MARC modification action in a job profile, the 035 created from the 001 and 003 isn't working.
  • UXPROD-1647 - Theme: Ability to maintain relationships between other apps when holdings/items are moved Open
    • Umbrella issues detailed data corruption when holdings/items are moved in Inventory and associated records in other apps aren't updated.
      • UICR-125 - Data corruption. When holding/item data are moved in Inventory, then the item in Courses is not updated accordingly Open
        • Data Corruption when holding/item is moved in Inventory, item in Courses isn't updated. No release information.
      • UIREQ-589 - [BE] Data corruption. When holding/item data are moved in Inventory, then the connected Request is not updated accordingly Open
        • Story: Data Corruption when holding/item is moved in Inventory, request on item isn't updated.
      • UIU-2082 - [BE] Data corruption. When holdings/item data are moved in Inventory, then the connected Fee/Fine is not updated accordingly Open
        • Data Corruption when holding/item is moved in Inventory, fee/fine on item isn't updated.
      • MODORDERS-642 - Data corruption. When holding/item data are moved in Inventory, then the connected Order lines are not updated accordingly In Refinement
        • For Morning Glory R2 2022: Data corruption when holdings/items are moved and associated POL aren't updated.
      • MODINVSTOR-671 - FOLIO inserting/allowing instanceFormatIds null elements Open
        • Data Corruption/Integrity: Instance Format Ids as Null. The problem extends to other identifiers. One commenter suggested that there is an issue between the UI and back end and currently the back end isn't validating what is coming from the UI. Please see comments for details.
  • MODORDERS-642 - Data corruption. When holding/item data are moved in Inventory, then the connected Order lines are not updated accordingly In Refinement
    • Release: Morning Glory R2 2022: When moving holdings and/or items, then the order lines are not updated accordingly. There are 2 potential workarounds - see issue for details.
    • UIIN-340 - Instance record. Look up Related title (edit mode) Open for release Lotus R1 2022.
  • MODINVSTOR-829 - Handle delete of statistical code associated with instance, holdings, or item properly.. In Review
    • Story relating to the deletion of statistical codes for FOLIO Inventory records. Currently, deleting the statistical code does not delete everything (the code Id still appears in the json) and can cause issues when working with the Inventory record.
  • MODDICORE-248 - MARC field protections apply to MARC modifications when they should not - DRAFT Blocked
    • Data Import Bug: Just created to get to resolve the issue of modifying marc files in DI that are also in the field protection list.
  •  MODCPCT-38 - Better strategy for retrieving the result status of record import Blocked 
  • MODDATAIMP-604 - Duplicate records in incoming file causes problems after overlay process with no error reported In progress
    • Bug, Priority TBD, Affects Version/s: None, Resolution: Unresolved
    • Release: Lotus R1 2022
    • Duplicate records in incoming records causes problems after overlay process with no error reported. See details as this affects quickMARC where the record is corrupted.
  • MODDATAIMP-613 - OCLC single record import takes extended time to complete when large data import jobs are running Open

...

  • Data Export:
  • MARC Holdings records:
    • And Data Import: MARC Holdings during data import flow, we should use pre-defined MARC Holdings source (which is created in the reference data with pre-defined id = 036ee84a-6afd-4c3c-9ad3-4a12ab875f59).
    • Functionality in Kiwi: This wiki page explains how you can test MARC holdings records in snapshot.
  • Administrative Notes:
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUXPROD-2867
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyMODINV-581
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyMODINV-582
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyMODINV-580
     
    • These concern the holdings, items, and instance records. We are some steps closer to the administrative notes for instances, holdings, and items.
  • Mapping rules: This only applies to institutions that have custom mapping rules. This is for the marc-bib.
    • If you have both custom and the default mapping rules, make sure to follow these steps for consistency:
        1. Send GET request to  /mapping-rules/marc-bib to retrieve the mapping rules
        2. Send PUT request to /mapping-rules/marc-bib and put in the body the result of step 1 
        3. Use the script to clear irrelevant records in the db (make sure the correct tenant name is used in the script)
  • quickMARC permissions:
    • View and edit MARC holdings record
  • OAI-PMH
    • Holdings without associated items are now included in the response
    • Harvesting times have improved. Baseline reports and release comparisons. To implement this, you will need to run the reindex (see release notes)
  • Source Record Manager/Other:
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyMODSOURMAN-468
      • This concerns creating a new API and db table that should store and represent information for the Data Import landing page. More for those using the API or accessing data via the db (such as LDP, perhaps Panorama?).
    • Identifier UUIDs as text values rather than json stream changed approved. This will help those working with the API or accessing the data via the db. This is to speed up the process of saving the UUIDs. This is for Lotus.