Research Data Classification Guidance & Data Storage Service

Research Data Classification Guidance

Whether faced with a relatively short-term project, or something considerably longer and more processing-intensive, it’s important to know what research data you should store where, and how it can be properly overseen for the duration of its lifecycle.

A short summary of the latest advice has been published on the IT and Library websites:

Research Data Classification Guidance & Data Storage Service (IT)

Storing and Handling Data - Data Classification (Library)

The full advice is published here: Research Information Management Guide to Data Classifications.

The new Research Data Storage Service is now live to help researchers procuring storage for their projects. 

Currently, the core Research Data Storage Service is entirely comprised of on-premise Dell EMC Isilon storage. Page three of the Research Information Management Guide to Data Classifications notes that this is suitable for data in Tiers 0/1, 2 and 3.  

If, based on this guidance, Isilon would be suitable, there are currently three storage options to choose from:

1. Standard performance storage (core): On-premise storage, split into separate faculty drives. Up to 1TB is available for free (storage over 1TB is also available but will require approval). Requests are subject to faculty validation.
2. Standard performance storage (extended core): A chargeable service providing further capacity beyond the standard storage allocation. You can purchase project-specific storage allocations, directly costed into grants or account codes. A grant code is needed to request this type of storage, and a Principal Investigator (PI) or data owner must oversee the data and its lifecycle at all times.
3. Fast performance core (SSD) storage: A chargeable service intended to provide enhanced performance storage specifically for intensive processing or faster data acquisition. This solution must be agreed with IT services to make sure it is appropriate for the intended usage. Again, a PI or data owner must oversee the data and its lifecycle at all times.

This is the first iteration of the service, with plans to add more storage options in the future.