history_swh

The url address to a GitHub, GitLab, or other recognized repository origin

origin_url

the domain name for the Software Heritage API

host

Note that unlike the generic <a rd-options="" href="/link/history?package=contentid&version=0.0.15" data-mini-rdoc="contentid::history">history</a> method, SWH history is repo-specific
rather than content-specific. An archive event adds all content from the repo
to the Software Heritage archival snapshot at once. Any individual file can still
be referenced by its content identifier.

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.

Carl Boettiger

contentid

An Interface for Content-Based Identifiers

Jorrit Poelen

NSF OAC 1839201 

history_swh function

Note that unlike the generic <a rd-options='' href='history'>history</a> method, SWH history is repo-specific
rather than content-specific. An archive event adds all content from the repo
to the Software Heritage archival snapshot at once. Any individual file can still
be referenced by its content identifier.

history_swh: return the history of archive events of a given software repository

Description

Usage

Arguments

See Also

Examples