Page Comparison

Week of March 21 Highlights

• Lotus Bugfest

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

    • ISBN and invalid ISBN identifier types not showing properly

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

    • MARC Authority - When user clicks on "Heading/Reference" value at result pane, exact matches for the value aren't highlighted

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

    • MARC Authority - Search doesn't start after editing the advanced search query from search box.

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

    • MARC Holdings - error appears when you save "MARC Holding" record after editing it in quickMARC

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

    • MARC Authority - Data Import fails for import of authority record

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

    • When viewing Instance, identifier pair values are misaligned. See also

      Jira Legacy
      server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIIN-1962

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

    • order export jobs showing are showing a "Currency" not found error message rather than successfully exporting orders to EDI

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

    • Data import fails to create FOLIO Holdings

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

    • Data Export: The search box do not contain searching value when User filtering result list by Record type in the Select Transformations

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

    • Sorting contributor types ignores spaces

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

    • Data Import: Records that were imported using DI and in that job had a MARC modification on the incoming file and where you then overlay that record using single record import result in an error

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

    • MARC Authority: Facet list for subjects has random value

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

    • Bound-with parts get empty collection

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

    • MARC Authority - updating advanced search model query doesn't return expected results

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

    • The original work was implemented with the work done on ticket UIIN-1645, but now when bugfest testers test in Bugfest Lotus these searches using the search option All, does not work. This can be reproduced in FOLIO Snapshot.

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

    • Inventory App icon: Sometimes the "Something went wrong" appears when this is clicked

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

    • Newly created tag doesn't appear in list and it's not possible to search for tag (tested on instance record)

Week of March 14 Highlights

Remember to participate in Bugfest!

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

  • Script to refresh instances when MARC to Instance mapping as changed, from the work of I. Wells.

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

  • For Lotus R1 2022. Fix the box to select which holdings to move to another instance to make sure it is more visible.

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

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

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

  • For Lotus R1 2022. When a record was exported and is now being updated and the 001 is the HRID, it was the case that the 035 was being generated again unnecessarily. This has been fixed.
• MODSOURCE-300 - Scripts for identifying and fixing invalid instanceIDs in SRS

Week of March 8 Highlights

• Bulk Edit pilot for users has been pushed to Morning Glory.

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

  • Unresolved: Holdings records only shows first 100 items  A very old bug from 2020, which has been solved long ago: 
  • https://bugfest-kiwi.folio.ebsco.com/inventory/view/2e93db10-f5ce-4e64-8ae5-4a8ac489e5dd?qindex=hrid&query=ho126544&segment=holdings&sort=title
•  

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

  • You can save an instance with a statistical code of "Select Code" which isn't a code.
• Library Data Platform Project
  • Bugfest: Seeking testers for the FOLIO LDP Query App
  • Metadb derived table query development: Metadb is still in development and being tested at the Univ. of Chicago. If you are interested in the next version of LDP 1, many of the derived tables from LDP 1 are being ported over to metadb.
  • LDLight: For users of LDLight, the schema naming is slightly ahead of Metadb schema naming convention. The tables without the t are the original ones from JSON including the JSON arrays. The tables with the underscore underscore t are the transformed JSON arrays.
• Tech Council Documentation: Changes proposed to the evaluation process for new development and roles of those involved in the evaluation.

Week of Feb. 28 Highlights

Lotus Bugfest Environment Preparation Plan

• Scheduled for this week: PO's finishing writing test cases
• Bugfest is fun. To sign up and get information contact Anton Emelianov on Slack

Library Data Platform Draft Website

• Description of LDP project and links to resources

Week of Feb. 14 Highlights

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

  
  
  • Data Import: Bug (P2) duplicates protected fields on update. No release assigned yet.

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

  • 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.
• Flow Descriptions for Data Import

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

Bugs:

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

  • Not all Inventory items display if you switch to a different App and then return to Inventory.

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.

2022-27-01 Highlights

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

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

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

  • Release Lotus R1 2022: After saving a marc holdings record, the inventory record displays rather than the marc holdings record.

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

  • Story: No release. This story is about adding instance relationship types to instances such as "Issued with", "Other edition available". This is related to the UI work to look up instance relationship types,

    Jira Legacy
    server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIIN-340

    for release Lotus R1 2022.

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

  • 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.
• Juniper Hotfix #5: Details. This concerns the log4j security vulnerability for the large part. There is also an update to fix the instance identifier type matching in Data Import. These are being reviewed for testing.

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

  • Data Import Bug: Just created no release set yet. Job profile crashes when actions in profile are changed.

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

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

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

  • Story: Investigate roll back options for mods source record storage. See description on solving data consistency options.

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

  • If you have preferences on how to nest matches, add your comments to this issue. Also note down what you can live with if your ideal nested match isn't possible yet.

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

  • New job profiles might show a list of data imports files that have used that job profile though since it has never been used that list should be empty.

2022-13-01 Highlights

Lotus R1 Release Notes - This will begin to be populated probably after 2/20/2022.

Bugfest tentative dates: March 11 - 25, 2022

2022-13-01 Highlights

Lotus (R1 2022)#Roadmap has a tentative date of April 4, 2022 for the release of R1 to the public. It looks like bugfest will happen in March 2022 which can be seen in the Lotus (R1 2022) Bugfest environment preparation plan.

Stories

• Story on deduplicating record identifiers for marc holdings, instances, items, and marc authorities. Release for Lotus R1 2022.

• Story to investigate time to import a single OCLC record when a large import is running. Release for Lotus R1 2022

Element Renaming

mod-inventory: Rename holdingsId to holdingId - being reviewed in code commit for pull request 453

2021-16-12 Highlights

Bugs:

Data Import:

• Jira Legacy
  server System Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODDICORE-231

  • Bug, P2, Affects Version/s: None, Resolution: Unresolved
  • Release: R2 2021 Bug Fix
  • DI has a complicated product ID and produce ID Type matching issue in regards to DI job profiles for updates.

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

  • Story, P2, Affects Version/s: None, Resolution None
  • No release info

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

    • Link to epic
  • There's a need to improve the strategy for retrieving the result status of record import on overlay/update. This approach works on import with frequent timeouts, for overlay/update, the end result is that the instance id is not returned.

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

  • Bug, P2, Affects Version/s: None, Resolution: Unresolved
  • Release: Lotus R1 2022
  • Record matches aren't decreased when additional match conditions are added to a job profile. If you have 2 matches, the expectation is that the second match is done on the set of the 1st match which isn't happening.

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

  • Bug, P2, Affects Version/s: None, Resolution Done. CLOSED
  • Release: R3 2021 Bug fix
  • Static match on Holdings permanent location doesn't work in Kiwi bugfest.

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

  • Bug, P2, Affects Version/s: None, Resolution: Unresolved
  • Release: R3 2021 Bug Fix
  • Data Import matches on identifier type and value separately resulting in incorrect matches in Kiwi bugfest - possible Juniper hotfix.

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

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

Stories vs bugs: Example of what we saw last week of the bug being changed into a story to investigate the extended time for OCLC single record import while large files of data import are running.

This is a spike. Story, P2, Affects Version/s: None, Resolution: Unresolved. Release: Lotus R1 2022

GitHub Changes or Drafts through code commits and pull requests:

Rename 'hGenreTerm' to 'genreTerm' currently in draft pull 721.

Prevent a resource being skipped during index for elastic search in draft pull 176.

New API for item checkout in draft pull 723.

2021-09-12 Highlights

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 for Lotus.