<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=windows-1252"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Helvetica, Arial, sans-serif">Hi Pat! (copy to Roger
Costello, proposer of HTTP "Meta-Location" header, that may help make
this discussion fruitful)<br>
<br>
I like very much your idea: for a given URL, there should be a standard
"derivation" to get its metadata / context.<br>
<br>
In an HTML document, we could have a <LINK with rel=link type:<br>
<a class="moz-txt-link-freetext" href="http://www.w3.org/TR/html401/types.html#type-links">http://www.w3.org/TR/html401/types.html#type-links</a><br>
But no "Metadata" type! May be "Index" could be used.<br>
This document suggests to use REL="META"<br>
<a class="moz-txt-link-freetext" href="http://vancouver-webpages.com/ml/draft-daviel-metadata-link-00.txt">http://vancouver-webpages.com/ml/draft-daviel-metadata-link-00.txt</a><br>
<br>
There is also the PROFILE attribute of the <HEAD<br>
<a class="moz-txt-link-freetext" href="http://www.w3.org/TR/html401/struct/global.html#h-7.4.4.3">http://www.w3.org/TR/html401/struct/global.html#h-7.4.4.3</a><br>
Anyway, we mainly store PDF (and not HTML documents) and we usually
cannot change the content of the documents we receive...<br>
<br>
I just checked and I see no HTTP verb or Header field that could carry
this "content independent" information<br>
<a class="moz-txt-link-freetext" href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html">http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html</a><br>
<br>
Idealy, "derivation" toward metadata should be done through HTTP (which
is content independent).<br>
May be one day the ACCEPT header could contain metadata/html (instead
of text/html) to indicate that metadata is requested and not the text
(content).<br>
<br>
People in W3C seem to discuss this:<br>
<a class="moz-txt-link-freetext" href="http://osdir.com/ml/org.w3c.tag/2003-02/msg00247.html">http://osdir.com/ml/org.w3c.tag/2003-02/msg00247.html</a><br>
They propose a new HTTP header: Meta-Location<br>
<a class="moz-txt-link-freetext" href="http://www.xfront.com/dist-reg/distributed-registry.html">http://www.xfront.com/dist-reg/distributed-registry.html</a><br>
So we will see in the future versions of HTTP...<br>
<br>
For now, does anybody controls the relation with Google so they could
add to their DSpace awareness a "Metadata" link to the document hit
indication, linking<br>
</font>
<pre wrap=""><font face="Helvetica, Arial, sans-serif"><a class="moz-txt-link-freetext" href="https://pacer.ischool.utexas.edu/bitstream/2081/859/1/Arrangement.doc">https://pacer.ischool.utexas.edu/bitstream/2081/859/1/Arrangement.doc</a>
</font></pre>
<font face="Helvetica, Arial, sans-serif">to<br>
</font>
<pre wrap=""><font face="Helvetica, Arial, sans-serif"><a class="moz-txt-link-freetext" href="https://pacer.ischool.utexas.edu/handle/2081/859">https://pacer.ischool.utexas.edu/handle/2081/859</a>
</font></pre>
<font face="Helvetica, Arial, sans-serif">Another idea would be to link
any incorrect bitstream to the metadata. Instead of sending :<br>
</font>
<h1><font color="#6633ff" face="Helvetica, Arial, sans-serif">Invalid
Identifier</font></h1>
<font color="#6633ff" face="Helvetica, Arial, sans-serif">The
identifier 2081/859/1/Arransqdsqd does not correspond to a valid
Bitstream in DSpace</font><font face="Helvetica, Arial, sans-serif"><br>
<br>
we could simply show the metadata page. So any corruption to the end of
the URL would help the user by showing the metadata record.<br>
Especially:<br>
</font>
<pre wrap=""><font face="Helvetica, Arial, sans-serif"><a class="moz-txt-link-freetext" href="https://pacer.ischool.utexas.edu/bitstream/2081/859/1/">https://pacer.ischool.utexas.edu/bitstream/2081/859/1/</a>
<big>and</big>
<a class="moz-txt-link-freetext" href="https://pacer.ischool.utexas.edu/bitstream/2081/859/">https://pacer.ischool.utexas.edu/bitstream/2081/859/</a>
<big>should return the metadata as it is usual to remove level to an URL to get an upper level Table of Content.</big>
<big>May be this (removing a level to an URL) could be a standard "URL based" way to go from a document to its context.
But, I know, Index is not Metadata ! To be implemented by Google? For DSpace?
For other sites, as a default generic method to contextualize a document???
Have a nice evening,
Christophe Dupriez
P.S. Mr.Costello site, XFront.com, seems packed up with interesting XSLT tutorials...</big>
</font></pre>
<br>
Pat Galloway a écrit :
<blockquote cite="mid467A8D34.3050001@ischool.utexas.edu" type="cite">
<pre wrap="">After having read the original post on this topic I was more than a
little concerned because we have restricted materials on our server; but
I tested using text in restricted Microsoft Word files and found no
hits; the same day, however, I retrieved on this string "Michael
Joyce—Arrangement-4/20/2005" which was the first text string in an
unrestricted Word document (but not in the DSPace metadata), and got
this result using regular Google search:
[DOC] Michael Joyce--ArrangementFile Format: Microsoft Word - View as HTML
Michael Joyce—Arrangement-4/20/2005 (updated 05/01/2005). Series I.
Works. (Subseries for each title). Series II. Academic Career ...
<a class="moz-txt-link-freetext" href="https://pacer.ischool.utexas.edu/bitstream/2081/859/1/Arrangement.doc">https://pacer.ischool.utexas.edu/bitstream/2081/859/1/Arrangement.doc</a>
Obviously if you go here it is impossible to get to the metadata unless
you know to sever the last two filepath elements. Clearly this might be
a concern for many reasons; but I was in the midst of writing an article
for Library Trends on archives and information retrieval, and found it
interesting (in the context of archival discussions about "exploding"
the authority of the finding aid) that opening DSpace to Web 2.0 permits
this broader, deracinated granular access. I would hope that it NOT be
made impossible, either on the DSpace or the Google side; just that
(since Google is DSpace-aware) the searcher be shown how to get the
metadata if indeed it is wanted for the searcher's purposes. Too often
we think it's up to us to determine what researchers need and want. Has
anyone heard any complaints from them?
Pat Galloway
School of Information
UNiversity of Texas
_______________________________________________
Dspace-general mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Dspace-general@mit.edu">Dspace-general@mit.edu</a>
<a class="moz-txt-link-freetext" href="http://mailman.mit.edu/mailman/listinfo/dspace-general">http://mailman.mit.edu/mailman/listinfo/dspace-general</a>
</pre>
</blockquote>
<br>
</body>
</html>