Close Menu
Get started free

Demystifying Knowledge Models

When you first hear about a "Knowledge Model", it may sound a bit overwhelming. This blog post explains everything about what the Knowledge Model is, how it works, and why it's important within the FAIR Wizard.

What is Knowledge Model

A Knowledge Model is an integral part of the FAIR Wizard, used to generate questionnaires. By completing these questionnaires, researchers create their Data Management Plans. The FAIR Wizard relies on the Knowledge Model to structure and generate the questionnaire.

The Knowledge Model is organized as a tree-like structure that contains all the elements needed to generate a questionnaire. Most importantly, it consists of Chapters that include Questions, along with other components. The full structure is illustrated in the image below.

Knowledge Model Structure
Knowledge Model Structure

Question Types

A Knowledge Model chapter contains questions. There are six different types of questions, each with its own attributes.

Other Knowledge Model Elements

Although questions are the cornerstone of a Knowledge Model, there are also other elements that help to guide Researchers to provide best possible answers to the Questionnaire.

Integration Question

Setting up an Integration Question can be a bit tricky. That's why we've already created blog posts on configuring an Integration Question and improving an Integration Question item template.

How to Create a Knowledge Model

The Knowledge Model Editor functionality is accessible to Data Steward and Admin roles in the FAIR Wizard. To create a Knowledge Model, navigate to the Knowledge Model Editor section in the menu. A new Knowledge Model can be created from scratch or by forking an existing one. Existing Knowledge Models can also be opened and edited.

Once an editor is open, all previously mentioned elements can be added to the Knowledge Model to facilitate the work of researchers. Multiple users can collaborate on a single Knowledge Model simultaneously, provided they have at least the Data Steward role.

Knowledge Model Editor
Knowledge Model Editor

Publishing a Knowledge Model

Once the Knowledge Model is complete, it is necessary to publish it for accessibility to researchers when they create their projects. Before publishing, fill in all desired fields in the Settings tab. It is also recommended to maintain a changelog in the Readme file, as the Knowledge Model is versioned and will evolve over time. Once the Knowledge Model is published, it can be used to create a project. A new Knowledge Model editor can also be created from any published Knowledge Model.

Knowledge Model Insights

The Analytics App of the FAIR Wizard provides a range of analytical views on various features of the FAIR Wizard. One of these is the Knowledge Model Insights, which offers invaluable information on how researchers work with Knowledge Models. It displays answers compiled from all questionnaires, grouped by the Knowledge Model used to create them.

More information about the Analytics and Knowledge Model insights can be found here.

Knowledge Model Insights
Knowledge Model Insights

Conclusion

Although the Knowledge Model may initially seem complex, working with them is not that complicated. The entire process can be narrowed down to a few steps:

  1. Create a Knowledge Model Editor, either from scratch or from an existing Knowledge Model.
  2. Edit or add everything you want to include in your Knowledge Model.
  3. Fill in the Knowledge Model metadata in the Settings tab.
  4. Publish the Knowledge Model.
  5. Repeat if necessary to create a new version.

The best possible approach to learn how exactly a Knowledge Model works is to open the editor and try to create one. Firstly, initial version of a Knowledge Model can be created. Then, based on feedback it is good to return to that Knowledge Model and further edit it, by adding or removing questions and other elements.

To generate the final Data Management Plan it is also necessary to create a Document Template. Read about that in one of our other blogposts, one on developing a document template and the other on dealing with Diversity of DMP Templates.