You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Data user
External software creator
PDS software engineer
PDS data archivist
Data provider
πͺ Motivation
so the user persona can know if the registry is up to date with the latest bundle releases and rapidly see the status of filtered bundles.
π Additional Details
This would be a flexible response both in xml/json and plugged into an html web page (eventually on the new PDS website as well). It would list the bundles (with optional filtering), their version, release date, bundle version latest modify date, last date updated in the registry, archive status, content type counts, observation date range (if applies).
Much of this can probably already be pulled from the PDS API. From my perspective, the key is to have a simple web page that lists the entries in horizontal format, so a basic user can quickly view the report without much effort. This is a sanity check type report for a user before they decide to pull responses from the registry and know if they will have access to the entire bundle. Also, users can double check that the full data release cycle has been completed.
βοΈ Acceptance Criteria
Given When I perform Then I expect
βοΈ Engineering Details
The text was updated successfully, but these errors were encountered:
jordanpadams
changed the title
As a data user/external software creator, I want to see the status of all or filtered bundles in the registry
As a Data User, I want to see the archive and tracking status of registered products
Nov 29, 2022
This is a good use case for the web modernization task
jordanpadams
changed the title
As a Data User, I want to see the archive and tracking status of registered products
As a user, I want to see the archive and tracking status of registered products
Dec 21, 2022
π§βπ¬ User Persona(s)
Data user
External software creator
PDS software engineer
PDS data archivist
Data provider
πͺ Motivation
so the user persona can know if the registry is up to date with the latest bundle releases and rapidly see the status of filtered bundles.
π Additional Details
This would be a flexible response both in xml/json and plugged into an html web page (eventually on the new PDS website as well). It would list the bundles (with optional filtering), their version, release date, bundle version latest modify date, last date updated in the registry, archive status, content type counts, observation date range (if applies).
Much of this can probably already be pulled from the PDS API. From my perspective, the key is to have a simple web page that lists the entries in horizontal format, so a basic user can quickly view the report without much effort. This is a sanity check type report for a user before they decide to pull responses from the registry and know if they will have access to the entire bundle. Also, users can double check that the full data release cycle has been completed.
βοΈ Acceptance Criteria
Given
When I perform
Then I expect
βοΈ Engineering Details
The text was updated successfully, but these errors were encountered: