<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>archivemati.ca &#187; System Requirements</title>
	<atom:link href="http://archivemati.ca/category/system-requirements/feed/" rel="self" type="application/rss+xml" />
	<link>http://archivemati.ca</link>
	<description>archives. technology.</description>
	<lastBuildDate>Wed, 01 Feb 2012 18:14:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>The Information Model to End All Information Models</title>
		<link>http://archivemati.ca/2006/12/08/the-information-model-to-end-all-information-models/</link>
		<comments>http://archivemati.ca/2006/12/08/the-information-model-to-end-all-information-models/#comments</comments>
		<pubDate>Fri, 08 Dec 2006 21:14:59 +0000</pubDate>
		<dc:creator>peterVG</dc:creator>
				<category><![CDATA[ICA-AtoM]]></category>
		<category><![CDATA[System Architecture]]></category>
		<category><![CDATA[System Requirements]]></category>

		<guid isPermaLink="false">http://archivemati.ca/?p=59</guid>
		<description><![CDATA[I am now beginning work on the second alpha iteration of the open-source ICA-AtoM software application. I am working on a considerable upgrade to the underlying object and database model which supports the application. As the application matures and evolves it will be relatively easy to make changes and updates to the application modules and [...]]]></description>
		<wfw:commentRss>http://archivemati.ca/2006/12/08/the-information-model-to-end-all-information-models/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Does my Digital Archives need a Digital Repository System?</title>
		<link>http://archivemati.ca/2006/11/27/does-my-digital-archives-need-a-digital-repository-system/</link>
		<comments>http://archivemati.ca/2006/11/27/does-my-digital-archives-need-a-digital-repository-system/#comments</comments>
		<pubDate>Tue, 28 Nov 2006 01:34:01 +0000</pubDate>
		<dc:creator>peterVG</dc:creator>
				<category><![CDATA[Digital Preservation]]></category>
		<category><![CDATA[System Architecture]]></category>
		<category><![CDATA[System Requirements]]></category>

		<guid isPermaLink="false">http://archivemati.ca/?p=56</guid>
		<description><![CDATA[I have had this discussions with colleagues several times over the past couple of years. Somebody is getting ready to prototype a digital archives at their archival institution and the first question they ask is, &#8220;which open-source repository system should I use? Dspace? Fedora? Greenstone? Eprints? &#8221; However, as a system analyst, I believe &#8220;what [...]]]></description>
		<wfw:commentRss>http://archivemati.ca/2006/11/27/does-my-digital-archives-need-a-digital-repository-system/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Archiving for CMS presentation at OSCMS Summit</title>
		<link>http://archivemati.ca/2006/02/07/archiving-for-cms-presentation-at-oscms-summit/</link>
		<comments>http://archivemati.ca/2006/02/07/archiving-for-cms-presentation-at-oscms-summit/#comments</comments>
		<pubDate>Wed, 08 Feb 2006 01:26:16 +0000</pubDate>
		<dc:creator>peterVG</dc:creator>
				<category><![CDATA[System Architecture]]></category>
		<category><![CDATA[System Requirements]]></category>
		<category><![CDATA[Web 2.0]]></category>

		<guid isPermaLink="false">http://archivemati.ca/?p=35</guid>
		<description><![CDATA[Today I gave a presentation on archiving for CMS at the Open Source Content Management Systems shindig (OSCMS Summit) here in (currently sunny) Vancouver. This is a PDF copy of my presentation slides: OSCMS Summit: Archiving Presentation (54kb) We started the presentation with an introduction to some of the basic digital preservation issues that I [...]]]></description>
		<wfw:commentRss>http://archivemati.ca/2006/02/07/archiving-for-cms-presentation-at-oscms-summit/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>System Requirements for Archives Access Systems (v.1)</title>
		<link>http://archivemati.ca/2005/11/04/system-requirements-for-archives-access-systems/</link>
		<comments>http://archivemati.ca/2005/11/04/system-requirements-for-archives-access-systems/#comments</comments>
		<pubDate>Fri, 04 Nov 2005 22:35:41 +0000</pubDate>
		<dc:creator>peterVG</dc:creator>
				<category><![CDATA[Archives Access Systems]]></category>
		<category><![CDATA[System Requirements]]></category>

		<guid isPermaLink="false">http://archivemati.ca/?p=18</guid>
		<description><![CDATA[In order to study existing Archives Access Systems and to develop prototypes that incorporate Web 2.0 features, I will need to develop a core set of generic system requirements that describes what an Archives Access System must be able to do. The first version of this core set of system requirements will be based on [...]]]></description>
		<wfw:commentRss>http://archivemati.ca/2005/11/04/system-requirements-for-archives-access-systems/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>System Requirements</title>
		<link>http://archivemati.ca/2005/11/04/system-requirements/</link>
		<comments>http://archivemati.ca/2005/11/04/system-requirements/#comments</comments>
		<pubDate>Fri, 04 Nov 2005 20:41:11 +0000</pubDate>
		<dc:creator>peterVG</dc:creator>
				<category><![CDATA[System Requirements]]></category>
		<category><![CDATA[Terms & Definitions]]></category>

		<guid isPermaLink="false">http://archivemati.ca/2005/11/04/system-requirements/</guid>
		<description><![CDATA[System requirements state what a system’s behaviours, properties, characteristics and features are in as unambiguous a way possible. The purpose of system requirement specifications is to accurately capture the requirements of the system’s owners, users and stakeholders. System requirements are drafted to ensure that all parties are in agreement on what system should be built [...]]]></description>
		<wfw:commentRss>http://archivemati.ca/2005/11/04/system-requirements/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

