migrate dataset permission

[solo...@gmail.com]

Upgraded from 3.x to 4.7.1

everything migrated except the dataset permission.

In our 3.x version, some of the datasets are not available to the public.When they clicked it redirect to the login page.

But on the migrated dataverse 4.7.1 all datasets are open without login. I did run migrate_permissions.sql

Thanks

[Durand, Gustavo]

Hi Solomon,

Could you please provide some more details?

- (in 3.6) When you say they clicked, where exactly are they clicking?

- are these dataset published?

- were the dataverse they were in (in 3.6) published?

If you could provide any links that I could look at, that would be useful. 

Thanks,

Gustavo

--
You received this message because you are subscribed to the Google Groups "Dataverse Migration Working Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-migration-wg+unsub...@googlegroups.com.
To post to this group, send email to dataverse-migration-wg@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-migration-wg/8c2011aa-4bd3-43f8-ab13-091f4c09fa9d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[solomon hm]

Hi Gustavo

Here are the links from both installation, I hope it will answer your question.

3.6  and 4.7.1  on both instant as an example please check dataset title "IWYP Hub trials and links with IWYP research projects"

Thanks!

Solomon

 

On Wed, Nov 15, 2017 at 8:43 PM, Durand, Gustavo <gdu...@iq.harvard.edu> wrote:

Hi Solomon,

Could you please provide some more details?

- (in 3.6) When you say they clicked, where exactly are they clicking?

- are these dataset published?

- were the dataverse they were in (in 3.6) published?

If you could provide any links that I could look at, that would be useful. 

Thanks,

Gustavo

On Wed, Nov 15, 2017 at 9:16 AM, solo...@gmail.com <solo...@gmail.com> wrote:

Upgraded from 3.x to 4.7.1

everything migrated except the dataset permission.

In our 3.x version, some of the datasets are not available to the public.When they clicked it redirect to the login page.

But on the migrated dataverse 4.7.1 all datasets are open without login. I did run migrate_permissions.sql

Thanks

--
You received this message because you are subscribed to the Google Groups "Dataverse Migration Working Group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-migration-wg+unsubscri...@googlegroups.com.

To post to this group, send email to dataverse-migration-wg@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-migration-wg/8c2011aa-4bd3-43f8-ab13-091f4c09fa9d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Solomon Hailemelekot
+251911249756

[Durand, Gustavo]

Ah, yes, I had forgotten we allowed studies in 3.x to be restricted. In 4.x we no longer allow that - that is if you publish, the metadata is always public.

What we did at Harvard is to effectively unpublish any restricted study that still needed to be not public. The caveat is that any such studies could only have one version, so we only migrated the latest version of those studies (i.e. did not include ddis from previous versions for these studies).

We then ran following scripts (in our case, we only were concerned with restricted studies in one particular dataverse, hence the join with the dataverse table; the queries, of course, could be modified to find all restricted studies) :

update dvobject

set publicationdate = null,

releaseuser_id = null

where id in (

select ds.id from dvobject ds_dvo, dataset ds, dataverse dv,_dvn3_study s

where ds_dvo.owner_id = dv.id

and dv.alias='XXXX'

and ds_dvo.id = ds.id

and ds.authority = s.authority

and ds.protocol = s.protocol

and ds.identifier = s.studyid

and s.restricted = true

)

update datasetversion

set versionstate = 'DRAFT',

versionNumber = null,

minorVersionNumber = null,

releasetime = null

where dataset_id in (

select ds.id from dvobject ds_dvo, dataset ds, dataverse dv,_dvn3_study s

where ds_dvo.owner_id = dv.id

and dv.alias='XXXX'

and ds_dvo.id = ds.id

and ds.authority = s.authority

and ds.protocol = s.protocol

and ds.identifier = s.studyid

and s.restricted = true

)

On Thu, Nov 16, 2017 at 2:06 AM, solomon hm <solo...@gmail.com> wrote:

Hi Gustavo

Here are the links from both installation, I hope it will answer your question.

3.6  and 4.7.1  on both instant as an example please check dataset title "IWYP Hub trials and links with IWYP research projects"

Thanks!

Solomon

 

On Wed, Nov 15, 2017 at 8:43 PM, Durand, Gustavo <gdu...@iq.harvard.edu> wrote:

Hi Solomon,

Could you please provide some more details?

- (in 3.6) When you say they clicked, where exactly are they clicking?

- are these dataset published?

- were the dataverse they were in (in 3.6) published?

If you could provide any links that I could look at, that would be useful. 

Thanks,

Gustavo

On Wed, Nov 15, 2017 at 9:16 AM, solo...@gmail.com <solo...@gmail.com> wrote:

Upgraded from 3.x to 4.7.1

everything migrated except the dataset permission.

In our 3.x version, some of the datasets are not available to the public.When they clicked it redirect to the login page.

But on the migrated dataverse 4.7.1 all datasets are open without login. I did run migrate_permissions.sql

Thanks

--
You received this message because you are subscribed to the Google Groups "Dataverse Migration Working Group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-migration-wg+unsubscri...@googlegroups.com.

To post to this group, send email to dataverse-migration-wg@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-migration-wg/8c2011aa-4bd3-43f8-ab13-091f4c09fa9d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Solomon Hailemelekot
+251911249756

[solomon hm]

Thank you so much, Gustavo for the info. 

Any plan to include restriction as 3.x? 

I'll check the workaround you mentioned to adopt with our dv.

thanks

--

Solomon Hailemelekot
+251911249756

[Durand, Gustavo]

I don't foresee that happening as the whole concept of publishing something is to make it publicly available. They key is the files are still able to be restricted and it's just the metadata that's public.

(there has been discussion of weather we did want to have unpublished versions, but there hasn't seem to be much demand for that)

Please let me know how the queries work for you and if I/we can help in other ways.

Gustavo

On Fri, Nov 17, 2017 at 3:38 AM, solomon hm <solo...@gmail.com> wrote:

Thank you so much, Gustavo for the info. 

Any plan to include restriction as 3.x? 

I'll check the workaround you mentioned to adopt with our dv.

thanks

On Fri, Nov 17, 2017 at 12:34 AM, Durand, Gustavo <gdu...@iq.harvard.edu> wrote:

--

Solomon Hailemelekot
+251911249756