Show dataset access expiry on the datasets page #184

New issue

Open

opened 2026-08-30 21:51:13 +00:00 by aaperis · 1 comment

aaperis commented

2026-08-30 21:51:13 +00:00

(Migrated from github.com)

Keeping it in icebox for now because this requires fetching visas.

Please describe the feature

As a user browsing datasets I have access to, I want to see when my access to each dataset expires, so I can plan downloads before the grant lapses.

Detailed description

The access grant carries an expiration date but it isn't surfaced in the UI. Users only find out access has expired when a download fails. This info is carried in the visas which we need to fetch in order to do this.

AC

Parse the expiration date for datasets access grant from token visas
Display it on a new column for each dataset.
Format consistently with other dates on the page.
Optional: Visually flag grants that expire soon.

Keeping it in icebox for now because this requires fetching visas. ## Please describe the feature As a user browsing datasets I have access to, I want to see when my access to each dataset expires, so I can plan downloads before the grant lapses. ## Detailed description The access grant carries an expiration date but it isn't surfaced in the UI. Users only find out access has expired when a download fails. This info is carried in the visas which we need to fetch in order to do this. ## AC - [ ] Parse the expiration date for datasets access grant from token visas - [ ] Display it on a new column for each dataset. - [ ] Format consistently with other dates on the page. - [ ] Optional: Visually flag grants that expire soon.

aaperis commented

2026-09-04 09:55:58 +00:00

(Migrated from github.com)

EDIT: Since at the moment we do not store or parse the c4gh passport it seems like doing so for this small UX improvement is an overikill.
After internal discusison, this seems like it should be implemented on the sda-download service side so that we can fetch it along with the rest of the metadata.

Moved to icebox until we discuss this GS team.

EDIT: Since at the moment we do not store or parse the c4gh passport it seems like doing so for this small UX improvement is an overikill. After internal discusison, this seems like it should be implemented on the sda-download service side so that we can fetch it along with the rest of the metadata. Moved to icebox until we discuss this GS team.