Page Comparison

Jennifer Eustis 

Bugs:

• Data Export new Issue: Only 1 Electronic Access type from the FOLIO Holdings records is exported. This is not planned for kiwi.

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MDEXP-480

• Data Export and Data Import flow: This is an operator error rather than a bug. If you export a file and then you go to import it and use the default profile, there is an error and the problem comes from the 999ff. The default profile is trying to create a new one when there is already a 999ff in the record. View Source disabled in Kiwi, concerns exported files being reimported with the 999. See workaround in issue.

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODSOURMAN-634

• Data integrity issues (Kiwi bugfest): Testing encountered issues of not being able to edit an instance record via quickMARC or the MARC and last updated date/time for holdings records.

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODSOURMAN-627

• Data Import sort by Record column: Testing revealed that this isn't working properly in Kiwi bugfest.

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODSOURMAN-625

• Data Import Spikes:

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODDATAIMP-423

  Jira Legacy
  server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODDATAIMP-438

  • Slow downs encountered when data import job is running for single imports and overlays. This Spike is a story rather than a bug. How do we track a story? We need to consider what the support group is also doing as this group is tracking bugs rather than stories. We should rethink how we do this so that we can track these issues. Could you block the issue until the Spike is completed?Ann-Marie has raised the priority of this.

Meet the teams which include Roadmaps. Modules Matrix: The preference is to go through the POs for comments and questions.

Kiwi Release Notes: These are still being worked on. Here are some highlights below grouped by topic or app:

• 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 Lotus
  • Question about the edits by different users on the same record. Whoever saves second will cause the edits of the first action to disappear. Optimistic locking will be turned on for Lotus. For Data Import, most of the time the issue will be on the user side where the manual updates will take longer.
  • Inventor

There were updates for all the SIG conveners.

For MM SIG, the discussion revolved around more timely announcements when underlying functionality changed that had implications for institutions. The example were changes to property names that broke some of the reports. Jennifer Eustis has volunteered to dig into release notes and changes.

Minutes - 2021-12-09 Meeting notes  (SIG Convenor updates are part of this page)

Charlotte Whitt 

Felix Hemme