Add private accession links from Submitter profile page

[only1chunts]

User Story

As a submitting author I want to be able to see the private/partially complete version of my dataset So that I can see how it is looking and check any details

Acceptance criteria

Given I have a dataset submission in progress (but not yet published) i.e. the dataset has any status from "user provided data" through to "private" (inclusive) see miro board for statuses. When I go to the "your datasets" section in my personal profile page and I have any datasets in my list of datasets that have a suitable status Then I see a link to the not yet published dataset(s) mockup page(s)
NB - This is the same page that curators call the mock-up page

Additional Information

Currently we have to email the private URL link to the user to check the dataset before publication, we should include the button on their personal page. To do this we need to get the submission wizard to allow spreadsheet upload before this can be done (Issue # ), and make sure the scripts we use to do direct uploads of the spreadsheet information to the database also create user accounts and email the submitter to ask them to complete their account activation (Issue # ).

Suitable status: from "User provided data" to "Private"

This is dependent on this ticket to be done:

• [ ] #1616

[only1chunts]

The users profile page in the "Your Datasets" tab is where the link to the private dataset page should be (see screenshot attached).

The Icon to put in that link should be something like the one here, but an Opensource / public domain version.

The link should open a pop-up window with NO URL bar, this is important because the users should not be able to just copy and paste the URL link to this private mockup page.

Ideally we should plaster all mockup pages with a watermark saying PROOF or PRE-PUBLICATION or something like that.

[lump1k]

Can you send me please example of this private accession link?

[only1chunts]

sent link via email

[rija]

• If we are to add new button icon, we need to redo all of them as we don't have original blueprints and we need to keep visual consistency
• We need check whether this is done already as part of the WL work

In any case, it seems like there are several use case around mockup pages that share the same foundation but vary slightly from use case to use case. Might an opportunity to refactor mockup page to make it easy to satisfy these present and future slight variations on the idea.

[only1chunts]

the white label code may well include a set of new icons already as I think they had the same problem, so it might be worth checking whats in there.