[Spike - API] Ensure all dates are UTC
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview of the Feature Request
This spike was triggered by a discussion of how to present dates in the SPA. We would like all dates being returned from the API to be UTC. The UI can convert those dates to the user's local timezone. Part of what is to be researched is how the dates are stored in Postgres, because that will affect the logic of APIs that handle dates. The current assumption is that all dates are stored as UTC, but we want to confirm that.
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
API User
What inspired the request?
Logic for displaying dates in the SPA
What existing behavior do you want changed?
Want to ensure all dates are returned as UTC
Any brand new behavior do you want to add to Dataverse?
Any open or closed issues related to this feature request?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by auditing the API responses that return dates and confirming how those values are stored in PostgreSQL. Document which date fields are already UTC, identify exceptions, and define the API-wide behavior needed for the SPA to convert dates locally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, postgresql
- Domain
- api, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100