00:03:08	Jennifer Parsons (she/her):	I actually logged in earlier and logged out because I was worried I was in the wrong place.
00:04:11	Katie Rahman:	Do we know when LC is going live?
00:05:14	Lynne Fors:	Replying to "Do we know when LC i..."

LC's website says: On Monday, June 30, 2025, the Library of Congress will launch its new online catalog platform.
PLEASE NOTE: Online requesting is now disabled through June 30th as part of this transition. For more information, please visit the Catalog Welcome Page.
00:05:24	Katie Rahman:	Thanks Christie and Jennifer.
00:05:46	Lynne Fors:	Replying to "Do we know when LC i..."

I assume it's this weekend-ish
00:06:08	Christie Thomas (she/her):	Do we have a notetaker today?
00:07:03	Christie Thomas (she/her):	@Jennifer Eustis If you lead the meeting, I will take notes since it does not look like we have a notetaker here today.
00:11:45	Jennifer Eustis:	Reacted to "@Jennifer Eustis If ..." with 🙏🏻
00:13:51	Ryan Taylor:	https://docs.google.com/spreadsheets/d/1K6Tuo4zT1GMgStu4xccDtescI-sa1ZcL8wAnp--fwEc/edit?gid=0#gid=0
00:15:12	Christie Thomas (she/her):	Well, we had two different use cases.
00:19:18	Lynne Fors:	Isn't there some sort of merge functionality that is on the wish list for Inventory? To help manage duplicate records
00:20:02	Lynne Fors:	Overwrite?
00:20:05	Jennifer Eustis:	Replying to "Isn't there some sor..."

I vaguely remember something about that.
00:20:27	Mary Aycock (she/her):	Reacted to "Overwrite?" with ➕
00:21:58	Lynne Fors:	Replying to "Isn't there some sor..."

I thought it was something that was purely in Inventory and not Data Import, i.e. preferred target record and the record you want to merge into it
00:22:27	Vivian Gould (she.her), MOBIUS:	Proposed terminology (my thoughts):
Insert - adds new record (no overlay)
Merge - adds new data to existing record
Replace/Overlay - Complete overwrites existing record
00:23:35	Christie Thomas (she/her):	Replying to "Proposed terminology..."

Can you say more about insert? If there is no record, would you need to use update? Or, would that be where there is an instance but no MARC record already?
00:23:44	Lynne Fors:	Replying to "Isn't there some sor..."

So the ETL process is avoided.
00:24:48	Robert Pleshar:	Insert to me implies putting something into something that already exists.
00:25:05	Yael:	Replying to "Insert to me implies..."

same
00:25:10	Jennifer Eustis:	Insert means add the field to the existing ones in the record
00:25:26	Lynne Fors:	Reacted to "Insert to me implies..." with ➕
00:28:04	Jennifer Eustis:	Great point Christie
00:28:07	Vivian Gould (she.her), MOBIUS:	I apologize. As I said in the meeting, I assumed we were including situations where we are creating a new record, which what I meant my Insert.
00:28:42	Lynne Fors:	Jira ticket in question: https://folio-org.atlassian.net/browse/UXPROD-4080
00:31:04	Vivian Gould (she.her), MOBIUS:	Reacted to "Insert means add the..." with 👍
00:32:32	Christie Thomas (she/her):	This is functionality that we would want to add to marc modifications, too.
00:32:39	Vivian Gould (she.her), MOBIUS:	Find/Replace?
00:36:53	Timothy Ryan Mendenhall (he/him):	I forget — is it possible to embed a job profile in another job profile?  This almost feels a bit like a job profile within a job profile
00:37:04	Christie Thomas (she/her):	It is not.
00:51:31	Christie Thomas (she/her):	You cannot.
00:53:01	Christie Thomas (she/her):	Should we add this as a feature to discuss in the future @Timothy Ryan Mendenhall (he/him)?
00:55:22	Timothy Ryan Mendenhall (he/him):	Maybe, but we would probably need to come up with some use cases.  I was just thinking that what we are discussing seems to involve field mapping, match, and action profiles working a single “object” within a larger job profile that may also have field mapping, match, and action profiles that exist independently
00:55:43	Christie Thomas (she/her):	Reacted to "Maybe, but we would ..." with 👍🏼
00:56:00	Jennifer Eustis:	https://folio-org.atlassian.net/wiki/spaces/DISIG/pages/4670269/Data+Import+Implementers+New+Functionality+Tracker
00:56:16	Timothy Ryan Mendenhall (he/him):	Thank you!