Releasing restricted metadata and data in 3.6

[Tim DiLauro]

Hi folks,

We are running DVN 3.6 build 114 and have run into the following problem releasing data.

For data that is meant to be embargoed, we have loaded the data and set the permissions as 'restricted' for both the studies and the files. Now that the embargo has been lifted on one of the the studies, we are attempting to release the data. We did this by changing the permissions to 'public' for both the study and its files. 

This new status is reflected in the interface, but when visiting this study from a non-logged in user, login is forced with a message indicating that the page is restricted. Is there something that we're doing wrong or perhaps a step that is missing?

Any guidance would be greatly appreciated.

Cheers,

~Tim

[Philip Durbin]

Hi Tim,

Have you already switched the study from "draft" to "released"? You can read about releasing studies in DVN 3.x here:

- http://guides.dataverse.org/en/3.6.2/dataverse-user-main.html#publishing-data
- http://guides.dataverse.org/en/3.6.2/dataverse-user-main.html#manage-studies

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 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/e876eac7-0fb6-4b29-a2a6-a956301ae295%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

[Tim DiLauro]

Hi Phil,

Thanks for the response. We did release the study[1]. The most recent release was today.

Also having some other seemingly related strangeness. For example, if I attempt to restrict a the associated files, like this[2] (screenshot just before I hit save) and then return to the same page, most still appear to be public and I see this [3].

After setting them all to public[3] (right before save) and upon returning to the file permissions, they all show public[4].

Even so, they all show as restricted to an anonymous user.[5]

Cheers,

~Tim

[1] https://archive.data.jhu.edu/dvn/dv/Nutrient_Sediment_Loadings_to_the_Chesapeake_Bay/faces/study/StudyPage.xhtml?globalId=hdl:TEST/10024&studyListingIndex=0_626da0ea6c8387ddfbf013bf70eb

[2] https://www.dropbox.com/s/unofc7bmd8zgm83/Screenshot%202015-08-19%2014.50.04.png?dl=0

[3] https://www.dropbox.com/s/1cno50nntzr54rg/Screenshot%202015-08-19%2014.52.13.png?dl=0

[4] https://www.dropbox.com/s/a7xiav0ys3kjw9b/Screenshot%202015-08-19%2014.53.22.png?dl=0

[5] https://www.dropbox.com/s/jlq0tgw9pigz7dy/Screenshot%202015-08-19%2014.58.17.png?dl=0

On Wednesday, August 19, 2015 at 8:08:10 AM UTC-4, Philip Durbin wrote:

Hi Tim,

Have you already switched the study from "draft" to "released"? You can read about releasing studies in DVN 3.x here:

- http://guides.dataverse.org/en/3.6.2/dataverse-user-main.html#publishing-data
- http://guides.dataverse.org/en/3.6.2/dataverse-user-main.html#manage-studies

Phil

On Tue, Aug 18, 2015 at 10:43 PM, Tim DiLauro <tim.d...@gmail.com> wrote:

Hi folks,

We are running DVN 3.6 build 114 and have run into the following problem releasing data.

For data that is meant to be embargoed, we have loaded the data and set the permissions as 'restricted' for both the studies and the files. Now that the embargo has been lifted on one of the the studies, we are attempting to release the data. We did this by changing the permissions to 'public' for both the study and its files. 

This new status is reflected in the interface, but when visiting this study from a non-logged in user, login is forced with a message indicating that the page is restricted. Is there something that we're doing wrong or perhaps a step that is missing?

Any guidance would be greatly appreciated.

Cheers,

~Tim

--

[Condon, Kevin]

Hi Tim,

In v3.6 we had an option to restrict all files at the dataverse level. Would you check to see whether that is set?

If it is set, that would explain things. The solution would then be to deselect it while making sure the files are restricted at the study level where appropriate.
In v4.0 the permissions have been simplified.

Regards,

Kevin

---

From: dataverse...@googlegroups.com [dataverse...@googlegroups.com] on behalf of Tim DiLauro [tim.d...@gmail.com]
Sent: Wednesday, August 19, 2015 2:59 PM
To: Dataverse Users Community
Cc: Durbin, Philip
Subject: Re: [Dataverse-Users] Releasing restricted metadata and data in 3.6

[Tim DiLauro]

Thanks, Kevin!

That did it. All is well again.

Cheers,

~Tim