Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guidance and best practice for nested RO-Crates #339

Open
stuzart opened this issue Jul 19, 2024 · 0 comments
Open

Guidance and best practice for nested RO-Crates #339

stuzart opened this issue Jul 19, 2024 · 0 comments
Labels
use-case A (potential) use-case for ROLite creation, consumption or integration

Comments

@stuzart
Copy link
Contributor

stuzart commented Jul 19, 2024

As an RO-Crate creator , I want create an RO-Crate that encapsulates other preexisting RO-Crates, down to multiple levels so that the full set of files and metadata are included within a single package.

For example, a Collection RO-Crate may contain Workflow and Data based RO-Crates, and that Collection RO-Crate may be included in an RO-Crate that describes an experiment. How to avoid a Russian doll situation, and what is the best practice here.

@stuzart stuzart added the use-case A (potential) use-case for ROLite creation, consumption or integration label Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
use-case A (potential) use-case for ROLite creation, consumption or integration
Projects
None yet
Development

No branches or pull requests

1 participant