Terminology

If you are not too familiar with the Data Stewardship Wizard terminology, here you can find definitions of the most frequently used words and phrases.

Administrator

A person who manages the organizational or institutional account. In the DSW this person can create and manage data management plans, knowledge models, templates, and content and systematic settings.

Change of Knowledge Model Item

Adding, editing, deleting of a knowledge item.

Clone Project

To copy / duplicate a Project.

Create Knowledge Model

‌It means creating a new Knowledge Model Branch that contains no Knowledge Model Events.

Create Knowledge Model Migration ‌

A user can select a new parent Knowledge Model for a Knowledge Model Branch that is outdated and create a Knowledge Model Migration.

Customization of Knowledge Model

An ordered collection of changes in another parent knowledge model.

Data Management Plan / DMP

Exported filled questionnaire using a selected template and format that should help a researcher with data management of his / her project.

Data Steward

A person who manages data from a variety of sources. In the DSW a data steward besides creating and managing the data management plans can also create and manage a new knowledge model.

Data Stewardship Wizard / DS Wizard / DSW

‌Our portal solution for Data Management Planning.

Edit Knowledge Model

It means creating a branch for a Knowledge Model Package that is owned by the organization of the current DSW instance. New versions can be published as the next version of the original Knowledge Model Package.

Editor Action

Using the Knowledge Model editor. Knowledge Model can be extended, and events are generated.

Export Knowledge Model

Knowledge Model Package can be exported out of the DSW instance in the form of a Knowledge Model Bundle file (with all its dependencies included).

FAIR Metrics

Metrics that show the FAIRness of the project i.e. how much are the FAIR (F - findable, A - accessible, I - interoperable, R - reusable) principles followed and also give suggestions on how to improve it.

Fork Knowledge Model‌

It means creating a branch for a Knowledge Model Package that is NOT owned by the organization of the current DSW instance. New versions are published as a new Knowledge Model Package.

Finalize Knowledge Model Migration

After all the changes are applied or rejected, the migration can be finalized, and the new version of the Knowledge Model Package can be published.

Generate Document

A Document output can be generated.

Import Knowledge Model

Knowledge Model Bundle file from outside of the DSW instance can be imported. The Knowledge Model Packages contained in the bundle can be then used in DSW.

Knowledge Model / KM

An ordered collection of interlinked KM Items, from which a questionnaire is generated. Identified by a KM ID. May be customized and released as a package. Identified by an ID that consists of Organization ID, KM ID, and Version. It can be exported/imported and further customized.

Knowledge Model Editor ‌

A tool for customization of a KM and its creation and publishing.

Knowledge Model Item

A chapter, question, answer, reference, expert, integration, tag, etc.

Knowledge Model Root / KM Root

A package with no ancestor packages.

Machine-Actionability

The ability of computers to find, access, interoperate, and reuse data without or just minimal help from human.

Migration of Knowledge Model

Upgrade of a KM with a newer version of the parent KM.

Organization

An infrastructure, institution, or a similar body that runs its own copy of DS Wizard. Identified by Organization ID.

Process Knowledge Model Migration

Change During the Knowledge Model migration, each change from the parent Knowledge Model is reviewed and either applied or rejected to the localization Knowledge Model.

Project (∼ Data Management Plan)

Data Stewardship Wizard provides a simple way to create a project using a Knowledge Model and fill the questionnaire in a smart way - only relevant questions for your case will be shown. A project in the DSW is approximately equaled to a data management plan. The dissimilarity is that a project can have a few phases - Before submitting the proposal, Before submitting the data management plan, and Before finishing the project. These phases differ in number and completeness of the questions answered in the project´s questionnaire.

Publish Knowledge Model

It means creating a new version of the Knowledge Model Package from the new events added to the Knowledge Model Branch.

Project Phases

A project can have few phases - Before submitting the proposal, Before submitting the data management plan, and Before finishing the project. These phases differ in number and completeness of the questions answered in the project´s questionnaire.

Questionnaire

A representation of the Knowledge Model in the shape of a form for filling-in.

Registry / DSW Registry

A possibility to use all the DSW available knowledge models, templates, and their updates by an organization or institution. In order to be able to join the registry, the organization / institution has to sign up for it in the System settings.

Researcher

A person who can create and manage her / his own data management plans while using common knowledge models available in the DSW tool. ‌

Save Branch ‌

Saving the branch simply saves all the events generated while using the editor.

Share Project

The visibility of the project (∼ data management plan) can be set to be completely private, or allow users to view your project or edit it. Moreover, it is possible to share it also with non-logged users.

Tags

A label attached to a Knowledge Model for the purpose of identification, or to give more information about it. A user can create different tags and mark different Knowledge Models with them.

Template

Specifying the template and format of the questionnaire will result in the final look of the DMP.

TODOs

A labeling system with which the unanswered questions in the questionnaire can be marked and answered later through the TODOs list. It helps to reassure that all the questions in the project (∼ data management plan) were being answered.