*This article is adapted from pre-existing resources located on the Digitization Knowledge Base

...

Bit rot is natural. Even though it might not seem like it, data can rot just like a log over time. It is an occurrence that language team workers must account for in their assets management. In the following modules, you will come to learn how to better prepare for bit rot and , make, and then store backups to restore data that undergoes corruption.

...

Simply, bit rot is data degradation or the process of data decay as a result of slowly accruing errors/issues. In a file's lifetime, changes in their bits (tiny amounts of data), importing, exporting, their physical and electronic containment, and even electric charge charges will slowly alter the information within. When these changes accrue to a point where you can no longer use or open the file, then the file is corrupted.

Many models and new tools for project members to use are working with new internal processes to prolong the lives of files and detect errors that might indicate data corruption. However, you still need to be aware of it and how it can occur with your data.

Certain decisions can reduce the environments and scenarios for bit rot to occur.

In this module, you will conceptualize and dive into what bit rot looks like for your data and materials.

...

If your storage system or location gets too hot, too cold, has been receiving lots of power surges over the years, or has become home to some critters like bugs or even moldmould, then bit rot can occur much faster than if information and data is stored differently.

...

Checksums are bits of data that attach to files that detect slight changes in the contents and internal structure. They can be used to clue you into when bit rot might be occurring in entries and recordings before they become unusable. For more information on embedding checksums onto your WAV files, please see this link to FV Checksum Article (once published) Embed checksums using BWF MetaEdit.

...

Why is It Important to a FirstVoices Project?

...

If backups are the single best method to address bit rot, then you need to come up with a strategy to store and make sure your backups are accessible, findable, and usable later.

A backup is a copy of stored data that is saved in multiple locations and later used to restore lost or corrupted data.

How you manage and create your backups varies. Workflow, human capacity, technical capacity, and storage space are huge factors that influence how you prepare and bundle these resources for use.

...

It is important to keep in mind who is going to be restoring backups and how long these backups will exist before being updated. If you leave the organization or pass on your responsibilities onto to another, it will be important to leave a guide or make your internal information structure (e.g. file naming and organization) inside your backups understandable for the next person.

...

Within this lesson, you will be presented with more backup scenarios like the one above and, at the end, be able to decide which one is the most feasible, useful, and secure for storing backups.

Ultimately, combining storage devices that both are easy-to-use to transfer information between FirstVoices team members and are stable for long-term storage is recommended in whatever your backup strategy turns out to be. Your backup strategy is also likely to change too. It all depends on your current workflow and capacity.

For a detailed discussion about these topics that also makes use of the educational materials showcased within the module, please also find the March 2021 DiGI Webinar with the topic, Backups & Bit Rot, here: Join or watch Digitization Webinars.