2017-08-31 Metadata Management Meeting Notes
Date
Attendees
Lisa McColl McColl
- Jacquie Samples
- Former user (Deleted)
- Jason Kovari
- Laura E Daniels
- jdolivarez
- Felix Hemme
- Dennis Christman
- Wayne Schneider
- Filip Jakobsen
- Charlotte Whitt
- Kathryn Harnish
- Ann-Marie Breaux (Deactivated)
- VBar
- Christie Thomas
- Natascha Owens
Goals
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
Update from the FOLIO Facilitators | jdolivarez | There will be a forum on GOKb, on September 13. Joseph will send out a sign up form. | |
Update from Product Council |
| ||
Linked Data Working Group | The group is slowly gathering numbers. Peter is started as the convener. Members are being solicited from across FOLIO SIG groups since there is a wide interest. | ||
Codex metadata Update | Kathryn Harnish; VBar | 1. Inventory documentation posted to the wiki. Review inventory and answer any questions. Kathryn presented the Inventory Metadata Elements set that she created on the wiki. Kathryn is focusing on what the data is that we need for the inventory portion of our records. What fields and subfields will need to be displayed as we work with inventory records? What kinds of data will we need to see in different contexts, such as Acquisitions vs. Circulation? The intent of the Inventory Metadata Elements is to define terms so we are all thinking in the same way. As much as possible the Codex element names were paralleled. Classification will be included in the Bib Level Elements. Flags on inventory record will be set through the user interface. The relationship between a flag set in the inventory and a flag at the Codex level is still being considered. They are not necessary equivalent. Kathryn will start a discuss thread for each the bib,holding,item levels to discuss these details.
| |
Bib/Item UX based on Codex Metadata Elements | Filip discussed what would display at the Item level. The first version: MarcEdit for editing, FOLIO is able to search and display the records and handle system-wide edits such as adding notes. Batch importing is beingconsidered envisioned. Options: 1) Whenever you pull in a file, the system could recognize that it is a MARC file 2) There could be a specific batch import area of FOLIO. In this scenario there could be templates guided by rules based on the source of the record. The way that it maps the fields would be determined by the source of the records. Filip is asking for feedback. When a record is imported, they go into the source record. The inventory space has to convert the data to a useable format for that purpose. Vince confirmed that the source record would be the edited version
Vince - A load is taking a MARC record, bringing it in. With that MARC record, FOLIO will create an instance (i.e. and internal ID). The merge problem needs to be solved by a set of rules. That is where the mapping comes in. Anne-Marie - MARC records are used to build and order, or to build an item. Vince - This is a seperate issue to be dealt with in the acquisition space. The MARC record is a conflation of multiple jobs/purposes. Christie - Updated and merging is very complicated. The holdings and items need logic as well, that will be dependent on the incoming bibliographic record. Vince - The ability to create a template that will help interpret the values
|