<?xml version="1.0" encoding="utf-8"?>
<!-- generator="Joomla! - Open Source Content Management" -->
<?xml-stylesheet href="/plugins/system/jce/css/content.css?8ab6cd2cdeacdd61316e109e01f39cdd" type="text/css"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Pilots - E-Ark Project</title>
		<description><![CDATA[]]></description>
		<link>https://eark-project.com/pilots-2/29-user-stories-scenarios</link>
		<lastBuildDate>Mon, 04 May 2020 18:05:35 +0000</lastBuildDate>
		<generator>Joomla! - Open Source Content Management</generator>
		<atom:link rel="self" type="application/rss+xml" href="https://eark-project.com/pilots-2/29-user-stories-scenarios?format=feed&amp;type=rss"/>
		<language>en-gb</language>
		<managingEditor>dlmforumweb@gmail.com (eark-project)</managingEditor>
		<item>
			<title>Pilot 1: Danish National Archives</title>
			<link>https://eark-project.com/pilots-2/29-user-stories-scenarios/118-pilot-1</link>
			<guid isPermaLink="true">https://eark-project.com/pilots-2/29-user-stories-scenarios/118-pilot-1</guid>
			<description><![CDATA[<p><strong>Scope: Submission Information Package creation on relational databases</strong></p>
<p><img src="https://eark-project.com/images/Resources/Denmark_Stacks.jpg" alt="Denmark Stacks" width="394" height="296" /></p>
<p>In Denmark, all public institutions are required by law to deliver certain data and information to the Danish National Archive for posterity. The role of the archivist is to determine what needs to be kept in the national interest and to select the information that needs to be stored and retained for future use.</p>
<p>The Danish National Archives is responsible for setting the technical standards for how public institutions must deliver this data, and these institutions must comply with these standards.  These standards are necessary in order to ensure that the information and data will be sustainable and accessible over the long term. However, this means that institutions must export and convert the data from their various systems to one specific preservation format, and this can be a complex and costly process.</p>
<p>Currently, the Danish National Archives can only offer guidance to the institutions about the format in which the data and information is to be exported, and yet can only accept the incoming data and information if it all complies with the technical standards set.&nbsp;The E-ARK tool tested in this pilot can attach to the most common systems used by the institutions and can export to the preservation format developed in E-ARK. As the E-ARK tool is very similar to the preservation format already used in the Danish National Archives, the tool allows institutions to export to the Danish preservation format.&nbsp;This means that, by making the E-ARK tool tested in this pilot universally available, it will become cheaper and easier for historic data to be delivered to the Danish National Archives.</p>
<p>The final product will also be accessible to other countries’ archives meaning that small nations can benefit from the tools arising from the collaboration and the technological expertise developed as part of the E-ARK project.</p>
<p><img src="https://eark-project.com/images/Resources/Denmark_Demo.jpg" alt="Denmark Demo" width="408" height="287" /></p>
<p>&nbsp;</p>]]></description>
			<author>cdpa@btinternet.com (David Anderson)</author>
			<category>Scenarios</category>
			<pubDate>Tue, 22 Nov 2016 10:26:04 +0000</pubDate>
		</item>
		<item>
			<title>Pilot 2: National Archives of Norway</title>
			<link>https://eark-project.com/pilots-2/29-user-stories-scenarios/119-pilot-2</link>
			<guid isPermaLink="true">https://eark-project.com/pilots-2/29-user-stories-scenarios/119-pilot-2</guid>
			<description><![CDATA[<p><strong>Scope: SIP creation and ingest of records</strong></p>
<p><img src="https://eark-project.com/images/Resources/Norway_Archive.jpg" alt="Norway Archive" /></p>
<p>This pilot focused on the initial stages data and information transfer from the producer to the archive.&nbsp;Before the data can be moved, it has to be organised and packaged in a way that meets the standards of the archive where it will be processed further. The pilot consisted of three scenarios with various types of content of different size and form.</p>
<p>(1) &nbsp;Database content</p>
<p>(2) &nbsp;Content related to the Noark-4 standard</p>
<p>(3) &nbsp;Content related to the Noark-5 standard</p>
<p>The format of the content was of interest to the E-ARK project inasmuch as it had to be validated according to local standards.&nbsp;Three types of software developed by one of the other partners (ES Solutions AB) in the E-ARK project were used:</p>
<p>(1) &nbsp;ESSArch Tools Producer (ETP). This is aimed at data producers.</p>
<p>(2) &nbsp;ESSArch Tools Archive (ETA). This services the front end of the repository/depot.</p>
<p>(3)&nbsp;&nbsp;ESSArch Preservation Platform (EPP). The repository/depot solution.</p>
<p>The tools all use international metadata standards such as OAIS, METS and PREMIS for the description of structure and actions on the content.&nbsp;During the pilot, the overall success of applying the tool support was evaluated.&nbsp;At a more detailed level, how size considerations versus time consumption, and details regarding the OAIS, METS and PREMIS implementation etc. were also assessed.</p>
<p><img src="https://eark-project.com/images/Resources/NAN_Team-small.jpg" alt="NAN Team small" width="412" height="275" /></p>
<p>&nbsp;</p>]]></description>
			<author>cdpa@btinternet.com (David Anderson)</author>
			<category>Scenarios</category>
			<pubDate>Tue, 22 Nov 2016 10:26:04 +0000</pubDate>
		</item>
		<item>
			<title>Pilot 3: National Archives of Estonia</title>
			<link>https://eark-project.com/pilots-2/29-user-stories-scenarios/120-pilot-3</link>
			<guid isPermaLink="true">https://eark-project.com/pilots-2/29-user-stories-scenarios/120-pilot-3</guid>
			<description><![CDATA[<p><strong>Scope: Ingest from government agencies</strong></p>
<p style="text-align: left;"><img src="https://eark-project.com/images/Resources/Estonia_Tallinn.jpg" alt="Estonia Tallinn" width="399" height="142" /></p>
<p style="text-align: left;"><span style="text-align: right;">The process of moving information from government agency record management systems to national archives where it can be sustained and made accessible can broadly be divided into four phases:</span></p>
<table style="height: 275px; width: 299px;" border="0">
<tbody>
<tr>
<td><img src="https://eark-project.com/images/Resources/Estonia_National_Archive.jpg" alt="Estonia National Archive" width="179" height="269" /></td>
<td>
<p>&nbsp; &nbsp; (1) Selection</p>
<p>&nbsp; &nbsp; (2) Extraction</p>
<p>&nbsp; &nbsp; (3) Transfer</p>
<p>&nbsp; &nbsp; (4) Acceptance</p>
<p>&nbsp;</p>
</td>
</tr>
</tbody>
</table>
<p>Usually, this is information which needs to be retained for an indefinite period of time and is relevant to both the agency that created it and to the nation as a whole. Each country must follow similar pathways yet naturally,&nbsp;there is much variation, which had led to a lack of a common approach or methodology.</p>
<p>The movement of material of archival value and the related metadata was tested in this pilot using a series of tools which implement the E-ARK information packaging specifications. It can be hard to persuade institutions to develop their own processes for doing this. By involving multiple partners and stakeholders in E-ARK, a universally available standard process has been created that means that individual agencies and archives will no longer need to find bespoke, customised solutions.</p>
<p>&nbsp;</p>]]></description>
			<author>cdpa@btinternet.com (David Anderson)</author>
			<category>Scenarios</category>
			<pubDate>Tue, 22 Nov 2016 10:26:04 +0000</pubDate>
		</item>
		<item>
			<title>Pilot 4: Business Archives National Archives of Estonia (supported by Estonian Business Archives)</title>
			<link>https://eark-project.com/pilots-2/29-user-stories-scenarios/121-pilot-4</link>
			<guid isPermaLink="true">https://eark-project.com/pilots-2/29-user-stories-scenarios/121-pilot-4</guid>
			<description><![CDATA[<p><strong>Scope: Migration and Ingest of Business Records from a Bespoke Business System</strong></p>
<p><img style="display: block; margin-left: auto; margin-right: auto;" src="https://eark-project.com/images/Resources/Estonia_Business_Archive.jpg" alt="Estonia Business Archive" /></p>
<p><br />Often, the cost of migrating information to a newer system can prove complex and prohibitively expensive. When commercial or private sector data is stored or left in databases that are then untouched for significant periods of time or become out of date, retrieving and reusing information can be difficult.</p>
<p>Companies need solutions to extract information that is still valuable though not in active use, but which needs to be kept for a variety of reasons – legal, compliance, business – and then reused. In this pilot&nbsp;the National Archives of Estonia worked alongside the Estonian Business Archives. As a service company to the private sector, the latter has extensive experience of and are familiar with the needs and requirements of the private sector.</p>
<p>This pilot tested the E-ARK Database Preservation Toolkit (DTP) at the SIP (submission information package) creation stage, allowing information to be transferred from old platforms to an interim standardised format which is then digestible by newer systems. The SIARD (Software Independent Archiving Relational Databases <a href="http://www.digitalpreservation.gov/formats/fdd/fdd000426.shtml">http://www.digitalpreservation.gov/formats/fdd/fdd000426.shtml</a>) tool was piloted to understand how to keep the data alive and sustainable for future use.&nbsp;It is hoped that SIARD will become the <em>de facto</em> industry standard in due course.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>]]></description>
			<author>cdpa@btinternet.com (David Anderson)</author>
			<category>Scenarios</category>
			<pubDate>Tue, 22 Nov 2016 10:26:04 +0000</pubDate>
		</item>
		<item>
			<title>Pilot 5: National Archives of Slovenia (supported by the Danish National Archives)</title>
			<link>https://eark-project.com/pilots-2/29-user-stories-scenarios/122-pilot-5</link>
			<guid isPermaLink="true">https://eark-project.com/pilots-2/29-user-stories-scenarios/122-pilot-5</guid>
			<description><![CDATA[<p><strong>Scope: Preservation and access to records with geodata</strong></p>
<p><img style="display: block; margin-left: auto; margin-right: auto;" src="https://eark-project.com/images/Resources/Slovenia_Env_Agency.jpg" alt="Slovenia Env Agency" /></p>
<p>This Pilot&nbsp;developed and tested guidelines and tools for archiving digital geographical maps which have in the past been used as a basis for decision making in government and other official procedures (e.g. granting planning permission and building permits, assessing&nbsp;where to levy taxes and in monitoring pollution).</p>
<p>Focusing on digital geographical data in vector format, the pilot produced guidelines that can be used for archiving the digital geodata and the required documentation, and which will ensure a proper understanding of and reuse of these records in the future.&nbsp;It also demonstrated that the integration of existing open source tools and the tools developed in the E-ARK Project can support the archiving process and access to such data.</p>
<p>Users benefited by gaining access to a wider range of geodata and by, using location-based search tools, by having the opportunity to use and compare additional descriptions of the required documents for the interpretation of and, significantly, the re-use of the geodata.</p>
<p><img style="display: block; margin-left: auto; margin-right: auto;" src="https://eark-project.com/images/Resources/Slovenia_Panorama.jpg" alt="Slovenia Panorama" width="473" height="203" /></p>]]></description>
			<author>cdpa@btinternet.com (David Anderson)</author>
			<category>Scenarios</category>
			<pubDate>Tue, 22 Nov 2016 10:26:04 +0000</pubDate>
		</item>
		<item>
			<title>Pilot 6: KEEP Solutions (supported by Insituto Superior Técnico)</title>
			<link>https://eark-project.com/pilots-2/29-user-stories-scenarios/123-pilot-6</link>
			<guid isPermaLink="true">https://eark-project.com/pilots-2/29-user-stories-scenarios/123-pilot-6</guid>
			<description><![CDATA[<p><strong>Scope: Integration between a live document management system and digital archiving and preservation service</strong></p>
<p><img src="https://eark-project.com/images/Resources/keep_headquarters.jpg" alt="keep headquarters" width="547" height="205" /></p>
<p>The life cycle of a record that needs to be archived usually falls into three phases:</p>
<p>(1) When the metadata and data are ‘live’ (being used and modified regularly).</p>
<p>(2) When the metadata and data are archived for a short period (up to 5 years).</p>
<p>(3) When the metadata and data are moved to a long-term repository for permanent conservation.</p>
<p>The aim of this pilot was to assess the efficacy of the E-ARK Information Package Specification. This defines how metadata and data should be packaged in order to move records between these phases. The pilot worked on a way to ensure that no relevant data or metadata was lost in the process. To accomplish this, a special integration tool was developed that implements the specification and orchestrates the entire transfer process.</p>
<p>&nbsp;</p>
<table style="height: 224px; width: 181px;" border="0" align="left">
<tbody>
<tr>
<td><img style="text-align: right;" src="https://eark-project.com/images/Resources/lfaria.jpg" alt="lfaria" /></td>
<td>&nbsp;</td>
</tr>
<tr>
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tbody>
</table>
<p>The information package used proved effective in terms of its flexibility and ability to cope with multiple data types. The pilot transferred about 2 TB of data between the archival service and the long-term preservation service. The institution’s archival service is not yet prepared to face the challenges of long-term digital preservation, so the records that were selected for permanent conservation were then transferred to a long-term digital repository (the third phase). The&nbsp;pilot worked with a public institution whose records were initially produced and managed in an electronic records management system (ERMS). These were mandated to be archived after their “live” phase and the first part of the pilot focussed on the assessment of the adequacy of the Information Package structure and the efficiency of the integration tool in handling the data and metadata (and supporting documentation) as it moved from the original system to the institution’s own internal archival service (the second phase).</p>
<p>The pilot also&nbsp;examined the earlier stages of the transfer of data and information and tested the E-ARK tools in that phase.</p>
<p>&nbsp;</p>]]></description>
			<author>cdpa@btinternet.com (David Anderson)</author>
			<category>Scenarios</category>
			<pubDate>Tue, 22 Nov 2016 10:26:04 +0000</pubDate>
		</item>
		<item>
			<title>Pilot 7: National Archives of Hungary (supported by the Danish National Archives)</title>
			<link>https://eark-project.com/pilots-2/29-user-stories-scenarios/124-pilot-7</link>
			<guid isPermaLink="true">https://eark-project.com/pilots-2/29-user-stories-scenarios/124-pilot-7</guid>
			<description><![CDATA[<p><strong>Scope: Access to databases</strong></p>
<p><img src="https://eark-project.com/images/Resources/Hungary_Archive.jpg" alt="Hungary Archive" width="444" height="300" /></p>
<p>When information is initially stored in databases used in offices and institutions, it is categorised according to the nature of the information. For example, individual tables are made of generic data such as names, addresses and so forth and are linked to other tables of relevant information.&nbsp;Multiple sets of data in these operational databases, where the original material is of interest to the originator and the archivist, are stored in a normalised form in order to maintain consistency.</p>
<p>When this data is moved to longer-term storage and access, the structure for storing the data is simplified into fewer datasets, grouping together sets extracted from the original database. This simpler structure is intended to be beneficial by making the data clearer and easier to interrogate, and for access to be more straightforward.</p>
<table style="height: 205px; width: 225px;" border="0" align="left">
<tbody>
<tr>
<td><img src="https://eark-project.com/images/Resources/IstfanAfoldi.jpg" alt="IstfanAfoldi" /></td>
<td>&nbsp;</td>
</tr>
</tbody>
</table>
<p>These are the data warehouses and they exist to ensure long-term sustainability for the data and to allow for interrogation by researchers requiring access to the data. This pilot tested the E-ARK ESSArch tool. This is designed to ensure that all the data is retained and that there is no loss of function as a result of the transition from the&nbsp;original relational database to the data warehouse.</p>
<p>Furthermore, this pilot also tested the efficacy of freely available web-based applications, such as Oracle APEX, in allowing researchers to get access to and use the data stored in the data warehouses. In some cases, companies and institutions such as banks, tax offices and public institutions only have their records in data warehouses, rather than in operational databases, so it is important that they are easy to understand and meet the requirements of those needing access.</p>
<p>In ‘rendering’ information, data needs to be provided in relevant ways and according to the specific requests of the researcher. Various tools are available for this with varying degrees of sophistication and at varying costs.</p>
<p>&nbsp;</p>]]></description>
			<author>cdpa@btinternet.com (David Anderson)</author>
			<category>Scenarios</category>
			<pubDate>Tue, 22 Nov 2016 10:26:04 +0000</pubDate>
		</item>
	</channel>
</rss>
