--
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/f81f49b4-a431-487a-bea0-00a702772e90%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
PhilHi Erin,My mental model for permissions in Dataverse is that each dataverse is an "island of permissions." By this I mean that there is no inheritance of permissions. The permissions don't leak out from the root dataverse to sub-dataverses. At the Harvard Dataverse, we let people publish datasets (and dataverses they create) in the root dataverse.I'm curious about where the documentation is falling down for you. I know it needs a lot of work! https://github.com/IQSS/dataverse/issues/2653 is related but if you want to create a fresh GitHub issue in your own words, that would probably be better.I hope this helps!
On Tue, Jun 27, 2017 at 1:55 PM, Erin MacPherson <Erin.Ma...@dal.ca> wrote:
Hi everyone,I'm looking for some feedback on how others manage their workflows within the root database.The default role for anyone assigned is contributer. However, we want it to be a self-curated tool, so I would like researchers to be able to publish their own data. However, if I gave them a curator role, does this mean that they would be able to publish any other dataset within the root dataverse? We will be setting up multiple dataverses for the different groups, but I was thinking if someone just wanted to add data for one project, they could just add it to the main dataverse and publish it, but I only want them to be able to publish their own. I've read a lot of the documentation surrounding this but I'm wondering how do others handle this?Many thanks,Erin
--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/f81f49b4-a431-487a-bea0-00a702772e90%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Phil,I think it's just me :) I'm wondering if someone just wants to put a dataset in the root dataverse and publish it.
Erin
On Tuesday, June 27, 2017 at 3:13:27 PM UTC-3, Philip Durbin wrote:
PhilHi Erin,My mental model for permissions in Dataverse is that each dataverse is an "island of permissions." By this I mean that there is no inheritance of permissions. The permissions don't leak out from the root dataverse to sub-dataverses. At the Harvard Dataverse, we let people publish datasets (and dataverses they create) in the root dataverse.I'm curious about where the documentation is falling down for you. I know it needs a lot of work! https://github.com/IQSS/dataverse/issues/2653 is related but if you want to create a fresh GitHub issue in your own words, that would probably be better.I hope this helps!
On Tue, Jun 27, 2017 at 1:55 PM, Erin MacPherson <Erin.Ma...@dal.ca> wrote:
Hi everyone,I'm looking for some feedback on how others manage their workflows within the root database.The default role for anyone assigned is contributer. However, we want it to be a self-curated tool, so I would like researchers to be able to publish their own data. However, if I gave them a curator role, does this mean that they would be able to publish any other dataset within the root dataverse? We will be setting up multiple dataverses for the different groups, but I was thinking if someone just wanted to add data for one project, they could just add it to the main dataverse and publish it, but I only want them to be able to publish their own. I've read a lot of the documentation surrounding this but I'm wondering how do others handle this?Many thanks,Erin
--
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+unsubscribe...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/f81f49b4-a431-487a-bea0-00a702772e90%40googlegroups.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
--
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/42197457-a81a-4bfe-b2fd-6fcf8b1b9255%40googlegroups.com.
Curator - Edit metadata, upload files, and edit files, edit Terms, Guestbook, File Restrictions (Files Access + Use), Edit Permissions/Assign Roles + Publish
Hi Phil,I think it's just me :) I'm wondering if someone just wants to put a dataset in the root dataverse and publish it.
Erin
On Tuesday, June 27, 2017 at 3:13:27 PM UTC-3, Philip Durbin wrote:
PhilHi Erin,My mental model for permissions in Dataverse is that each dataverse is an "island of permissions." By this I mean that there is no inheritance of permissions. The permissions don't leak out from the root dataverse to sub-dataverses. At the Harvard Dataverse, we let people publish datasets (and dataverses they create) in the root dataverse.
I'm curious about where the documentation is falling down for you. I know it needs a lot of work! https://github.com/IQSS/dataverse/issues/2653 is related but if you want to create a fresh GitHub issue in your own words, that would probably be better.I hope this helps!
On Tue, Jun 27, 2017 at 1:55 PM, Erin MacPherson <Erin.Ma...@dal.ca> wrote:
Hi everyone,
I'm looking for some feedback on how others manage their workflows within the root database.
The default role for anyone assigned is contributer. However, we want it to be a self-curated tool, so I would like researchers to be able to publish their own data. However, if I gave them a curator role, does this mean that they would be able to publish any other dataset within the root dataverse? We will be setting up multiple dataverses for the different groups, but I was thinking if someone just wanted to add data for one project, they could just add it to the main dataverse and publish it, but I only want them to be able to publish their own. I've read a lot of the documentation surrounding this but I'm wondering how do others handle this?
Many thanks,Erin
--
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+unsubscribe...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/f81f49b4-a431-487a-bea0-00a702772e90%40googlegroups.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
--
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/42197457-a81a-4bfe-b2fd-6fcf8b1b9255%40googlegroups.com.
Hi again - to hopefully clarify, would assigning a curator role to someone at the root dataverse level allow them to publish another persons dataset in the root dataverse. I think that is where I am not clear.
Erin
On Tuesday, June 27, 2017 at 3:21:48 PM UTC-3, Erin MacPherson wrote:
Hi Phil,I think it's just me :) I'm wondering if someone just wants to put a dataset in the root dataverse and publish it.
Erin
On Tuesday, June 27, 2017 at 3:13:27 PM UTC-3, Philip Durbin wrote:
PhilHi Erin,My mental model for permissions in Dataverse is that each dataverse is an "island of permissions." By this I mean that there is no inheritance of permissions. The permissions don't leak out from the root dataverse to sub-dataverses. At the Harvard Dataverse, we let people publish datasets (and dataverses they create) in the root dataverse.
I'm curious about where the documentation is falling down for you. I know it needs a lot of work! https://github.com/IQSS/dataverse/issues/2653 is related but if you want to create a fresh GitHub issue in your own words, that would probably be better.I hope this helps!
On Tue, Jun 27, 2017 at 1:55 PM, Erin MacPherson <Erin.Ma...@dal.ca> wrote:
Hi everyone,
I'm looking for some feedback on how others manage their workflows within the root database.
The default role for anyone assigned is contributer. However, we want it to be a self-curated tool, so I would like researchers to be able to publish their own data. However, if I gave them a curator role, does this mean that they would be able to publish any other dataset within the root dataverse? We will be setting up multiple dataverses for the different groups, but I was thinking if someone just wanted to add data for one project, they could just add it to the main dataverse and publish it, but I only want them to be able to publish their own. I've read a lot of the documentation surrounding this but I'm wondering how do others handle this?
Many thanks,Erin
--
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+unsubscribe...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/f81f49b4-a431-487a-bea0-00a702772e90%40googlegroups.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
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/af23ef7c-8f8d-4f0b-b303-34ae443b3d39%40googlegroups.com.To post to this group, send email to dataverse-community@googlegroups.com.
I think our e-mails crossed paths. :) Hopefully what I sent answered your question, but to be clear, yes it would allow them to publish another persons dataset in that dataverse.What you want to do is change the setting I mentioned, which is not the same as assigning Curator role at the Dataverse level. That setting defines the role assigned by default to creators of new Datasets at the Dataset they created.
On Tue, Jun 27, 2017 at 2:27 PM, Erin MacPherson <Erin.Ma...@dal.ca> wrote:
Hi again - to hopefully clarify, would assigning a curator role to someone at the root dataverse level allow them to publish another persons dataset in the root dataverse. I think that is where I am not clear.Erin
On Tuesday, June 27, 2017 at 3:21:48 PM UTC-3, Erin MacPherson wrote:
Hi Phil,I think it's just me :) I'm wondering if someone just wants to put a dataset in the root dataverse and publish it.
Erin
On Tuesday, June 27, 2017 at 3:13:27 PM UTC-3, Philip Durbin wrote:
PhilHi Erin,My mental model for permissions in Dataverse is that each dataverse is an "island of permissions." By this I mean that there is no inheritance of permissions. The permissions don't leak out from the root dataverse to sub-dataverses. At the Harvard Dataverse, we let people publish datasets (and dataverses they create) in the root dataverse.
I'm curious about where the documentation is falling down for you. I know it needs a lot of work! https://github.com/IQSS/dataverse/issues/2653 is related but if you want to create a fresh GitHub issue in your own words, that would probably be better.I hope this helps!
On Tue, Jun 27, 2017 at 1:55 PM, Erin MacPherson <Erin.Ma...@dal.ca> wrote:
Hi everyone,
I'm looking for some feedback on how others manage their workflows within the root database.
The default role for anyone assigned is contributer. However, we want it to be a self-curated tool, so I would like researchers to be able to publish their own data. However, if I gave them a curator role, does this mean that they would be able to publish any other dataset within the root dataverse? We will be setting up multiple dataverses for the different groups, but I was thinking if someone just wanted to add data for one project, they could just add it to the main dataverse and publish it, but I only want them to be able to publish their own. I've read a lot of the documentation surrounding this but I'm wondering how do others handle this?
Many thanks,Erin
--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/f81f49b4-a431-487a-bea0-00a702772e90%40googlegroups.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
--
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...@googlegroups.com.
Hi Phil and Gustavo,I think you have both answered my questions, thank you :) I'll keep it at the Contributer level at the root Dataverse, and change it to curator at the Dataset level. I think I just got confused with the different levels.Thanks again, and also thank you all for the awesome community workshop!
Erin
On Tuesday, June 27, 2017 at 3:31:59 PM UTC-3, Gustavo Durand wrote:
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/af23ef7c-8f8d-4f0b-b303-34ae443b3d39%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/3810f153-01f9-44ba-9e3d-294e7338738c%40googlegroups.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/3810f153-01f9-44ba-9e3d-294e7338738c%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/CAF2sSef%2B_C1-XnkVJuSq2vh4MJKLnq3OiajameK8Ac8q%3DNtPcw%40mail.gmail.com.
The confusing thing is that "Contributor" appears in the Dataverse-level permissions:But it actually refers to the role the user has for datasets they added, not for the dataverse as a whole. It took me quite some time to figure that out. I do wonder if there's some better way to explain/label/conceptualize that, but I don't have anything constructive at the moment.
On Tue, Jun 27, 2017 at 4:13 PM, Durand, Gustavo <gdu...@iq.harvard.edu> wrote:
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/3810f153-01f9-44ba-9e3d-294e7338738c%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+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/CAF2sSef%2B_C1-XnkVJuSq2vh4MJKLnq3OiajameK8Ac8q%3DNtPcw%40mail.gmail.com.
--
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/CAOSYSD6r6Bf1NPJn-y8dxXpeQ8uTzeR5FAcHaj%2B6xCrmajt5dg%40mail.gmail.com.