In summary, it mentions the "official" way to write units for dates with the extra that time is optional in this case.

I did not remember we had kept that piece of metadata for PET and thought we had fallen back on using scans.tsv to keep track of that. Doesn't that open the door for this piece of metadata to be stored in 2 different places and also have potentially conflicted info if that piece of information is stored in both places? (Sorry to have missed that one before the final merge and sorry to not remember how this discussion was resolved... Feel free to ignore).

Yeah - that's the alternative. I guess it would be most clean to have everything in the scans.tsv/json file.

+1 for deprecating ScanDate and recommending using acq_time in scans.tsv.

Putting in scans.tsv is a better alternative -- it allows tool builders to consistently look for the time irrespective of modality

Thank you all - I believe we seem to have a consensus. I will go ahead and make the necessary changes to the specification and the validator, and then make a PR.

We need to keep the field around for backwards compatibility and mark it deprecated. I made a proposal in edf0237.

I made a proposal in edf0237.

@effigies it's a bit unclear to me where that commit is. Is it on your fork? Maybe you could make a PR to Martin's branch (or push directly since he's agreed with your suggestion)

Thanks @mnoergaard for starting this and everybody else for reviewing.