Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Another critical aspect of Data Management is consideration of which datasets are the most valuable and what protections need to be in place for them. Discussed in this section, are the different stages data could be in, what to consider before choosing a storage option, a comparison of the storage offerings from ARCC, and long-term planning for the data.



Stages of Data

During a research project, data takes on different stages of use each with a different storage requirement. Some research projects will use all of these stages, some will only use a few.

  1. Potential Data - data that are not yet collected, but there is a plan to store them. This storage could be temporary prior to transfer to a more permanent place, or is immediately transferred from an instrument etc.

  2. Raw Data - This transitional stage includes everything that is collected from the potential stage and could be stored in the same temporary place if deemed not as valuable, or in a more permanent place if keeping raw is determined to be valuable.

  3. Prepared Data - This stage describes the pre-processing of the raw data that prepares for a model or other processes. This should be stored or transferred to storage that will optimize the process.

  4. Intermediate Data - This stage is the most temporary of all data, it could be a step in a process that creates these data before processing into final data or simulated data that helps train a model, these data should be stored in a highly performant in read and write operations and backups are not necessarily a requirement.

  5. Final Data - The resulting data of a process. These data tell the story of the research and indicate the results. They should be stored in a safe place if the process is difficult to re-do.

  6. Published Data - These data are the same as the final data, but may be in a different format for data sharing. Possibly a compressed file stored on a repository.

  7. Archived Data - This stage of data are no longer needed for ongoing research projects but are not deleted. Stored somewhere in “cold” storage in the most cost effective way possible.


Assessing the Needs

Two Column Tables are nice ways to separate content/ Background info along with a code example on the same “Slide”. Please notice the table width. This should stop scroll bars from appearing

  • Bullets are nice to include for distinct points

  • yep

  • they

  • sure

  • are

    This is 14 lines

Please use the "code snippet" in the + button when creating code examples. Also please do not go
past the width of the table. This is to prevent scroll bars appearing













This is the Max number of code lines to show on an example

Comparing Storage Options

Limit to 16 lines in the example. 














This is the end

Considering Other Requirements

Two Column Tables are nice ways to separate content/ Background info along with an image example on the same “Slide”. Please notice the table width. This should stop scroll bars from appearing

  • Bullets are nice to include for distinct points

  • yep

  • they

  • sure

  • are

    This is 14 lines

image-20240514-000033.png


How to Decide

image-20240514-000127.png


Next Steps

Link to Previous sub-module or Home Module

Align left link to next sub-module or home

  • No labels