Data Management Plan
A data management plan asks the researcher to consider how data and associated products of research (such as code or other files) will be handled across the life span of a project and beyond. This includes how the data will be stored, secured, accessed, documented, formatted and versioned. The plan should also include where and when data will be shared, if it will be made publicly available, how it will be licensed for reuse and how and for how long data will be archived. Both general best practices for data management and archiving should be considered as well as any discipline-specific practices for file formats, metadata and documentation that would support the discovery and reuse of the data. If your research involves human subjects or other sensitive information, ethics, consent, and de-identification of data should also be addressed.
Research Informatics Services- Planning & Design
Research Informatics has provided guiance to support researchers in completing thier data management and sharing plan, as described in the National Institutes of Health (NIH). Here you will find resources and tools aligned with the NIHs final policy
Data Concierge- for assistance, information & resources with the DMSP dataconcierge@kumc.edu. Build Your Plan- Planning & Design Create Data Management Plans that meet requirements and promote your research.
You have free access to an online tool for writing DMPs: To use the DMPTool. You just need to sign in as a KUMC researcher, and you’ll have access to templates, example DMPs, and KUMC-specific guidance. You can also find some helpful public guidance on using DMPTool To build your Data Management Plan visit this link DMPTool Map out the processes and resources for the entire data life cycle. Start with the project goals (desired outputs, outcomes, and impacts) and work backwards to build a data management plan, supporting data policies, and sustainability plans.
Observations are made either by hand or with sensors or other instruments and the data are placed a into digital form. You can structure the process of collecting data up front to better implement data management. Employ quality assurance and quality control procedures that enhance the quality of data (e.g., training participants, routine instrument calibration) and identify potential errors and techniques to address them
For more informationvisit DataONE's Data Management Assurance Stage
Document data by describing the why, who, what, when, where, and how of the data. Metadata, or data about data, are key to data sharing and reuse, and many tools such as standards and software are available to help describe data. For more information about Data Types Briefly describe the scientific data to be managed and shared: Demographic, clinical, and MRI, 1H fMRS and fMRI imaging data will be acquired from 110 affected youth and 110 matched healthy controls (described in detail in sections C.3 and C.4 of this application). All data will be de-identified prior to receipt by the repository, but the information needed to generate a global unique identifier for the NIMH Data Archive (NDA) will be collected for each subject. Sufficient data from this project will be preserved to enable sharing via NDA data of sufficient quality to validate and replicate research findings described in the Aims. NIMH requires data measured from human subjects to be shared using the NDA In addition to the subject level data described above, all 1H fMRS and fMRI task related paradigm designs and experiment definitions will be deposited in the NDA.
Participant age, sex, ethnicity, height, weight, socioeconomic status, and other demographic data will be collected using the following instruments as defined in NDA:
Research Subject and Pedigree (ndar_subject01) Demographics Short Form (demsf01) Ethnic Group Questionnaire (ethgrp01) Height and Weight (height_weight01) Hollingshead Socioeconomic Rating Scale (ses01) Pubertal Development Scale (pds01) Edinburgh Handedness Inventory (edinburgh_hand01) WASI-2 (wasi201)" In compliance with NOT-MH-20-067, the following data will be collected to facilitate aggregation of this data set with other data sets: DSM Crosscutting for Youth (dsm5crossch01) RCADS-25 (rcads2501) Kiddie-SADS-Present and Lifetime Version (ksads_pl01) Children’s Yale-Brown Obsessive Compulsive Scale (cybocs01) Schedule for Obsessive-Compulsive and Other Behavioral Syndromes (Hanna. Schedule for Obsessive-Compulsive and Other Behavioral Syndromes, Ann Arbor: University of Michigan, 2010, new data dictionary will be defined in NDA) Dimensional Obsessive Compulsive Scale (docs01) Yale Global Tic Severity Scale (yale01) Child Behavior Checklist (cbcl01) Multidimensional Anxiety Scale for Child Parent and Self (masc_p01) Conners 3 (conners3_ps01) Adolescent Depression Rating Scale (doi:10.1186/1471-244X-7-2, new data dictionary will be defined in NDA) 1H fMRS and fMRI data will be shared with the Image (image03), Imaging Work Flow (iwf01), and Imaging Collection (imagingcollection01) data dictionaries as defined in NDA. Create analyses and visualizations to identify patterns, test hypotheses, and illustrate finding. During this process record your methods, document data processing steps, and ensure your data are reproduceable. Research Informatics Services- Data Analysis The clinical data will be analyzed with custom Python code written using the statsmodels, numpy, and pandas packages, all of which are freely available. 1H fMRS spectra will be analyzed with LCModel 6.3 software using LCMgui, which is freely available. fMRI images will be analyzed using the SPM8 toolbox for MATLAB. While MATLAB is commercial software, most universities have site licenses available and the SPM8 toolbox is free. It is also possible that the toolbox might run in Octave, an open-source alternative to MATLAB, but we have not tried it. All code will be shared on our GitHub lab website. The code can be found by searching for “labname” on GitHub. The main readme.md file for the project will also include instructions and parameter choices for the GUI-based analyses. Plan to preserve data in the short term to minimize potential losses (e.g., via accidents), and in the long term so that project stakeholders and others can access, interpret, and use the data in the future. Decide what data to preserve, where to preserve it, and what documentation needs to accompany the data.
For more information visit DataONE's Data Presevation Stage
Research Informatics Services- Storage & Archive KU ScholarWorks (KUSW) is the institutional repository at the University of Kansas, Lawrence and Edwards campuses. Its aim is to centralize and provide persistent and reliable access to the research output, scholarship, and creative works of faculty, academic staff, and students at KU in addition to housing digital content from the University Archives. KUSW complements traditional publishing outlets by increasing access to the scholarly journal literature produced by KU researchers and by hosting journals edited by KU faculty and departments. As an evolving resource, an ongoing focus of the repository is to capture emerging research driven by the intellectual environment of the campus, in addition to providing access to documents that are of permanent value to the University.
The collections in KUSW are focused on the research, scholarship, creative works of KU faculty and researchers, and in some cases students, as well as materials that document the history of the University and reflect its intellectual environment. All data will be deposited to NDA starting 12 months after the award begins and will be deposited every six months thereafter following the usual NDA data submission dates. Data will be findable for the research community through the NDA Collection that will be established when this application is funded. For all publications, an NDA study will be created. Each of those studies is assigned a digital object identifier (DOI). This data DOI will be referenced in the publication to allow the research community easy access to the exact data used in the publication. Note that NIH encourages scientific data to be shared as soon as possible, and no later than the time of an associated publication or end of the performance period, whichever comes first. NIH also encourages researchers to make scientific data available for as long as they anticipate it being useful for the larger research community, institutions, and/or the broader public.
Indicate how compliance with the DMS Plan will be monitored and managed, the frequency of oversight, and by whom (e.g., title, roles). This element refers to oversight by the funded institution, rather than by NIH. The DMS Policy does not create any expectations about who will be responsible for Plan oversight at the institution.
Research Informatics Services- Oversight of Data Management and Sharing See our Guidance for Institutional Repositories and Oversight(Planning & Design) Data from multiple sources are combined into a form that can be readily analyzed. For example, you could combine citizen science project data with other sources of data to enable new analyses and investigations.
For more information please visitDataONE's Data Presevation Stage
Identify complementary data sets that can add value to project data. Strategies to help endure the data have maximum impact include registering the project on a project directory site, depositing data in an open repository, and adding data descriptions to metadata clearing houses.
Describe how compliance with this Plan will be monitored and managed, frequency of oversight, and by whom at your institution (e.g., titles, roles). The Office of Sponsored Programs at University X that will be administering this award has created a data management and sharing plan compliance system as part of their process for submitting the annual NIH progress report. That Office is collecting information related to the number of research participants that are deposited each reporting year. The Office of Sponsored Programs will also look for the NDA data DOIs from NDA Studies and will include that information in the annual progress report. Validation Schedule (this section is required by NIMH) If funded, within 6 months of the Notice of Award date we will submit a Data Submission Agreement signed by the principal investigators and an institutional business official, as well as define and complete the Data Expected section of this project. Uploads of all initial demographic, clinical, and raw structural MRI, 1H fMRS and fMRI research data will be completed using the second submission cycle deadline following the Notice of Award date. Subsequent data uploads will be harmonized, validated, and submitted biannually on the standard January 15th and July 15th submission deadlines.
We also plan to use the NDA validation tool as a quality control measure in the laboratory. The data manager in charge of submitting data to NDA will help researchers in the group validate their data once every month.
Data Management Elements
Resources for the Data Plan
Best Practices
For students and others new to data management, DataONE provides a Best Practices Primer as an introduction to this Best Practices database and data management in general.
Collect & Create
Assurance Stage
Data Descriptions
Sample Plans: Data Type
Consider the following:
Sample Plans: Standards
State what common data standards will be applied to the scientific data and associated metadata to enable interoperability of datasets and resources and provide the name(s) of the data standards that will be applied and describe how these data standards will be applied to the scientific data generated by the research proposed in this project. If applicable, indicate that no consensus standards exist.
The clinical assessments we plan to collect for this study include:
Data Analysis
Sample Plans: Related Tools, Software and/or Code
Consider the following:
Archive & Preservation
Sample Plans: Data Preservation, Access, and Associated Timelines
Give plans and timelines for data preservation and access, including:
Data Sharing
Data Visualization & Integration”
Data Discovery
Sample Plans: Oversight of Data Management and Sharing
University of Kansas Medical Center
Research Informatics
Student Center, 3001C
3901 Rainbow Boulevard
Kansas City KS 66160
913-588-7251
Research and Project Requests: dataconcierge@kumc.edu
HERON and REDCap support: ocriosupport@kumc.edu