Dataverse 4.20 global and local roles

[Dario Basset]

We have dataverse 4.20.

We are trying to configure global custom roles, but we read that 4.20 version does not have a delete global role functionality. Is it possible to issue a delete global role command in 4.20?

It seems that in our installation the (dataverse collection) delete role is not working. In fact, if we issue:

            curl -H X-Dataverse-key:xxxxxxxx -X DELETE https://dataverse.unimi.it/api/roles/9

we get:

{"status":"ERROR","message":"Command edu.h.....impl.DeleteRoleCommand@279b9e35 failed: null"}

which is not understandable by us.

What can we do to delete that (dataverse collection) custom role?

Thx a lot in advance.

[Philip Durbin]

Hi Dario,

Sorry for the slow reply. It looks like you found the other thread at https://groups.google.com/g/dataverse-community/c/2M9A7uo4KpM/m/zVcoQKt3AAAJ

It sounds like deleting roles may be buggy. Can you please open an issue about this?

Generally speaking, I don't think installations should be creating their own roles. The flexibility is nice but I think of it more as a feature core developers can build on rather than something to play with, especially in production. :)

If you have a need regarding permissions and roles, I'd suggest opening an issue. Here's an example of one that resulted in a permission being split into two (in Dataverse 5.9) to better serve a need: https://github.com/IQSS/dataverse/issues/8109

Thanks,

Phil

--
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-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/803126bd-7cf1-4228-b38e-bebba3aeec4en%40googlegroups.com.

--

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

[Dario Basset]

Thank you Phil.

Ok, I'll open the bug.

To be more specific on what we want to implement, we would like to have a workflow where all data and metadata is managed by our researchers, while publishing is managed by dedicated people. We would like to have roles where anything (including granting permissions) on the sub-tree is permitted but publishing. We want curators to publish.

We saw that the contributor role is close to what we want to get, but it cannot completely manage its dataverse collection sub-tree.

Thank you to give us hints about the workflow, if it is feasible.

[Philip Durbin]

Thanks, Dario.

What you're saying makes sense. If you could create a separate issue about "everything but publishing", I'd appreciate it.

Thanks,

Phil

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/e7f88520-a65a-4e74-b0bd-f7942b7c736en%40googlegroups.com.

[Dario Basset]

Here we are: 

https://github.com/IQSS/dataverse/issues/9358

You received this message because you are subscribed to a topic in the Google Groups "Dataverse Users Community" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dataverse-community/5bZqCRFP8BU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CABbxx8FwqvTYzoFkLo_7euiepaR2BAoQ60JTHvagB0J2w4TAVA%40mail.gmail.com.