[
https://jira.duraspace.org/browse/DS-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18153#action_18153
]
Tim Donohue commented on DS-396:
--------------------------------
Hi Sands,
Two brief comments on the code in 1.7.0 RC1:
(1) First, I wonder if the 'google-metadata.properties' file you created should
be placed in 'config/crosswalks/' so that it's alongside the existing
'xhml-head-item.properties' (which also maps metadata to the HTML metatags).
That way it's easier to do all the HTML <meta> tag mappings in one place, as
needed.
(2) I'd also like to continue to discuss enabling this feature by default in
1.7.0. I'll bring that up in tomorrow's DSpace Developers meeting so we can
see if we can gain a consensus.
> Provide metatags used by Google Scholar for enhanced indexing
> -------------------------------------------------------------
>
> Key: DS-396
> URL: https://jira.duraspace.org/browse/DS-396
> Project: DSpace
> Issue Type: New Feature
> Reporter: Sarah Shreeves
> Assignee: Sands Fish
> Priority: Major
> Fix For: 1.7.0
>
> Attachments: google-scholar-impl-quickndirty.patch,
> google_scholar_for_dri_alt_and_mirage.patch
>
>
> 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:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
