contentid: An Interface for Content-Based Identifiers

An interface for creating, registering, and resolving content-based identifiers for data management. Content-based identifiers rely on the 'cryptographic' hashes to refer to the files they identify, thus, anyone possessing the file can compute the identifier using a well-known standard algorithm, such as 'SHA256'. By registering a URL at which the content is accessible to a public archive (such as Hash Archive) or depositing data in a scientific repository such 'Zenodo', 'DataONE' or 'SoftwareHeritage', the content identifier can serve many functions typically associated with A Digital Object Identifier ('DOI'). Unlike location-based identifiers like 'DOIs', content-based identifiers permit the same content to be registered in many locations.

Version: 0.0.18
Depends: R (≥ 4.0)
Imports: openssl (≥ 1.4.2), httr, curl, fs, tools, methods
Suggests: knitr, rmarkdown, testthat, covr, thor, vroom, spelling
Published: 2023-10-23
DOI: 10.32614/CRAN.package.contentid
Author: Carl Boettiger ORCID iD [aut, cre], Jorrit Poelen ORCID iD [aut], NSF OAC 1839201 [fnd] (
Maintainer: Carl Boettiger <cboettig at>
License: MIT + file LICENSE
NeedsCompilation: no
Language: en-US
Materials: README NEWS
CRAN checks: contentid results


Reference manual: contentid.pdf
Vignettes: Introduction to 'contentid'


Package source: contentid_0.0.18.tar.gz
Windows binaries: r-devel:, r-release:, r-oldrel:
macOS binaries: r-release (arm64): contentid_0.0.18.tgz, r-oldrel (arm64): contentid_0.0.18.tgz, r-release (x86_64): contentid_0.0.18.tgz, r-oldrel (x86_64): contentid_0.0.18.tgz
Old sources: contentid archive

Reverse dependencies:

Reverse imports: rfishbase, taxadb, taxalight
Reverse suggests: bdc


Please use the canonical form to link to this page.