Metatab and Metapack
Metadata for Mortals
Metatab stores metadata in a spreadsheet, alongside data, ensuring that the metadata is easy to create, easy to read, and cannot be separated from the data. Metapack builds data packages with Metatab metadata.
Metatab is a way of writing and storing metadata in the same spreadsheet as a dataset. Because it uses a tool every user already has — a spreadsheet — it is much simpler than documenting metadata in XML or JSON, resulting in more public datasets being properly documented. Metadata is easily read by people and can be programmatically converted to machine formats like JSON, so, with a spreadsheet extension, metadata can be validated while users enter it, and the metadata allows for sophisticated automatic processing.
Metatab is a core part of Metapack, a data packaging format that uses Metatab formatted metadata files for building ZIP, Excel and Directory based data packages.
The Metatab/Metapack system includes:
- A specification for how to write standard metadata elements in a tabular format
- CLI Programs for building metadata files and data packages
- Code libraries for parsing and manipulating Metatab data
We also have demonstrations of:
- Spreadsheet extensions that help users create valid metadata
- A web service that supports the spreadsheet extensions
The core of the project is the Metatab data format, which allows complex information to be represented in a simple, readable way in a spreadsheet. Using Metatab, a data producer can open a dataset in a spreadsheet, and quickly create valid metadata that conforms to standards. After publication, Data consumers can read and understand the metadata with no training and no additional tools.
The Metatab project is just getting started, and we need your help.
- Data Producers. We’re looking for government agencies who produce public data to provide input on their data workflows and other requirements.
- Data Consumers. If you use public data and would like better metadata, knowing what you need will help us get the project funded.
For more information, contact: Eric Busboom.
Metadata Shouldn’t Be Hard
Most of the time, metadata is hard, so most public data producers don’t bother with it. Standard metadata, like Dublin Core, has easy-to-remember metadata terms and elements, but linking it to a file involves writing what most users consider cryptic formats, like RDF, XML, or JSON. Metadata uses standard Dublin Core metadata elements, but allows users to read and write them in a very familar, readable format.
Compare a typical Metatab definition of two metadata elements with the equivalent metadata in RDF:
|Title||An Example Data bundle|
|Description||This data bundle is an example of how simple a data bundle can be.|
<?xml version="1.0"?> <!DOCTYPE rdf:RDF SYSTEM "http://dublincore.org/2000/12/01-dcmes-xml-dtd.dtd"> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/"> <rdf:Description > <dc:title>An Example Data bundle</dc:title> <dc:description xml:lang="en">This data bundle is an example of how simple a data bundle can be.</dc:creator> </rdf:Description> </rdf:RDF>
Easier metadata means more metadata, so allowing public data producers to manage metadata in simple, comprehensible formats with tools they already have will result in more public data being fully documented.
Using Metatab is simple. A typical public data workflow with Metatab would involve:
- A user opens a spreadsheet of data, then adds the Metatab extension to the spreadsheet.
- The Metatab extension creates new worksheets for metadata and a schema, also known as a data dictionary. Metatab reads the data and automatically generates the data dictionary.
- As the user types, the Metatab extension validates the user’s entries, ensuring the metadata is always valid.
- When the user is finished, the file can be saved directly to a data repository like Socrata or CKAN.
Because Metatab is sensible to both humans and computers, it’s easy for people to write metadata that programs can use to alter data. After saving Metatab-formatted spreadsheets, datasets can be automatically uploaded to data repositories like Socrata or CKAN, including all of the metadata. Datasets can be properly routed for approval using workflow tools like Screendoor. Programs can understand what data columns mean and automatically geocode addresses or turn census codes into place names.
The Metatab spreadsheet extension — for both Excel and Google Docs — validates metadata as the user types to ensure that it is always correct. By including a ConformsTo element, users can set the standard used to validate the metadata. By creating a ConformsTo document (which is also a Metatab format file) and making it available on the web, organizations can create their own extensions to metadata elements.
Join the Project
Metatab is an early stage project. The specifications for the Metatab format are nearly complete, and we’re writing the spreadsheet extensions, but we’ll need your help, particularly for providing additional requirements, refining the design, testing, and piloting the early deployments. If you or your organization either produces public data or consumes public data, we’d like to talk to you about your needs. We’re particularly interested in working with state and county health agencies and the public and private organizations that use public health data.
If your organization would benefit from better metadata, please contact the project manager, Eric Busboom, at email@example.com or 619-363-2607.