BLOG - 2021-09-29
With the recent announcement that Hypergraph will evolve into a web publishing platform for research modules (with a new name forthcoming), Liberate Science also signed up to become a member of CrossRef.
This means we'll start issuing ("minting") Digital Object Identifiers (DOIs) for research modules in the near future. A clear and long-term strategy for this is valuable, and I want to share that journey openly.
In this post, I expand how our DOIs will look like.
A DOI is like an entry in a phonebook, resolving an ID (name) to information about that ID - most often a URL. Each DOI is constructed with a prefix for the issuer (
10.53962 in our case) and a suffix for the specific content.
The suffix has to be unique and is strongly recommended to be opaque (e.g., not include the date of issuing). This DOI Primer provides more in-depth information on DOIs (your favorite TV show probably has one too!).
We will generate DOIs inspired by Martin Fenner's "Cool DOIs" idea.
In short this means our DOIs will look like this:
Specifically, we will generate DOI suffixes using the following algorithm:
As an example, we'll do the same procedure for an example number. For ease of the example, we'll aim for only four characters (
xxxx) instead of eight (
[11101, 10001, 0011](note the last one is not five characters, but can be right filled with zeroes, as
00011are both 3 in binary)
29, 17, 3
15,123 % 32 = 19which is a
xh3kresulting in our DOI
As mentioned before, our DOIs will have eight characters (
xxxx-xxxx), which allows for roughly 17 billion unique suffixes, which we do not expect to exhaust in our lifetime.
If we do end up exhausting these 17 billion options, we can always extend the schema with another four characters:
xxxx-xxxx-xxxx. In that situation we may have paid CrossRef billions because each issued DOI for a journal article would cost us around $1 (on top of our yearly membership fees).
DOIs are most frequently issued for papers, preprints, books, and some other types. It remains unclear at the moment what type a research module would fall under (if any), as these have specific needs regarding provenance (e.g., parent modules). How we will end up implementing our automated registration is something we will also have to figure out.
I will keep you posted on how this develops through future blog posts.