Just to add a few notes to Peter's detailed examples... On 11/6/2013 10:07 AM, Peter Dietz wrote: > I would say DSpace is doing a "good" job of producing Scholar tags > (highwire) for the most part. There are some edge cases, as mentioned > above by others, that other systems could be doing a better job. I don't > know enough about (EPrints / BePress) scholar support to weigh in. There > is a config setting > https://github.com/DSpace/DSpace/blob/master/dspace/config/crosswalks/google-metadata.properties > that you will NEED to modify to map your custom metadata profile, to > Google Scholar (highwire) metadata fields. > > Citing specific examples, DSpace out-of-the-box, only supports mapping > to the citation_pdf_url, when you only have one bitstream, and it is a > PDF, in the ORIGINAL bundle. In any other circumstance, it will punt, > and not add a citation_pdf_url. > > The reason for that is if you have multiple PDF's, DSpace doesn't have > enough information to know which one is the "best" PDF that contains > your article. Or, in other cases, people use multiple bundles to store > their content. Or, you have multiple formats available, such as word, > text/latex, and again, DSpace can't say which one is the best. So, if > you are deviating from the simple use-case, then you'll need to > customize the logic for determining the citation_pdf_url, likely > altering some Java code to do so.
There's a proposed fix/change for this "citation_pdf_url" logic (which was requested by Google Scholar folks) for the upcoming DSpace 4.0...see comments in: https://jira.duraspace.org/browse/DS-1483 (So this may be improved in DSpace 4.0...it's a proposed bug fix we are looking into right now.) > Another example of things that Scholar doesn't like is the > dc.date.issued being set to the date submitted (i.e. today's date, if > you just submitted). So, if that article you just submitted was actually > published elsewhere a few months ago, but the version you submit to your > IR has today's date, then scholar has conflicting information about the > Date of that article, and doesn't think of them as multiple > versions/sources of the same content. DSpace 4.0 has some changes > regarding that, as it tries not to add date.issued of today, for > anything that you mark as previously published. As Peter mentions, this is already improved in the upcoming DSpace 4.0 release. For details see the most recent comments on: https://jira.duraspace.org/browse/DS-1481 So, these are two great examples of where Google Scholar has talked with us about possible improvements to DSpace (based on issues Google has run into) and we've taken that feedback and made fixes/improvements in the next release of DSpace. It also is a great example of why it's important to stay up-to-date with DSpace releases, if you want the latest and greatest Google Scholar improvements. We are constantly tweaking DSpace for better Search Engine Optimization (and based on feedback directly from Google and others). So, if you are on an older version of DSpace, it often is not as "optimized" as more recent versions. - Tim ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
