Show access conditions for restricted file (before login, ideally)

42 views
Skip to first unread message

Sebastian Karcher

unread,
Jul 11, 2017, 3:03:28 PM7/11/17
to Dataverse Users Community
When I have a restricted file such as
https://demo.dataverse.org/dataset.xhtml?persistentId=doi:10.5072/FK2/OFYOGI&version=1.0
is there any way to show the access conditions (without putting them into the description field) before a user requests access/logs in?

The specific users story is that a lot of our files are going to be accessible to all authenticated users -- but there's no way to tell for someone just visiting our site that that's all they need to do.

If this isn't possible, would this make sense as a feature request/ticket?

Philip Durbin

unread,
Jul 11, 2017, 8:36:56 PM7/11/17
to dataverse...@googlegroups.com
Hi Sebastian,

It sounds a lot like this issue:

Request Access: User Should Get Pop Up with Terms of Use + Terms of Access when clicking Request Access button - https://github.com/IQSS/dataverse/issues/2872

That said, I prefer it when GitHub issues are in the names of people who are are actively interested in the feature, so if you'd like to open a fresh one in your own words we can close the old one as a duplicate.

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-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/ba4c201c-5578-4a0d-b5ad-7a11e3272586%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--

Sebastian Karcher

unread,
Jul 12, 2017, 3:55:25 PM7/12/17
to Dataverse Users Community

Janet McDougall - Australian Data Archive

unread,
Jul 13, 2017, 8:03:30 PM7/13/17
to Dataverse Users Community, philip...@harvard.edu
hi Phil & Sebastian
I can see this would be helpful if data files within a published data set have different Terms of Use + Terms of Access, although if terms & access for data files within a data set are different, maybe they should be published in separate data sets?  

Anyway, the TERMS (metadata) should provide the conditions for Terms of Use + Terms of Access for the data set without the user logging in.  Or have i missed something?

I think the popup is a good idea but terms & access conditions are often quite lengthy - could a pop up point to the TERMS tab so the user can benefit from the full metadata fields?

Am interested to hear your thoughts.
Janet


On Wednesday, 12 July 2017 10:36:56 UTC+10, Philip Durbin wrote:
Hi Sebastian,

It sounds a lot like this issue:

Request Access: User Should Get Pop Up with Terms of Use + Terms of Access when clicking Request Access button - https://github.com/IQSS/dataverse/issues/2872

That said, I prefer it when GitHub issues are in the names of people who are are actively interested in the feature, so if you'd like to open a fresh one in your own words we can close the old one as a duplicate.

Phil
On Tue, Jul 11, 2017 at 3:03 PM, Sebastian Karcher <sebastiank...@u.northwestern.edu> wrote:
When I have a restricted file such as
https://demo.dataverse.org/dataset.xhtml?persistentId=doi:10.5072/FK2/OFYOGI&version=1.0
is there any way to show the access conditions (without putting them into the description field) before a user requests access/logs in?

The specific users story is that a lot of our files are going to be accessible to all authenticated users -- but there's no way to tell for someone just visiting our site that that's all they need to do.

If this isn't possible, would this make sense as a feature request/ticket?

--
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.

Sebastian Karcher

unread,
Jul 13, 2017, 9:50:09 PM7/13/17
to dataverse...@googlegroups.com, Durbin, Philip
The Terms of use are visible in the tab (though indeed hard to make the connection to the restricted files, so a link might help), but the terms of use are at the dataset level. The terms of access are at the file level and can (and do) vary within a dataset. 


On Thu, Jul 13, 2017 at 8:03 PM, Janet McDougall - Australian Data Archive <janet.m...@anu.edu.au> wrote:
hi Phil & Sebastian
I can see this would be helpful if data files within a published data set have different Terms of Use + Terms of Access, although if terms & access for data files within a data set are different, maybe they should be published in separate data sets?  

Anyway, the TERMS (metadata) should provide the conditions for Terms of Use + Terms of Access for the data set without the user logging in.  Or have i missed something?

I think the popup is a good idea but terms & access conditions are often quite lengthy - could a pop up point to the TERMS tab so the user can benefit from the full metadata fields?

Am interested to hear your thoughts.
Janet


On Wednesday, 12 July 2017 10:36:56 UTC+10, Philip Durbin wrote:
Hi Sebastian,

It sounds a lot like this issue:

Request Access: User Should Get Pop Up with Terms of Use + Terms of Access when clicking Request Access button - https://github.com/IQSS/dataverse/issues/2872

That said, I prefer it when GitHub issues are in the names of people who are are actively interested in the feature, so if you'd like to open a fresh one in your own words we can close the old one as a duplicate.

Phil
On Tue, Jul 11, 2017 at 3:03 PM, Sebastian Karcher <sebastiank...@u.northwestern.edu> wrote:
When I have a restricted file such as
https://demo.dataverse.org/dataset.xhtml?persistentId=doi:10.5072/FK2/OFYOGI&version=1.0
is there any way to show the access conditions (without putting them into the description field) before a user requests access/logs in?

The specific users story is that a lot of our files are going to be accessible to all authenticated users -- but there's no way to tell for someone just visiting our site that that's all they need to do.

If this isn't possible, would this make sense as a feature request/ticket?

--
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.

--
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.

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



--
Sebastian Karcher, PhD
www.sebastiankarcher.com

Janet McDougall - Australian Data Archive

unread,
Jul 14, 2017, 6:57:30 AM7/14/17
to Dataverse Users Community
Yes agree that terms of access makes sense per data file which is why having data file access described at dataset level seems awkward - for datasets that have varying access conditions for restricted files. As posted earlier, maybe access located with the data file description would enable access variations to be described at this level. Where would this metadata be collected? Anyway this will become more relevant to us so is of interest. Hope I'm explaining myself here....

Mercè Crosas

unread,
Jul 14, 2017, 10:23:42 AM7/14/17
to dataverse...@googlegroups.com
I'd like to add that terms of access and data user agreements at the file level will also be needed to support DataTags, which define the level of sensitive of each file.

Mercè


> On Jul 14, 2017, at 6:57 AM, Janet McDougall - Australian Data Archive <janet.m...@anu.edu.au> wrote:
>
> Yes agree that terms of access makes sense per data file which is why having data file access described at dataset level seems awkward - for datasets that have varying access conditions for restricted files. As posted earlier, maybe access located with the data file description would enable access variations to be described at this level. Where would this metadata be collected? Anyway this will become more relevant to us so is of interest. Hope I'm explaining myself here....
>
> --
> 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/e233b3fb-433a-4727-8d5a-324fd99826eb%40googlegroups.com.

Jonathan Crabtree

unread,
Jul 14, 2017, 10:33:17 AM7/14/17
to dataverse...@googlegroups.com
Merce

I agree. We have a need for that coming very soon too.

Jon
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/07D1FEB6-930F-44F6-85F0-C7FF87B1B58D%40gmail.com.
Reply all
Reply to author
Forward
0 new messages