TreeBASE Submission Mockups

From Dryad wiki
Jump to: navigation, search

External Identifiers

1. File External Repository Identifier Submission #1 (2010-07-20)

Option to link/add external ID to remote repository; drop-down of repositories; added IDs are removable; Label says "optional" -- all the others below probably should include that as well.

File-external-id-1.png

Comments:

  • users might not understand whether the file upload and ID are EITHER/OR, or if when they upload a file and enter an ID, Dryad assumes the external ID corresponds to the datafile. --Tjvision 21:36, 20 July 2010 (EDT)


2. File External Repository Identifier Submission #2 (2010-07-20)

Some say drop-downs are bad because user can't see the options without taking additional steps, so here is a select box alternative.

File-external-id-2.png

Comments:

  • here

3. File External Repository Identifier Submission #3 (2010-07-20)

Another option would be radio buttons.

File-external-id-3.png

Comments:

  • whichever one of these interfaces is ultimately used, there should be an Other option that requires them to fill in a text box with the name (and/or URL?) of that repository. --Tjvision 21:36, 20 July 2010 (EDT)
  • In this case, would we try to parse what they input to see if it's a repository we can export to or just record the number and repository in the record (perhaps for later integration)?--Kc140 21:55, 20 July 2010 (EDT)


4. File External Repository Identifier Submission #4 (2010-07-20)

Here is an example of a file that already has one ID associated with it, but it might have more than one external place in which it can be found; add button to right rather than below here too.

File-external-id-4.png

Comments:

  • it's confusing at to whether multiple selections refer to the same data at two different repositories, or there are two different datasets at the same or different repositories. --Tjvision 21:36, 20 July 2010 (EDT)


5. File External Repository Identifier Submission #5 (2010-07-20)

Same as above (add button to right) but this time with the drop-down of repositories option.

File-external-id-5.png

Comments:

  • here

Submission to External Repository

Requirements Clarification

Note it is technically difficult to edit items on the summary page -- @mire suggested moving this choice to the data file page.

Todd said (below): "keep the whole partner repository submission interface away from users who don't need it".

Hilmar suggested that all of the selection be done in one place, so users only have to think about it once. Ryan agrees that this is simplest in terms of not bothering the user more than necessary.

The full package needs to be processed by the handshaking code, because some repositories (TreeBASE) will want to treat all files they receive as a single package, while others (GenBank) will want each file submitted individually.

Mockups

6. BagIt-Stage External Repo Submission #1 (2010-07-20)

Option, at end of data file submission process, to upload selected files to external repositories. This option uses drop-downs for the repositories and the existing data file list.

Bagit-stage-1.png

Comments:

  • here


7. BagIt-Stage External Repo Submission #2 (2010-07-20)

On the other hand, it might be better to give the upload process its own cognitive space so that users recognize it as a separate (and optional) process; this is still using inline drop-downs and click-through CC0 acceptance.

Bagit-stage-2.png

Comments:

  • I slightly prefer this one to #8, but not sure I can defend my preference.--Tjvision 21:36, 20 July 2010 (EDT)
  • Is there a need for the CCZero checkbox here -- haven't they have already agreed to those terms for each file?--Tjvision 21:36, 20 July 2010 (EDT)
  • I thought we had discussed at one of the earlier All-Hands meetings that we wanted a second explicit confirmation that they were licensing it under this license since it was going offsite.--Kc140 21:55, 20 July 2010 (EDT)

8. BagIt-Stage External Repo Submission #3.1 (2010-07-20)

Alternatively, we could give the upload process its own page. Possible advantages may be fewer clicks for large numbers of data files (because we could use something other than drop-downs) and maximize CC0 acceptance and a cleaner cognitive space (its own) for the process.

Bagit-stage-3.png

Comments:

  • I'm wary of adding to the number of pages, but it would be nice to keep the whole partner repository submission interface away from users who don't need it. That could be done in part by keeping all the partner repository elements within the same page, but having the full options only show up when authors select them.--Tjvision 21:36, 20 July 2010 (EDT)
  • Yes, this could be set up to pop open within the page when the button is pushed, instead of opening a new page; maybe something other than a button could also be used (a link?)--Kc140 21:55, 20 July 2010 (EDT)


9. BagIt-Stage External Repo Submission #3.1-1 (2010-07-20)

Option #1 for having the upload part on its own page; using select boxes and a single check for upload and CC0 acceptance.

Bagit-stage-3-1.png

Comments:

  • here


10. BagIt-Stage External Repo Submission #3.1-2 (2010-07-20)

Optino #2 for having the upload part on its own page; using select boxes and a single CC0 acceptance paired with individual file consent.

Bagit-stage-3-2.png

Comments:

  • this requires two clicks where one would suffice, so prefer #11 --Tjvision 21:36, 20 July 2010 (EDT)

[[Category:]]