Change date parsing - Githubissues

kamerynB commented 1 month ago

Problem Description: Dates are inconsistently parsed throughout the codebase.

Expected Behavior/Solution: Dates should be parsed in a consistent manner.

Requirements:

[ ] Rather than using the being_of_the_begin value, epoch data points will be parsed
- [ ] _seconds_since_epoch_begin_of_the_begin for dates parsed from the /timespan property
- [ ] _seconds_since_epoch_begin_of_the_begin and _seconds_since_epoch_end_of_the_end for dates in /timespan that have ranges
[ ] Facets will be parsed using the epoch time passed by ML (this will be covered in #39)

Needed for promotion: If an item on the list is not needed, it should be crossed off but not removed.

[ ] Wireframe/Mockup - Mike
[ ] Committee discussions - Sarah
[ ] Feasibility/Team discussion - Sarah
[ ] Backend requirements - TBD
[ ] Frontend requirements- TBD
[ ] Are new regression tests required for QA - Amy
[ ] Questions
List of questions for discussions. Answers should be documented within the issue.

UAT/LUX Examples: TBD

Dependencies/Blocks: N/A

Related Github Issues:

Related links: N/A

Wireframe/Mockup: The frontend should render and behave as it did before.

roamye commented 4 weeks ago

IT Team Meeting 8/16: No performance test is needed for this issue & these updates can go on the 9/3 release when the milestone is available.

clarkepeterf commented 3 weeks ago

@kamerynB the frontend should also pass epoch times (in seconds) in the JSON search syntax with the MarkLogic api

clarkepeterf commented 3 weeks ago

@kamerynB we should also have some requirements about handling dates outside of the supported range of the Javascript Date class

kamerynB commented 3 weeks ago

@clarkepeterf I will add that!

roamye commented 2 weeks ago

From IT Team meeting 8/23 & UAT (8/26) - this needs to have UAT examples before moving to prioritization review.

project-lux / lux-frontend