How can I limit the access to a Dataverse to only registered users?

[Jose Antonio Galeano Cardenas]

We have installed Dataverse on our server and created a test Dataverse and inside it we created many dataverses and datasets, some of the published, some of them are not published.

How can I limit the visibility of the parent test Dataverse so it is not shown when a user isn't logged in?

[Philip Durbin]

Hi! It might be easiest for us to help if you use https://demo.dataverse.org to recreate the situation you're describing so that we can click around and see exactly what you mean. Alternatively, screenshots would help.

My first though is that when a dataverse (or dataset or file) is published it is always visible to all, even people who are not logged in. Unpublished datasets within that published dataverse will not be visible, of course, except to those who have access to it.

Apologies if I don't understand your question. Please also feel free to create a GitHub issue with screenshots at https://github.com/IQSS/dataverse/issues if you think that will be a better way to discuss this. You can also reach us at http://chat.dataverse.org for real-time discussion, when we're logged in and paying attention. :)

Thanks,

Phil

On Thu, Feb 28, 2019 at 8:07 AM Jose Antonio Galeano Cardenas <antoni...@gmail.com> wrote:

We have installed Dataverse on our server and created a test Dataverse and inside it we created many dataverses and datasets, some of the published, some of them are not published.

How can I limit the visibility of the parent test Dataverse so it is not shown when a user isn't logged in?

--
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 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/b0925582-b92b-4aae-aa04-c403c8e5c0d8%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

[Sebastian Karcher]

I don't know if this is helpful, but if you don't mind the metadata and datasets being visible and just want the files to be only accessible by registered, logged-in users, you can restrict all files on publication and then grant permission to the group :authenticated-users . That's what we do at QDR. But obviously that doesn't work if you really want the entire dataverse and its contents to be completely invisible (out of curiousity: what's the use case for that?). 

With invisible datasets, you also run into problems if you're using DOIs, since it's bad practice to issue DOIs that don't resolve for everyone (and the metadata would be public through Datacite anyway).

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

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

--

Sebastian Karcher, PhD
www.sebastiankarcher.com

[Jose Antonio Galeano Cardenas]

Thank your for your response Philip. My main question is, how can I make a published dataverse not visible to users that haven't logged in? Below is our Dataverse site, those 3 dataverse that appear have been published but are test dataverses and we don't want them to be visible to users that haven't logged in.

On Thursday, February 28, 2019 at 8:30:38 AM UTC-5, Philip Durbin wrote:

Hi! It might be easiest for us to help if you use https://demo.dataverse.org to recreate the situation you're describing so that we can click around and see exactly what you mean. Alternatively, screenshots would help.

My first though is that when a dataverse (or dataset or file) is published it is always visible to all, even people who are not logged in. Unpublished datasets within that published dataverse will not be visible, of course, except to those who have access to it.

Apologies if I don't understand your question. Please also feel free to create a GitHub issue with screenshots at https://github.com/IQSS/dataverse/issues if you think that will be a better way to discuss this. You can also reach us at http://chat.dataverse.org for real-time discussion, when we're logged in and paying attention. :)

Thanks,

Phil

On Thu, Feb 28, 2019 at 8:07 AM Jose Antonio Galeano Cardenas <antoni...@gmail.com> wrote:

We have installed Dataverse on our server and created a test Dataverse and inside it we created many dataverses and datasets, some of the published, some of them are not published.

How can I limit the visibility of the parent test Dataverse so it is not shown when a user isn't logged in?

--
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/b0925582-b92b-4aae-aa04-c403c8e5c0d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jose Antonio Galeano Cardenas]

Sebastian, thank you. I was able to not show the Datasets and Files, the Dataverse was created as a test, so it's content is not useful since it containes "dirty" data. We haven't assign DOIs yet.

On Thursday, February 28, 2019 at 8:38:38 AM UTC-5, Sebastian Karcher wrote:

I don't know if this is helpful, but if you don't mind the metadata and datasets being visible and just want the files to be only accessible by registered, logged-in users, you can restrict all files on publication and then grant permission to the group :authenticated-users . That's what we do at QDR. But obviously that doesn't work if you really want the entire dataverse and its contents to be completely invisible (out of curiousity: what's the use case for that?). 

With invisible datasets, you also run into problems if you're using DOIs, since it's bad practice to issue DOIs that don't resolve for everyone (and the metadata would be public through Datacite anyway).

On Thu, Feb 28, 2019 at 8:30 AM Philip Durbin <philip...@harvard.edu> wrote:

Hi! It might be easiest for us to help if you use https://demo.dataverse.org to recreate the situation you're describing so that we can click around and see exactly what you mean. Alternatively, screenshots would help.

My first though is that when a dataverse (or dataset or file) is published it is always visible to all, even people who are not logged in. Unpublished datasets within that published dataverse will not be visible, of course, except to those who have access to it.

Apologies if I don't understand your question. Please also feel free to create a GitHub issue with screenshots at https://github.com/IQSS/dataverse/issues if you think that will be a better way to discuss this. You can also reach us at http://chat.dataverse.org for real-time discussion, when we're logged in and paying attention. :)

Thanks,

Phil

On Thu, Feb 28, 2019 at 8:07 AM Jose Antonio Galeano Cardenas <antoni...@gmail.com> wrote:

We have installed Dataverse on our server and created a test Dataverse and inside it we created many dataverses and datasets, some of the published, some of them are not published.

How can I limit the visibility of the parent test Dataverse so it is not shown when a user isn't logged in?

--
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/b0925582-b92b-4aae-aa04-c403c8e5c0d8%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.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CABbxx8HeukkkxkAaQGC3ghdjJBngKLj3ky4ZzDifSG_UZYyrxA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Philip Durbin]

Thanks for the screenshot and the further explanation. Published dataverses are always visible to the world. They're public. You don't have to log in to see them. What if you were able to "unpublish" dataverses that don't yet have any published datasets? Would that help? You could hack on the database and Solr to achieve this but I wouldn't recommend it. Please feel free to open a GitHub issue at https://github.com/IQSS/dataverse/issues to describe the problem you're having. In that issue, perhaps the community can brainstorm on solutions, create a pull request to improve the documentations, and/or create a pull request to add a new feature that would help.

Thanks,

Phil

On Thu, Feb 28, 2019 at 8:55 AM Jose Antonio Galeano Cardenas <antoni...@gmail.com> wrote:

Thank your for your response Philip. My main question is, how can I make a published dataverse not visible to users that haven't logged in? Below is our Dataverse site, those 3 dataverse that appear have been published but are test dataverses and we don't want them to be visible to users that haven't logged in.

On Thursday, February 28, 2019 at 8:30:38 AM UTC-5, Philip Durbin wrote:

Hi! It might be easiest for us to help if you use https://demo.dataverse.org to recreate the situation you're describing so that we can click around and see exactly what you mean. Alternatively, screenshots would help.

My first though is that when a dataverse (or dataset or file) is published it is always visible to all, even people who are not logged in. Unpublished datasets within that published dataverse will not be visible, of course, except to those who have access to it.

Apologies if I don't understand your question. Please also feel free to create a GitHub issue with screenshots at https://github.com/IQSS/dataverse/issues if you think that will be a better way to discuss this. You can also reach us at http://chat.dataverse.org for real-time discussion, when we're logged in and paying attention. :)

Thanks,

Phil

On Thu, Feb 28, 2019 at 8:07 AM Jose Antonio Galeano Cardenas <antoni...@gmail.com> wrote:

We have installed Dataverse on our server and created a test Dataverse and inside it we created many dataverses and datasets, some of the published, some of them are not published.

How can I limit the visibility of the parent test Dataverse so it is not shown when a user isn't logged in?

--
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 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/b0925582-b92b-4aae-aa04-c403c8e5c0d8%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-commu...@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/8792501e-519b-486f-a18c-7b1919bbd302%40googlegroups.com.

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

[Pete Meyer]

Hi Jose,

Depending on your use case, and some of your installation details, this might be something that you could handle at the web layer (since restricting access to published dataverses/dataset metadata isn't supported at the application layer).  In other words, use the apache configuration to require authentication for dataverse pages (and possibly allow unauthenticated access to the url pattern matching dataset pages, to avoid the potential issue Sebastion mentioned with DOIs with unresolvable target urls).

This might be a reasonable approach for internal evaluation or development; but it also gets very close to the "here there be dragons" part of the conceptual map - it would require more work from your system administrators, your target users would have to be on the same page, and you should allow for the possibility that other things may behave unexpectedly.

Best,

Pete