deploy: 0496dcc

_sources/specification.md.txt

@@ -57,7 +57,9 @@ Below we describe each level of the `rawdata` folder hierarchy in more detail. T
 * Session-level folders *must* be prefixed with a key-value pair that is unique for each session. The key *must* be `ses` and the value *must* be numerical, e.g. `ses-01`.
 * Sessions *should* be assigned ascending numerical labels as they are added to the project. The labels *should* be prefixed with an arbitrary number of 0s for consistent indentation and sorting, e.g. `ses-01`, `ses-02`, `ses-03`.
 * Additional key-value pairs with alphanumerical labels *may* be appended after the `ses` key-value pair. For example, dates can be added as follows: `ses-001_date-20230310`. The keys *should* be consistent across subjects.
-* If a date field is added, it *should* be in the format `YYYYMMDD`.
+* If a `date` field is added, it *should* be in the format `YYYYMMDD`.
+* If a `time` field is added, it *should* be in the format `HHMMSS`
+* If a `datetime` field is added, it *should* be in [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) format `YYYYMMDDTHHMMSS` e.g. `20231225T133015`.
 * Different sessions *may* contain different combinations of datatypes.
 
 :::{hint}

specification.html

@@ -404,7 +404,9 @@ <h3>Session<a class="headerlink" href="#session" title="Link to this heading">#<
 <li><p>Session-level folders <em>must</em> be prefixed with a key-value pair that is unique for each session. The key <em>must</em> be <code class="docutils literal notranslate"><span class="pre">ses</span></code> and the value <em>must</em> be numerical, e.g. <code class="docutils literal notranslate"><span class="pre">ses-01</span></code>.</p></li>
 <li><p>Sessions <em>should</em> be assigned ascending numerical labels as they are added to the project. The labels <em>should</em> be prefixed with an arbitrary number of 0s for consistent indentation and sorting, e.g. <code class="docutils literal notranslate"><span class="pre">ses-01</span></code>, <code class="docutils literal notranslate"><span class="pre">ses-02</span></code>, <code class="docutils literal notranslate"><span class="pre">ses-03</span></code>.</p></li>
 <li><p>Additional key-value pairs with alphanumerical labels <em>may</em> be appended after the <code class="docutils literal notranslate"><span class="pre">ses</span></code> key-value pair. For example, dates can be added as follows: <code class="docutils literal notranslate"><span class="pre">ses-001_date-20230310</span></code>. The keys <em>should</em> be consistent across subjects.</p></li>
-<li><p>If a date field is added, it <em>should</em> be in the format <code class="docutils literal notranslate"><span class="pre">YYYYMMDD</span></code>.</p></li>
+<li><p>If a <code class="docutils literal notranslate"><span class="pre">date</span></code> field is added, it <em>should</em> be in the format <code class="docutils literal notranslate"><span class="pre">YYYYMMDD</span></code>.</p></li>
+<li><p>If a <code class="docutils literal notranslate"><span class="pre">time</span></code> field is added, it <em>should</em> be in the format <code class="docutils literal notranslate"><span class="pre">HHMMSS</span></code></p></li>
+<li><p>If a <code class="docutils literal notranslate"><span class="pre">datetime</span></code> field is added, it <em>should</em> be in <a class="reference external" href="https://en.wikipedia.org/wiki/ISO_8601">ISO8601</a> format <code class="docutils literal notranslate"><span class="pre">YYYYMMDDTHHMMSS</span></code> e.g. <code class="docutils literal notranslate"><span class="pre">20231225T133015</span></code>.</p></li>
 <li><p>Different sessions <em>may</em> contain different combinations of datatypes.</p></li>
 </ul>
 <div class="admonition hint">