data-management-organization

Organize research data with naming conventions, metadata documentation, version control, and FAIR-aligned preservation.

1|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/RHuebner1972/doctoral-second-brain --skill data-management-organization-rhuebner1972
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-management-organization
Source: https://github.com/RHuebner1972/doctoral-second-brain/tree/main/skills/data-management-organization
Command: npx skills add https://github.com/RHuebner1972/doctoral-second-brain --skill data-management-organization-rhuebner1972

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research data quickly becomes chaotic without structure: files get lost, versions conflict, sensitive participant information is mishandled, and analyses become impossible to reproduce. This Skill provides a complete system for organizing, documenting, securing, and preserving research data so your work stays reproducible and compliant with IRB and funder requirements. ## Core Features & Use Cases - Folder Structure & Naming Conventions: Establishes a numbered project hierarchy (raw data, processed data, analysis, documentation) with standardized file naming templates like INT_2024_001_2024-01-15_v1.mp3. - Documentation & Metadata: Provides templates for data dictionaries, qualitative codebooks, README files, and processing logs that record every transformation applied to your data. - Security & Preservation: Covers sensitivity classification, de-identification procedures, encryption, 3-2-1 backup strategy, long-term format preservation, and repository deposit with data availability statements. - Use Case: A doctoral student collecting 50 confidential interviews uses this Skill to set up an encrypted folder structure, de-identify transcripts with pseudonyms, maintain a version control log, and write a data management plan for their IRB protocol. ## Quick Start Help me set up a data management system for my dissertation research, including folder structure, file naming conventions, and a data dictionary for my interview and survey data.

Frequently Asked Questions about data-management-organization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize research data files for a dissertation?

Use a numbered folder hierarchy separating raw data, processed data, analysis scripts, documentation, and outputs. Apply consistent file naming with project code, data type, identifier, ISO date, and version number, and keep a README at the project root.

What is a data dictionary and how do I create one?

A data dictionary defines every variable in your dataset, including name, label, data type, value range, units, coding scheme, and missing value codes. Create one as a spreadsheet and update it whenever variables are added or transformed.

How do I de-identify interview transcripts for qualitative research?

Replace names with pseudonyms, generalize dates to month and year, remove contact details, and broaden specific locations to regions. Store the name-to-pseudonym mapping in a separate encrypted file, and remove distinctive details that could re-identify participants.

What is the 3-2-1 backup rule for research data?

Keep three copies of important data on two different storage media with one copy offsite. A typical setup is an encrypted local drive, an institutional server, and encrypted cloud storage, plus an archived external drive stored securely offsite.

Should I use Git or manual versioning for research data files?

Manual versioning with incremental version numbers and a change log works for small solo projects. Git is better for collaborative or code-heavy analysis because it tracks full change history, supports branching, and allows rollback to previous states.

What file formats are best for long-term data preservation?

Use open, non-proprietary formats: CSV instead of XLSX, TXT or Markdown instead of DOCX, WAV instead of MP3, and TIF instead of JPG. Test readability every five to seven years and store multiple geographically separated copies.