Dealing with various date formats

[anderspeders]

The current database holds disclosures marked by YYYY only but not on specific time series: DD-MM-YYYY.

How should we accomodate data collection on various formats?

Should we aim to collect start date and end date for each disclosure or would YYYY (based on start date or end date) be sufficient?

[mattfullerton]

From a quick look through the code it looks like hold full dates for everything except production and payments. It could well be that we only display dates in some cases because the month/day info is perceived to be inaccurate. For example this fact is true on 1st January at 1am:
http://resourceprojects.org/project/pe-las%20-5k6jsk - actually a place where we shouldn't be showing the month/day/time.

The extremely correct solution would be to mark all dates with an accuracy flag as far down as day (hour/minute seems overkill) and then display them accordingly.

For disclosures specifically, we are showing full dates:
http://resourceprojects.org/sources
http://resourceprojects.org/source/585bb9e68bb3aa000f212101

And then there are probably silly things like setting the source date of a report to be that of when we download it:
https://github.com/NRGI/ResourceProjects.org/blob/master/server/dataprocessing/companieshouse.js#L743 😊

In terms of dealing with various time formats, the import tries hard:
https://github.com/NRGI/ResourceProjects.org/blob/master/server/dataprocessing/googlesheets.js#L105