Add "Add Data" to navbar, plus Host Dataverse input to create dataverse/dataset forms

[TaniaSchlatter]

One way to have people create more dataverses is to make it easier to see how to do it. People who get to dataverse from google and bypass the home page or search results page don't see a clear way to add data.

One solution: adding a button to the header on every page will help make it clear how to add to Harvard Dataverse.

Adding a button. The button has a dropdown to select a new dataverse or new dataset, as current Add Data functionality from the buttons on the home page:

If users are not logged in, the Log in/Sign in popup with a link to sign up (issue #6170) is shown.
Proposed flow:

Removing the "Add Data" button from the search results page, and showing it on the header for not logged in users:

[TaniaSchlatter]

Adding the ability to add data from the header means that users need to be able to select the dataverse and/or dataset that they want to deposit data to or create a dataverse in. We would want to show users the dataverses they have permission to add to. This needs to be thought through for admins so that we do not show all options.

[mheppler]

[SORRY: Mistakenly left this comment on the wrong issue on 3/8.]

Adding this feature should including resolving this issue, Moving Dataverses + Datasets: Provide way in the UI for a user to do this #2073.

The navbar contains links for actions at the root/installation level. When you sign up for an account, the account is created at the highest level. When you use the search input, you are searching all contents of the root/installation. Following that logic, clicking "Add Data" would deposit the dataset/dataverse into the root dataverse, which goes against the preferred workflow, of depositing datasets into your own dataverse.

[ALSO: Adding comments from other related issues that were closed as those issues were consolidated into this issue.]

@ajirnyi commented on Jan 14, 2016 in issue #2874

When the base URL is long enough (e.g. 49 symbols in our test case), the Identifier entry field is too short except for very wide browser windows, and it is not possible to see the text entered there (see example below). The issue is most noticeable in Firefox (box is too small up to screen width of 1183 pixels, after which it instantly expands), but is present in all browsers.

...

@kaitlinnewson commented on Oct 17, 2017 in issue #4212

Hi Harvard team!

We received a report from one of our users about display issues on the 'Create a new dataverse' page. I've tested this in both the Scholars Portal instance and the Harvard instance, have tested in Chrome (v 61.0.3163.100) and Firefox (v 56.0), and am using OSX 10.11.6.

The issue seems to happen at a screen width of 990px or less, and causes text overlap and the inability to see text entered into the identifier field. I've attached a couple of screenshots for reference.

Let me know if you need any more information!

[djbrooke]

@TaniaSchlatter I moved this over to the design column on the board. Feel free to move back to inbox if this is not the correct status.

[TaniaSchlatter]

Related issue #5493 (closed), #5874: Push researchers towards Dataverse Creation and Dataset Linking from Journal Acceptance Notifications

[TaniaSchlatter]

Docs that break down:

• Current flow for adding data and linking

• Additional ideas for adding data and linking

[pdurbin]

Related: As the creator of a dataverse I'd like to know how to make an "Add Data" button appear for non-logged in users to encourage user interaction #5718

[djbrooke]

• Consider a configuration option for whether or not it displays on the custom homepage
• We could consider a different experience (drop down vs type ahead) depending on the number of dataverses available for selection (consider 5 as a start)
• Noted some performance concerns about the dataverses list, but we've done work in this area so it may now be more performant (caching? does changing host update dataverse metadata fields? does changing host update dataset template dropdown?)
• The goal is more participation and more users uploading data, so we don't want it under the name drop down, we should consider internationalization issues re: width
• We could use Google Analytics or look at the number of records in the DB
• Evaluate responsiveness of Dataverse create form (Dataverse creation: Indentifier field width too small #2874, Responsiveness: 'Create Dataverse' page is not responsive and breaks on smaller screen sizes #4212)