00:06:22	Jennifer Eustis:	https://site.pheedloop.com/event/wolfcon2026/call-for-proposals
00:08:02	Christie Thomas (she/her):	I think that the zoom link in the meeting minutes is wrong. There is another meeting with a few folks in attendance.
00:11:02	Maura Byrne:	Same! I’ve been working in April 2020 for many years now.
00:11:44	Jennifer Eustis:	https://docs.google.com/spreadsheets/d/10ZWdtsskTl5gZiTdPHJd9x1q9TyHDbRkBYovirOZYZU/edit?gid=0#gid=0
00:12:22	Laura Daniels:	I remember a cross-app deletion discussion from WolfCon in 2020 (Texas A&M)
00:13:13	Jennifer Eustis:	https://docs.google.com/spreadsheets/d/1xm26GuSPJZQXkt53DS4wtpUpTLIYMjL1Kz8UQ9yqEnA/edit?gid=766960785#gid=766960785
00:15:30	Vivian Gould:	The concerns are compounded for ECS sites, since the tenants can't see each other's data.
00:15:40	Maura Byrne:	Reacted to "The concerns are com..." with 💯
00:16:59	Owen Stephens:	https://open-libr-foundation.slack.com/archives/C04DS8DN9J6/p1770892848066939?thread_ts=1770831814.436029&cid=C04DS8DN9J6
00:17:04	Owen Stephens:	https://folio-org.atlassian.net/wiki/spaces/DD/pages/1780396/FOLIO+Cross-Application+Data+Sync+Solution#Data-sync-working-group---TC-Updates-&-Outcome-(August-3,-2022)
00:17:08	Jennifer Eustis:	https://folio-org.atlassian.net/wiki/spaces/TC/pages/5054313/DR-000004+-+Cross+application+data+sync+proposal
00:17:10	Owen Stephens:	https://folio-org.atlassian.net/wiki/spaces/TC/pages/5054313/DR-000004+-+Cross+application+data+sync+proposal
00:18:48	Alissa Hafele:	apologies - I have a conflict and will have to sneak out at half past
00:19:11	Tara Barnett (Index Data):	Reacted to "apologies - I have a..." with ❤️
00:23:44	Laura Daniels:	I think Christie makes an excellent point. There is not going to be one deletion process to rule them all.
00:23:56	Susanne Gill (BVB):	Reacted to "I think Christie mak..." with 👍
00:25:33	Kristin Martin:	Sort of like an "undo" function for a data import process gone awry
00:25:39	Vivian Gould:	To Christie's point, it's difficult to test and train when we can't delete the records used for testing and training.
00:25:49	Maura Byrne:	Reacted to "Sort of like an "und..." with 👍🏻
00:25:57	Maura Byrne:	Reacted to "I think Christie mak..." with 👍
00:26:35	Christie Thomas (she/her):	Yes, but sometimes we don't find out for weeks so I don't know if an undo would solve all of the problems. If we had preview and undo for data import that would help a lot.
00:26:48	Maura Byrne:	Reacted to "To Christie's point,..." with ➕
00:27:03	Christie Thomas (she/her):	Reacted to "To Christie's point,..." with ➕
00:27:15	Alissa Hafele:	Reacted to "I think Christie mak..." with 👍
00:29:24	Maura Byrne:	Reacted to "Yes, but sometimes w..." with 👍🏻
00:33:48	Owen Stephens:	Tombstoning definitely feels like it could work - again we need an agreed technical approach that says how FOLIO modules should implement this
00:33:52	Owen Stephens:	I think if there are specific things that cause problems (like an EDI load) then another approach might be for there to be much better support for ‘test loads’ which emulate the load but keep a record of all transactions are can somehow roll them back.
00:34:28	Maura Byrne:	💯Christie
00:34:34	Vivian Gould:	Reacted to "💯Christie" with 💯
00:36:14	Jennifer Eustis:	That might be a feature of metadb
00:36:28	Laura Daniels:	Replying to "That might be a feat..."

I suspect you are correct
00:36:41	Tara Barnett (Index Data):	Replying to "That might be a feat..."

Oh, like available for reporting but not in the “FOLIO” data?
00:36:46	Jennifer Eustis:	Replying to "That might be a feat..."

For items we delete we can't see them anymore
00:37:57	Tara Barnett (Index Data):	So is this ultimately a question about prioritization?
00:38:15	Martin Scholz:	Confluence uses a kind of tombstone for user that no longer exist, eg.
https://folio-org.atlassian.net/wiki/spaces/FOLIOtips/pages/5672571/Working+with+FOLIO+APIs
00:38:37	Jennifer Eustis:	Reacted to "{B89A0E39-86B5-4D59-B4D9-85BFEB1DEF3F}.png" with 👍🏻
00:38:41	Tara Barnett (Index Data):	Reacted to "{B89A0E39-86B5-4D59-B4D9-85BFEB1DEF3F}.png" with 👍🏻
00:40:32	Christie Thomas (she/her):	There are internal folio tables where deleted inventory records are stored: audit-instance, audit-holdings, audit- items.
00:40:33	Tara Barnett (Index Data):	Does a UI delete without guardrails offer much of an improvement over the API?
00:41:01	Tara Barnett (Index Data):	Reacted to "There are internal f..." with ❤️
00:41:07	Jennifer Eustis:	Deletion of items and holdings is on the high level roadmap for bulk edit, https://folio-org.atlassian.net/wiki/spaces/BULKEDIT/pages/2524679/High+Level+Roadmap+for+Bulk+Edit+App
00:41:08	Martin Scholz:	Replying to "Does a UI delete wit..."

you can do it without knwoing about the api 🙂
00:41:15	Laura Daniels:	Replying to "Does a UI delete wit..."

It would for those of us who aren't comfortable using apis
00:41:32	Laura Daniels:	Reacted to "you can do it withou..." with ➕
00:41:39	Martin Scholz:	Reacted to "There are internal f..." with 💡
00:42:26	Christie Thomas (she/her):	There is a plan for deletion in place then?
00:42:27	Tara Barnett (Index Data):	Replying to "Does a UI delete wit..."

On the other hand, I like a bit of friction in place for potentially dangerous things.
00:42:40	Jennifer Eustis:	Replying to "There is a plan for ..."

using BE
00:43:02	Jennifer Eustis:	Replying to "There is a plan for ..."

https://folio-org.atlassian.net/browse/UXPROD-3230
00:43:17	Jennifer Eustis:	Replying to "There is a plan for ..."

https://folio-org.atlassian.net/browse/UXPROD-4022
00:44:34	Vivian Gould:	Reacted to "It would for those o..." with 💯
00:44:49	Owen Stephens:	Apps implement blocks on delete as they see fit. For example in Serials we allow deletes for things that don’t have other things attached (e.g. you can delete a publication pattern if there are no pieces linked to it)
00:45:59	Owen Stephens:	What we don’t have is a “delete everything in this stack of things” but I think that’s a prioritisation issue rather than not being possible
00:49:00	Laura Daniels:	If only developers didn't need to eat, pay rent, etc.
00:49:59	Owen Stephens:	That’s exactly what the previous discussion was about, and the doc Jennifer/I linked to says how it should be done
00:50:07	Jennifer Eustis:	Reacted to "That’s exactly what ..." with 💯
00:50:47	Laura Daniels:	I see a lot of arguments for raising this with PC
00:51:24	Laura Daniels:	Replying to "I see a lot of argum..."

since PC is working on prioritization
00:52:00	Tara Barnett (Index Data):	Reacted to "since PC is working ..." with ❤️
00:52:11	Maura Byrne:	Reacted to "I see a lot of argum..." with ➕
00:53:41	Christie Thomas (she/her):	Thanks, Owen.
00:55:34	Tara Barnett (Index Data):	If someone commissioned delete functionality to be developed, would the outstanding questions around consistency/strategy prevent the work from moving forward?
00:55:53	Christie Thomas (she/her):	Replying to "If someone commissio..."

Good question.
00:56:14	Laura Daniels:	Reacted to "Good question." with ➕
00:56:51	Maura Byrne:	That sounds like a permissions thing.
00:57:02	Laura Daniels:	Caveat Deletor
00:57:11	Maura Byrne:	Reacted to "Caveat Deletor" with 💯
00:57:12	Tara Barnett (Index Data):	Reacted to "Caveat Deletor" with 😂
00:57:15	Kristin Martin:	Reacted to "Caveat Deletor" with 😂
00:57:39	Christie Thomas (she/her):	Reacted to "Caveat Deletor" with 😂
00:59:43	Owen Stephens:	I agree @Maura Byrne … although I also know I’ve done “whoopsies” and caused myself and others headaches!
00:59:52	Christie Thomas (she/her):	Reacted to "I agree @Maura Byrne..." with 💯
00:59:54	Laura Daniels:	Reacted to "I agree @Maura Byrne..." with 💯
00:59:58	Maura Byrne:	Reacted to "I agree @Maura Byrne..." with 💯
01:01:16	Maura Byrne:	Reacted to "Good question." with ➕
01:01:20	Jennifer Eustis:	Thank you everyone!
01:01:23	Laura Daniels:	This was a great discussion, thanks
01:01:32	Owen Stephens:	Replying to "I agree @Maura Byrne..."

The ability to do good test runs is something I think is missing from FOLIO alongside the batch delete