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
Ambiguity in UI labels for the last_modified and revision_timestamp fields #3028
Labels
Comments
@augusto-herrmann You are right, what you are proposing makes more sense. Do you want to submit a pull request? It seems like a very small change |
I can work on it |
gleb-rudenko
pushed a commit
to gleb-rudenko/ckan
that referenced
this issue
Feb 22, 2017
Thanks for the PR, @gleb-rudenko ! |
@augusto-herrmann, np 👍 |
@amercader, any progress with this one? |
wardi
added a commit
that referenced
this issue
Mar 28, 2017
…ified-and-revision_timestamp-fields #3028 / UI labels for the last_modified and revision_timestamp fields
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The meaning and presentation of the fields should be more clear and consistent.
last_modified: the date and time when the actual data has been last changed
revision_timestamp: the date and time when the resource metadata has been last changed
If this is the correct meaning for the fields, the visual label on the templates for the resource should be consistent with that:
last_modified -> "Data last updated"
revision_timestamp -> "Metadata last updated"
Currently these fields are used interchangeably to display the same label "Last updated". See
<td>{{ h.render_datetime(res.last_modified) or h.render_datetime(res.revision_timestamp) or h.render_datetime(res.created) or _('unknown') }}</td>
https://github.com/ckan/ckan/blob/master/ckan/templates/package/resource_read.html#L158
This problem was mentioned in passing on #1874 but was not fixed there as it was not the main topic of discussion.
The text was updated successfully, but these errors were encountered: