<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Thinking about Our Fedora Disseminators</title>
	<atom:link href="http://dltj.org/article/fedora-disseminators/feed/" rel="self" type="application/rss+xml" />
	<link>http://dltj.org/article/fedora-disseminators/</link>
	<description>We&#039;re Disrupted, We&#039;re Librarians, and We&#039;re Not Going to Take It Anymore</description>
	<lastBuildDate>Thu, 02 Sep 2010 08:58:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Disruptive Library Technology Jester :: Building an Institutional Repository Interface Using EJB3 and JBoss Seam</title>
		<link>http://dltj.org/article/fedora-disseminators/comment-page-1/#comment-11285</link>
		<dc:creator>Disruptive Library Technology Jester :: Building an Institutional Repository Interface Using EJB3 and JBoss Seam</dc:creator>
		<pubDate>Fri, 19 Jan 2007 04:01:33 +0000</pubDate>
		<guid isPermaLink="false">http://dltj.org/2006/05/fedora-disseminators/#comment-11285</guid>
		<description>[...] The paradigm of handling different media types within the DRC application is guided in large part by the notion of disseminators for FEDORA objects and the Digital Library Federation Aquifer Asset Actions experiments. The underlying concept is to push the media-specific content handling into the digital object repository and to have the presentation interface consume those content handlers as it is preparing the end-user presentation. [...]</description>
		<content:encoded><![CDATA[<p>[...] The paradigm of handling different media types within the DRC application is guided in large part by the notion of disseminators for FEDORA objects and the Digital Library Federation Aquifer Asset Actions experiments. The underlying concept is to push the media-specific content handling into the digital object repository and to have the presentation interface consume those content handlers as it is preparing the end-user presentation. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OhioLINK Disseminators - FedoraWiki</title>
		<link>http://dltj.org/article/fedora-disseminators/comment-page-1/#comment-3793</link>
		<dc:creator>OhioLINK Disseminators - FedoraWiki</dc:creator>
		<pubDate>Mon, 11 Sep 2006 21:42:25 +0000</pubDate>
		<guid isPermaLink="false">http://dltj.org/2006/05/fedora-disseminators/#comment-3793</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] There is [some background material] leading up to this perspective that may be useful to review. (It also has a general discussion about what disseminators are and why they are important.) Keep in mind that OhioLINK’s Fedora repository vision doesn’t expect to have one front end; rather we anticipate getting to the repository data from a number of genre-, topic-, or technology-specific interfaces. In doing so, a lot of the intelligence about how to handle media types needs to go into the disseminators. With this perspective, one thinks about how an object can present itself in generic ways to a wide variety of interfaces. The name/label of a disseminator in the repository has three parts:   action  presentation  optional sizing parameters [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><a href="http://dev.wp-plugins.org/wiki/Kramer"><img src="http://dltj.org/wp-content/plugins/kramer/kramer.php?kramer=gif-icon" class="technorati-balloon" alt="Kramer auto Pingback" style="border:0;" /></a>[...] There is [some background material] leading up to this perspective that may be useful to review. (It also has a general discussion about what disseminators are and why they are important.) Keep in mind that OhioLINK’s Fedora repository vision doesn’t expect to have one front end; rather we anticipate getting to the repository data from a number of genre-, topic-, or technology-specific interfaces. In doing so, a lot of the intelligence about how to handle media types needs to go into the disseminators. With this perspective, one thinks about how an object can present itself in generic ways to a wide variety of interfaces. The name/label of a disseminator in the repository has three parts:   action  presentation  optional sizing parameters [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Disruptive Library Technology Jester :: Analysis of CDL&#8217;s XTF textIndexer to Replace the Local Files with FEDORA Objects</title>
		<link>http://dltj.org/article/fedora-disseminators/comment-page-1/#comment-2996</link>
		<dc:creator>Disruptive Library Technology Jester :: Analysis of CDL&#8217;s XTF textIndexer to Replace the Local Files with FEDORA Objects</dc:creator>
		<pubDate>Wed, 23 Aug 2006 01:17:35 +0000</pubDate>
		<guid isPermaLink="false">http://dltj.org/2006/05/fedora-disseminators/#comment-2996</guid>
		<description>[...] just the XML transformation tool would be needed (as in this snipped from SrcTreeProcessor.java): &#182; PLAIN TEXT JAVA:  IndexSource srcFile = null; if&#040; format.equalsIgnoreCase&#040;&quot;XML&quot;&#041; &#041;&#123; &#160; &#160; InputSource finalSrc = new InputSource&#040; systemId &#041;; &#160; &#160; srcFile = new XMLIndexSource&#040; finalSrc, srcPath, key,  &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;preFilters, displayStyle, lazyStore &#041;; &#160; &#160; if&#040; removeDoctypeDecl &#041; &#160; &#160; &#160; &#160; &#040;&#040;XMLIndexSource&#041;srcFile&#041;.removeDoctypeDecl&#040; true &#041;; &#125; [...]</description>
		<content:encoded><![CDATA[<p>[...] just the XML transformation tool would be needed (as in this snipped from SrcTreeProcessor.java): &#182; PLAIN TEXT JAVA:  IndexSource srcFile = null; if&#40; format.equalsIgnoreCase&#40;&#8221;XML&#8221;&#41; &#41;&#123; &nbsp; &nbsp; InputSource finalSrc = new InputSource&#40; systemId &#41;; &nbsp; &nbsp; srcFile = new XMLIndexSource&#40; finalSrc, srcPath, key,  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;preFilters, displayStyle, lazyStore &#41;; &nbsp; &nbsp; if&#40; removeDoctypeDecl &#41; &nbsp; &nbsp; &nbsp; &nbsp; &#40;&#40;XMLIndexSource&#41;srcFile&#41;.removeDoctypeDecl&#40; true &#41;; &#125; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Disruptive Library Technology Jester &#187; Fedora Disseminators to Enable Accessible Repository Content</title>
		<link>http://dltj.org/article/fedora-disseminators/comment-page-1/#comment-60</link>
		<dc:creator>Disruptive Library Technology Jester &#187; Fedora Disseminators to Enable Accessible Repository Content</dc:creator>
		<pubDate>Sat, 06 May 2006 03:04:30 +0000</pubDate>
		<guid isPermaLink="false">http://dltj.org/2006/05/fedora-disseminators/#comment-60</guid>
		<description>[...] why not? Let&#8217;s look back at the &#8220;presentation&#8221; part of the disseminator label: &#182;  A presentation can be oneof: [...]</description>
		<content:encoded><![CDATA[<p>[...] why not? Let&#8217;s look back at the &#8220;presentation&#8221; part of the disseminator label: &#182;  A presentation can be oneof: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the jester</title>
		<link>http://dltj.org/article/fedora-disseminators/comment-page-1/#comment-53</link>
		<dc:creator>the jester</dc:creator>
		<pubDate>Wed, 03 May 2006 17:14:36 +0000</pubDate>
		<guid isPermaLink="false">http://dltj.org/2006/05/fedora-disseminators/#comment-53</guid>
		<description>Muriel -- very interesting work!  Thanks for passing it along.  I took a quick look at the Asset Actions page (it took me a while to figure out that I had to search the collection at the top to see any of the enhancements rather than use the links to the raw collection websites at the bottom) and then printed out the documents to read over lunch.  It sounds like there is a lot of thought here about actions that can be applied to objects, so I&#039;m going to dig deeper.</description>
		<content:encoded><![CDATA[<p>Muriel &#8212; very interesting work!  Thanks for passing it along.  I took a quick look at the Asset Actions page (it took me a while to figure out that I had to search the collection at the top to see any of the enhancements rather than use the links to the raw collection websites at the bottom) and then printed out the documents to read over lunch.  It sounds like there is a lot of thought here about actions that can be applied to objects, so I&#8217;m going to dig deeper.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Muriel Foulonneau</title>
		<link>http://dltj.org/article/fedora-disseminators/comment-page-1/#comment-51</link>
		<dc:creator>Muriel Foulonneau</dc:creator>
		<pubDate>Tue, 02 May 2006 23:04:13 +0000</pubDate>
		<guid isPermaLink="false">http://dltj.org/2006/05/fedora-disseminators/#comment-51</guid>
		<description>A sub-group of Fedora adopters and the Digital Library Federation working Group has been working on expanding the Fedora disseminator. We have experimented [an expression of] those disseminators for images with content harvested through OAI. The demonstrator is here http://rama.grainger.uiuc.edu/assetactions/, it integrates the Collector tool developed at Virginia on distributed content, whichever the system used. I am working on a way of generating those disseminators based on OAI records and an application developed by Tom Habing here at UIUC to generate thumbnails (same model as Alexa and Thumbshots.org but for OAI records).
All this to say that generally, we are trying to do something like that and any help and feedback would be useful.</description>
		<content:encoded><![CDATA[<p>A sub-group of Fedora adopters and the Digital Library Federation working Group has been working on expanding the Fedora disseminator. We have experimented [an expression of] those disseminators for images with content harvested through OAI. The demonstrator is here <a href="http://rama.grainger.uiuc.edu/assetactions/" rel="nofollow">http://rama.grainger.uiuc.edu/assetactions/</a>, it integrates the Collector tool developed at Virginia on distributed content, whichever the system used. I am working on a way of generating those disseminators based on OAI records and an application developed by Tom Habing here at UIUC to generate thumbnails (same model as Alexa and Thumbshots.org but for OAI records).<br />
All this to say that generally, we are trying to do something like that and any help and feedback would be useful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: τεχνοσοφια &#187; The Jester&#8217;s Case for Fedora</title>
		<link>http://dltj.org/article/fedora-disseminators/comment-page-1/#comment-50</link>
		<dc:creator>τεχνοσοφια &#187; The Jester&#8217;s Case for Fedora</dc:creator>
		<pubDate>Tue, 02 May 2006 21:57:14 +0000</pubDate>
		<guid isPermaLink="false">http://dltj.org/2006/05/fedora-disseminators/#comment-50</guid>
		<description>[...] The third piece, Thinking about Our Fedora Disseminators, highlights Fedora as a repository system that&#8217;s put real emphasis on digital preservation.  While other repository systems allow for preservation of an object and its metadata, Fedora grants one the ability to preserve the behavior of digital objects and the datastreams thereof, a potential approach to the issue of format migration/emulation.  Through a dissemination abstraction (the &#8220;behavior definition&#8221;) one might apply the same abstract behaviors to items in different formats, saving one the time of defining redundant behaviors.  My explanation is rather vague and incomplete, so I would encourage you to read Peter&#8217;s third piece in detail.  The point is that &#8220;for each record, the application simply asked the repository to deliver a thumbnail of the object. And the repository, regardless of media type, delivered one.&#8221;  [...]</description>
		<content:encoded><![CDATA[<p>[...] The third piece, Thinking about Our Fedora Disseminators, highlights Fedora as a repository system that&#8217;s put real emphasis on digital preservation.  While other repository systems allow for preservation of an object and its metadata, Fedora grants one the ability to preserve the behavior of digital objects and the datastreams thereof, a potential approach to the issue of format migration/emulation.  Through a dissemination abstraction (the &#8220;behavior definition&#8221;) one might apply the same abstract behaviors to items in different formats, saving one the time of defining redundant behaviors.  My explanation is rather vague and incomplete, so I would encourage you to read Peter&#8217;s third piece in detail.  The point is that &#8220;for each record, the application simply asked the repository to deliver a thumbnail of the object. And the repository, regardless of media type, delivered one.&#8221;  [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
