Hey Folks,
We are running a data packaging task group in GREI and have some questions for the community - kind of urgent on the replies:)
Which packaging approaches do you consider “up-and-coming” or emerging in your domain (e.g., biomedical, environmental, social sciences)?
Thanks so much
Sonia and DV IQSS Team -
@Amber Leahey
Hmm, my first thought is RO-Crate, which @Balázs Pataki @Eryk Kulikowski @Ozgur Karadeniz and @Dieuwertje Bloemen have all worked on. Balázs recently pointed me to a great writeup of Dataverse support for RO-Crate (all implemented by the folks mentioned above!) over at https://www.researchobject.org/ro-crate/dataverse . I opened this issue to remind to to add it to the guides:
Explain RO-Crate support better in the guides #11934
See also #dev > RO-Crate! :smile:
Yes, I agree with Phil, definitely RO-Crate!
Another important packaging standard that Dataverse already supports is BagIt. See https://guides.dataverse.org/en/6.8/installation/config.html#bagit-export
Correct. What standards do we not support, that we should consider supporting
Thanks
Well, right now BagIt is very much a backend thing. Users can't download a BagIt by clicking a button. That might be a nice thing to add, if there's demand for it.
agree, i think about system generated DDI Codebooks and READMEs and ask why there isn't a button to add these as items into the deposits? Because downloads detach these data packages from the DV metadata a bit, why not support deposit packages with READMEs and Codebooks by reusing metadata in the Dataverse system? (which btw some in our community are now supporting see example from UofT (https://dv-readme-gen-dev.deno.dev/) and UBC (https://github.com/ubc-library-rc/dataverse_utils) and McMaster (https://rdm.mcmaster.ca/readme) and we are forming a little README integration tool WG- stay tuned)
For Codebooks > this largely exists within DV and with Data Explorer >
image.png
Philip Durbin 🚀 said:
Well, right now BagIt is very much a backend thing. Users can't download a BagIt by clicking a button. That might be a nice thing to add, if there's demand for it.
agree, and if we can add to the Bagit spec for including DDI XML that would be great. And make this more easily part of Admin workflows, right now we provide exports in Bagit as an alternative to Dataverse - Archivematica integration users. I can see how a stored Bagit copy in addition to the DV storage replication we have will be important in the future.
For biomedical and sensitive data, we are seeing a lot of research data management software, REDCAP, Physio net etc. these systems can export metadata and data for packaging for users to upload to a Dataverse repo, but reviewing these kinds of data deposit workflows to support more standardized approaches would be great.
Geospatial - we need more support for ISO 19115 for specialized geospatial metadata support in DV (which we are working on now...), I think improved identification for .LAZ lidar data and geodatabase continues to be needed.
Last updated: Jan 09 2026 at 14:18 UTC