<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-GB">
	<id>https://coptr.digipres.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Edpinsent</id>
	<title>COPTR - User contributions [en-gb]</title>
	<link rel="self" type="application/atom+xml" href="https://coptr.digipres.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Edpinsent"/>
	<link rel="alternate" type="text/html" href="https://coptr.digipres.org/Special:Contributions/Edpinsent"/>
	<updated>2026-05-25T04:43:03Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.35.14</generator>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=AOR_(Assessing_Organisational_Readiness)&amp;diff=2706</id>
		<title>AOR (Assessing Organisational Readiness)</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=AOR_(Assessing_Organisational_Readiness)&amp;diff=2706"/>
		<updated>2015-05-20T14:13:44Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Infobox_tool&lt;br /&gt;
|purpose=Assessing Institutional Digital Assets: Self-assessment tool for describing institutional readiness and capabilities for digital asset management and digital preservation&lt;br /&gt;
|homepage=http://aida.jiscinvolve.org/wp/&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add one or more categories to describe the function of the tool, such as:&lt;br /&gt;
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --&amp;gt;&lt;br /&gt;
[[Category:Planning]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add relevant categories to describe the content type that the tool addresses, such as:&lt;br /&gt;
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&amp;lt;!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The AIDA project (2008-2009) aimed to:&lt;br /&gt;
&lt;br /&gt;
* Create a tool, based on a proven model, to enable institutions to perform self-assessment of their readiness for digital asset management and digital preservation&lt;br /&gt;
* Suggest options and strategies for each stage of institutional readiness&lt;br /&gt;
* Provide recommendations on how to improve institutional readiness&lt;br /&gt;
* Produce a decision tool for assessing assets which takes into account institutional readiness&lt;br /&gt;
* Explore decisions relating to preservation options and their effect on costs&lt;br /&gt;
* Provide some indications of the possible costs of digital preservation, based on these outputs&lt;br /&gt;
&lt;br /&gt;
AIDA's approach to building the self-assessment tool is based primarily on the successful Cornell model for describing institutional readiness and capabilities for digital preservation. It is known that the preservation options available to an institution will vary between institutions, due to different states of preparedness between them. The asset management tool will take this into account when recommending options or highlighting threats to assets.&lt;br /&gt;
&lt;br /&gt;
AIDA's approach to asset management will seek to bring together the best elements of the expertise of records managers, librarians, data curators, repository managers and others in developing an institution-wide approach to asset management. The tools, guidance and case studies will help institutions understand how to take small steps forward to improve institutional maturity in regard to digital asset management and preservation concerns.&lt;br /&gt;
&lt;br /&gt;
== User Experiences ==&lt;br /&gt;
&amp;lt;!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[http://www.tandfonline.com/doi/abs/10.1080/0194262X.2012.648098#.VVyWPEbmVCA A review and evaluation of the AIDA toolkit] as used by Los Alamos National Laboratory Research Library, 2012 (NB - behind a paywall).&lt;br /&gt;
&lt;br /&gt;
== Development Activity ==&lt;br /&gt;
&amp;lt;!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Add the OpenHub.com ID for the tool, if known. --&amp;gt;&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|releases_rss=&lt;br /&gt;
|issues_rss=&lt;br /&gt;
|mailing_lists=&lt;br /&gt;
|ohloh_id=&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=SCOUT&amp;diff=2705</id>
		<title>SCOUT</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=SCOUT&amp;diff=2705"/>
		<updated>2015-05-20T14:09:58Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Infobox_tool&lt;br /&gt;
|purpose=A brief description&lt;br /&gt;
|homepage=http://openpreservation.org/knowledge/blogs/2013/12/16/scout-preservation-watch-system/&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add one or more categories to describe the function of the tool, such as:&lt;br /&gt;
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --&amp;gt;&lt;br /&gt;
[[Category:Planning]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add relevant categories to describe the content type that the tool addresses, such as:&lt;br /&gt;
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&amp;lt;!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''General'''&lt;br /&gt;
&lt;br /&gt;
Scout is a preservation watch system developed within the [http://www.scape-project.eu/ SCAPE project]. It provides an ontological knowledge base to centralize all necessary information to detect preservation risks and opportunities. It uses plugins to allow easy integration of new sources of information, as file format registries, tools for characterization, migration and quality assurance, policies, human knowledge and others. The knowledge base can be easily browsed and triggers can be installed to automatically notify users of new risks and opportunities. Examples of such notification could be: content fails to conform to defined policies, a format became obsolete or new tools able to render your content are available.&lt;br /&gt;
&lt;br /&gt;
'''Risk'''&lt;br /&gt;
&lt;br /&gt;
The reason why we should worry about preservation of digital content and why some preservation action needs to be done is closely related to the idea that content is at risk. The risk relates to the potential of losing something of value, weighted against the potential of gaining something of value. In digital preservation, the risk relates to losing long-term and continuous access (or usability) of content by the intended users and it is weighted against the cost (or profit) of maintaining such access. The long-term and continuous aspects of this access mean that there should be a continuous and long-term process that knows when content is misaligned with the requirements of the intended users, and this process is preservation watch.&lt;br /&gt;
&lt;br /&gt;
'''Technology watch'''&lt;br /&gt;
&lt;br /&gt;
In practice preservation watch becomes even more complex as long-term and continuous are many times conflicting requirements. To tackle this, an institution would normally define a &amp;quot;preservation format&amp;quot; which tries to fulfill the long-term access requirement, and create &amp;quot;access&amp;quot; or &amp;quot;dissemination&amp;quot; copies, which are optimized for user community.&lt;br /&gt;
&lt;br /&gt;
Monitoring if content is aligned with the long-term and continuous access requirements, i.e. if selected preservation and access format are still adequate, is a big endeavor that quickly becomes infeasible with large-scale content. Institutions are normally able to tackle the usual suspects, like images and text documents, but are unable to process the long tail of file formats that almost all institutions have.&lt;br /&gt;
&lt;br /&gt;
[[File:V2Nyc6h.png|300px]]&lt;br /&gt;
&lt;br /&gt;
Luis Faria gave a [http://www.slideshare.net/SCAPEproject/webinar-uncovering-preservationrisks SCAPE Webinar] on the Tool in July 2014.&lt;br /&gt;
&lt;br /&gt;
== User Experiences ==&lt;br /&gt;
&amp;lt;!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Development Activity ==&lt;br /&gt;
&amp;lt;!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Add the OpenHub.com ID for the tool, if known. --&amp;gt;&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|releases_rss=&lt;br /&gt;
|issues_rss=&lt;br /&gt;
|mailing_lists=&lt;br /&gt;
|ohloh_id=&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=AOR_(Assessing_Organisational_Readiness)&amp;diff=2704</id>
		<title>AOR (Assessing Organisational Readiness)</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=AOR_(Assessing_Organisational_Readiness)&amp;diff=2704"/>
		<updated>2015-05-20T14:09:02Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Infobox_tool&lt;br /&gt;
|purpose=Assessing Institutional Digital Assets: Self-assessment tool for describing institutional readiness and capabilities for digital asset management and digital preservation&lt;br /&gt;
|homepage=http://aida.jiscinvolve.org/wp/&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add one or more categories to describe the function of the tool, such as:&lt;br /&gt;
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --&amp;gt;&lt;br /&gt;
[[Category:Planning]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add relevant categories to describe the content type that the tool addresses, such as:&lt;br /&gt;
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&amp;lt;!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The AIDA project (2008-2009) aimed to:&lt;br /&gt;
&lt;br /&gt;
* Create a tool, based on a proven model, to enable institutions to perform self-assessment of their readiness for digital asset management and digital preservation&lt;br /&gt;
* Suggest options and strategies for each stage of institutional readiness&lt;br /&gt;
* Provide recommendations on how to improve institutional readiness&lt;br /&gt;
* Produce a decision tool for assessing assets which takes into account institutional readiness&lt;br /&gt;
* Explore decisions relating to preservation options and their effect on costs&lt;br /&gt;
* Provide some indications of the possible costs of digital preservation, based on these outputs&lt;br /&gt;
&lt;br /&gt;
AIDA's approach to building the self-assessment tool is based primarily on the successful Cornell model for describing institutional readiness and capabilities for digital preservation. It is known that the preservation options available to an institution will vary between institutions, due to different states of preparedness between them. The asset management tool will take this into account when recommending options or highlighting threats to assets.&lt;br /&gt;
&lt;br /&gt;
AIDA's approach to asset management will seek to bring together the best elements of the expertise of records managers, librarians, data curators, repository managers and others in developing an institution-wide approach to asset management. The tools, guidance and case studies will help institutions understand how to take small steps forward to improve institutional maturity in regard to digital asset management and preservation concerns.&lt;br /&gt;
&lt;br /&gt;
== User Experiences ==&lt;br /&gt;
&amp;lt;!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Development Activity ==&lt;br /&gt;
&amp;lt;!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Add the OpenHub.com ID for the tool, if known. --&amp;gt;&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|releases_rss=&lt;br /&gt;
|issues_rss=&lt;br /&gt;
|mailing_lists=&lt;br /&gt;
|ohloh_id=&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=AOR_(Assessing_Organisational_Readiness)&amp;diff=2703</id>
		<title>AOR (Assessing Organisational Readiness)</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=AOR_(Assessing_Organisational_Readiness)&amp;diff=2703"/>
		<updated>2015-05-20T14:07:54Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Infobox_tool&lt;br /&gt;
|purpose=Assessing Institutional Digital Assets: Self-assessment tool for describing institutional readiness and capabilities for digital asset management and digital preservation&lt;br /&gt;
|image={{PAGENAMEE}}.png&lt;br /&gt;
|homepage=http://aida.jiscinvolve.org/wp/&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add one or more categories to describe the function of the tool, such as:&lt;br /&gt;
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --&amp;gt;&lt;br /&gt;
[[Category:Planning]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add relevant categories to describe the content type that the tool addresses, such as:&lt;br /&gt;
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&amp;lt;!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The AIDA project (2008-2009) aimed to:&lt;br /&gt;
&lt;br /&gt;
* Create a tool, based on a proven model, to enable institutions to perform self-assessment of their readiness for digital asset management and digital preservation&lt;br /&gt;
* Suggest options and strategies for each stage of institutional readiness&lt;br /&gt;
* Provide recommendations on how to improve institutional readiness&lt;br /&gt;
* Produce a decision tool for assessing assets which takes into account institutional readiness&lt;br /&gt;
* Explore decisions relating to preservation options and their effect on costs&lt;br /&gt;
* Provide some indications of the possible costs of digital preservation, based on these outputs&lt;br /&gt;
&lt;br /&gt;
AIDA's approach to building the self-assessment tool is based primarily on the successful Cornell model for describing institutional readiness and capabilities for digital preservation. It is known that the preservation options available to an institution will vary between institutions, due to different states of preparedness between them. The asset management tool will take this into account when recommending options or highlighting threats to assets.&lt;br /&gt;
&lt;br /&gt;
AIDA's approach to asset management will seek to bring together the best elements of the expertise of records managers, librarians, data curators, repository managers and others in developing an institution-wide approach to asset management. The tools, guidance and case studies will help institutions understand how to take small steps forward to improve institutional maturity in regard to digital asset management and preservation concerns.&lt;br /&gt;
&lt;br /&gt;
== User Experiences ==&lt;br /&gt;
&amp;lt;!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Development Activity ==&lt;br /&gt;
&amp;lt;!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Add the OpenHub.com ID for the tool, if known. --&amp;gt;&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|releases_rss=&lt;br /&gt;
|issues_rss=&lt;br /&gt;
|mailing_lists=&lt;br /&gt;
|ohloh_id=&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=AOR_(Assessing_Organisational_Readiness)&amp;diff=2702</id>
		<title>AOR (Assessing Organisational Readiness)</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=AOR_(Assessing_Organisational_Readiness)&amp;diff=2702"/>
		<updated>2015-05-20T14:06:38Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: Created page with &amp;quot;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;  {{Infobox_tool |purpose=Self-assessment tool for describing institutional readiness and capabilities f...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Infobox_tool&lt;br /&gt;
|purpose=Self-assessment tool for describing institutional readiness and capabilities for digital asset management and digital preservation&lt;br /&gt;
|image={{PAGENAMEE}}.png&lt;br /&gt;
|homepage=http://aida.jiscinvolve.org/wp/&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add one or more categories to describe the function of the tool, such as:&lt;br /&gt;
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add relevant categories to describe the content type that the tool addresses, such as:&lt;br /&gt;
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --&amp;gt;&lt;br /&gt;
[[Category:Planning]] &lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&amp;lt;!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The AIDA project (2008-2009) aimed to:&lt;br /&gt;
&lt;br /&gt;
* Create a tool, based on a proven model, to enable institutions to perform self-assessment of their readiness for digital asset management and digital preservation&lt;br /&gt;
* Suggest options and strategies for each stage of institutional readiness&lt;br /&gt;
* Provide recommendations on how to improve institutional readiness&lt;br /&gt;
* Produce a decision tool for assessing assets which takes into account institutional readiness&lt;br /&gt;
* Explore decisions relating to preservation options and their effect on costs&lt;br /&gt;
* Provide some indications of the possible costs of digital preservation, based on these outputs&lt;br /&gt;
&lt;br /&gt;
AIDA's approach to building the self-assessment tool is based primarily on the successful Cornell model for describing institutional readiness and capabilities for digital preservation. It is known that the preservation options available to an institution will vary between institutions, due to different states of preparedness between them. The asset management tool will take this into account when recommending options or highlighting threats to assets.&lt;br /&gt;
&lt;br /&gt;
AIDA's approach to asset management will seek to bring together the best elements of the expertise of records managers, librarians, data curators, repository managers and others in developing an institution-wide approach to asset management. The tools, guidance and case studies will help institutions understand how to take small steps forward to improve institutional maturity in regard to digital asset management and preservation concerns.&lt;br /&gt;
&lt;br /&gt;
== User Experiences ==&lt;br /&gt;
&amp;lt;!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Development Activity ==&lt;br /&gt;
&amp;lt;!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Add the OpenHub.com ID for the tool, if known. --&amp;gt;&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|releases_rss=&lt;br /&gt;
|issues_rss=&lt;br /&gt;
|mailing_lists=&lt;br /&gt;
|ohloh_id=&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=SCOUT&amp;diff=2701</id>
		<title>SCOUT</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=SCOUT&amp;diff=2701"/>
		<updated>2015-05-20T13:53:10Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Infobox_tool&lt;br /&gt;
|purpose=A brief description&lt;br /&gt;
|homepage=http://openpreservation.org/knowledge/blogs/2013/12/16/scout-preservation-watch-system/&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add one or more categories to describe the function of the tool, such as:&lt;br /&gt;
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add relevant categories to describe the content type that the tool addresses, such as:&lt;br /&gt;
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --&amp;gt;&lt;br /&gt;
[[Category:Planning]]&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&amp;lt;!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''General'''&lt;br /&gt;
&lt;br /&gt;
Scout is a preservation watch system developed within the [http://www.scape-project.eu/ SCAPE project]. It provides an ontological knowledge base to centralize all necessary information to detect preservation risks and opportunities. It uses plugins to allow easy integration of new sources of information, as file format registries, tools for characterization, migration and quality assurance, policies, human knowledge and others. The knowledge base can be easily browsed and triggers can be installed to automatically notify users of new risks and opportunities. Examples of such notification could be: content fails to conform to defined policies, a format became obsolete or new tools able to render your content are available.&lt;br /&gt;
&lt;br /&gt;
'''Risk'''&lt;br /&gt;
&lt;br /&gt;
The reason why we should worry about preservation of digital content and why some preservation action needs to be done is closely related to the idea that content is at risk. The risk relates to the potential of losing something of value, weighted against the potential of gaining something of value. In digital preservation, the risk relates to losing long-term and continuous access (or usability) of content by the intended users and it is weighted against the cost (or profit) of maintaining such access. The long-term and continuous aspects of this access mean that there should be a continuous and long-term process that knows when content is misaligned with the requirements of the intended users, and this process is preservation watch.&lt;br /&gt;
&lt;br /&gt;
'''Technology watch'''&lt;br /&gt;
&lt;br /&gt;
In practice preservation watch becomes even more complex as long-term and continuous are many times conflicting requirements. To tackle this, an institution would normally define a &amp;quot;preservation format&amp;quot; which tries to fulfill the long-term access requirement, and create &amp;quot;access&amp;quot; or &amp;quot;dissemination&amp;quot; copies, which are optimized for user community.&lt;br /&gt;
&lt;br /&gt;
Monitoring if content is aligned with the long-term and continuous access requirements, i.e. if selected preservation and access format are still adequate, is a big endeavor that quickly becomes infeasible with large-scale content. Institutions are normally able to tackle the usual suspects, like images and text documents, but are unable to process the long tail of file formats that almost all institutions have.&lt;br /&gt;
&lt;br /&gt;
[[File:V2Nyc6h.png|300px]]&lt;br /&gt;
&lt;br /&gt;
Luis Faria gave a [http://www.slideshare.net/SCAPEproject/webinar-uncovering-preservationrisks SCAPE Webinar] on the Tool in July 2014.&lt;br /&gt;
&lt;br /&gt;
== User Experiences ==&lt;br /&gt;
&amp;lt;!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Development Activity ==&lt;br /&gt;
&amp;lt;!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Add the OpenHub.com ID for the tool, if known. --&amp;gt;&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|releases_rss=&lt;br /&gt;
|issues_rss=&lt;br /&gt;
|mailing_lists=&lt;br /&gt;
|ohloh_id=&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=SCOUT&amp;diff=2700</id>
		<title>SCOUT</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=SCOUT&amp;diff=2700"/>
		<updated>2015-05-20T13:52:02Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Infobox_tool&lt;br /&gt;
|purpose=A brief description&lt;br /&gt;
|homepage=http://openpreservation.org/knowledge/blogs/2013/12/16/scout-preservation-watch-system/&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add one or more categories to describe the function of the tool, such as:&lt;br /&gt;
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add relevant categories to describe the content type that the tool addresses, such as:&lt;br /&gt;
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --&amp;gt;&lt;br /&gt;
[[Category:Planning]]&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&amp;lt;!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''General'''&lt;br /&gt;
&lt;br /&gt;
Scout is a preservation watch system developed within the [http://www.scape-project.eu/ SCAPE project]. It provides an ontological knowledge base to centralize all necessary information to detect preservation risks and opportunities. It uses plugins to allow easy integration of new sources of information, as file format registries, tools for characterization, migration and quality assurance, policies, human knowledge and others. The knowledge base can be easily browsed and triggers can be installed to automatically notify users of new risks and opportunities. Examples of such notification could be: content fails to conform to defined policies, a format became obsolete or new tools able to render your content are available.&lt;br /&gt;
&lt;br /&gt;
'''Risk'''&lt;br /&gt;
&lt;br /&gt;
The reason why we should worry about preservation of digital content and why some preservation action needs to be done is closely related to the idea that content is at risk. The risk relates to the potential of losing something of value, weighted against the potential of gaining something of value. In digital preservation, the risk relates to losing long-term and continuous access (or usability) of content by the intended users and it is weighted against the cost (or profit) of maintaining such access. The long-term and continuous aspects of this access mean that there should be a continuous and long-term process that knows when content is misaligned with the requirements of the intended users, and this process is preservation watch.&lt;br /&gt;
&lt;br /&gt;
'''Technology watch'''&lt;br /&gt;
&lt;br /&gt;
In practice preservation watch becomes even more complex as long-term and continuous are many times conflicting requirements. To tackle this, an institution would normally define a &amp;quot;preservation format&amp;quot; which tries to fulfill the long-term access requirement, and create &amp;quot;access&amp;quot; or &amp;quot;dissemination&amp;quot; copies, which are optimized for user community.&lt;br /&gt;
&lt;br /&gt;
Monitoring if content is aligned with the long-term and continuous access requirements, i.e. if selected preservation and access format are still adequate, is a big endeavor that quickly becomes infeasible with large-scale content. Institutions are normally able to tackle the usual suspects, like images and text documents, but are unable to process the long tail of file formats that almost all institutions have.&lt;br /&gt;
&lt;br /&gt;
[[File:V2Nyc6h.png]]&lt;br /&gt;
&lt;br /&gt;
Luis Faria gave a [http://www.slideshare.net/SCAPEproject/webinar-uncovering-preservationrisks SCAPE Webinar] on the Tool in July 2014.&lt;br /&gt;
&lt;br /&gt;
== User Experiences ==&lt;br /&gt;
&amp;lt;!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Development Activity ==&lt;br /&gt;
&amp;lt;!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Add the OpenHub.com ID for the tool, if known. --&amp;gt;&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|releases_rss=&lt;br /&gt;
|issues_rss=&lt;br /&gt;
|mailing_lists=&lt;br /&gt;
|ohloh_id=&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=SCOUT&amp;diff=2699</id>
		<title>SCOUT</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=SCOUT&amp;diff=2699"/>
		<updated>2015-05-20T13:46:44Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: /* Description */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Infobox_tool&lt;br /&gt;
|purpose=A brief description&lt;br /&gt;
|homepage=http://openpreservation.org/knowledge/blogs/2013/12/16/scout-preservation-watch-system/&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add one or more categories to describe the function of the tool, such as:&lt;br /&gt;
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add relevant categories to describe the content type that the tool addresses, such as:&lt;br /&gt;
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --&amp;gt;&lt;br /&gt;
[[Category:Planning]]&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&amp;lt;!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''General'''&lt;br /&gt;
&lt;br /&gt;
Scout is a preservation watch system being developed within the SCAPE project. It provides an ontological knowledge base to centralize all necessary information to detect preservation risks and opportunities. It uses plugins to allow easy integration of new sources of information, as file format registries, tools for characterization, migration and quality assurance, policies, human knowledge and others. The knowledge base can be easily browsed and triggers can be installed to automatically notify users of new risks and opportunities. Examples of such notification could be: content fails to conform to defined policies, a format became obsolete or new tools able to render your content are available.&lt;br /&gt;
&lt;br /&gt;
'''Risk'''&lt;br /&gt;
&lt;br /&gt;
The reason why we should worry about preservation of digital content and why some preservation action needs to be done is closely related to the idea that content is at risk. The risk relates to the potential of losing something of value, weighted against the potential of gaining something of value. In digital preservation, the risk relates to losing long-term and continuous access (or usability) of content by the intended users and it is weighted against the cost (or profit) of maintaining such access. The long-term and continuous aspects of this access mean that there should be a continuous and long-term process that knows when content is misaligned with the requirements of the intended users, and this process is preservation watch.&lt;br /&gt;
&lt;br /&gt;
'''Technology watch'''&lt;br /&gt;
&lt;br /&gt;
In practice preservation watch becomes even more complex as long-term and continuous are many times conflicting requirements. To tackle this, an institution would normally define a &amp;quot;preservation format&amp;quot; which tries to fulfill the long-term access requirement, and create &amp;quot;access&amp;quot; or &amp;quot;dissemination&amp;quot; copies, which are optimized for user community.&lt;br /&gt;
&lt;br /&gt;
Monitoring if content is aligned with the long-term and continuous access requirements, i.e. if selected preservation and access format are still adequate, is a big endeavor that quickly becomes infeasible with large-scale content. Institutions are normally able to tackle the usual suspects, like images and text documents, but are unable to process the long tail of file formats that almost all institutions have.&lt;br /&gt;
&lt;br /&gt;
[[File:V2Nyc6h.png]]&lt;br /&gt;
&lt;br /&gt;
== User Experiences ==&lt;br /&gt;
&amp;lt;!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Development Activity ==&lt;br /&gt;
&amp;lt;!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Add the OpenHub.com ID for the tool, if known. --&amp;gt;&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|releases_rss=&lt;br /&gt;
|issues_rss=&lt;br /&gt;
|mailing_lists=&lt;br /&gt;
|ohloh_id=&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=SCOUT&amp;diff=2698</id>
		<title>SCOUT</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=SCOUT&amp;diff=2698"/>
		<updated>2015-05-20T13:46:23Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Infobox_tool&lt;br /&gt;
|purpose=A brief description&lt;br /&gt;
|homepage=http://openpreservation.org/knowledge/blogs/2013/12/16/scout-preservation-watch-system/&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add one or more categories to describe the function of the tool, such as:&lt;br /&gt;
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add relevant categories to describe the content type that the tool addresses, such as:&lt;br /&gt;
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --&amp;gt;&lt;br /&gt;
[[Category:Planning]]&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&amp;lt;!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''General'''&lt;br /&gt;
&lt;br /&gt;
Scout is a preservation watch system being developed within the SCAPE project. It provides an ontological knowledge base to centralize all necessary information to detect preservation risks and opportunities. It uses plugins to allow easy integration of new sources of information, as file format registries, tools for characterization, migration and quality assurance, policies, human knowledge and others. The knowledge base can be easily browsed and triggers can be installed to automatically notify users of new risks and opportunities. Examples of such notification could be: content fails to conform to defined policies, a format became obsolete or new tools able to render your content are available.&lt;br /&gt;
&lt;br /&gt;
'''Risk'''&lt;br /&gt;
&lt;br /&gt;
The reason why we should worry about preservation of digital content and why some preservation action needs to be done is closely related to the idea that content is at risk. The risk relates to the potential of losing something of value, weighted against the potential of gaining something of value. In digital preservation, the risk relates to losing long-term and continuous access (or usability) of content by the intended users and it is weighted against the cost (or profit) of maintaining such access. The long-term and continuous aspects of this access mean that there should be a continuous and long-term process that knows when content is misaligned with the requirements of the intended users, and this process is preservation watch.&lt;br /&gt;
&lt;br /&gt;
'''Technology watch'''&lt;br /&gt;
&lt;br /&gt;
In practice preservation watch becomes even more complex as long-term and continuous are many times conflicting requirements. To tackle this, an institution would normally define a &amp;quot;preservation format&amp;quot; which tries to fulfill the long-term access requirement, and create &amp;quot;access&amp;quot; or &amp;quot;dissemination&amp;quot; copies, which are optimized for user community.&lt;br /&gt;
&lt;br /&gt;
Monitoring if content is aligned with the long-term and continuous access requirements, i.e. if selected preservation and access format are still adequate, is a big endeavor that quickly becomes infeasible with large-scale content. Institutions are normally able to tackle the usual suspects, like images and text documents, but are unable to process the long tail of file formats that almost all institutions have.&lt;br /&gt;
&lt;br /&gt;
[[File:File:V2Nyc6h.png]]&lt;br /&gt;
&lt;br /&gt;
== User Experiences ==&lt;br /&gt;
&amp;lt;!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Development Activity ==&lt;br /&gt;
&amp;lt;!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Add the OpenHub.com ID for the tool, if known. --&amp;gt;&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|releases_rss=&lt;br /&gt;
|issues_rss=&lt;br /&gt;
|mailing_lists=&lt;br /&gt;
|ohloh_id=&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=SCOUT&amp;diff=2697</id>
		<title>SCOUT</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=SCOUT&amp;diff=2697"/>
		<updated>2015-05-20T13:44:34Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Infobox_tool&lt;br /&gt;
|purpose=A brief description&lt;br /&gt;
|image={{File:V2Nyc6h.png}}&lt;br /&gt;
|homepage=http://openpreservation.org/knowledge/blogs/2013/12/16/scout-preservation-watch-system/&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add one or more categories to describe the function of the tool, such as:&lt;br /&gt;
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add relevant categories to describe the content type that the tool addresses, such as:&lt;br /&gt;
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --&amp;gt;&lt;br /&gt;
[[Category:Planning]]&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&amp;lt;!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''General'''&lt;br /&gt;
&lt;br /&gt;
Scout is a preservation watch system being developed within the SCAPE project. It provides an ontological knowledge base to centralize all necessary information to detect preservation risks and opportunities. It uses plugins to allow easy integration of new sources of information, as file format registries, tools for characterization, migration and quality assurance, policies, human knowledge and others. The knowledge base can be easily browsed and triggers can be installed to automatically notify users of new risks and opportunities. Examples of such notification could be: content fails to conform to defined policies, a format became obsolete or new tools able to render your content are available.&lt;br /&gt;
&lt;br /&gt;
'''Risk'''&lt;br /&gt;
&lt;br /&gt;
The reason why we should worry about preservation of digital content and why some preservation action needs to be done is closely related to the idea that content is at risk. The risk relates to the potential of losing something of value, weighted against the potential of gaining something of value. In digital preservation, the risk relates to losing long-term and continuous access (or usability) of content by the intended users and it is weighted against the cost (or profit) of maintaining such access. The long-term and continuous aspects of this access mean that there should be a continuous and long-term process that knows when content is misaligned with the requirements of the intended users, and this process is preservation watch.&lt;br /&gt;
&lt;br /&gt;
'''Technology watch'''&lt;br /&gt;
&lt;br /&gt;
In practice preservation watch becomes even more complex as long-term and continuous are many times conflicting requirements. To tackle this, an institution would normally define a &amp;quot;preservation format&amp;quot; which tries to fulfill the long-term access requirement, and create &amp;quot;access&amp;quot; or &amp;quot;dissemination&amp;quot; copies, which are optimized for user community.&lt;br /&gt;
&lt;br /&gt;
Monitoring if content is aligned with the long-term and continuous access requirements, i.e. if selected preservation and access format are still adequate, is a big endeavor that quickly becomes infeasible with large-scale content. Institutions are normally able to tackle the usual suspects, like images and text documents, but are unable to process the long tail of file formats that almost all institutions have.&lt;br /&gt;
&lt;br /&gt;
== User Experiences ==&lt;br /&gt;
&amp;lt;!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Development Activity ==&lt;br /&gt;
&amp;lt;!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Add the OpenHub.com ID for the tool, if known. --&amp;gt;&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|releases_rss=&lt;br /&gt;
|issues_rss=&lt;br /&gt;
|mailing_lists=&lt;br /&gt;
|ohloh_id=&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=SCOUT&amp;diff=2696</id>
		<title>SCOUT</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=SCOUT&amp;diff=2696"/>
		<updated>2015-05-20T13:43:46Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Infobox_tool&lt;br /&gt;
|purpose=A brief description&lt;br /&gt;
|image={{File:V2Nyc6h}}.png&lt;br /&gt;
|homepage=http://openpreservation.org/knowledge/blogs/2013/12/16/scout-preservation-watch-system/&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add one or more categories to describe the function of the tool, such as:&lt;br /&gt;
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add relevant categories to describe the content type that the tool addresses, such as:&lt;br /&gt;
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --&amp;gt;&lt;br /&gt;
[[Category:Planning]]&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&amp;lt;!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''General'''&lt;br /&gt;
&lt;br /&gt;
Scout is a preservation watch system being developed within the SCAPE project. It provides an ontological knowledge base to centralize all necessary information to detect preservation risks and opportunities. It uses plugins to allow easy integration of new sources of information, as file format registries, tools for characterization, migration and quality assurance, policies, human knowledge and others. The knowledge base can be easily browsed and triggers can be installed to automatically notify users of new risks and opportunities. Examples of such notification could be: content fails to conform to defined policies, a format became obsolete or new tools able to render your content are available.&lt;br /&gt;
&lt;br /&gt;
'''Risk'''&lt;br /&gt;
&lt;br /&gt;
The reason why we should worry about preservation of digital content and why some preservation action needs to be done is closely related to the idea that content is at risk. The risk relates to the potential of losing something of value, weighted against the potential of gaining something of value. In digital preservation, the risk relates to losing long-term and continuous access (or usability) of content by the intended users and it is weighted against the cost (or profit) of maintaining such access. The long-term and continuous aspects of this access mean that there should be a continuous and long-term process that knows when content is misaligned with the requirements of the intended users, and this process is preservation watch.&lt;br /&gt;
&lt;br /&gt;
'''Technology watch'''&lt;br /&gt;
&lt;br /&gt;
In practice preservation watch becomes even more complex as long-term and continuous are many times conflicting requirements. To tackle this, an institution would normally define a &amp;quot;preservation format&amp;quot; which tries to fulfill the long-term access requirement, and create &amp;quot;access&amp;quot; or &amp;quot;dissemination&amp;quot; copies, which are optimized for user community.&lt;br /&gt;
&lt;br /&gt;
Monitoring if content is aligned with the long-term and continuous access requirements, i.e. if selected preservation and access format are still adequate, is a big endeavor that quickly becomes infeasible with large-scale content. Institutions are normally able to tackle the usual suspects, like images and text documents, but are unable to process the long tail of file formats that almost all institutions have.&lt;br /&gt;
&lt;br /&gt;
== User Experiences ==&lt;br /&gt;
&amp;lt;!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Development Activity ==&lt;br /&gt;
&amp;lt;!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Add the OpenHub.com ID for the tool, if known. --&amp;gt;&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|releases_rss=&lt;br /&gt;
|issues_rss=&lt;br /&gt;
|mailing_lists=&lt;br /&gt;
|ohloh_id=&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=SCOUT&amp;diff=2695</id>
		<title>SCOUT</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=SCOUT&amp;diff=2695"/>
		<updated>2015-05-20T13:43:16Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: Created page with &amp;quot;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;  {{Infobox_tool |purpose=A brief description |image={{V2Nyc6h}}.png |homepage=http://openpreservation.o...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Infobox_tool&lt;br /&gt;
|purpose=A brief description&lt;br /&gt;
|image={{V2Nyc6h}}.png&lt;br /&gt;
|homepage=http://openpreservation.org/knowledge/blogs/2013/12/16/scout-preservation-watch-system/&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add one or more categories to describe the function of the tool, such as:&lt;br /&gt;
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add relevant categories to describe the content type that the tool addresses, such as:&lt;br /&gt;
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --&amp;gt;&lt;br /&gt;
[[Category:Planning]]&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&amp;lt;!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''General'''&lt;br /&gt;
&lt;br /&gt;
Scout is a preservation watch system being developed within the SCAPE project. It provides an ontological knowledge base to centralize all necessary information to detect preservation risks and opportunities. It uses plugins to allow easy integration of new sources of information, as file format registries, tools for characterization, migration and quality assurance, policies, human knowledge and others. The knowledge base can be easily browsed and triggers can be installed to automatically notify users of new risks and opportunities. Examples of such notification could be: content fails to conform to defined policies, a format became obsolete or new tools able to render your content are available.&lt;br /&gt;
&lt;br /&gt;
'''Risk'''&lt;br /&gt;
&lt;br /&gt;
The reason why we should worry about preservation of digital content and why some preservation action needs to be done is closely related to the idea that content is at risk. The risk relates to the potential of losing something of value, weighted against the potential of gaining something of value. In digital preservation, the risk relates to losing long-term and continuous access (or usability) of content by the intended users and it is weighted against the cost (or profit) of maintaining such access. The long-term and continuous aspects of this access mean that there should be a continuous and long-term process that knows when content is misaligned with the requirements of the intended users, and this process is preservation watch.&lt;br /&gt;
&lt;br /&gt;
'''Technology watch'''&lt;br /&gt;
&lt;br /&gt;
In practice preservation watch becomes even more complex as long-term and continuous are many times conflicting requirements. To tackle this, an institution would normally define a &amp;quot;preservation format&amp;quot; which tries to fulfill the long-term access requirement, and create &amp;quot;access&amp;quot; or &amp;quot;dissemination&amp;quot; copies, which are optimized for user community.&lt;br /&gt;
&lt;br /&gt;
Monitoring if content is aligned with the long-term and continuous access requirements, i.e. if selected preservation and access format are still adequate, is a big endeavor that quickly becomes infeasible with large-scale content. Institutions are normally able to tackle the usual suspects, like images and text documents, but are unable to process the long tail of file formats that almost all institutions have.&lt;br /&gt;
&lt;br /&gt;
== User Experiences ==&lt;br /&gt;
&amp;lt;!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Development Activity ==&lt;br /&gt;
&amp;lt;!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Add the OpenHub.com ID for the tool, if known. --&amp;gt;&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|releases_rss=&lt;br /&gt;
|issues_rss=&lt;br /&gt;
|mailing_lists=&lt;br /&gt;
|ohloh_id=&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=File:V2Nyc6h.png&amp;diff=2694</id>
		<title>File:V2Nyc6h.png</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=File:V2Nyc6h.png&amp;diff=2694"/>
		<updated>2015-05-20T13:42:50Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=DRAMBORA&amp;diff=2693</id>
		<title>DRAMBORA</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=DRAMBORA&amp;diff=2693"/>
		<updated>2015-05-20T13:29:53Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox_tool&lt;br /&gt;
|purpose=DRAMBORA offers a quantifiable insight into the severity of risks faced by repositories right now, and an effective means for reporting these.&lt;br /&gt;
|image=&lt;br /&gt;
|homepage=http://www.repositoryaudit.eu/&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Delete the Categories that do not apply --&amp;gt;&lt;br /&gt;
[[Category:Organisational Audit]]&lt;br /&gt;
[[Category:Planning]]&lt;br /&gt;
&lt;br /&gt;
= Description =&lt;br /&gt;
DRAMBORA (Digital Repository Audit Method Based On Risk Assessment) originated as a paper-based methodology for helping repository managers to develop a documented understanding of the risks they face, expressed in terms of probability and potential impact. These risks are then mapped to organisational aspirations and effort allocations in order to facilitate ongoing organisational development and resource allocation. In short, DRAMBORA offers a quantifiable insight into the severity of risks faced by repositories right now, and an effective means for reporting these.&lt;br /&gt;
====Using DRAMBORA====&lt;br /&gt;
The best and most efficient way of carrying out a DRAMBORA audit is by using DRAMBORA Interactive, an online tool which guides you through the audit process on a step-by-step basis. DRAMBORA Interactive provides a host of real-world risk exemplars which you can use or modify for your own repository&amp;amp;#39;s circumstances. Finally, DRAMBORA Interactive&amp;amp;#39;s powerful reporting functionality enables you to export your risk register in a variety of formats, providing a powerful business case for increasing the security and stability of your repository.&lt;br /&gt;
====Benefits of DRAMBORA====&lt;br /&gt;
Carrying out a DRAMBORA audit helps provide peace of mind with regard to growing, valuable and at-risk digital collections. It can strengthen the trust of users and staff, increase efficiency by helping to focus and refine operational policies, and may even highlight potential opportunities for repository managers to leverage increased development potential by offering a clear way to demonstrate the risks related to shortfalls in repository funding.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= User Experiences =&lt;br /&gt;
&lt;br /&gt;
OhioLINK engaged in an audit process using DRAMBORA to assess whether they could claim to be trustworthy. See &amp;quot;Planning a digital preservation assessment using TRAC:CC and DRAMBORA&amp;quot; (2007)&lt;br /&gt;
&lt;br /&gt;
http://dltj.org/article/trac-and-drambora/&lt;br /&gt;
&lt;br /&gt;
Examined by the ECrystals project in 2009, who concluded &amp;quot;DRAMBORA takes a more quantified approach to assessing repositories and would therefore work best for an established repository looking for self-assessment.&amp;quot; See ''Preservation Planning for&lt;br /&gt;
Crystallography Data'': JISC eCrystals Federation Project (2009)&lt;br /&gt;
&lt;br /&gt;
http://opus.bath.ac.uk/21536/1/ECrystals-WP4-PP-090625.pdf&lt;br /&gt;
&lt;br /&gt;
The Southampton KeepIt Course assessed the use of DRAMBORA in the context of preserving research data. (2010)&lt;br /&gt;
&lt;br /&gt;
http://blog.soton.ac.uk/keepit/tag/drambora/&lt;br /&gt;
&lt;br /&gt;
= Development Activity =&lt;br /&gt;
&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|ohloh_id=DRAMBORA&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=DRAMBORA&amp;diff=2692</id>
		<title>DRAMBORA</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=DRAMBORA&amp;diff=2692"/>
		<updated>2015-05-20T13:28:22Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: /* User Experiences */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox_tool&lt;br /&gt;
|purpose=DRAMBORA offers a quantifiable insight into the severity of risks faced by repositories right now, and an effective means for reporting these.&lt;br /&gt;
|image=&lt;br /&gt;
|homepage=http://www.repositoryaudit.eu/&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Delete the Categories that do not apply --&amp;gt;&lt;br /&gt;
[[Category:Organisational Audit]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Description =&lt;br /&gt;
DRAMBORA (Digital Repository Audit Method Based On Risk Assessment) originated as a paper-based methodology for helping repository managers to develop a documented understanding of the risks they face, expressed in terms of probability and potential impact. These risks are then mapped to organisational aspirations and effort allocations in order to facilitate ongoing organisational development and resource allocation. In short, DRAMBORA offers a quantifiable insight into the severity of risks faced by repositories right now, and an effective means for reporting these.&lt;br /&gt;
====Using DRAMBORA====&lt;br /&gt;
The best and most efficient way of carrying out a DRAMBORA audit is by using DRAMBORA Interactive, an online tool which guides you through the audit process on a step-by-step basis. DRAMBORA Interactive provides a host of real-world risk exemplars which you can use or modify for your own repository&amp;amp;#39;s circumstances. Finally, DRAMBORA Interactive&amp;amp;#39;s powerful reporting functionality enables you to export your risk register in a variety of formats, providing a powerful business case for increasing the security and stability of your repository.&lt;br /&gt;
====Benefits of DRAMBORA====&lt;br /&gt;
Carrying out a DRAMBORA audit helps provide peace of mind with regard to growing, valuable and at-risk digital collections. It can strengthen the trust of users and staff, increase efficiency by helping to focus and refine operational policies, and may even highlight potential opportunities for repository managers to leverage increased development potential by offering a clear way to demonstrate the risks related to shortfalls in repository funding.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= User Experiences =&lt;br /&gt;
&lt;br /&gt;
OhioLINK engaged in an audit process using DRAMBORA to assess whether they could claim to be trustworthy. See &amp;quot;Planning a digital preservation assessment using TRAC:CC and DRAMBORA&amp;quot; (2007)&lt;br /&gt;
&lt;br /&gt;
http://dltj.org/article/trac-and-drambora/&lt;br /&gt;
&lt;br /&gt;
Examined by the ECrystals project in 2009, who concluded &amp;quot;DRAMBORA takes a more quantified approach to assessing repositories and would therefore work best for an established repository looking for self-assessment.&amp;quot; See ''Preservation Planning for&lt;br /&gt;
Crystallography Data'': JISC eCrystals Federation Project (2009)&lt;br /&gt;
&lt;br /&gt;
http://opus.bath.ac.uk/21536/1/ECrystals-WP4-PP-090625.pdf&lt;br /&gt;
&lt;br /&gt;
The Southampton KeepIt Course assessed the use of DRAMBORA in the context of preserving research data. (2010)&lt;br /&gt;
&lt;br /&gt;
http://blog.soton.ac.uk/keepit/tag/drambora/&lt;br /&gt;
&lt;br /&gt;
= Development Activity =&lt;br /&gt;
&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|ohloh_id=DRAMBORA&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=DRAMBORA&amp;diff=2691</id>
		<title>DRAMBORA</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=DRAMBORA&amp;diff=2691"/>
		<updated>2015-05-20T13:24:01Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: /* User Experiences */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox_tool&lt;br /&gt;
|purpose=DRAMBORA offers a quantifiable insight into the severity of risks faced by repositories right now, and an effective means for reporting these.&lt;br /&gt;
|image=&lt;br /&gt;
|homepage=http://www.repositoryaudit.eu/&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Delete the Categories that do not apply --&amp;gt;&lt;br /&gt;
[[Category:Organisational Audit]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Description =&lt;br /&gt;
DRAMBORA (Digital Repository Audit Method Based On Risk Assessment) originated as a paper-based methodology for helping repository managers to develop a documented understanding of the risks they face, expressed in terms of probability and potential impact. These risks are then mapped to organisational aspirations and effort allocations in order to facilitate ongoing organisational development and resource allocation. In short, DRAMBORA offers a quantifiable insight into the severity of risks faced by repositories right now, and an effective means for reporting these.&lt;br /&gt;
====Using DRAMBORA====&lt;br /&gt;
The best and most efficient way of carrying out a DRAMBORA audit is by using DRAMBORA Interactive, an online tool which guides you through the audit process on a step-by-step basis. DRAMBORA Interactive provides a host of real-world risk exemplars which you can use or modify for your own repository&amp;amp;#39;s circumstances. Finally, DRAMBORA Interactive&amp;amp;#39;s powerful reporting functionality enables you to export your risk register in a variety of formats, providing a powerful business case for increasing the security and stability of your repository.&lt;br /&gt;
====Benefits of DRAMBORA====&lt;br /&gt;
Carrying out a DRAMBORA audit helps provide peace of mind with regard to growing, valuable and at-risk digital collections. It can strengthen the trust of users and staff, increase efficiency by helping to focus and refine operational policies, and may even highlight potential opportunities for repository managers to leverage increased development potential by offering a clear way to demonstrate the risks related to shortfalls in repository funding.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= User Experiences =&lt;br /&gt;
&lt;br /&gt;
OhioLINK engaged in an audit process using DRAMBORA to assess whether they could claim to be trustworthy. See &amp;quot;Planning a digital preservation assessment using TRAC:CC and DRAMBORA&amp;quot; (2007)&lt;br /&gt;
&lt;br /&gt;
http://dltj.org/article/trac-and-drambora/&lt;br /&gt;
&lt;br /&gt;
The Southampton KeepIt Course assessed the use of DRAMBORA in the context of preserving research data. (2010)&lt;br /&gt;
&lt;br /&gt;
http://blog.soton.ac.uk/keepit/tag/drambora/&lt;br /&gt;
&lt;br /&gt;
= Development Activity =&lt;br /&gt;
&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|ohloh_id=DRAMBORA&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=DRAMBORA&amp;diff=2690</id>
		<title>DRAMBORA</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=DRAMBORA&amp;diff=2690"/>
		<updated>2015-05-20T13:22:28Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: /* User Experiences */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox_tool&lt;br /&gt;
|purpose=DRAMBORA offers a quantifiable insight into the severity of risks faced by repositories right now, and an effective means for reporting these.&lt;br /&gt;
|image=&lt;br /&gt;
|homepage=http://www.repositoryaudit.eu/&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Delete the Categories that do not apply --&amp;gt;&lt;br /&gt;
[[Category:Organisational Audit]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Description =&lt;br /&gt;
DRAMBORA (Digital Repository Audit Method Based On Risk Assessment) originated as a paper-based methodology for helping repository managers to develop a documented understanding of the risks they face, expressed in terms of probability and potential impact. These risks are then mapped to organisational aspirations and effort allocations in order to facilitate ongoing organisational development and resource allocation. In short, DRAMBORA offers a quantifiable insight into the severity of risks faced by repositories right now, and an effective means for reporting these.&lt;br /&gt;
====Using DRAMBORA====&lt;br /&gt;
The best and most efficient way of carrying out a DRAMBORA audit is by using DRAMBORA Interactive, an online tool which guides you through the audit process on a step-by-step basis. DRAMBORA Interactive provides a host of real-world risk exemplars which you can use or modify for your own repository&amp;amp;#39;s circumstances. Finally, DRAMBORA Interactive&amp;amp;#39;s powerful reporting functionality enables you to export your risk register in a variety of formats, providing a powerful business case for increasing the security and stability of your repository.&lt;br /&gt;
====Benefits of DRAMBORA====&lt;br /&gt;
Carrying out a DRAMBORA audit helps provide peace of mind with regard to growing, valuable and at-risk digital collections. It can strengthen the trust of users and staff, increase efficiency by helping to focus and refine operational policies, and may even highlight potential opportunities for repository managers to leverage increased development potential by offering a clear way to demonstrate the risks related to shortfalls in repository funding.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= User Experiences =&lt;br /&gt;
&lt;br /&gt;
OhioLINK engaged in an audit process using DRAMBORA to assess whether they could claim to be trustworthy. See &amp;quot;Planning a digital preservation assessment using TRAC:CC and DRAMBORA&amp;quot; (2007)&lt;br /&gt;
&lt;br /&gt;
http://dltj.org/article/trac-and-drambora/&lt;br /&gt;
&lt;br /&gt;
= Development Activity =&lt;br /&gt;
&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|ohloh_id=DRAMBORA&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=NDSA_Levels_of_Preservation&amp;diff=2689</id>
		<title>NDSA Levels of Preservation</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=NDSA_Levels_of_Preservation&amp;diff=2689"/>
		<updated>2015-05-20T13:15:34Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;&lt;br /&gt;
{{Infobox_tool&lt;br /&gt;
|purpose=The &amp;quot;Levels of Digital Preservation&amp;quot; are a tiered set of recommendations for how organizations should begin to build or enhance their digital preservation activities.&lt;br /&gt;
|image=&lt;br /&gt;
|homepage=http://www.digitalpreservation.gov/ndsa/activities/levels.html&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add one or more categories to describe the function of the tool, such as:&lt;br /&gt;
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add relevant categories to describe the content type that the tool addresses, such as:&lt;br /&gt;
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --&amp;gt;&lt;br /&gt;
[[Category:Planning]]&lt;br /&gt;
[[Category:Organisational_Audit]]&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&amp;lt;!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --&amp;gt;&lt;br /&gt;
A work in progress by the NDSA, it is intended to be a relatively easy-to-use set of guidelines useful not only for those just beginning to think about preserving their digital assets, but also for institutions planning the next steps in enhancing their existing digital preservation systems and workflows. It allows institutions to assess the level of preservation achieved for specific materials in their custody, or their entire preservation infrastructure. It is not designed to assess the robustness of digital preservation programs as a whole since it does not cover such things as policies, staffing, or organizational support. The guidelines are organized into five functional areas that are at the heart of digital preservation systems: storage and geographic location, file fixity and data integrity, information security, metadata, and file formats.&lt;br /&gt;
&lt;br /&gt;
It is expected that the Levels of Digital Preservation will be updated over time as additional feedback is received, experience is gained implementing its recommendations and as empirical research provides detailed information about data loss. For this reason, each iteration of the Levels will be versioned.&lt;br /&gt;
&lt;br /&gt;
http://www.digitalpreservation.gov/ndsa/working_groups/documents/Levels_v1.pdf&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
[[File:Levels v1.jpg]]&lt;br /&gt;
&lt;br /&gt;
== User Experiences ==&lt;br /&gt;
&amp;lt;!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The United States Geological Survey Fundamental Science Practices Advisory Committee Data Preservation Subcommittee has developed a set of preservation recommendations (pdf) based on the original NDSA levels guidelines. &lt;br /&gt;
&lt;br /&gt;
http://www.digitalpreservation.gov/ndsa/working_groups/documents/USGS_Guidelines_for_the_Preservation_of_Digital_Scientific_Data_Final.pdf&lt;br /&gt;
&lt;br /&gt;
AVPreserve did a mapping exercise in 2014 to compare the NDSA Levels with ISO 16363.&lt;br /&gt;
&lt;br /&gt;
http://www.avpreserve.com/papers-and-presentations/mapping-standards-for-richer-assessments-ndsa-levels-of-digital-preservation-and-iso-163632012/&lt;br /&gt;
&lt;br /&gt;
== Development Activity ==&lt;br /&gt;
&amp;lt;!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Add the OpenHub.com ID for the tool, if known. --&amp;gt;&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|releases_rss=&lt;br /&gt;
|issues_rss=&lt;br /&gt;
|mailing_lists=&lt;br /&gt;
|ohloh_id=&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=NDSA_Levels_of_Preservation&amp;diff=2675</id>
		<title>NDSA Levels of Preservation</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=NDSA_Levels_of_Preservation&amp;diff=2675"/>
		<updated>2015-05-13T16:20:08Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;&lt;br /&gt;
{{Infobox_tool&lt;br /&gt;
|purpose=The &amp;quot;Levels of Digital Preservation&amp;quot; are a tiered set of recommendations for how organizations should begin to build or enhance their digital preservation activities.&lt;br /&gt;
|image=&lt;br /&gt;
|homepage=http://www.digitalpreservation.gov/ndsa/activities/levels.html&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add one or more categories to describe the function of the tool, such as:&lt;br /&gt;
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add relevant categories to describe the content type that the tool addresses, such as:&lt;br /&gt;
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --&amp;gt;&lt;br /&gt;
[[Category:Planning]]&lt;br /&gt;
[[Category:Organisational_Audit]]&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&amp;lt;!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --&amp;gt;&lt;br /&gt;
A work in progress by the NDSA, it is intended to be a relatively easy-to-use set of guidelines useful not only for those just beginning to think about preserving their digital assets, but also for institutions planning the next steps in enhancing their existing digital preservation systems and workflows. It allows institutions to assess the level of preservation achieved for specific materials in their custody, or their entire preservation infrastructure. It is not designed to assess the robustness of digital preservation programs as a whole since it does not cover such things as policies, staffing, or organizational support. The guidelines are organized into five functional areas that are at the heart of digital preservation systems: storage and geographic location, file fixity and data integrity, information security, metadata, and file formats.&lt;br /&gt;
&lt;br /&gt;
It is expected that the Levels of Digital Preservation will be updated over time as additional feedback is received, experience is gained implementing its recommendations and as empirical research provides detailed information about data loss. For this reason, each iteration of the Levels will be versioned.&lt;br /&gt;
&lt;br /&gt;
http://www.digitalpreservation.gov/ndsa/working_groups/documents/Levels_v1.pdf&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
[[File:Levels v1.jpg]]&lt;br /&gt;
&lt;br /&gt;
== User Experiences ==&lt;br /&gt;
&amp;lt;!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The United States Geological Survey Fundamental Science Practices Advisory Committee Data Preservation Subcommittee has developed a set of preservation recommendations (pdf) based on the original NDSA levels guidelines. &lt;br /&gt;
&lt;br /&gt;
http://www.digitalpreservation.gov/ndsa/working_groups/documents/USGS_Guidelines_for_the_Preservation_of_Digital_Scientific_Data_Final.pdf&lt;br /&gt;
&lt;br /&gt;
== Development Activity ==&lt;br /&gt;
&amp;lt;!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Add the OpenHub.com ID for the tool, if known. --&amp;gt;&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|releases_rss=&lt;br /&gt;
|issues_rss=&lt;br /&gt;
|mailing_lists=&lt;br /&gt;
|ohloh_id=&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=NDSA_Levels_of_Preservation&amp;diff=2674</id>
		<title>NDSA Levels of Preservation</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=NDSA_Levels_of_Preservation&amp;diff=2674"/>
		<updated>2015-05-13T16:18:25Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;&lt;br /&gt;
{{Infobox_tool&lt;br /&gt;
|purpose=The &amp;quot;Levels of Digital Preservation&amp;quot; are a tiered set of recommendations for how organizations should begin to build or enhance their digital preservation activities.&lt;br /&gt;
|image=&lt;br /&gt;
|homepage=http://www.digitalpreservation.gov/ndsa/activities/levels.html&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add one or more categories to describe the function of the tool, such as:&lt;br /&gt;
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add relevant categories to describe the content type that the tool addresses, such as:&lt;br /&gt;
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --&amp;gt;&lt;br /&gt;
[[Category:Planning]]&lt;br /&gt;
[[Category:Organisational_Audit]]&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&amp;lt;!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --&amp;gt;&lt;br /&gt;
A work in progress by the NDSA, it is intended to be a relatively easy-to-use set of guidelines useful not only for those just beginning to think about preserving their digital assets, but also for institutions planning the next steps in enhancing their existing digital preservation systems and workflows. It allows institutions to assess the level of preservation achieved for specific materials in their custody, or their entire preservation infrastructure. It is not designed to assess the robustness of digital preservation programs as a whole since it does not cover such things as policies, staffing, or organizational support. The guidelines are organized into five functional areas that are at the heart of digital preservation systems: storage and geographic location, file fixity and data integrity, information security, metadata, and file formats.&lt;br /&gt;
&lt;br /&gt;
It is expected that the Levels of Digital Preservation will be updated over time as additional feedback is received, experience is gained implementing its recommendations and as empirical research provides detailed information about data loss. For this reason, each iteration of the Levels will be versioned.&lt;br /&gt;
&lt;br /&gt;
http://www.digitalpreservation.gov/ndsa/working_groups/documents/Levels_v1.pdf&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
{{Levels v1}}.jpg&lt;br /&gt;
&lt;br /&gt;
== User Experiences ==&lt;br /&gt;
&amp;lt;!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The United States Geological Survey Fundamental Science Practices Advisory Committee Data Preservation Subcommittee has developed a set of preservation recommendations (pdf) based on the original NDSA levels guidelines. &lt;br /&gt;
&lt;br /&gt;
http://www.digitalpreservation.gov/ndsa/working_groups/documents/USGS_Guidelines_for_the_Preservation_of_Digital_Scientific_Data_Final.pdf&lt;br /&gt;
&lt;br /&gt;
== Development Activity ==&lt;br /&gt;
&amp;lt;!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Add the OpenHub.com ID for the tool, if known. --&amp;gt;&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|releases_rss=&lt;br /&gt;
|issues_rss=&lt;br /&gt;
|mailing_lists=&lt;br /&gt;
|ohloh_id=&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=File:Levels_v1.jpg&amp;diff=2673</id>
		<title>File:Levels v1.jpg</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=File:Levels_v1.jpg&amp;diff=2673"/>
		<updated>2015-05-13T16:16:31Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=NDSA_Levels_of_Preservation&amp;diff=2672</id>
		<title>NDSA Levels of Preservation</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=NDSA_Levels_of_Preservation&amp;diff=2672"/>
		<updated>2015-05-13T16:13:48Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;&lt;br /&gt;
{{Infobox_tool&lt;br /&gt;
|purpose=The &amp;quot;Levels of Digital Preservation&amp;quot; are a tiered set of recommendations for how organizations should begin to build or enhance their digital preservation activities.&lt;br /&gt;
|image=&lt;br /&gt;
|homepage=http://www.digitalpreservation.gov/ndsa/activities/levels.html&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add one or more categories to describe the function of the tool, such as:&lt;br /&gt;
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add relevant categories to describe the content type that the tool addresses, such as:&lt;br /&gt;
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --&amp;gt;&lt;br /&gt;
[[Category:Planning]]&lt;br /&gt;
[[Category:Organisational_Audit]]&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&amp;lt;!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --&amp;gt;&lt;br /&gt;
A work in progress by the NDSA, it is intended to be a relatively easy-to-use set of guidelines useful not only for those just beginning to think about preserving their digital assets, but also for institutions planning the next steps in enhancing their existing digital preservation systems and workflows. It allows institutions to assess the level of preservation achieved for specific materials in their custody, or their entire preservation infrastructure. It is not designed to assess the robustness of digital preservation programs as a whole since it does not cover such things as policies, staffing, or organizational support. The guidelines are organized into five functional areas that are at the heart of digital preservation systems: storage and geographic location, file fixity and data integrity, information security, metadata, and file formats.&lt;br /&gt;
&lt;br /&gt;
It is expected that the Levels of Digital Preservation will be updated over time as additional feedback is received, experience is gained implementing its recommendations and as empirical research provides detailed information about data loss. For this reason, each iteration of the Levels will be versioned.&lt;br /&gt;
&lt;br /&gt;
http://www.digitalpreservation.gov/ndsa/working_groups/documents/Levels_v1.pdf&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
== User Experiences ==&lt;br /&gt;
&amp;lt;!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The United States Geological Survey Fundamental Science Practices Advisory Committee Data Preservation Subcommittee has developed a set of preservation recommendations (pdf) based on the original NDSA levels guidelines. &lt;br /&gt;
&lt;br /&gt;
http://www.digitalpreservation.gov/ndsa/working_groups/documents/USGS_Guidelines_for_the_Preservation_of_Digital_Scientific_Data_Final.pdf&lt;br /&gt;
&lt;br /&gt;
== Development Activity ==&lt;br /&gt;
&amp;lt;!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Add the OpenHub.com ID for the tool, if known. --&amp;gt;&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|releases_rss=&lt;br /&gt;
|issues_rss=&lt;br /&gt;
|mailing_lists=&lt;br /&gt;
|ohloh_id=&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=NDSA_Levels_of_Preservation&amp;diff=2671</id>
		<title>NDSA Levels of Preservation</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=NDSA_Levels_of_Preservation&amp;diff=2671"/>
		<updated>2015-05-13T16:11:01Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;&lt;br /&gt;
{{Infobox_tool&lt;br /&gt;
|purpose=The &amp;quot;Levels of Digital Preservation&amp;quot; are a tiered set of recommendations for how organizations should begin to build or enhance their digital preservation activities.&lt;br /&gt;
|homepage=http://www.digitalpreservation.gov/ndsa/activities/levels.html&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add one or more categories to describe the function of the tool, such as:&lt;br /&gt;
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add relevant categories to describe the content type that the tool addresses, such as:&lt;br /&gt;
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --&amp;gt;&lt;br /&gt;
[[Category:Planning]]&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&amp;lt;!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --&amp;gt;&lt;br /&gt;
A work in progress by the NDSA, it is intended to be a relatively easy-to-use set of guidelines useful not only for those just beginning to think about preserving their digital assets, but also for institutions planning the next steps in enhancing their existing digital preservation systems and workflows. It allows institutions to assess the level of preservation achieved for specific materials in their custody, or their entire preservation infrastructure. It is not designed to assess the robustness of digital preservation programs as a whole since it does not cover such things as policies, staffing, or organizational support. The guidelines are organized into five functional areas that are at the heart of digital preservation systems: storage and geographic location, file fixity and data integrity, information security, metadata, and file formats.&lt;br /&gt;
&lt;br /&gt;
It is expected that the Levels of Digital Preservation will be updated over time as additional feedback is received, experience is gained implementing its recommendations and as empirical research provides detailed information about data loss. For this reason, each iteration of the Levels will be versioned.&lt;br /&gt;
&lt;br /&gt;
http://www.digitalpreservation.gov/ndsa/working_groups/documents/Levels_v1.pdf&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
== User Experiences ==&lt;br /&gt;
&amp;lt;!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The United States Geological Survey Fundamental Science Practices Advisory Committee Data Preservation Subcommittee has developed a set of preservation recommendations (pdf) based on the original NDSA levels guidelines. &lt;br /&gt;
&lt;br /&gt;
http://www.digitalpreservation.gov/ndsa/working_groups/documents/USGS_Guidelines_for_the_Preservation_of_Digital_Scientific_Data_Final.pdf&lt;br /&gt;
&lt;br /&gt;
== Development Activity ==&lt;br /&gt;
&amp;lt;!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Add the OpenHub.com ID for the tool, if known. --&amp;gt;&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|releases_rss=&lt;br /&gt;
|issues_rss=&lt;br /&gt;
|mailing_lists=&lt;br /&gt;
|ohloh_id=&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=NDSA_Levels_of_Preservation&amp;diff=2670</id>
		<title>NDSA Levels of Preservation</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=NDSA_Levels_of_Preservation&amp;diff=2670"/>
		<updated>2015-05-13T16:09:38Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Infobox_tool&lt;br /&gt;
|purpose=The &amp;quot;Levels of Digital Preservation&amp;quot; are a tiered set of recommendations for how organizations should begin to build or enhance their digital preservation activities. &lt;br /&gt;
|homepage=http://www.digitalpreservation.gov/ndsa/activities/levels.html&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add one or more categories to describe the function of the tool, such as:&lt;br /&gt;
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add relevant categories to describe the content type that the tool addresses, such as:&lt;br /&gt;
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&amp;lt;!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --&amp;gt;&lt;br /&gt;
A work in progress by the NDSA, it is intended to be a relatively easy-to-use set of guidelines useful not only for those just beginning to think about preserving their digital assets, but also for institutions planning the next steps in enhancing their existing digital preservation systems and workflows. It allows institutions to assess the level of preservation achieved for specific materials in their custody, or their entire preservation infrastructure. It is not designed to assess the robustness of digital preservation programs as a whole since it does not cover such things as policies, staffing, or organizational support. The guidelines are organized into five functional areas that are at the heart of digital preservation systems: storage and geographic location, file fixity and data integrity, information security, metadata, and file formats.&lt;br /&gt;
&lt;br /&gt;
It is expected that the Levels of Digital Preservation will be updated over time as additional feedback is received, experience is gained implementing its recommendations and as empirical research provides detailed information about data loss. For this reason, each iteration of the Levels will be versioned.&lt;br /&gt;
&lt;br /&gt;
http://www.digitalpreservation.gov/ndsa/working_groups/documents/Levels_v1.pdf&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
== User Experiences ==&lt;br /&gt;
&amp;lt;!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The United States Geological Survey Fundamental Science Practices Advisory Committee Data Preservation Subcommittee has developed a set of preservation recommendations (pdf) based on the original NDSA levels guidelines. &lt;br /&gt;
&lt;br /&gt;
http://www.digitalpreservation.gov/ndsa/working_groups/documents/USGS_Guidelines_for_the_Preservation_of_Digital_Scientific_Data_Final.pdf&lt;br /&gt;
&lt;br /&gt;
== Development Activity ==&lt;br /&gt;
&amp;lt;!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Add the OpenHub.com ID for the tool, if known. --&amp;gt;&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|releases_rss=&lt;br /&gt;
|issues_rss=&lt;br /&gt;
|mailing_lists=&lt;br /&gt;
|ohloh_id=&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
	<entry>
		<id>https://coptr.digipres.org/index.php?title=NDSA_Levels_of_Preservation&amp;diff=2669</id>
		<title>NDSA Levels of Preservation</title>
		<link rel="alternate" type="text/html" href="https://coptr.digipres.org/index.php?title=NDSA_Levels_of_Preservation&amp;diff=2669"/>
		<updated>2015-05-13T16:07:52Z</updated>

		<summary type="html">&lt;p&gt;Edpinsent: Created page with &amp;quot;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;  {{Infobox_tool |purpose=The “Levels of Digital Preservation&amp;quot;are a tiered set of recommendations for ...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Use the structure provided in this template, do not change it! --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Infobox_tool&lt;br /&gt;
|purpose=The “Levels of Digital Preservation&amp;quot;are a tiered set of recommendations for how organizations should begin to build or enhance their digital preservation activities. &lt;br /&gt;
|homepage=http://www.digitalpreservation.gov/ndsa/activities/levels.html&lt;br /&gt;
|license=&lt;br /&gt;
|platforms=&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;!-- Note that to use the image field, you should leave the value as {{PAGENAMEE}}.png (or similar) and upload a copy of the image. Hot-linking is not supported. If you don't want an image, just remove that line. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add one or more categories to describe the function of the tool, such as:&lt;br /&gt;
[[Category:Metadata Extraction]] or [[Category:Preservation System]] or [[Category:Backup]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left) --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Add relevant categories to describe the content type that the tool addresses, such as:&lt;br /&gt;
[[Category:Audio]] or [[Category:Document]] or [[Category:Research Data]]&lt;br /&gt;
Choose carefully, and view the list of existing categories first (see the Navigation sidebar on the left). If the tool works on any content type, do not add a category. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&amp;lt;!-- Describe the what the tool does, focusing on it's digital preservation value. Keep it factual. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== User Experiences ==&lt;br /&gt;
&amp;lt;!-- Add hotlinks to user experiences with the tool (eg. blog posts). These should illustrate the effectiveness (or otherwise) of the tool. Use a bullet list. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Development Activity ==&lt;br /&gt;
&amp;lt;!-- Provide *evidence* of development activity of the tool. For example, RSS feeds for code issues or commits. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Add the OpenHub.com ID for the tool, if known. --&amp;gt;&lt;br /&gt;
{{Infobox_tool_details&lt;br /&gt;
|releases_rss=&lt;br /&gt;
|issues_rss=&lt;br /&gt;
|mailing_lists=&lt;br /&gt;
|ohloh_id=&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Edpinsent</name></author>
	</entry>
</feed>