<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: ANDS Metadata store: starting point</title>
	<atom:link href="http://ptsefton.com/2010/02/02/ands-metadata-store-starting-point.htm/feed" rel="self" type="application/rss+xml" />
	<link>http://ptsefton.com/2010/02/02/ands-metadata-store-starting-point.htm</link>
	<description>This seems to be a workblog</description>
	<lastBuildDate>Thu, 22 Jul 2010 22:51:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Basil Dewhurst</title>
		<link>http://ptsefton.com/2010/02/02/ands-metadata-store-starting-point.htm/comment-page-1#comment-1633</link>
		<dc:creator>Basil Dewhurst</dc:creator>
		<pubDate>Thu, 04 Feb 2010 22:57:50 +0000</pubDate>
		<guid isPermaLink="false">http://ptsefton.com/2010/02/02/ands-metadata-store-starting-point.htm#comment-1633</guid>
		<description>Regarding the OAI-PMH, from the perspective of an aggregator, where repositories do not support deleted records it is difficult to keep information up-to-date without dropping all records from a contributor and completely re-harvesting them.  We have to do this for services like Australian Research Online and Picture Australia on a regular basis to ensure that the information we provide is as accurate as possible.  It seems to me that having to do full re-harvests goes against the intention of the OAI protocol where, in the ideal case, an initial harvest picks up all available metadata and incremental harvests pick up new, modified and deleted records.  From an aggregator&#039;s perspective it would be ideal if repositories supported deleted records (at the very least) transiently. 

Regarding People Australia, People Australia is a currently functioning system that ingests party records from contributors, matches names (automatically or by hand), assigns a public persistent identifier and makes records available for humans and machines in a range of formats.  Some example records: 
Maybanke Anderson (feminist and activist) http://nla.gov.au/nla.party-466159
Thomas Huxley (&#039;Darwin&#039;s bulldog&#039;) http://nla.gov.au/nla.party-869246 
Michael Cappo (AIMS researcher) http://nla.gov.au/nla.party-471077

More information about the People Australia project is available via the National Library&#039;s new Trove service at http://trove.nla.gov.au/general/aboutPeople.

Through the ANDS funded ARDC Party Infrastructure Project, the National Library plans to extend the existing People Australia infrastructure to handle data from the research sector, assign persistent identifiers and provide party data back to the sector.  Also the project will be developing software that allows managers in the research sector to manage their party data and obtain persistent identifiers.

Regarding data models and parties, for a Party Infrastructure to function well in the ARDC it is critical that enough contextual information about a person or organisation is recorded, stored in and provided from research sector repositories.  This contextual information (eg birth/death dates, subject areas, institutional affiliation, occupations, roles, activities) is important for end users, aggregators and repository managers for distinguishing between people, for identifying the resources/data they create, for managing these resources/data and reporting about them.</description>
		<content:encoded><![CDATA[<p>Regarding the OAI-PMH, from the perspective of an aggregator, where repositories do not support deleted records it is difficult to keep information up-to-date without dropping all records from a contributor and completely re-harvesting them.  We have to do this for services like Australian Research Online and Picture Australia on a regular basis to ensure that the information we provide is as accurate as possible.  It seems to me that having to do full re-harvests goes against the intention of the OAI protocol where, in the ideal case, an initial harvest picks up all available metadata and incremental harvests pick up new, modified and deleted records.  From an aggregator&#8217;s perspective it would be ideal if repositories supported deleted records (at the very least) transiently. </p>
<p>Regarding People Australia, People Australia is a currently functioning system that ingests party records from contributors, matches names (automatically or by hand), assigns a public persistent identifier and makes records available for humans and machines in a range of formats.  Some example records:<br />
Maybanke Anderson (feminist and activist) <a href="http://nla.gov.au/nla.party-466159" rel="nofollow">http://nla.gov.au/nla.party-466159</a><br />
Thomas Huxley (&#8216;Darwin&#8217;s bulldog&#8217;) <a href="http://nla.gov.au/nla.party-869246" rel="nofollow">http://nla.gov.au/nla.party-869246</a><br />
Michael Cappo (AIMS researcher) <a href="http://nla.gov.au/nla.party-471077" rel="nofollow">http://nla.gov.au/nla.party-471077</a></p>
<p>More information about the People Australia project is available via the National Library&#8217;s new Trove service at <a href="http://trove.nla.gov.au/general/aboutPeople" rel="nofollow">http://trove.nla.gov.au/general/aboutPeople</a>.</p>
<p>Through the ANDS funded ARDC Party Infrastructure Project, the National Library plans to extend the existing People Australia infrastructure to handle data from the research sector, assign persistent identifiers and provide party data back to the sector.  Also the project will be developing software that allows managers in the research sector to manage their party data and obtain persistent identifiers.</p>
<p>Regarding data models and parties, for a Party Infrastructure to function well in the ARDC it is critical that enough contextual information about a person or organisation is recorded, stored in and provided from research sector repositories.  This contextual information (eg birth/death dates, subject areas, institutional affiliation, occupations, roles, activities) is important for end users, aggregators and repository managers for distinguishing between people, for identifying the resources/data they create, for managing these resources/data and reporting about them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
