2019-08-08 Metadata Management Meeting notes

A coordinating committee is forming to work on the agenda and logistics for WolfCon 2020. This will include but not be limited to FOLIO working meetings.

The Privacy SIG is being revivied

Holly Mistlebauer gave an update on Capacity Planning:

Capacity Planning / MVP update

MVP recommendations from the Capacity Planning Team should be available next week.

Harry Kaplanian has started drafting a "reverse RFP" document. He began with Acquistions and will be addressing Inventory next. This document is available in the PC google drive if anyone is interested in reviewing it.

Container Small Group Update - Group has been working on some modelling. There are drawings available in Google Drive, if interested

Data Export Subgroup - Laura thanked those who volunteered for the group.

Data Import - Ann-Marie reviewed feedback on MARC to Instance mapping. She presented the changes to the developers.

MARCCat - The next meeting should be help on Monday, August 12

Ann-Marie reported that At Cult is doing some cleanup in Jira. Some features may arise from that activity. Laura will try to make sure we are made aware of this. 

Natascha who was part of the original subgroup that dealt with bound-with/in-analytics requirements group, reported on their past activity. In her memory some in the group wanted to link items, some link instances. Natascha feels we need now to address the item to item relationship. She mentioned considering this in terms of circulation 

Felix (via chat) - "This is our small area in the Google Drive folder (data samples, drawings etc.): https://drive.google.com/drive/folders/1JKppoiWoeXe6C8G2T6W7lYMv2HA9Fyya"

Laura wondered if the Jira for Instance to Instance (UXPROD-1856) relationship is independent of the Jira for Item to Item relationship (UXPROC-1241) . Felix stated that they do not depend on each other in any way. The RA group is interested in this discussion due to circulation concerns. Laura also mentioned there has been some confusion in some thinking that container records will fill this need - which is not the plan. 

Example of container model shown (link?) "Archival collection with container and instance option 1" There is a desire that a container that have one or more instances, and also that a container can have items that are not connected to instances, but relate to the container.

Felix (via chat): "I totally agree with UChicago that we need more input from the US libraries re. item to item linking. At that time it turned out that each institution dealt with bound-withs differently and that it would be difficult to generate a uniform solution in a new system."

Jason - the discussion of a container should be brought before a group of special collections/archival specialists. 

Michelle stressed that the value of a container could be to show through dynamic linked relationships between collections, parent/child or instance to instance - several levels. They are going to ask

Rita (via chat) - "Is the function of a "container" to build any kind of hierarchy in metadata? (You could also think about linking an instance for the greater Ressource to instances for the components ... Will you use a container to describe a multipart monograph?" Laura answered "It depends. A container is a way to represent a hierarchy." 

Laura invited the group to add drawings to the FOLIO > Metadata_Management > Container folder

Michelle (via chat, regarding the container example) - "This might very well be a case of a parent/child relationship between two different instances, with the same item [Box 3] linking to both via holdings (if that’s possible?), and thinking about it as a container could be complicating things"

Multiple Graphical Representations

Note: Charlotte has added following feature description (UXPROD) in Jira: 

UXPROD-1646 - Getting issue details... STATUS

Christie expressed hesitation about being too prescriptive about what the JSON should look like. She suggested spending time on the Functional Requirements. Suggestions for additional functional requirements were added to the Google doc: DRAFT - Multiple graphical representations in FOLIO. (Also linked above.) 

The group also would like to make recommendations as to what this should look like in the FOLIO interface. Example systems that work well?

https://wiki.folio.org/pages/viewpage.action?pageId=78336464

VZG

Stanford

Index Data