<?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: Distributed Version Control and Library Metadata</title>
	<atom:link href="http://journal.code4lib.org/articles/86/feed" rel="self" type="application/rss+xml" />
	<link>http://journal.code4lib.org/articles/86</link>
	<description></description>
	<lastBuildDate>Wed, 22 May 2013 14:07:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Idle Hands Are The Devil&#8217;s Plaything &#171; thesecretmirror.com</title>
		<link>http://journal.code4lib.org/articles/86/comment-page-1#comment-3917</link>
		<dc:creator>Idle Hands Are The Devil&#8217;s Plaything &#171; thesecretmirror.com</dc:creator>
		<pubDate>Tue, 07 Jun 2011 05:50:26 +0000</pubDate>
		<guid isPermaLink="false">http://journal.code4lib.org/articles/86#comment-3917</guid>
		<description><![CDATA[[...] (ahem, vote for mine, if you&#039;re so inclined): Building on Galen Charlton&#039;s investigations into distributed version control systems for metadata management, I offer a prototype system for managing archival finding aids in EAD (Encoded Archival [...]]]></description>
		<content:encoded><![CDATA[<p>[...] (ahem, vote for mine, if you&#039;re so inclined): Building on Galen Charlton&#039;s investigations into distributed version control systems for metadata management, I offer a prototype system for managing archival finding aids in EAD (Encoded Archival [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Gorman</title>
		<link>http://journal.code4lib.org/articles/86/comment-page-1#comment-935</link>
		<dc:creator>Jon Gorman</dc:creator>
		<pubDate>Mon, 21 Jul 2008 16:11:44 +0000</pubDate>
		<guid isPermaLink="false">http://journal.code4lib.org/articles/86#comment-935</guid>
		<description><![CDATA[Ah, interesting.  I haven&#039;t done as much with the distributed version control systems as the...well, traditional ones I guess you would call them.  Obviously I need to play around with them a little more.]]></description>
		<content:encoded><![CDATA[<p>Ah, interesting.  I haven&#8217;t done as much with the distributed version control systems as the&#8230;well, traditional ones I guess you would call them.  Obviously I need to play around with them a little more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jakub Narebski</title>
		<link>http://journal.code4lib.org/articles/86/comment-page-1#comment-929</link>
		<dc:creator>Jakub Narebski</dc:creator>
		<pubDate>Sun, 20 Jul 2008 21:27:38 +0000</pubDate>
		<guid isPermaLink="false">http://journal.code4lib.org/articles/86#comment-929</guid>
		<description><![CDATA[@Jon Gorman: Git does rename detection based on similarity score, so it should not matter whether one person caled file &#039;foo&#039; and second &#039;bar&#039; when creating almost the same file: they should merge correctly.]]></description>
		<content:encoded><![CDATA[<p>@Jon Gorman: Git does rename detection based on similarity score, so it should not matter whether one person caled file &#8216;foo&#8217; and second &#8216;bar&#8217; when creating almost the same file: they should merge correctly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Gorman</title>
		<link>http://journal.code4lib.org/articles/86/comment-page-1#comment-205</link>
		<dc:creator>Jon Gorman</dc:creator>
		<pubDate>Mon, 30 Jun 2008 15:41:14 +0000</pubDate>
		<guid isPermaLink="false">http://journal.code4lib.org/articles/86#comment-205</guid>
		<description><![CDATA[Love the idea and I&#039;ve been arguing for something similar for a while.  (I&#039;d love a change history for our records).

One other possible issue that popped into my head this weekend is the possibility two different records get created for the same resource at about the same time in two different libraries.  

Say Susan at X makes a record for &quot;How to conquer the world in thirty days; by Khan&quot;.  Bill at Y got the book around the same week or so and Susan hadn&#039;t actually submitted her file (1234.mrc) upstream yet.  Bill doesn&#039;t find any existing records and creates a new one as well (24444.mrc).  Now we start getting fragmentation.

The way most dvcs work on is based off filename I believe.  This could be an issue if each institution assigns a record for the same source with different conventions.  We could try to use an identifier with ways of correcting for conflicts with identical isbns in different books, etc.

This makes me a little worried we&#039;d have to do some custom tweaking of a dvcs, which might be nightmarish.  I suppose we&#039;ll probably need to create custom searches and indexes anyhow from the system, but we can reuse some tools for that.]]></description>
		<content:encoded><![CDATA[<p>Love the idea and I&#8217;ve been arguing for something similar for a while.  (I&#8217;d love a change history for our records).</p>
<p>One other possible issue that popped into my head this weekend is the possibility two different records get created for the same resource at about the same time in two different libraries.  </p>
<p>Say Susan at X makes a record for &#8220;How to conquer the world in thirty days; by Khan&#8221;.  Bill at Y got the book around the same week or so and Susan hadn&#8217;t actually submitted her file (1234.mrc) upstream yet.  Bill doesn&#8217;t find any existing records and creates a new one as well (24444.mrc).  Now we start getting fragmentation.</p>
<p>The way most dvcs work on is based off filename I believe.  This could be an issue if each institution assigns a record for the same source with different conventions.  We could try to use an identifier with ways of correcting for conflicts with identical isbns in different books, etc.</p>
<p>This makes me a little worried we&#8217;d have to do some custom tweaking of a dvcs, which might be nightmarish.  I suppose we&#8217;ll probably need to create custom searches and indexes anyhow from the system, but we can reuse some tools for that.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
