Research data can be loosely defined as information collected, observed, or created for purposes of analysis to produce original research and/or necessary to validate research findings and results.

To help you decide if you should tag a piece of research data for later migration, consider the following:

It is suggested that the following research data should be tagged, regardless of whether the data are associated with funding or not.

· Data from outside agencies or institutions that are subject to restricted use agreements/data use or data sharing agreements that typically have terms or restrictions about storage, access, and retention or destruction of the data

· Personally Identifiable Information (PII) which is information that is uniquely associated with an individual person (e.g., HIPAA privacy rules identify 18 items such as name, mailing address, email address, social security number, etc. that are considered to be forms of PII)

· Highly sensitive data where disclosure could result in embarrassment or harm (e.g., criminal behavior, sexual behavior, illegal drug use, etc. )

· Data where it may be possible to infer the identity of someone participating in a research study even though there are no PII (e.g., when cross-referencing variables such as age, sex, race, census block could result in the identification of identity)

· Data that are integral to commercialization activities or intellectual property (e.g., patent development; unique databases; algorithms)

Examples of research data that do not necessarily need to be tagged and can be migrated with other information in your Box or Google folder include:

· Background research related to authoring a book, monograph, chapter, anthology

· Analyses of environmental samples (e.g., air, water, soil, biological materials, and wastes) as long as not associated with the categories above (e.g., identifiable with a particular location where the disclosure could result in embarrassment or harm)

· Chemical/biochemical analyses (e.g., proteomics, mass spec) as long as not associated with the categories above

Only if that data is related to a Research endeavor. The default M365 storage location is compliant with HIPAA and FERPA.

The folder structure is up to the owner of the Research data. Data that is subject to specific data security requirements should be grouped together.

Yes, all research data needs to be tagged.

The change of the “owner” role is for migration purposes only. You will maintain control and ownership of your data at all times. After the migration is complete, these temporary owners will be removed.

Sharing settings will be unchanged when data is moved into the ITS created folder in Box or your Google Shared drive. Once Data is migrated into the M365 environment sharing settings will need to be recreated.

Yes, you can edit, create, share and delete data as you normally would after you tag it as research data.

The details of the new Research data storage services are still being developed. They are being designed with the flexibility to accommodate complex, secure and large volume research data. More information about these offerings will be released soon.

Not at this time. Labels will be applied post migration. Labels have no bearing on the compliance level of data in M365. Higher labels will have restrictions on them to now allow external sharing by default.

Copying the data will create a duplicate of it in these 2 locations. If you are sure you have copied everything, you can delete the data stored in the original location. If you need assistance please contact 6tech@uncg.edu.

Changing the folder name is for migration purposes only. After the migration you will be able to change the name back.

The change in of the “ownership” role is temporary for migration purposes. Our migration tool work on data “ownership” to know where to move data to. After the migration this role will be reverted. You will maintain control of your data throughout the migration process.

If you have self migrated data into M365 please contact 6tech@uncg.edu for assistance.

If you have over 500GB of data to move, we recommend breaking that data into “chunks” of 500GB or less and moving one chunk at a time to make it easier to verify it is all present in the ITS Created Box Folder.