Package: projectData 0.1.0

Brad Blaser

projectData: Deferred Access to Installed Data Collections

Registers installed, documented data packages as named collections without reading their data, exposes objects through deferred bindings, resolves name conflicts through explicit primary and preference choices, keeps provenance, and offers a loader interface for resources that need format-specific restoration.

Authors:Brad Blaser [aut, cre, cph]

projectData_0.1.0.tar.gz
projectData_0.1.0.zip(r-4.7-any)projectData_0.1.0.zip(r-4.6-any)
projectData_0.1.0.tar.gz(r-4.7-any)projectData_0.1.0.tar.gz(r-4.6-any)
projectData_0.1.0.tgz(r-4.6-emscripten)
manual.pdf |manual.html✨
DESCRIPTION |NEWS
card.svg |card.png
projectData/json (API)

# Install 'projectData' in R:
install.packages('projectData', repos = c('https://cran.r-universe.dev', 'https://cloud.r-project.org'))

Bug tracker:https://github.com/blaserlab/projectdata/issues

On CRAN:

Conda:

3.00 score 8 scripts 23 exports 0 dependencies

Last updated from:dee5e82581. Checks:6 OK. Indexed: yes.

TargetResultTimeFilesSyslog
linux-develOK158
source / vignettesOK223
linux-releaseOK170
windows-develOK243
windows-releaseOK282
wasm-releaseOK79

Exports:data_attachdata_catalogdata_collectionsdata_configdata_detachdata_getdata_helpdata_infodata_inspectdata_loaderdata_loader_adapterdata_loader_adddata_loader_removedata_loadersdata_manifest_draftdata_manifest_validatedata_manifest_writedata_maskingdata_preferdata_preferencesdata_primarydata_querydata_retry

Dependencies:

Using projectData
Why projectData? | 1. Install | 2. Attach | 3. Use | Looking at what is attached | Getting objects explicitly | Getting one object without attaching | First-access messages | Looking at a package without attaching it | Conflicts | Script datasets | Cleaning up | What this does not do
Rendered fromprojectData.Rmdusingknitr::rmarkdown

Last update: 2026-11-11
Started: 2026-11-11

Writing a projectData adapter
1. Why adapters exist | 2. How the adapter architecture works | Resources and objects | The loader | When each operation runs | Manifests and discovery are alternatives | 3. Building a minimal adapter: tinydisk | The format | The loader declaration | Discovery | Validation | Opening | 4. Registering and using an adapter | 5. Distributing adapters and declaring resources | An adapter package is not a data package | Packaging the adapter | Declaring resources in a manifest | Authoring root: source tree vs. installed layout | When the adapter is not installed | 6. Disk-backed resources and lifecycle considerations | 7. Advanced behavior and troubleshooting | Resource identity and caching | Discovery precedence | Registration-time and first-access checks | Roots, layouts, and relative paths | Symlinks and filesystem limits | Optional dependencies and failures | Safety checklist | 8. A real-world example: projectData.monocle3 | 9. Further reading
Rendered fromadapters.Rmdusingknitr::rmarkdown

Last update: 2026-11-11
Started: 2026-11-11