timezone information

[LucieContamin]

Per suggestions from Koji, should we add a "timezone" information field in the admin.json schema? As different Hubs are on different timezome, it might be interesting to store that information especially if, for example, the submission date start/end date of the Hub need to be precise.

[nickreich]

Agree that this should be in admin.json

[annakrystalli]

Need a valid timezone array.

[annakrystalli]

Have now added a timezone property.

Couple of questions:

• How should we handle daylight savings? Although I've gone for UTC, I'm now questioning it as it's very difficult to account for daylight savings as not all countries observe them and those who do do not change on the same day, which itself varies form year to year! I feel the safest is to actually use TZ database names (e.g. Europe/London), which are location based. R can use these to convert dates to other timezones, accounting for daylight savings. It does mean a really long list of potential valid values in the schema though. Have a look at use tz database names & enum list of timezones. #4 #24 for a possible implementation of this proposal.
• Are we making timezone required? I'm opting for yes for now.