Skip to content

fix: bad formatting for acquisition start datetime #138

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
dbirman merged 1 commit into from
May 20, 2026
Merged

fix: bad formatting for acquisition start datetime #138

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion docs/source/policies_practices/data_organization.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ All primary data assets have the following naming convention:

A few points:

- Format `<acquisition-start-datetime>: yyyymmdd_HH-MM-SS`
- Format `<acquisition-start-datetime>: YYYY-MM-DD_hh-mm-ss`
- This should be the start of acquisition, in the local time zone.
- The local time-zone is documented in metadata files
- All tokens (e.g. `<subject-id>`) must not contain underscores or illegal filename characters. Subject ID is not strictly necessary – only the timestamp is essential. However, it is part of the current naming convention because it helps people visually browse for data.
Expand Down
Loading