WolfCon - This is now scheduled for May 7 to May 11. It will be held in downtown Durham, NC. Details will come from Jenny Boyer, Director of OLE Strategic Planning, or a member of the planning committee.
Update from Reporting SIG - Testing a data lake. If you go to the Product Council Minutes, you'll find a link to the recording of the meeting that talks about the proof of concept that was done for this.
Peter Murray is looking for a plug-in for Confluence to have a tool to use to present and organize ideas for FOLIO. The Product Council will look for feedback as to its usefulness.
MARC batchloading working group - will meet again Filip will be sending out more info soon
Inventory advanced searching group - Doodle poll sent out to find date/time for meeting
Sysops Data migration subgroup - Lynn attended the meeting Monday. They'll be working on a gap analysis over the next few weeks & then share it out with the SIG's; we'll use a SIG meeting to discuss the gap analysis & invite reps from the data migration subgroup to attend.
Charlotte spoke with RM SIG on Friday. They came up with some framing questions that Charlotte will share with us.
The Special Collections and Archives Working Group will have a meeting this Monday at 2:00 EST. Link will be sent out as well as a confirmation.
Charlotte - The Codex search is comparable to the Dublin Core. The data from the cataloging model will be from MARC.
Flow of information: Cataloging goes to Inventory which goes to Codex
Charlotte - MARC record will be loaded into Inventory and then is transformed. Cataloging will have separate storage of data.
Entity level search vs. search in local level (the local database produced by cataloging module itself).
Discussion about what will be searched, for what purpose and where? Will the @Cult product have search capabilities? The timing is important. Tiziana asked for a document with use cases related to how a cataloger will use WeCat inventory app. They need use cases - what is the first step? What can be found in Codex in that is not in local database and vice versa. They could use more information. What are the specific steps that each cataloger
Clarification of what information is living where?
Lynn - WeCat has MARC records. We need to be able to pull out lists of items, lists of holdings, lists of bibs based on results sets.
Jacquie (Duke) - We do need to be able to access all types of records for global edits. Sometimes global edits need to affect changes outside the bib/holding/item . We need to consider the linked data world,
Christie (Chicago) - Agrees with Jacquie. Problem siloing MARC data in WeCat app. There are other apps that need MARC information. This makes it better if this info "lives" in the Inventory app - that should be the main store. If WeCat becomes the local storage - how will that data sync across FOLIO?
Ann-Marie - Agrees as well. Where is data loaded so it can "explode" into holdings, items, order, data. Once loaded, will one update affect changes wherever needed?
Charlotte - Diagram reflects understanding that may be dated:
Lynn - Use cases. Are they useful to Charlotte's team as they relate to Inventory?
Charlotte - Yes, use cases for WeCat and FOLIO Inventory are both useful.
Tiziana emphasized the need for @Cult to know where they information is going to live.
Charlotte and Tiziana will talk to together to figure out where information
Patty - Important for SIG to write use case, but developers figure out how and where it will happen.
