<?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: Best Practice Proposal for a DESCRIPTION Datastream</title> <atom:link href="http://dltj.org/article/description-datastream/feed/" rel="self" type="application/rss+xml" /><link>http://dltj.org/article/description-datastream/</link> <description>We&#039;re Disrupted, We&#039;re Librarians, and We&#039;re Not Going to Take It Anymore</description> <lastBuildDate>Tue, 22 May 2012 19:03:41 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>By: Re: [Fedora-commons-users] Where to store things you need to search?</title><link>http://dltj.org/article/description-datastream/comment-page-1/#comment-45242</link> <dc:creator>Re: [Fedora-commons-users] Where to store things you need to search?</dc:creator> <pubDate>Mon, 22 Feb 2010 10:46:35 +0000</pubDate> <guid isPermaLink="false">http://dltj.org/2006/09/description-datastream/#comment-45242</guid> <description>&lt;!--%kramer-ref-pre%--&gt;[...] Steve. I also ran across this quotation at http://dltj.org/article/description-datastream/ &quot;working with Fedora&#039;s compulsory Dublin Core (DC) datastream started one thinking about the [...]&lt;!--%kramer-ref-post%--&gt;</description> <content:encoded><![CDATA[<p><img src="http://cdn.dltj.org/wp-content/plugins/kramer/kramer.gif" class="technorati-balloon" alt="Kramer auto Pingback" style="border:0;" />[...] Steve. I also ran across this quotation at <a href="http://dltj.org/article/description-datastream/" rel="nofollow">http://dltj.org/article/description-datastream/</a> &quot;working with Fedora&#39;s compulsory Dublin Core (DC) datastream started one thinking about the [...]</p> ]]></content:encoded> </item> <item><title>By: Sergio Berna</title><link>http://dltj.org/article/description-datastream/comment-page-1/#comment-5730</link> <dc:creator>Sergio Berna</dc:creator> <pubDate>Tue, 17 Oct 2006 14:24:21 +0000</pubDate> <guid isPermaLink="false">http://dltj.org/2006/09/description-datastream/#comment-5730</guid> <description>[quote post=&quot;109&quot;]“to establish a practice of creating an in-line XML2 datastream with the label ‘DESCRIPTION’ that contains the primary descriptive metadata for each object.”[/quote]Interesting proposal. Do you know of any recopilation project of these denominations of fedora inline datastreams?In my case I have need for several descriptive datastreams. That need a richer vocabulary.The first datastream would be the descriptive datastream, using the tag you propose.Then would follow preservation datastreams, Rights management datastream, format especification datastream, relations management datastream and many more that maybe thinking a little ahead could be equally named such as your proposal implies.</description> <content:encoded><![CDATA[<p>[quote post="109"]“to establish a practice of creating an in-line XML2 datastream with the label ‘DESCRIPTION’ that contains the primary descriptive metadata for each object.”[/quote]</p><p>Interesting proposal. Do you know of any recopilation project of these denominations of fedora inline datastreams?</p><p>In my case I have need for several descriptive datastreams. That need a richer vocabulary.</p><p>The first datastream would be the descriptive datastream, using the tag you propose.</p><p>Then would follow preservation datastreams, Rights management datastream, format especification datastream, relations management datastream and many more that maybe thinking a little ahead could be equally named such as your proposal implies.</p> ]]></content:encoded> </item> <item><title>By: the jester</title><link>http://dltj.org/article/description-datastream/comment-page-1/#comment-3840</link> <dc:creator>the jester</dc:creator> <pubDate>Tue, 12 Sep 2006 16:32:12 +0000</pubDate> <guid isPermaLink="false">http://dltj.org/2006/09/description-datastream/#comment-3840</guid> <description>[quote comment=&quot;3837&quot;]At Indiana, we&#039;re keeping as little as possible in Fedora&#039;s default DC datastream, and lumping all other metadata into a METS document in a METDADATA datastream (&lt;a href=&quot;http://wiki.dlib.indiana.edu/confluence/x/uQE&quot; rel=&quot;nofollow&quot;&gt;philosophy&lt;/a&gt;, &lt;span class=&quot;removed_link&quot; title=&quot;http://fedora.dlib.indiana.edu:9090/fedora/get/iudl:4420&quot;&gt;sample object&lt;/span&gt;).[/quote]I would note for those that haven&#039;t followed the &quot;philosophy&quot; link, that &quot;as little as possible&quot; in Indiana&#039;s case is:&lt;blockquote&gt; It currently includes only these items:Title PURL for the object (if this is an item-level object) in an Identifier field Fedora PID for the object in an Identifier fieldThe &quot;real&quot; DC record (if present) will be in the [descriptive metadata] of the METS document, alongside any other descriptive metadata. &lt;a href=&quot;http://wiki.dlib.indiana.edu/confluence/pages/viewpage.action?pageId=441#FedoraMetadataStoragePhilosophy-DublinCore&quot; rel=&quot;nofollow&quot;&gt;http://wiki.dlib.indiana.edu/confluence/pages/viewpage.action?pageId=441#FedoraMetadataStoragePhilosophy-DublinCore&lt;/a&gt; &lt;/blockquote&gt; That certainly is bare-bones, but it makes a great deal of sense.Thanks for the comment and the links to the examples, Ryan!&lt;p style=&quot;padding:0;margin:0;font-style:italic;&quot; class=&quot;removed_link&quot;&gt;The text was modified to remove a link to http://fedora.dlib.indiana.edu:9090/fedora/get/iudl:4420 on January 19th, 2011.&lt;/p&gt;</description> <content:encoded><![CDATA[<p>[quote comment="3837"]At Indiana, we&#8217;re keeping as little as possible in Fedora&#8217;s default DC datastream, and lumping all other metadata into a METS document in a METDADATA datastream (<a href="http://wiki.dlib.indiana.edu/confluence/x/uQE" rel="nofollow">philosophy</a>, <span class="removed_link" title="http://fedora.dlib.indiana.edu:9090/fedora/get/iudl:4420">sample object</span>).[/quote]</p><p>I would note for those that haven&#8217;t followed the &#8220;philosophy&#8221; link, that &#8220;as little as possible&#8221; in Indiana&#8217;s case is:</p><blockquote><p> It currently includes only these items:</p><p>Title<br /> PURL for the object (if this is an item-level object) in an Identifier field<br /> Fedora PID for the object in an Identifier field</p><p>The &#8220;real&#8221; DC record (if present) will be in the [descriptive metadata] of the METS document, alongside any other descriptive metadata.<br /> <a href="http://wiki.dlib.indiana.edu/confluence/pages/viewpage.action?pageId=441#FedoraMetadataStoragePhilosophy-DublinCore" rel="nofollow">http://wiki.dlib.indiana.edu/confluence/pages/viewpage.action?pageId=441#FedoraMetadataStoragePhilosophy-DublinCore</a></p></blockquote><p>That certainly is bare-bones, but it makes a great deal of sense.</p><p>Thanks for the comment and the links to the examples, Ryan!<p style="padding:0;margin:0;font-style:italic;" class="removed_link">The text was modified to remove a link to <a href="http://fedora.dlib.indiana.edu:9090/fedora/get/iudl:4420" rel="nofollow">http://fedora.dlib.indiana.edu:9090/fedora/get/iudl:4420</a> on January 19th, 2011.</p> ]]></content:encoded> </item> <item><title>By: Ryan</title><link>http://dltj.org/article/description-datastream/comment-page-1/#comment-3837</link> <dc:creator>Ryan</dc:creator> <pubDate>Tue, 12 Sep 2006 15:58:13 +0000</pubDate> <guid isPermaLink="false">http://dltj.org/2006/09/description-datastream/#comment-3837</guid> <description>This is definitely a reasonable approach. Indiana, Tufts, and Virginia are all taking similar approaches. The only difference is in the details. At Indiana, we&#039;re keeping as little as possible in Fedora&#039;s default DC datastream, and lumping all other metadata into a METS document in a METDADATA datastream (&lt;a href=&quot;http://wiki.dlib.indiana.edu/confluence/x/uQE&quot; rel=&quot;nofollow&quot;&gt;philosophy&lt;/a&gt;, &lt;span class=&quot;removed_link&quot; title=&quot;http://fedora.dlib.indiana.edu:9090/fedora/get/iudl:4420&quot;&gt;sample object&lt;/span&gt;). Tufts keeps a fairly complete record in the default DC, but the fully-complete records are in DCA-ADMIN and DCA-META (&lt;a href=&quot;http://dl.tufts.edu:8080/fedora/get/tufts:UA069.005.DO.00001&quot; title=&quot;Sample Object&quot; rel=&quot;nofollow&quot;&gt;sample object&lt;/a&gt;). Virginia has their own metadata format, which can be found on their &lt;a href=&quot;http://www.lib.virginia.edu/digital/metadata/index.html&quot; rel=&quot;nofollow&quot;&gt;metadata site&lt;/a&gt;.&lt;p style=&quot;padding:0;margin:0;font-style:italic;&quot; class=&quot;removed_link&quot;&gt;The text was modified to remove a link to http://fedora.dlib.indiana.edu:9090/fedora/get/iudl:4420 on January 19th, 2011.&lt;/p&gt;</description> <content:encoded><![CDATA[<p>This is definitely a reasonable approach. Indiana, Tufts, and Virginia are all taking similar approaches. The only difference is in the details. At Indiana, we&#8217;re keeping as little as possible in Fedora&#8217;s default DC datastream, and lumping all other metadata into a METS document in a METDADATA datastream (<a href="http://wiki.dlib.indiana.edu/confluence/x/uQE" rel="nofollow">philosophy</a>, <span class="removed_link" title="http://fedora.dlib.indiana.edu:9090/fedora/get/iudl:4420">sample object</span>). Tufts keeps a fairly complete record in the default DC, but the fully-complete records are in DCA-ADMIN and DCA-META (<a href="http://dl.tufts.edu:8080/fedora/get/tufts:UA069.005.DO.00001" title="Sample Object" rel="nofollow">sample object</a>). Virginia has their own metadata format, which can be found on their <a href="http://www.lib.virginia.edu/digital/metadata/index.html" rel="nofollow">metadata site</a>.<p style="padding:0;margin:0;font-style:italic;" class="removed_link">The text was modified to remove a link to <a href="http://fedora.dlib.indiana.edu:9090/fedora/get/iudl:4420" rel="nofollow">http://fedora.dlib.indiana.edu:9090/fedora/get/iudl:4420</a> on January 19th, 2011.</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Served from: dltj.org @ 2012-05-23 01:58:16 by W3 Total Cache -->
