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.
Define format agnostic structure and syntax requirements.
Identify candidate serializations and file formats (yml, csv, json, etc.) and any specific format requirements.
Create example data dictionaries using the specification.
Identify future work opportunities.
Timeline
Work will run for approximately two to three months, starting in early 2019.
Participation
This working group needs both developers and metadata experts!
Meeting Times & Communication Channels
Note that following current best practices within Hydra, Working and Interest groups should use an existing channel unless and until it becomes clear that a dedicated channel is needed. This section should specify which existing channel(s) will be used: e.g., samvera-tech, samvera-partners, samvera-community@googlegroups.com. When using a shared channel, individual working groups should start the subject line with their name in []s, such as [archives] for the Archives Working Group. If and when a dedicated channel is needed, the new channel should be well publicized and open to any interested subscribers/participants in the community.
Members
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 particpants should accept that the materials to which they contribute may be released under a Creative Commons Attribution 4.0 International License..
- facilitator's name here, facilitator (facilitator's institution here)
- your name here (your institution here)
Resources
- helpful links
Meeting Notes
- list of links
- or table of meeting notes