Julie,<br><br>Do you know if users were doing *Google* searches (as opposed to Google Scholar searches)?<br>I didn't turn up any bitstream results in Google Scholar, but there are plenty in Google proper.<br><br>For instance, I get "about 908" results by searching Google for
<br>site://scholarworks.iu.edu/dspace/bitstream/<br>For examples of searches that retrieve both bitstreams and metadata records, a search for<br>site://scholarworks.iu.edu/dspace/ <br>yields "about 6190" results.
<br><br>Here are two examples of a bitstream appearing with higher rank than its metadata record. In these cases I couldn't find the metadata record in the search results. YMMV.<br><br>-Jodi<br><br>1)<font size="-1"><span class="a">
The 14th result in a Google search for <br>"indiana geological survey" site://scholarworks.iu.edu/dspace/<br></span></font><font size="-1"><span class="a">is a bitstream:</span></font><font size="-1"><b></b><br>
<span class="a"><a href="https://scholarworks.iu.edu/dspace/bitstream/2022/432/1/Steinmetz+et+al+Data+Preservation+at+GSA+23Oct06.ppt">https://scholarworks.iu.edu/dspace/bitstream/2022/432/1/Steinmetz+et+al+Data+Preservation+at+GSA+23Oct06.ppt
</a> </span><a class="fl" href="http://www.google.com/search?hl=en&lr=&client=firefox-a&channel=s&rls=org.mozilla:en-US:official&as_qdr=all&q=related:https://scholarworks.iu.edu/dspace/bitstream/2022/432/1/Steinmetz%2Bet%2Bal%2BData%2BPreservation%2Bat%2BGSA%2B23Oct06.ppt">
</a><span class="bl"></span></font><br><br>I could not find the metadata record ( <a href="http://hdl.handle.net/2022/432">http://hdl.handle.net/2022/432</a> aka <a href="https://scholarworks.iu.edu/dspace/handle/2022/432">
https://scholarworks.iu.edu/dspace/handle/2022/432</a> ) in the (about 187) search results.<br><br>Results in Google Scholar are, of course, different. (No site search is possible there.)<br>"indiana geological survey" author:j-steinmetz
<br>gives the metadata record as the third result.<br>----------------------------------------------------------------------<br><div><font size="-1"><span class="a">2) A Google search for<br>site://scholarworks.iu.edu/dspace/
</span></font><font size="-1"><span class="a"></span></font><br>gives a bitstream as the sixth result:<br><font size="-1"><span class="a"><a href="https://scholarworks.iu.edu/dspace/bitstream/2022/226/1/B42D.pdf">https://scholarworks.iu.edu/dspace/bitstream/2022/226/1/B42D.pdf
</a><br>
</span></font><br>Metadata record is at <a href="http://hdl.handle.net/2022/226">http://hdl.handle.net/2022/226</a> AKA <a href="https://scholarworks.iu.edu/dspace/handle/2022/226/">https://scholarworks.iu.edu/dspace/handle/2022/226/
</a><br>AKA <a href="https://scholarworks.iu.edu/dspace/handle/2022/226/1">https://scholarworks.iu.edu/dspace/handle/2022/226/1</a><br><font size="-1">I didn't turn up the metadata record in the first 1000 (of "about 6,190"
</font>) Google results.<br><strong><code></code></strong><br>I did not find it in Google Scholar by (for instance)<br><font size="-1"><span class="a">author:Carr,DD sand indiana<br>
</span></font><br><font size="-1"><span class="a"></span></font><br><span class="gmail_quote"><br><br>On 6/19/07, <b class="gmail_sendername">MacKenzie Smith</b> <<a href="mailto:kenzie@mit.edu">kenzie@mit.edu</a>> wrote:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Julie,<br><br>This is very interesting... Google Scholar's indexing of item metadata
<br>vs bitstreams has evolved over the years. Early on they thought users<br>were absolutely not interested in seeing item records -- they want to go<br>directly to the bitstreams -- but I think that belief has changed and
<br>now they are definitely indexing both item metadata and bitstreams.<br><br>In this case, I wasn't able to reproduce the problem in Google Scholar.<br>I searched by terms that were only in the metadata and only in the PDF,
<br>and in all cases GS took me to the item record first... I couldn't find<br>a search that took me directly to the bitstream (although I've seen that<br>behavior in the past). Do you know how your user got to that result?
<br><br>Anyway, assuming there are still cases where GS takes the user directly<br>to the bitstream, I think they'd be interested in your feedback. The<br>particular bitstream you provided is a great example of why a user might
<br>need to go through an item record... the bitstream has absolutely no<br>embedded metadata or other context to help the user figure out what<br>they're looking at.<br><br>Maybe Rob Tansley can also comment, or we can take this up again with
<br>Anurag at Google Scholar.<br><br>MacKenzie<br>><br>> We've had complaints from users who have found out-of-context DSpace<br>> documents with Google searches, such as<br>> _https://scholarworks.iu.edu/dspace/bitstream/2022/1333/1/7(1)81-
82.pdf_<br>> <<a href="https://scholarworks.iu.edu/dspace/bitstream/2022/1333/1/7%281%2981-82.pdf">https://scholarworks.iu.edu/dspace/bitstream/2022/1333/1/7%281%2981-82.pdf</a>><br>><br>><br>> There is, of course, a DSpace metadata record, but the Google search
<br>> retrieves the document itself with no link to the metadata record.<br>> We're considering disallowing access to the bitstream path so that<br>> users will not be confronted with raw documents with no metadata
<br>> context, but do not want to lose the full-text searching<br>> functionality. Has anyone found a solution to this problem?<br>><br>> Thanks in advance for help.<br>><br>> Julie Bobay, Director for Scholarly Communication Initiatives
<br>> Indiana University Bloomington Libraries<br>> Wells Library E1060<br>> Bloomington, IN 47405<br>> 812-855-7743<br>><br><br><br>--<br>MacKenzie Smith<br>Associate Director for Technology<br>MIT Libraries
<br><br>_______________________________________________<br>Dspace-general mailing list<br><a href="mailto:Dspace-general@mit.edu">Dspace-general@mit.edu</a><br><a href="http://mailman.mit.edu/mailman/listinfo/dspace-general">
http://mailman.mit.edu/mailman/listinfo/dspace-general</a><br></blockquote></div><br>