datalad / datalad-registry

MIT License
0 stars 2 forks source link

"Register" DataLad with identifiers.org? #67

Open yarikoptic opened 6 years ago

yarikoptic commented 6 years ago

What is the problem?

We should register our prefix (datalad:) which would disambiguate the DataLad UUID(is it possible? or only by path?) to the location(s?) of the dataset.

I wondered even if that should be used as "the registry" (#947) we proposed to work on: they already seems to provide many needed pieces, but not sure if it would be "open" for "anonymous" submission of the entries/pointers. in our case registry should be the one "checking" the target urls and fetching/aggregating

TODOs:

mih commented 5 years ago

This looks very good!

https://registry.identifiers.org/prefixregistrationrequest

soichih commented 3 years ago

Does identifiers.org provide services like datacite/doi - but limited to the bioinformatics?

yarikoptic commented 3 years ago

AFAIK it doesn't provide dois. Not sure if provides citations (didn't check). We use it for dandi archive so not limited to a field AFAIK

adswa commented 3 years ago

There seems to be consensus to do it, right?

Can we brainstorm together what to put in the fields?


Namespace Details

Namespace Name:

The name of the new ID space. Example: Protein Data Bank.

datalad

Description

Short description of the ID space in one or multiple sentences. Example: The Protein Data Bank is the single worldwide archive of structural data of biological macromolecules.

DataLad is a Python-based tool for the joint management of code, data, and their relationship, built on top of a versatile system for data logistics (git-annex) and the distributed version control system (Git).

Requested Prefix

Character string meant to precede the colon in resolved identifiers. No spaces or punctuation, only lowercase alphanumerical characters, underscores and dots. Example: pdb.

datalad

Sample Id

An example local identifier. Example: 2gc4.

TODO

Regex pattern

A regular expression definition of the IDs in this namespace. Example: ^[0-9][A-Za-z0-9]{3}$.

TODO

Supporting references (Optional)

Supporting references (URLs, citations), if any, to published work describing the resource. Enter one per line. Example: https://doi.org/10.1093/nar/28.1.235.

https://doi.org/10.21105/joss.03262

Additional information (Optional)

Anything else you wish to tell or ask us.

TODO


Institution details

Which institution should we put there? It looks like it accepts only one. FZJ would be https://ror.org/02nv7yv05, Dartmouth college would be https://ror.org/049s0rh22


Provider details

This could be copied over from the institution we input, or we need to create descriptions ourselves for, e.g., datalad as an organization.

Name

The name of the provider. Example: ChEBI (Chemical Entities of Biological Interest).

Description

Short description of the provider in one or multiple sentences. Example: ChEBI (Chemical Entities of Biological Interest) at EMBL-EBI.

Home URL

URL for a home page that describes the role of the provider in the current namespace. Example: http://www.pdbe.org/.

Provider code

This is a unique identifier for the provider within the namespace, for forced resolution requests. No spaces or punctuation, only lowercase alphanumerical characters, underscores and dots. Example: pdb.

URL Pattern

A URL-like string specifying a rule for resolving this identifier. The rule should contain the key "{$id}", which acts as a placeholder for the resolution services. Example: http://www.ebi.ac.uk/pdbe/entry/pdb/{$id}.

Location

The location from which the provider is offering its services (main location in case of multiple ones).


Requester details

Fullname

email

yarikoptic commented 2 years ago

I will transfer to registry since most likely it would be something like datalad:uuid and we would need to resolve correspondingly etc.

yarikoptic commented 8 months ago

I have initiated registration for registry, but then realized that it better gets associated with CON. Submitted application -- Now we got ROR for CON: https://ror.org/04tfhh831 , the github issue was