2025-03-19 Data Import Subgroup Meeting Notes

Announcements:

Ryan

WOLFcon 2025: Call for proposals is out. The deadline is April 25, 2025.

UAT Set for Delete Enhancements

Ryan

Link to UAT : https://forms.office.com/r/Lf6pccP6eK

Link to documentation: https://folio-org.atlassian.net/wiki/x/X4BSN?atlOrigin=eyJpIjoiZTYxOWUzMzRjOTc3NDdlZDg0NWI4NDdlOTY1OGJhNGUiLCJwIjoiYyJ9
still soft delete, new flag added, syncing, more details in the documentation - please do the UAT and share any questions, ideas, etc. with Ryan. Testing will end in a week.

Ryan will check if Bulk Edit has been updated based on the work done.

Extend functionality of Electronic access (MARC 856)

Jennifer Eustis

UXPROD-4467: Electronic Access Block--New Elements (Instance, Holdings, Items)Open

This has been open since 2023. Possibly even earlier. How can we get this scheduled as part of a release? Has been discussed in MM SIG in regard to the 857. Talked about it an Chicago WOLFcon. Would be really helpful to get it done. Bigger question is how do we get tickets that are just hanging into the queue. Currently we take the public note but not the non-public note. Not sure why it is this way. It would be helpful if we could better understand how decisions are being made, how things are added to the pipeline. Some functionality is still very thin thread and its not clear how we get the whole thing done. Because of the thin threads we are creating work arounds and putting data in a place because we can, and not where we want it. Then when the full process is developed there is not way for us to get the information from the old place into the correct place because that wasn’t part of the new development. Data standards change and that affects our processes as well. Ryan says that the Trillium release would be a good time to discuss workflows and approaches to development. Both regarding specific updates but also for the long term, what we can do with data standard changes as they come up. Maybe worth bringing to the whole MM SIG so we can schedule things out in the short term and long term depending on the needs of the community. Just because something is not urgent does not mean it is not important.
Christie asks how we can be more proactive. Is there a way to make it easier to get these things in more smoothly.
Jennifer E: lots of intense development happening but in terms of maintenance there really isn’t a process. Maybe not a discussion just for MM SIG since it touches on so many apps. Christie suggests maybe a discussion for Wolfcon?
Ryan asks how often these changes to MARC are made. Happens twice a year but Christie suggests that even once a year would be helpful. Does not need to be in real time as long as we know that there is a process in place so that it will happen. Ryan suggests one release a year for getting up to date on MARC changes. If everyone was aligned it would be easier.
Sara - not just MARC, also across the items, and holdings. Uses the format even when its not in MARC. We need to think broader than just MARC in Data Import and Export. We need a full review to see what other apps and app interaction needs to be updated.

Ryan will look where this specific issue can fit in the schedule. May be difficult as it touches on many apps.

Christie will write up a proposal for WOLFcon and will share her ideas in the slack channel.

Review and fix individual fields

Jennifer Eustis

UXPROD-4080: Review and fix MARC Updates for individual fieldsDraft

How does this work currently? Do we need to document this and the behavior we want to see?
Jennifer: Saw this that repeating fields was an issue even though she has done it without issue for some fields. Do we need to flesh out this ticket? What is the behavior that we want.
Ryan planned it for a potential for Trillium but agrees that we need to review.
Jennifer’s job to replace an existing repeatable field (035) worked for her. Both for replacing fields and updating the $a. When they tried to do it for the 6XX subject fields it didn’t work as well. Weird behavior for protected fields. Worked for very different content but not for similar fields. Did not behave as expected. It was as if there was a logic for updating but we don’t know what the logic was.
Christie - thinks that this is working. She doesn’t use it but thinks that other do. She will find the information and confirm on slack.
Ryan thinks that some of these got updated on other tickets. Testing and tracking will be super helpful to see what needs to be done.

@Jennifer Eustis will create a spreadsheet so we can track what works and what doesn’t.
@Ryan Taylor will look into the stories on the ticket

Documentation Discussion: Identify gaps/needs

Ryan/All

Spreadsheet for tracking documentation needs:

@Autumn Faulkner will have an update next week