Logo Utrecht University

YODA

Data lifecycle in Yoda

The Data Lifecycle is reflected in the following use case in Yoda

Yoda in 10 steps

  1. Rosa starts research “Ebola Virus Test”, evt, and collects data.
  2. Rosa asks access to Yoda.
  3. Data Manager creates group “evt” with group manager Rosa.
  4. Rosa adds her fellow researchers to her group.
  5. Rosa and her fellow researchers and can upload their data to Yoda
  6. Rosa c.s. can work together on the data in the research area.
  7. Rosa prepares datapackages of the data she wants to be stored permanently in the Vault and submits them.
  8. The Data Manager checks the packages before storing in the Vault.
  9. The evt data from the Vault can be published via the Catalogue.
  10. Copy from Vault to Research area.

 

In the next part the 10 steps are described in more detail.

 

In this example Yoda is used without the Intake module. The workflow using The Intake module is discussed in Yoda Portal Intake.

1

Rosa starts research “Ebola Virus Test”, evt, and collects data.
The “Ebola Virus Test” research will produce different files: Microscope images, text files and lab results.

2

Rosa asks access to Yoda.

For a new Yoda project, there are two possibilities:

  • The project is run by a faculty or group that don’t use Yoda.
  • The project is run by a faculty or group where Yoda is already in use.

In the first case the researcher will find information via the UU RDM platform or contact Yoda’s functional application manager

fb@yoda.nl

If Yoda is already known in the faculty and the research would fit in an already running project, access can be requested by mailing the category’s Data Manager.

The Data Manager will grant access, create a new group and will give you Group Manager rights.

3

Data Manager creates group “evt” with group manager Rosa.

Data Manager creates group “evt” with group manager Rosa.

A group is a number of researchers working on the same project.

The Data Manager will create a group for the “Ebola Virus Test” research. The name of the group will be “evt”.

Rosa is assigned group manager of the evt group.

Three folders are automatically created 

  • research-evt
  • vault-evt
  • (intake-evt)

You will see them in the Yoda portal but you will also find three folders in the Yoda tree in for instance Explorer.

4

Rosa adds her fellow researchers to her group.

Rosa will add her fellow researchers to the group. Each member should have the proper access.

5

Rosa and her fellow researchers  and  can upload their data to Yoda (research-evt).

All group members (except those with Read Only rights) can upload files with data to the evt project in Yoda by drag and drop in Explorer from their laptop to the research-evt folder.

Dragging to the Vault is impossible.

More about the Research area in Research Module.

6

Rosa and colleagues can work on the data in the research-evt.

All group members can work together on the data in the research area. After saving a file a new revision is created.

More about revisions can be read in Revisions.

7

Rosa prepares datapackages of the data she wants to be stored permanently and submits them.

Rosa decides which folders from her research should be permanently stored in the Vault. The Vault will only accept datapackages; data accompanied by metadata.

The researchers will open the folders to add applicable metadata in Yoda.

You are advised to read MetaData elaborated to learn about copying metadata files and thus saving time.

Only after all the mandatory metadata fields are filled the package can be submitted to the Vault. Some metadata fields are not applicable to all files and thus these fields are optional.

Yoda validates the yoda-metadata, when submitting the datapackage to the vault. By submitting the datapackage the data in the research area will automatically be locked.

More about datapackages in Datapackage.

8

The Data Manager checks the packages before storing in the Vault.

After a datapackage is submitted the Data Manager will check whether the mandatory metadata fields are filled with relevant text

(in contradiction to something like “later”) in every field. Only after consent the Data Manager accepts the DataPackage for permanent storage in the Vault.

More about the checks can be found in Checks by the Data Manager.

After accepting the datapackage the data in the research area will still be locked.

Working with the data in the research area will only be possible after un-locking after the datapackage is Secured (actually copied to/stored) in the Vault.

More about Lock and Unlock can be found in Lock.

9

The evt data can be published via the Catalogue.

By publishing you can make the metadata of your datapackage stored in the Vault findable in the Catalogue. You can publish your datapackage from within the Yoda portal.

You will receive a Persistent Identifier, DOI (Digital Object Identifier) automatically, thus your data can be:

  • Referred to in articles or other datasets;
  • found in the Yoda Catalogue via its metadata;
  • Depending on the conditions under which you’ve published it, accessed.

10

Copy from Vault to Research area.

When a folder from the Research area is Secured in the Vault the folder in Research is locked. It can be used after unlocking.

From the same folder, a new datapackage can be created and submitted.

Yoda will store this new datapackage in the Vault without overwriting the original datapackage.

The Vault functions as an archive for all versions. In case you want to use an older version this can be copied from the Vault to the Research area.

Note that Rosa needs access to the vault datapackage and to the corresponding research group (e.g. research-evt) in order to be able to copy from Vault to Research.