Standardising timespamps

[Remi-Gau]

in the vast majority of cases, if you have not touched anything, you will overwrite files, except:

• the job files (as a .mat and .json) has a time stamp: YYYYMMDD_HHMM

╰─(env) ⠠⠵ ls demos/MoAE/outputs/derivatives/cpp_spm-preproc/jobs/auditory/sub-01
20220110_1558_jobs_matlabbatch_SPM12_spatial_preprocessing-individual-IXI549Space.json
20220110_1558_jobs_matlabbatch_SPM12_spatial_preprocessing-individual-IXI549Space.mat
20220110_1616_jobs_matlabbatch_SPM12_spatial_preprocessing-individual-IXI549Space.json
20220110_1616_jobs_matlabbatch_SPM12_spatial_preprocessing-individual-IXI549Space.mat

• if you have used saveOptions at some point (most of the default getOptions templates include this as a last function call), then the options you have used to run this are saved with a time stamp too.

ls demos/MoAE/cfg 
options_date-202201050942.json                options_task-auditory_date-202201101206.json
options_date-202201050943.json                options_task-auditory_date-202201101214.json
options_date-202201050951.json                options_task-auditory_date-202201101222.json
options_date-202201112057.json                options_task-auditory_date-202201101331.json

---

Just realizing that the names and time stamp could used in a more consistent manner in those cases. Will open an issue to fix this.

Originally posted by @Remi-Gau in #470 (comment)

[Remi-Gau]

• filenames that include a timestamp should start with the time stamp to facilitate sorting
• use the BIDS data format for time stamps: YYYY-MM-DDThh:mm:ss
• shorten matlabbatch names:
  • Not OK: 20220110_1616_jobs_matlabbatch_SPM12_spatial_preprocessing-individual-IXI549Space.mat
  • OK: `2022-01-10T16:16_batch_spatial_preprocessing-individual-IXI549Space.mat