Updates to UC 9

[marisalim]

Add things to edit in the use case (e.g., description, tasks, reqs) - https://use-cases.nih-cfde.org/uc-0009/

reviews

• https://hackmd.io/k6GupdmjQy-stCxn8ttuzw?edit
• https://hackmd.io/ylGbQtQgSVGfTo3kSF0rqA?view

[marisalim]

draft workflow:

1. Check email for invite to join NIH CFDE Submitters, click on “Click here to apply for membership” in the email
2. Sign into Globus with email used for onboarding to CFDE
3. On “Join Group” page, click “Link It Now”
4. On “Link an identity” page, click “Continue”
5. Check email for verification code and enter on Globus page to authenticate email, click “Submit”
6. On “Log into your primary identity” page, click “Continue”. Fill out info (name, org) and click “Accept Invitation”.
7. Check email for confirmation email (i.e., “Application Approved - Welcome to NIH CFDE GTEx Submitters”)
8. Go to https://app.nih-cfde.org/ and log in. Click your name, click "My Profile". Check that under "Groups" it says you're a Submitter for your DCC
9. Click on “Data Review” tab to open “Submitted Datapackage” page
10. Click on "Summary Charts" to look at dynamic plots of submitted data
11. Click "User Guide" tab for documentation about using the portal
12. ...

[marisalim]

to address from reviews

uc description

• [x] we should define what “Review Catalog” is - is it the entire submitted datapackage?
• [x] uc refers to a walk-through tutorial - that is basically the wiki right now, how to reference it? ...don't think we want to put links in the uc descriptions..
• [ ] add a bit more about what persona is supposed to be doing to check portal submission (click what, check what). this use case felt the same as UC8 (DCC validates data). The tasks/reqs are different, but the pages I was looking at were almost the same - UC8 was just more specific about what I should check to validate the data. how to differentiate?

task

• [x] some tasks may be future functions of the portal, but not currently obvious how to test - we can leave them in the UC but let's add the in progress emoji next to tasks that are not testable yet
  • t-0026: Compare different available team Review Catalogs: did not use this because there’s only 1 LINCS submission right now, but also didn’t find functionality/guide for how to compare - is it manual?
  • t-0028: Notify team data administrator there are Review Catalogs to review: is there a way to ping team members via the portal or would this be via email, etc.?
• [x] reorder tasks

req

• [x] r-00041: The cfde ingest tool shows errors/warnings/summaries: this requirement makes more sense for the data submission use case, rather than data review. --> this is hard to test, but after some more clicking have seen more errors and warning pop ups on the portal.
• [x] just a note: this use case has a placeholder for requirements TBD (r-99999: requirement to be determined)