2026-03-04 Data Import SIG Meeting

Recordings are posted Here (2022+) and Here (pre-2022) Slack channel for Q&A, discussion between meetings

Requirements details Here Additional discussion topics in Subgroup parking lot

Attendees: @Christie Thomas @Robert Pleshar @Megan Toye @Autumn Faulkner @Vivian Gould @Katie Rahman @Kim Wiljanen @Lynne Fors
Notetaker: @Whitney Christopher , @Autumn Faulkner , @Yael Hod , @Robert Pleshar

Links:

Agenda:

	Item	Notes
Announcements
	WOLFcon 2026 accepting proposals to March 25th. Early Bird registration open until July 28th. https://site.pheedloop.com/event/wolfcon2026/home/ Record deletion discussion @ App Interaction SIG - March 4, 2026.	Guidelines are now available. Ryan is working on a proposal on deletion alignment. The discussion at the App SIG was very interesting. How to do you keep information and record status in sync if there are dependencies and may impact relationships between records/Apps/Integrations. We revisited the challenge of deleting record and how hard it’ll be to move on a solution. We teased out the use cases and work on those in the meantime. We also thought about junk data and cleaning that up and having records just go away. The community can define terms (soft versus hard delete) and how these can be implemented. A lot of this has been figured out. What does it mean to do the same thing in batch? How do we better manage dependencies when FOLIO is a microservices approach? There’s been enough decision making that individual groups can prioritize this group and rely on the community to get the work done.

Discussion (New Topic or Jira Issue)
Autumn Faulkner	Data Import Documentation follow up discussion. What goes on wiki vs. http://folio.org etc.	Autumn is working on a project to review, consolidate, and re-organize the DI SIG wiki. There’s administrative documentation. Then there is the how-to documentation. The docs.folio.org isn’t the place for this stuff. There is a difference between training and documentation. We need to take a look at the process and slow down. Is there space to free up time for documentation? As things are implemented and ready for release. Autumn will do an audit and propose some new trees or pages. This needs to be part of the regular work of the SIG. Could we establish within the SIG that is the documentation point person? Is there some way to deprecate old pages? With a hierarchy of pages, it is easier to hammer out where things go where. Link to Autumn’s notes: Autumn will provide an audit and recommendations going forward Christie & Jennifer will work on a topic calendar Document this in a decision log
Delete Authority Records	https://folio-org.atlassian.net/browse/UXPROD-4627 . This is functionality slated for Umbrellaleaf.	There is a need to delete authority records in batches. One use case was for an overlap review between MeSH and LCSH, to delete a set of MeSH. Right now the only workaround is to go to the hosting vendor to delete the entire set. The other use case is duplication and junk data. Where did you set the HRID to begin with 1? This is a required field and probably should have used the last number used. There are 2 (or more) issues here. How do you manage authority files? How do you delete them? There was also a problem with the logs. This could be an opportunity to link the number generator with this. There is no documentation about managing the MARC Authority files. The MM SIG might be a good venue for asking on how to manage the authorities.

Housekeeping
Next SIG meeting	2026-03-11 (Workshop) Test if MARC to instance match will work for this change https://folio-org.atlassian.net/browse/MODDATAIMP-1199 Profile building for updating an item before the instance and holdings. Christie Thomas has tested locally with the following import profile which updated the item, but not the instance or holdings.

	Actions/Decisions Needed	To do
Roadmap Discussion (At same time of a new release)
MVP Discussion (at the same time of a new release)

Upcoming meetings/agenda topics: --

Chat: