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

Could not parse date in yyyy-MM-ddZ format #29

Closed
tdddblog opened this issue Sep 22, 2020 · 2 comments · Fixed by #31
Closed

Could not parse date in yyyy-MM-ddZ format #29

tdddblog opened this issue Sep 22, 2020 · 2 comments · Fixed by #31
Assignees
Labels
bug Something isn't working

Comments

@tdddblog
Copy link
Contributor

Some OREX labels (collections) have <start_date_time> in "yyyy-MM-ddZ" format (e.g., 2016-09-08Z) which Harvest could not parse. For example, OREX/OCAMS/data_calibrated/collection_ocams_data_calibrated.xml collection.

It doesn't look like a valid date. A date without time, but with a timezone considered invalid, at least in Java. Timezone usually makes sense if there is both a date and a time.

Need confirmation that "2016-09-08Z" is valid or not in PDS labels.

@tloubrieu-jpl
Copy link
Member

@jordanpadams will send @tdddblog the regex of the supported date format so that Eugene can fix it.

@tdddblog tdddblog linked a pull request Sep 24, 2020 that will close this issue
jordanpadams pushed a commit that referenced this issue Sep 24, 2020
Resolves #29
Resolves #30

* Handle yyyy-MM-ddZ format

* Handle yyyy-MM-ddZ format

* (1) Use a list instead of a set for multivalues fields. (2) Generate a list of fields in /out folder.

Co-authored-by: Eugene <karpenko@RAYL-AI846797.jpl.nasa.gov>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants