Define default guidance groups (aka tags)

[briri]

We need to review the existing DMPTool guidance and the Themes defined in the current DMPTool.

We want to define the initial groups that will need to be setup in the new system (e.g. Data Preservation, etc.) and then map out in this ticket what those groups are and what the initial guidance should be.

We should also note which (if not all) of these groups are a standard part of every DMP.

It would also be worth looking at the most used templates in the current DMPTool to see if any other guidance groups should be included.

[briri]

The following CSV contains the list of themes currently used in the DMPTool along with some counts to show popularity/usage. query_result.csv

I included the "description" field in the CSV and found it interesting. The text appears to be generic guidance for the theme (probably the original DCC guidance) but I do not see it referenced or displayed anywhere in the tool.

We have had complaints/requests about redundancy between questions on many templates and the data we ask users to provide in the new research outputs tab and collaborators tab (e.g. why have a section/questions asking about project collaborators and their roles, data formats and volumes, which repositories will be used, etc. when we collect that in a structured ways now).

Since we're rethinking these in general, I took the themes from the current system above and some conversations with different AI chat bots to came up with the following revised/consolidated list:

• Budget Description of the budget available for data collection, use and preservation including software licensing, personnel and storage costs
• Data collection How the data will be collected or generated, primary and secondary sources that will be used and any instruments that will be used
• Data description The types of data that will be collected along with their formats and estimated volumes.
• Data organization & documentation Descriptions naming conventions, metadata standards that will be used along with data dictionaries and glossaries
• Data quality & integrity Methods used to ensure data quality and integrity and any procedures used for validation
• Data sharing Policies and procedures for how the data will be shared with collaborators and/or the public, restrictions to access and the licenses and permissions used
• Data storage & backup Where the data will be stored, the backup strategy and frequency and how long it will be retained
• Ethical considerations Ethical considerations during data collection, use or sharing and how informed consent will be obtained from participants
• Roles & responsibilities Descriptions of the project team members and their roles
• Security & privacy Who will have access to the data and how that access will be controlled, how the data will be encrypted and relevant compliance with regulations or standards (e.g. HIPAA, GDPR)
• Training & support Training that will be provided to team members on data management practices and support for data issues

I'm wondering if we should even consider removing Roles & responsibilities or Data storage & backup as tags and instead figure out a way to take the structured data we're collecting and auto-generate a narrative statement for the PDFs.

[bofstein]

Let's look at a query of how often tags are used together to make a call on combining them

[briri]

Here are the uses of themes currently. There is a lot of overlap:

Themes used per Org Guidance: themes_per_guidance.csv

Themes used per Template Section: themes_per_section.csv