Open sgoggins opened 8 years ago
Implementation idea: Use the Wikibase instance to store and let people search for manifests.
Possibly use DOI's generated by DataCite, Zenoto, Figshare or EasyID as the identifiers ... Could be under Flossmole possibly? EasyID has an API
Wikidata uses Wikibase to do this - everything gets a 'Q' id assigned when created, and you can track their history over time as well - see https://www.wikidata.org/wiki/Q30 for an example (that refers to the United States)
(and people usually use UIs like http://tools.wmflabs.org/reasonator/?&q=30 to view/edit rather than wikibase itself, or bots to do mass edits)
There should be a manifest primary key (identifier for each data set) generator and repository for manifests developed. People should have the option of storing data sets at the same time and this should be connected to the developed Jupyter Hub Infrastructure.
The API should be built to provide important fields like: Manifest Version ID ... etc (See Manifest)