Provenance for a resource — getaca

Answers, for a cached resource: which package declared it, which registry state and which policy resolved it, the exact version, declared and observed checksums, which mirror served it, when it was fetched and when it was last fully verified, its license and DOI, any processor applied, which getaca retrieved it, and the local path. Suitable for a reproducibility appendix or a bug report.

Usage

getaca_info(
  name,
  package = NULL,
  registry = NULL,
  version = NULL,
  processed = TRUE
)

Arguments

name: Resource name as declared by package.
package: Declaring package. The resource identity is package / name / version, so two packages declaring the same name never collide.
registry: A registry() object, for standalone use without a declaring package.
version: Explicit version, bypassing channel resolution. Use this to hold an analysis to one release.
processed: Apply the declared processor(), when there is one, and return the processed path. FALSE returns the raw artefact.

Value

A getaca_entry, or NULL when the resource is not cached.

Details

The registry state appears as a registry_digest(), so the declaration that resolved the resource can be identified exactly rather than by a number someone kept in step by hand.