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
As an organization that does not run a separate data repository we want to give our data stuarts a chance to review data before they are finally opened/published.
KU Leuven has developed a dataverse extension for this:
It would be great, if we could add such functionality to our repo. However, our approach to handle complex metadata separate from dataverse, may complicate adapting their solution.
The text was updated successfully, but these errors were encountered:
This may alternatively be solved on the side of the local (ELN/LIMS) systems which could have an analogue workflow to prepare sets of files for uploading to repo4cat.
I attended the call today and saw the presentation which should also be published on dataverse-TV in the next days.
This is a really nice extension. Currently it is limited to datasets curation workflows. Collections (and probably organizations) are not supported. As I understood, it is currently not possible to have organization-specific or collections-specific review steps or (permission-wise) independent groups of reviewers. Both would be required to use it for repo4cat.
As an organization that does not run a separate data repository we want to give our data stuarts a chance to review data before they are finally opened/published.
KU Leuven has developed a dataverse extension for this:
It would be great, if we could add such functionality to our repo. However, our approach to handle complex metadata separate from dataverse, may complicate adapting their solution.
The text was updated successfully, but these errors were encountered: