Calcyte is (will be) a toolkit for managing metadata for collections of content
via automatically generated spreadsheets and for creating static HTML repositories.
Calcyte targets the Draft DataCrate Packaging format v0.2.
At this stage Calcyte does not Bag content, it jsut creates Working DataCrates.
This document specifies a method of organising file-based data with associated metadata, known as DataCrate in both human and machine readable formats, based on the schema.org linked-data vocabularly, supplemented with terms from the SPAR ontologies and [PCDM] where schema.org does not have coverage. The motivation for this work comes from the research domain.
A DataCrate is a dataset a set of files contained in a single directory. There are two ways of organizing a DataCrate.
For working data or data that does not need to be distributed with checksums, a Working DataCrate is a plain-old directory containing payload data files, with two metadata files at the root; one for humans and one for machines.
For distribution, or archiving; where integrity is important, a Bagged DataCrate is a BagIt bag conforming to the DataCrate BagIt profile with the payload files in the /data directory. A Bagged DataCrate has a clear separation between metadata and payload, and can be integrity-checked using the checksums in the BagIt manifest.
Calcyte is (will be) a toolkit for managing metadata for collections of content
via automatically generated spreadsheets and for creating static HTML repositories.
Calcyte targets the Draft DataCrate Packaging format v0.2.
At this stage Calcyte does not Bag content, it jsut creates Working DataCrates.
Within GOKb, participants can work on creating high-quality data in areas that mesh with their skills and priorities. The data can then be reused by anyone, for any purpose. Potential use cases include knowledge bases providers looking to supplement their data, libraries building open source software, and individuals experimenting with open data.
This paper introduces application profiles as a type of metadata schema. We use application profiles as a way of making sense of the differing relationship that implementors and namespace managers have towards metadata schema, and the different ways they use and develop schema. The idea of application profiles grew out of UKOLN's work on the DESIRE project (1), and since then has proved so helpful to us in our discussions of schemas and registries that we want to throw it out for wider discussion in the run-up to the DC8 Workshop in Ottawa in October.
DataCite, CrossRef und mEDRA lieferen auf Anforderung Metadaten zu einer DOI in verschiedenen Formaten zurück: RDF XML (application/rdf+xml), RDF Turtle (text/turtle), Citeproc JSON (application/vnd.citationstyles.csl+json), Formatted text citation (text/x-bibliography), BibTeX (application/x-bibtex),
DataCite und CrossRef: RIS (application/x-research-info-systems)
Nur DataCite: Schema.org in JSON-LD (application/vnd.schemaorg.ld+json), DataCite XML (application/vnd.datacite.datacite+xml)
Nur CrossRef: CrossRef Unixref XML (application/vnd.crossref.unixref+xml)
Nur mEDRA: ONIX for DOI (application/vnd.medra.onixdoi+xml)
METS: An Overview & Tutorial: Metadata Encoding and Transmission Standard (METS) Official Web Site. The METS schema is a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium. The standard is maintained in the Network Development and MARC Standards Office of the Library of Congress, and is being developed as an initiative of the Digital Library Federation.