Our mission at Hugging Face is to democratize good machine learning. That features best practices that make ML models and datasets more reproducible, higher documented, and easier to make use of and share.
To resolve this challenge, we’re excited to announce that you may now generate a DOI on your model or dataset directly from the Hub!
DOIs could be generated directly out of your repo settings, and anyone will then find a way to cite your work by clicking “Cite this model/dataset” in your model or dataset page 🔥.
DOIs in a nutshell and why do they matter?
DOIs (Digital Object Identifiers) are strings uniquely identifying a digital object, anything from articles to figures, including datasets and models. DOIs are tied to object metadata, including the thing’s URL, version, creation date, description, etc. They’re a commonly accepted reference to digital resources across research and academic communities; they’re analogous to a book’s ISBN.
DOIs make finding details about a model or dataset easier and sharing them with the world via a everlasting link that may never expire or change. As such, datasets/models with DOIs are intended to persist perpetually and should only be deleted upon filing a request with our support.
How are DOIs being assigned by Hugging Face?
We’ve partnered with DataCite to permit registered Hub users to request a DOI for his or her model or dataset. Once they’ve filled out the mandatory metadata, they receive a shiny latest DOI 🌟!
If ever there’s a new edition of a model or dataset, the DOI can easily be updated, and the previous version of the DOI gets outdated. This makes it easy to check with a selected version of an object, even when it has modified.
Have ideas for more improvements we will make? Many features, similar to this, come directly from community feedback. Please drop us a note or tweet us at @HuggingFace to share yours or open a difficulty on huggingface/hub-docs 🤗
Thanks DataCite team for this partnership! Thanks also Alix Leroy, Bram Vanroy, Daniel van Strien and Yoshitomo Matsubara for starting and fostering the discussion on this hub-docs GitHub issue.
