Skip to content
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

Depositor cannot view embargoed dataset #2708

Open
simholt opened this issue Feb 7, 2025 · 2 comments
Open

Depositor cannot view embargoed dataset #2708

simholt opened this issue Feb 7, 2025 · 2 comments
Labels
Bug Priority: Critical This is for issues that are blocking significant work or are preventing the system from functioning

Comments

@simholt
Copy link
Contributor

simholt commented Feb 7, 2025

So something similar happened in 2019 and I wonder if the dataset worktype got missed? Or is just a bug.

hx11xq645 has been approved. It is under a private embargo and the depositor cannot view it. The item shows up on their Profile but clicking through gives a "The item you are trying to access is under embargo until March 6, 2027" message.

Related Issue: #1878

@simholt simholt added Bug Priority: Critical This is for issues that are blocking significant work or are preventing the system from functioning labels Feb 7, 2025
@CGillen
Copy link
Contributor

CGillen commented Feb 10, 2025

Has anyone w/ an embargo that starts as private had this issue w/ non-datasets? From what I can test w/o logging in as one of these depositors, it seems like embargos that start as OSU are visible to the depositor, but those that start as private are not, regardless of work type

@simholt
Copy link
Contributor Author

simholt commented Feb 11, 2025

private visibility should always be visible by the depositor, which I thought got fixed in #1878 ?
Okay, Christa helped test -- she was able to view her own private dataset submission! QA pass--

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Priority: Critical This is for issues that are blocking significant work or are preventing the system from functioning
Projects
None yet
Development

No branches or pull requests

2 participants