Page Comparison

2022-10-02 Highlights

Lotus has been pushed back a sprint for a March 9, 2022 release. The Lotus R1 2022 release notes are only slowly being populated.

Development Teams Feature Boards:

• FOLIJET
• Instances backlog

...

2022-03-02 Highlights

• 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).

    • Jira Legacy
      server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-829

    • Jira Legacy
      server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-830

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-3463

  • 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.

• Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-1647

  • Umbrella issues detailed data corruption when holdings/items are moved in Inventory and associated records in other apps aren't updated.

    • Jira Legacy
      server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UICR-125

      • Data Corruption when holding/item is moved in Inventory, item in Courses isn't updated. No release information.

    • Jira Legacy
      server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIREQ-589

      • Story: Data Corruption when holding/item is moved in Inventory, request on item isn't updated.

    • Jira Legacy
      server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIU-2082

      • Data Corruption when holding/item is moved in Inventory, fee/fine on item isn't updated.

    • Jira Legacy
      server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIOR-682

      • For Morning Glory R2 2022: Data corruption when holdings/items are moved and associated POL aren't updated.

    • Jira Legacy
      server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-671

      • 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.
• Check out the Cross Release Statistics.

...

• Data Export:
  • Through the support of MinIO data export is now hosting agnostic.
  • Recommended threshold on number of records to export is 300,000.  Data export performance report for the Kiwi release.
• 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
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-2867

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINV-581

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINV-582

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINV-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. 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
    server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODSOURMAN-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.