Editing NDSA Levels of Preservation
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 14: | Line 14: | ||
The overall structure of the chart is progressive -- the actions in the first level are either necessary prerequisites for those in the second to fourth levels or are themselves the most pressing activities to accomplish first. Broadly speaking, as one moves up each of the tiers from Level 1 to Level 4, one is moving from the basic need to ensure bit preservation towards broader requirements for keeping track of digital content and being able to ensure that it can be made available over longer periods of time. | The overall structure of the chart is progressive -- the actions in the first level are either necessary prerequisites for those in the second to fourth levels or are themselves the most pressing activities to accomplish first. Broadly speaking, as one moves up each of the tiers from Level 1 to Level 4, one is moving from the basic need to ensure bit preservation towards broader requirements for keeping track of digital content and being able to ensure that it can be made available over longer periods of time. | ||
− | |||
− | |||
== User Experiences == | == User Experiences == | ||
Line 23: | Line 21: | ||
http://www.digitalpreservation.gov/ndsa/working_groups/documents/USGS_Guidelines_for_the_Preservation_of_Digital_Scientific_Data_Final.pdf | http://www.digitalpreservation.gov/ndsa/working_groups/documents/USGS_Guidelines_for_the_Preservation_of_Digital_Scientific_Data_Final.pdf | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Development Activity == | == Development Activity == | ||
<!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --> | <!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --> | ||
<!-- Add the OpenHub.com ID for the tool, if known. --> | <!-- Add the OpenHub.com ID for the tool, if known. --> |