The new resource-listing UI provides a way to surface last modified dates, as seen on the /staging page.
The /groups page now uses the resource-listing UI. This will soon also be the case for /groups/<groupName> pages. This work required modifications to the UI so that it would work in the absence of last-modified dates, because the charon/getAvailable API returns a list of resources (narratives & datasets) which don't include any information about the date the file was uploaded/modified.
Were the last-modified information available it would improve the UI on these pages by allowing for chronological sorting and identifying which resources had been recently updated.
Details
For individual groups pages and the summary /groups page the server obtains the data via a list objects call to S3 which returns data including the LastModified timestamp¹.
¹ This isn't the same as when the dataset was updated (as recorded in the dataset JSON's meta.updated field) however last-modified timestamps is also what the /staging and /pathogens pages use.
² An additional property shouldn't affect consumers of the API but this is something to keep in mind (primarily Auspice, but perhaps others - the CLI?).
Context
The new resource-listing UI provides a way to surface last modified dates, as seen on the /staging page.
The /groups page now uses the resource-listing UI. This will soon also be the case for
/groups/<groupName>pages. This work required modifications to the UI so that it would work in the absence of last-modified dates, because thecharon/getAvailableAPI returns a list of resources (narratives & datasets) which don't include any information about the date the file was uploaded/modified.Were the last-modified information available it would improve the UI on these pages by allowing for chronological sorting and identifying which resources had been recently updated.
Details
For individual groups pages and the summary /groups page the server obtains the data via a list objects call to S3 which returns data including the
LastModifiedtimestamp¹.Our API ultimately returns data which looks like:
We could extend this response to include an additional property² (e.g.
lastModified: YYYY-MM-DD).This data would then be easily parsed by the callback supplied to the list-resources UI and thus shown in the UI.
¹ This isn't the same as when the dataset was updated (as recorded in the dataset JSON's
meta.updatedfield) however last-modified timestamps is also what the /staging and /pathogens pages use.² An additional property shouldn't affect consumers of the API but this is something to keep in mind (primarily Auspice, but perhaps others - the CLI?).