You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey I have a small (but maybe annoying to implement) request. Let me know what you think. When I think of Research Objects, I think big bulky static objects however, they can be incredibly portable because users can define external data. This means that RO-Crates are incredibly portable! It would be awesome to be able to turn these lightweight crates into their big bulky archive-ready formats with the stoke of a key.
Use Case: A researcher downloads an RO from a repository and wants to resolve all of the externally defined data in ro-crate-metadata.jsonld.
I don't think that this is a particularly common use case however, it's one of the primary reasons people use other formats such as BD-Bag (gives them a fetch.txt and their software can resolve entries). RO-Crate stores equivalent information and with a little parsing, should be able to be feature parity. I find that to be a really neat feature that's definitely worth advertising.
The text was updated successfully, but these errors were encountered:
Thanks for the input.
I just added a template to work on this method soon. It would be included in the library for ro-crate specification 1.1, which defined the basis to define remote datasets.
Hey I have a small (but maybe annoying to implement) request. Let me know what you think. When I think of Research Objects, I think big bulky static objects however, they can be incredibly portable because users can define external data. This means that RO-Crates are incredibly portable! It would be awesome to be able to turn these lightweight crates into their big bulky archive-ready formats with the stoke of a key.
Use Case: A researcher downloads an RO from a repository and wants to resolve all of the externally defined data in
ro-crate-metadata.jsonld
.I don't think that this is a particularly common use case however, it's one of the primary reasons people use other formats such as BD-Bag (gives them a fetch.txt and their software can resolve entries). RO-Crate stores equivalent information and with a little parsing, should be able to be feature parity. I find that to be a really neat feature that's definitely worth advertising.
The text was updated successfully, but these errors were encountered: