Cleaned up branding/customization info in Configuration > Installation Guide #4556
Conversation
…tallation Guide. [ref #4555]
There was a problem hiding this comment.
The pull request is fine but at some point we should consider the user experience of someone who is setting up Dataverse for the first time. There's a lot of optional configuration that should be presented in a more clear manner to get an installation off on the right foot. I left a comment about this.
|
|
||
| Customizing the Root Dataverse | ||
| ++++++++++++++++++++++++++++++ | ||
| In order for non-superusers to start creating dataverses or datasets, you need click "Edit" then "Permissions" and make choices about which users can add dataverses or datasets within the root dataverse. (There is an API endpoint for this operation as well.) Again, the user who creates a dataverse will be granted the "Admin" role on that dataverse. Non-superusers who are not "Admin" on the root dataverse will not be able to to do anything useful until the root dataverse has been published. |
There was a problem hiding this comment.
I'm fine with how the title of this section is not called "Root Dataverse Permissions" but I'm afraid that it reads as a merciless wall of text, starting out with lots of detail on the plumbing rather than stating clearly why the reader should care about any of this. This section is probably the place where we should help the person installing Dataverse avoid several pitfalls. Here are the pain points an solutions:
- I just installed Dataverse and none of my users can do anything.
- Publish the root dataverse and configure permissions in order for non-superusers to create dataverses or datasets. See Users created with no roles, cannot use UI #4515 for an example of this confusion.
- I've been using Dataverse for a little while and I'm not happy with how things are organized.
- API endpoints to move datasets and dataverses around are being developed. Meanwhile, before you allow lots of dataverses and datasets to be created, you should about what sort of organizational hierarchy of dataverses you want under the root dataverse and adjust the permissions to achieve that goal.
- It's not obvious to me that metadata fields need to be configured.
- Give your local metadata experts the "Admin" role on various dataverses and have them configure metadata fields. Consider using templates. Notice that you can benefit from facets if you configure them.
There are probably more pain points but these are the ones that come immediately to mind.
Related Issues
Pull Request Checklist