Skip to content

Parks patch dataOrg #524

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jliermann merged 3 commits into from
Jun 23, 2026
Merged

Parks patch dataOrg #524

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a0da892
modify point on git for versioning
nap84 Jun 22, 2026
10d908e
add: johnny decimal to folder structure
nap84 Jun 22, 2026
6b46caf
Merge branch 'localisation' into parks-patch-dataOrg
jliermann Jun 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions docs/30_data/30_data_organisation.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,9 +72,9 @@ Stash snapshots or simply track changes and allow to find something that existed

#### Possible Solutions

- Low number of requirements: manage manually e.g. by keeping a log where the changes for each respective file is documented, version by version.
- For automatic management of versioning, conflict resolution and back-tracing capabilities, use a proper version control software such as [Git](https://git-scm.com/), hosted either remotely on a portal such as Codeberg, Forgejo, SourceHut, or at your home institution (most usually GitLab). Very strong with uncompressed, readable and comparable files such as text files or csv.
- Use a Cloud Storage service (see [Data Storage and Archiving](/docs/data_storage)) that provides automatic file versioning. Very strong on spreadsheets, text files and slides.
- Low number of requirements: manage manually e.g. by keeping a log where the changes for each respective file is documented, version by version.
- For automatic management of versioning, conflict resolution and back-tracing capabilities, use a proper version control software such as [Git](https://git-scm.com/), which can be installed for free locally, while hosted solutions e.g. [GitHub](https://github.com/) or your home institution faciliate collaboration. Highly recommended for uncompressed, readable, and comparable files such as text files or csv.
- Use a Cloud Storage service (see [Data Storage and Archiving](/docs/data_storage)) that provides automatic file versioning. Very strong on spreadsheets, text files and slides.

## Files: types of metadata

Expand Down Expand Up @@ -110,6 +110,8 @@ Folders should:

The top folder should have a README.txt file describing the folder structure and what files are contained within the folders. This file should also contain explanation of the file naming convention.

If you need help getting started with a structure for your projects, methods such as [Jonny Decimal](https://johnnydecimal.com/) can help.

#### An example by [RDMKit](https://rdmkit.elixir-europe.org/data_organisation.html#what-is-the-best-way-to-name-a-file):

```
Expand Down