Elements: Temporal Extent, Update Frequency, Release Date

[torrin47]

From @torrin47 on September 10, 2018 23:36

All of these elements are optional and should validate as ISO 8601 Dates or ranges. Maybe they could be grouped?

_Copied from original issue: USEPA/EPA_Environmental_DatasetGateway#74

[torrin47]

From @jzichichi on September 20, 2018 18:17

@torrin47 - @aergul and I were wondering which element "Release Date" maps to in the POD schema?

[torrin47]

Not sure how to explain why the element name is so different from the Label - the element name is "issued":

https://project-open-data.cio.gov/v1.1/schema/#issued

[torrin47]

From @aergul on September 20, 2018 18:37

Does "issued" or equivalent appear in EPA schema?

[torrin47]

Ahh, yes, so the technical specification was intended to be limited to those elements that were:

1. Mandatory in POD or
2. Mandatory in ISO or
3. Where EPA had some additional guidance or requirement above and beyond the base guidance for those schemas.

issued is one of those elements that are optional and we had nothing to add to the POD guidance. There are only a few others that fall into this category, but we do need to include them in this tool - I'm pretty sure I captured them all in GitHub issues. And that means we also need to include them in our guidance JSON - using the guidance from the Project Open Data site.

[torrin47]

From @aergul on September 22, 2018 16:46

I'm putting this out there without a separate field for update frequency for now. It doesn't make sense to have two separate widgets to enter the periodicity of the data set. I'm inclined to have "Last Update" be a date entry only and "Update Frequency" to be the vehicle for entering periodicity (as @torrin47 suggested in #67 ) and handle json element generation behind the scenes but it has implications for validation and guidance that we might want to talk about before doing so.

[torrin47]

From @jzichichi on September 23, 2018 3:3

@aergul - perhaps we can discuss this Monday at our check-in. I agree it seems confusing to have the user enter periodicity twice.

[torrin47]

Going to let user optionally leave last update blank and use periodicity to set repeating interval. if both are blank, both are invalid.

[torrin47]

From @aergul on September 26, 2018 3:17

Changes implemented

[torrin47]

From @jzichichi on September 26, 2018 12:19

@aergul - appears to work as described above. Moving to EPA column for @torrin47 to review

[torrin47]

👍

[torrin47]

Sounds like we need to make sure that Update Frequency is very clearly optional, potentially by hiding it unless a user chooses to make it visible or ensuring that if the element is blank, the icon shows as a grey question mark, rather than the red X.

[jzichichi]

@torrin47 Update Frequency has been updated so that it doesn't show a red X upon load; is this sufficient or do you want to consider something that goes further with respect to visibility....

[torrin47]

👍