[
http://jira.dspace.org/jira/browse/DS-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Dietz updated DS-396:
---------------------------
Fix Version/s: 1.7
It would be good to resolve this, and any other "best practice" Scholar issues
in 1.7.
- Presenting best meta tags ( citation_* vs DC.* ), and perhaps adding to
dspace.cfg some defaults for mapping.
- Having a new browse-by of "new in the last two weeks", to get new articles
indexed, and perhaps reduce google crawling load.
- citation_pdf_url -- refer to a file in the same subdirectory as the HTML
abstract ? /handle/1234/5678 and /bitstream/1234/5678/1/full-text.pdf
> Provide metatags used by Google Scholar for enhanced indexing
> -------------------------------------------------------------
>
> Key: DS-396
> URL: http://jira.dspace.org/jira/browse/DS-396
> Project: DSpace 1.x
> Issue Type: New Feature
> Reporter: Sarah Shreeves
> Assignee: Sands Fish
> Fix For: 1.7
>
>
> In August 2009 I posted a query to the DSpace general list about whether or
> not anyone else had seen strange indexing of items in DSpace (see
> http://mailman.mit.edu/pipermail/dspace-general/2009-August/002996.html) and
> MacKenzie Smith posted a follow up that stated she had seen the same things
> (http://mailman.mit.edu/pipermail/dspace-general/2009-August/002998.html).
> MacKenzie followed up with Anurag Acharya at Google Scholar to inquire about
> this and he indicated that better support for the Google metatags schema
> would help mitigate this problem. It looks like the metatags are (though we'd
> want to confirm this with the Google Scholar team).
> <meta name="citation_journal_title" content="Journal Name">
> <meta name="citation_authors" content="Last Name1, First Name1; Last Name2,
> First Name2">
> <meta name="citation_title" content="Article Title">
> <meta name="citation_date" content="01/01/2007">
> <meta name="citation_volume" content="10">
> <meta name="citation_issue" content="1">
> <meta name="citation_firstpage" content="1">
> <meta name="citation_lastpage" content="15">
> <meta name="citation_doi" content="10.1074/jbc.M309524200">
> <meta name="citation_pdf_url"
> content="http://www.publishername.org/10/1/1.pdf";>
> <meta name="citation_abstract_html_url"
> content="http://www.publishername.org/cgi/content/abstract/10/1/1";>
> <meta name="citation_fulltext_html_url"
> content="http://www.publishername.org/cgi/content/full/10/1/1";>
> <meta name="dc.Contributor" content="Last Name1, First Name1">
> <meta name="dc.Contributor" content="Last Name2, First Name2">
> <meta name="dc.Title" content="Article Title">
> <meta name="dc.Date" content="01/01/2007">
> <meta name="citation_publisher" content="Publisher Name">
> I realize that supporting this level of granularity puts pressure on how we
> structure metadata but I believe as a repository manager that it's critical
> that we get this kind of support for Google Scholar into DSpace out of the
> box - and hopefully will help minimize the problems that IDEALS has seen.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
