Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a manifest key generator and repository #10

Open
sgoggins opened this issue May 24, 2016 · 4 comments
Open

Create a manifest key generator and repository #10

sgoggins opened this issue May 24, 2016 · 4 comments

Comments

@sgoggins
Copy link
Member

sgoggins commented May 24, 2016

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)

@sgoggins
Copy link
Member Author

Implementation idea: Use the Wikibase instance to store and let people search for manifests.

@sgoggins
Copy link
Member Author

Possibly use DOI's generated by DataCite, Zenoto, Figshare or EasyID as the identifiers ...
Could be under Flossmole possibly?
EasyID has an API

@yuvipanda
Copy link
Contributor

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)

@yuvipanda
Copy link
Contributor

(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)

@sgoggins sgoggins added this to the Omaha, August 2016 milestone Jul 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants