manage users

[Frank Andreas Sposito]

Hello everyone,

A couple of questions about user management, one localized, the other perhaps more general.

We're experiencing configuration problems on our production server and aren't sure how to resolve them. One critical issue is that we no longer have access to the "Manage Users" function on the dashboard. The box has simply vanished for all users, including dataverseAdmin. Is it possible that our system admin inadvertantly turned off the user management functionality when configuring our server? If so, is there a way to turn it back on?

On a more general note, we are looking for ways to circumscribe user privileges for our root dataverse and for all sub-dataverses. The reason is that it has been decided that AUSSDA will not function as a fully open access repository and will require users to register and authenticate in order to download most of our data sets. Also, users will not be allowed to create sub-dataverses (our staff will do it for them) or change user privileges in sub-dataverses. All data uploads will be "guided", which means that our staff will actually do the uploading for our users. I understand that it is possible to set user privileges for each user and dataverse, but is there a way to restrict access globally such that it cascades to all sub-dataverses, like a kind of inheritance?

Thanks for the help. Best, Frank

Frank Andreas Sposito

The Austrian Social Sciences Data Archive

[Don Sizemore]

Good morning,

Not to ask a silly question, but is your dataverseAdmin (or equivalent) still a superuser? From a test server:

dvntest=> select * from authenticateduser where id='1';
 id |  affiliation  |        email        | firstname | lastname | position | superuser | useridentifier | emailconfirmed |     createdtime     |      lastlogintime      |     lastapiusetime     
----+---------------+---------------------+-----------+----------+----------+-----------+----------------+----------------+---------------------+-------------------------+-------------------------
  1 | Dataverse.org | oduma...@unc.edu | Dataverse | Admin    | Admin    | t         | dataverseAdmin |                | 2000-01-01 00:00:00 | 2018-02-06 07:08:07.071 | 2018-01-25 15:38:06.013

On the second question, it sounds like you want a pool of archivists with privileges, then any new users would be given the Member and/or File Downloader role. I'll let smarter people than me chime in on that one, but note that if your users will be "Institutional" you'll likely be affected by https://github.com/IQSS/dataverse/issues/3407

Donald

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/352709fc-8ba7-48fd-a327-1327829dbfcf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Philip Durbin]

I'm not sure how much this helps but http://guides.dataverse.org/en/4.8.5/installation/config.html#root-dataverse-permissions describes how out of the box nobody except a superuser can create a dataverse or dataset and provides instructions on how to allow non-superusers to create dataverses and datasets. It sounds like you want to remove role assignments from the ":authenticated-users" group. This can be done programmatically via API if you have a lot of these (look for "assignments" at http://guides.dataverse.org/en/4.8.5/api/native-api.html ).

There is no inheritance of permissions from one dataverse to its children. Each dataverse is an island of permissions.

I hope this helps,

Phil

p.s. Weird that the dashboard is gone but I like Don's idea of checking to make sure you have that superuser boolean.

To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsubscribe...@googlegroups.com.

To post to this group, send email to dataverse-community@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/352709fc-8ba7-48fd-a327-1327829dbfcf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CAPfMOawnfGEkHSLjrPuAadCsL2tN2MXSWnjdOq27zVQ9ZKBvxg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[Frank Andreas Sposito]

Donald,

Thanks very much. I've sent this to our system admin, who seems excited about the idea and thinks it's promising. Will report back results when he have them.

To post to this group, send email to dataverse...@googlegroups.com.