<?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"
	>
<channel>
	<title>Comments on: More on Repositories</title>
	<atom:link href="http://www.logicaloperator.net/2008/06/more-on-repositories/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.logicaloperator.net/2008/06/more-on-repositories/</link>
	<description></description>
	<pubDate>Fri, 21 Nov 2008 17:48:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Logical Operator</title>
		<link>http://www.logicaloperator.net/2008/06/more-on-repositories/#comment-10</link>
		<dc:creator>Logical Operator</dc:creator>
		<pubDate>Mon, 16 Jun 2008 13:16:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.logicaloperator.net/?p=12#comment-10</guid>
		<description>Peter, thanks for commenting. I totally agree - I was looking it from the "holy grail" viewpoint, where anything we create as scholars could be automagically sucked into the repository just because we wanted it to happen. Of course, practically, there's a) no system that will be completely transparent, b) no such system, and c) no reason to encourage outmoded (or inefficient) workflows.

I think the trick is convincing people the workflow &lt;i&gt;should&lt;/i&gt; change! But if there's real value in the new workflow we present, then I think that trick is a little easier to pull off. Your point is well taken.</description>
		<content:encoded><![CDATA[<p>Peter, thanks for commenting. I totally agree - I was looking it from the &#8220;holy grail&#8221; viewpoint, where anything we create as scholars could be automagically sucked into the repository just because we wanted it to happen. Of course, practically, there&#8217;s a) no system that will be completely transparent, b) no such system, and c) no reason to encourage outmoded (or inefficient) workflows.</p>
<p>I think the trick is convincing people the workflow <i>should</i> change! But if there&#8217;s real value in the new workflow we present, then I think that trick is a little easier to pull off. Your point is well taken.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PT&#8217;s blog &#187; Blog Archive &#187; More on negative click or net benefit repositories</title>
		<link>http://www.logicaloperator.net/2008/06/more-on-repositories/#comment-9</link>
		<dc:creator>PT&#8217;s blog &#187; Blog Archive &#187; More on negative click or net benefit repositories</dc:creator>
		<pubDate>Mon, 16 Jun 2008 04:03:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.logicaloperator.net/?p=12#comment-9</guid>
		<description>[...] the proposal we put, which seems to be along the lines of what Chris from the Logical Operator blog suggested in response to Chris R. From our proposal:The goal of this project is to build a smart user-friendly repository ingest [...]</description>
		<content:encoded><![CDATA[<p>[...] the proposal we put, which seems to be along the lines of what Chris from the Logical Operator blog suggested in response to Chris R. From our proposal:The goal of this project is to build a smart user-friendly repository ingest [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Sefton</title>
		<link>http://www.logicaloperator.net/2008/06/more-on-repositories/#comment-8</link>
		<dc:creator>Peter Sefton</dc:creator>
		<pubDate>Mon, 16 Jun 2008 03:02:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.logicaloperator.net/?p=12#comment-8</guid>
		<description>I pretty much agree with your approach, including the desire to build a scholarly workbench application, but in my own reply to Chris R's 'Negative click' post I wanted to make the point that there are some workflows that are not going to work.

You say:
# Integrates with any workflow
# Involves no (or essentially no) extra activities on the part of the scholar

I think this needs to be looked at in a broader context. Some workflows are not worth encouraging eg if you had people who wanted to type things on paper then have it entered into a word processor then you'd go and help them. A lot of researchers are using their word processors as typewriters and in the process throwing away of lot of stuff they could capture as they write, like document structure, or labels on diagrams.

There's no reason that users can't do new stuff - it just has to be worth it, and displace some of the old stuff they used to do. If all we're going to do is tie into workflows that should be changing anyway then we may as well give up.</description>
		<content:encoded><![CDATA[<p>I pretty much agree with your approach, including the desire to build a scholarly workbench application, but in my own reply to Chris R&#8217;s &#8216;Negative click&#8217; post I wanted to make the point that there are some workflows that are not going to work.</p>
<p>You say:<br />
# Integrates with any workflow<br />
# Involves no (or essentially no) extra activities on the part of the scholar</p>
<p>I think this needs to be looked at in a broader context. Some workflows are not worth encouraging eg if you had people who wanted to type things on paper then have it entered into a word processor then you&#8217;d go and help them. A lot of researchers are using their word processors as typewriters and in the process throwing away of lot of stuff they could capture as they write, like document structure, or labels on diagrams.</p>
<p>There&#8217;s no reason that users can&#8217;t do new stuff - it just has to be worth it, and displace some of the old stuff they used to do. If all we&#8217;re going to do is tie into workflows that should be changing anyway then we may as well give up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Logical Operator</title>
		<link>http://www.logicaloperator.net/2008/06/more-on-repositories/#comment-7</link>
		<dc:creator>Logical Operator</dc:creator>
		<pubDate>Fri, 13 Jun 2008 15:31:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.logicaloperator.net/?p=12#comment-7</guid>
		<description>I'm glad it clicked! I just wanted to make sure I didn't tromp any toes out there. We all help each other climb higher, after all.

-Chris</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad it clicked! I just wanted to make sure I didn&#8217;t tromp any toes out there. We all help each other climb higher, after all.</p>
<p>-Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Sheppard</title>
		<link>http://www.logicaloperator.net/2008/06/more-on-repositories/#comment-6</link>
		<dc:creator>Nick Sheppard</dc:creator>
		<pubDate>Fri, 13 Jun 2008 15:29:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.logicaloperator.net/?p=12#comment-6</guid>
		<description>Hi Chris

I appreciate the "modular" approach wasn't your idea per se and I have also been reading around some of the other blogs but your explication switched on a little light-bulb in my head; possibly just a late Friday afternoon phenomenon!</description>
		<content:encoded><![CDATA[<p>Hi Chris</p>
<p>I appreciate the &#8220;modular&#8221; approach wasn&#8217;t your idea per se and I have also been reading around some of the other blogs but your explication switched on a little light-bulb in my head; possibly just a late Friday afternoon phenomenon!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Modular repository? &#171; PERSoNA News</title>
		<link>http://www.logicaloperator.net/2008/06/more-on-repositories/#comment-5</link>
		<dc:creator>Modular repository? &#171; PERSoNA News</dc:creator>
		<pubDate>Fri, 13 Jun 2008 14:58:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.logicaloperator.net/?p=12#comment-5</guid>
		<description>[...] by Nick on June 13, 2008  Here is an interesting post from www.logicaloperator.net suggesting the idea of a modular repository that integrates a variety of specialised [...]</description>
		<content:encoded><![CDATA[<p>[...] by Nick on June 13, 2008  Here is an interesting post from <a href="http://www.logicaloperator.net" rel="nofollow">http://www.logicaloperator.net</a> suggesting the idea of a modular repository that integrates a variety of specialised [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
