Sensitive Data: Restricted Metadata Block

[posixeleni]

I have a use case where a professor would like to use Dataverse for teaching and for students to submit their datasets to, but there are privacy issues (e.g., FERPA) related to any student information being collected on a site.

Only certain metadata fields would have identifiable information. We would need to find a way to restrict a block of metadata so that only people who have proper permissions could see these fields and make sure it's FERPA-compliant.

The datasets would not have any identifiable information so DataTags / Secure Dataverse would need to help with this.

[mercecrosas]

DataTags can help with this issue in the future by supporting tagging
metadata as well as data.

Mercè Crosas, Ph.D.
Director of Data Science, IQSS
Harvard University
http://iq.harvard.edu/merce-crosas

On Wed, Sep 3, 2014 at 10:26 AM, posixeleni notifications@github.com
wrote:

I have a use case where a professor would like to use Dataverse for
teaching and for students to submit their datasets to, but there are
privacy issues (e.g., FERPA) related to any student information being
collected on a site.

The datasets would not have any identifiable information so DataTags /
Secure Dataverse would not necessarily help with this.

Only certain metadata fields would have identifiable information. We would
need to find a way to restrict a block of metadata so that only people who
have proper permissions could see these fields and make sure it's
FERPA-compliant.

Reply to this email directly or view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_IQSS_dataverse_issues_902&d=AAMCaQ&c=WO-RGvefibhHBZq3fL85hQ&r=MoES6dokjPLLcKaEAd7qaCuTcYZ4jLjEOBQnbbJ9BaA&m=wOdhVyVpqUXVNlBH4D9zKUqFrnQrjF2jjm_Zs7wbOn0&s=Y9lvsN1YydBPucFVteVA9EnH7BVhEQkySGpU9Zyja9g&e=
.

[pdurbin]

This reminds me a bit about how our general rule is "if metadata is published, it's searchable and discoverable" per #57 but how we go counter to this in the case of email field types, which we have made not searchable (for privacy): #759.

[posixeleni]

I have another use case from @muelle12 where the user wishes to be able to restrict ALL metadata for their dataset to be viewable and searchable only to people/groups they give permission/access to.

[pdurbin]

the user wishes to be able to restrict ALL metadata for their dataset to be viewable and searchable only to people/groups they give permission/access to.

The workaround for Dataverse 4.0 is to not publish the dataset. The act of publishing a dataset makes the metadata searchable and discoverable via browse. See also #57 (comment)

[muelle12]

Who can see unpublished datasets? Is there going to be a way to give permissions to view but not edit/change unpublished datasets for a particular dataverse? The GSD really appreciated the ability in 3.6 to publish a dataset in an unpublished Dataverse.

[posixeleni]

@scolapasta can you comment on @muelle12 's question #902 (comment) about permissions for unpublished datasets?