Create Documentation for Superusers in User Guide

[posixeleni]

@pdurbin indicated that the documentation from Super Users needs to be updated for 4.0 and this ticket is a placeholder for us to update this page:

https://github.com/IQSS/dataverse/edit/4.0.1/doc/sphinx-guides/source/user/super-user.rst

In 3.6 Super Users were able to do many things in the UI so @scolapasta there are some features we need your help figuring out what we can currently support in 4.0 for super users in the UI and what will be coming down the road

• Harvesting
• Bulk Upload
• Web Analytics?

[pdurbin]

I just wanted to note that @mcrosas and I seem to prefer "superuser" (no dash) over "super-user". I assume this extends to "Superuser" over "Super User."

[posixeleni]

@pdurbin please feel free to make these changes in the file

[bencomp]

So this is not necessarily related to the Administration documentation? My role in 3.6 is both information manager ("administrator") and superuser, so to me Superuser Action and Administration are related.

[pdurbin]

As I (mentioned yesterday](http://irclog.iq.harvard.edu/dataverse/2015-05-28#i_20253) products such as RHEL have separate guides for installation and administration:

• Installation Guide
• System Administrator's Guide

As @bencomp mentioned, often in practice the same individual would be reading these guides. These are people who have the ability to make themselves a superuser and make raw edits to the databases as necessary.

45f13cc is where I started a new "Administration" page under the Installation Guide but I'm really not sure how best to organize this. In some ways a separate guide makes sense to me. I'd love to hear thoughts from @eaquigley @posixeleni @sbarbosadataverse and @kcondon on where best to put this information about the care and feeding of a Dataverse installation.

[posixeleni]

@pdurbin @bencomp to clarify this Super User documentation is meant for Administrators of an entire Dataverse repository for post-installation and would be for features a Super User (Aka Super Admin) would be able to do in the Dataverse GUI (which we use to have features for in the 3.6 User Guides).

[pdurbin]

@posixeleni where should we document SQL scripts that people like @bencomp or @kcondon will need to run until a GUI can be built? I mean for things like deleting an API token: http://guides.dataverse.org/en/next/installation/administration.html#deleting-an-api-token

[posixeleni]

@pdurbin If it's post-installation this can't be in the Installation guide, right? Nor in the API Guide? So would have to be in this section of the User guide, I suppose, with a caveat that this needs to be done outside of the GUI for now.