Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Date parsing for date ranges #208

Open
M-Nicholls opened this issue May 4, 2017 · 5 comments
Open

Date parsing for date ranges #208

M-Nicholls opened this issue May 4, 2017 · 5 comments
Labels

Comments

@M-Nicholls
Copy link
Contributor

M-Nicholls commented May 4, 2017

dd-mm-yyyy/dd-mm-yyyy doesn't parse in the eventDate field
yyyy-mm-dd/yyyy-mm-dd does parse correctly

capability to cater for start and end dates as separate fields on ingest would be useful e.g. startEventDate endEventDate. Values would not be stored but would be converted to a single properly formatted eventDate field for ingest.

@ansell
Copy link
Contributor

ansell commented May 5, 2017

Darwin Core specifies eventDate as being ISO8601. It might be simpler to clean up the dates prior to loading rather than adding non-ISO8601 parsing logic to biocache-store.

@djtfmartin
Copy link
Member

this should just be another format to add to the existing dateparser.

@djtfmartin
Copy link
Member

was there a conclusion to this one @ansell @M-Nicholls ?

@ansell
Copy link
Contributor

ansell commented Apr 25, 2018

I haven't looked into any of the date parsing, including the non-compliant date ranges noted here. One user noted that even parsing valid ISO8601 date ranges is broken though, filed separately as #245

@djtfmartin
Copy link
Member

This is fixed on 2.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants