2026-01-07 Data Import SIG Meeting Notes

Item

Announcements

Looking for more use cases

The document below is for the use case of match from marc to marc, submatch to holdings, update marc srs, update holdings, and then modify marc.

Will this work also apply to other use cases?

Question for group: Can you share other use cases with Ryan?

https://folio-org.atlassian.net/wiki/spaces/DD/pages/1778826

https://folio-org.atlassian.net/wiki/spaces/DD/pages/1778826/3.+Modify+MARC_BIB#id-3.ModifyMARC_BIB-:~:text=5.%20Match%20and%20update%20MARC%20Bib%2C%20holdings%20%2B%20modify%20MARC%20Bib%20(Available%20since%20Trillium)

Ryan will double check that this applies to any situation where the marc modification comes last. If Ryan needs more use cases, we can do this in lab.

Discussion (New Topic or Jira Issue)

New Topic

Reconfiguring of meeting schedule: Decide to implement or open the floor for discussion

Hello @here, in Data Import SIG meeting, we discussed meeting cadence in relation to Meeting Calming proposal from Product Council. We have a proposal for this group that will be shared more widely in MM and Acq. that you can find in this decision log. A summary of this proposal is:The SIG found that meetings have a lot of material that we aren’t getting to. We are still doing a lot outside of the business meeting. The “Refining ‘use a qualifier’” is a good example where we ask for volunteers to test and think through functionality outside of the SIG meeting. This puts a lot of pressure on everyone. It also means that we don’t share in discussing and testing. In response to this as well as the  from the Product Council, the SIG would like to propose the following:1. The SIG business meeting alternates with the lab session. One week is a SIG business meeting. The next week is the lab session using the same zoom url as the SIG meeting and occurs at the same time as the SIG. When lab falls on the last week, we can cancel this meeting to have a week of no meetings.

1. There will be one discussion topic. We will take as much time as we need to discuss the topic (either an existing issue or a new requested feature). Once discussion is complete, we will move on.

2. We will add “Next Agenda” to our agenda so that we formulate the next agenda as a SIG

3. We will keep the Thursday lab time in case anyone needs this hour to test or record some issue they are working through.

4. We recognize that issues arise and that some need our attention at that moment rather than waiting. We will do our best as a community to address those in a timely manner. An example is a bug after upgrade such as Data Import not working.

We are seeking the community's comments and thoughts through to Jan. 7, 2026. This will be an agenda topic for our Jan. 7th meeting as whether to implement or not this proposal.

DI Meetings every Wednesday at 1PM EST

• Week 1: DI SIG

• Week 2: DI Workshop

• Week 3: DI SIG

• Week 4: Nothing

• Week 5: Nothing

Thursday is still alternate with lab.

Revision of existing issues for 856/Electronic Access.

https://folio-org.atlassian.net/browse/UIIN-2579 linked to https://folio-org.atlassian.net/browse/UXPROD-4467 linked to https://folio-org.atlassian.net/browse/UIIN-2577

We have a variety of issues with regard to MARC field 856, subfields and indicators. Jeannette recently asked if indicators 3 or 4 are part of this work. What about the 857 field?

These need to be broken up into more issues. Some of this work falls under Metadata Management. There’s a lot to unpack to get this off the ground. Is part of our analysis to see what happens first and then reach out to other groups such as the MM to organize that work?

UIIN-2577 also means we have to add those values to the drop down for Electronic Access.

For the relationship, we can’t use indicators. Some use a $f to denote that only because that is what we have currently.

Ryan will look into if we can use indicators in field mapping profiles.

How should we approach it? Should we determine all the moving parts? UIIN-2577 has a good scope.

Should we push this forward if this falls under a different SIG? We should raise this in a MM meeting and understand their priorities and work together to figure out joint priorities and development.

Match Criteria

https://folio-org.atlassian.net/browse/UXPROD-5669

Review decision.

Based on our discussion from last time, this issue will remove the options to have only “exactly matches” and users can make use of “Use a qualifier” and “Only compare part of the value” option applied to Incoming and Existing records.

Yes, this looks good. Ryan will begin to talk to the team to include in the Trillium release.

Housekeeping

Next Workshop Meeting

Should we focus on the refinement of qualifiers with a lab focused on our work in progress followed by a business meeting where we share the results?

Next week:

Test if the same action can be used multiple times in the same job profile.

Test if the same submatch can be used multiple times in the same job profile.

Actions/Decisions Needed

Roadmap Discussion (At same time of a new release)

MVP Discussion (at the same time of a new release)