Machine-readable Metadata Modeling Specification (M3) Working Group
Scope & Objectives
There have been a number of projects, discussions, and brainstorming around better ways to define, document, and use metadata models. This working group will develop a draft specification for a machine-readable format for metadata modeling, which can be used to generate human/user-facing documentation, batch data entry templates, and define system functionality (and maybe more!)
Potential benefits include:
Automating creation and maintenance of in-sync, up-to-date human-readable documentation and batch data entry templates
Enable development of code/gems/microservices which are not tied to specific institutional metadata models and are thus easier to reuse
Facilitate sharing and reuse of metadata models
Support formal releases and versioning of metadata models
Enable development of more flexible infrastructure through abstraction of metadata
With supporting infrastructure, simplify the process for adding new metadata elements or changing metadata based configuration settings, reducing work required and opportunities for errors
Work on an initial draft specification is in the Houndstooth repository and is based on Scooby Snacks and Dog Biscuits
Other related community work:
Deliverables & Timeframe
Deliverables
Develop a data dictionary for meta-metadata properties to enable documentation generation and code configuration.
Identify candidate serializations and file formats (yml, csv, json, etc.) and any specific format requirements.
Create example data dictionaries using the specification.
Timeline
Work will run for approximately two to three months, starting in early 2019.
Meeting Times & Communication Channels
Weekly meeting - Updated meeting time - starting June 5, 2019
- Wednesdays 10:00-10:30am PST/1:30-1:30pm EST/ 6:30-6:30pm GMT
- Zoom meeting link https://ucsd.zoom.us/j/188825841
Members
This working group needs both developers and metadata experts!
Note that Working Groups must have participants from three different Partners. All members of a working group producing software must be licensed Samvera contributors covered by the appropriate CLAs. Other types of contributions such as requirements, design, best practices, documentation, etc. - do not require CLAs but participants should accept that the materials to which they contribute may be released under a Creative Commons Attribution 4.0 International License..
- Chrissy Rissmeyer (she/her), co-facilitator (UC Santa Barbara)
- Arwen Hutt, co-facilitator (UC San Diego)
- Alexandra Dunn (UC Santa Barbara)
- jen young (Northwestern)
- Jason Partridge (Oxford)
- sarahbarkla (Oxford)
- Julie Allinson (Co-Sector)
- Randall Floyd(Indiana)
- Juliet Hardesty (Indiana)
- Daniel Pierce (Indiana)
- Ryan Johnson (UC San Diego)
- Anna Goslen (UNC Chapel Hill)
- Adam Wead (Penn State)
- ruth.k.tillman (Penn State)
- LaRita Robinson (Notre Dame)
- Ned Henry (UC Santa Cruz)
- Aaron Neslin (WPI)
- Jenn Colt (Cornell)
- Claudia Horning (UCLA)
- arcadia (Stanford)
- Cara Key (Oregon State University)
- alexander.may (Tufts University)
- Annamarie Klose (Ohio State University)
Resources
Meeting Notes
- list of links
- or table of meeting notes