[Dspace-devel] [DuraSpace JIRA] Updated: (DS-396) Provide metatags used by Google Scholar for enhanced indexing
[ https://jira.duraspace.org/browse/DS-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz updated DS-396: --- Attachment: google-scholar-impl-quickndirty.patch Added a simple patch which provides for basic implementation of the required changes. It will display a citation_pdf_url in the case where there is only one public content bitstream and its mimetype is PDF. We should have something committed to improve the vast majority of instances in Scholar for 1.7 (This is not the work that MIT has been working on, but a quick and dirty implementation to move forward on this). > 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 > > > 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). > > > > > > > > > > content="http://www.publishername.org/10/1/1.pdf";> > content="http://www.publishername.org/cgi/content/abstract/10/1/1";> > content="http://www.publishername.org/cgi/content/full/10/1/1";> > > > > > > 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 -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-396) Provide metatags used by Google Scholar for enhanced indexing
[ https://jira.duraspace.org/browse/DS-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sands Fish updated DS-396: -- Attachment: google_scholar_for_dri_alt_and_mirage.patch Attaching a patch here to integrate the Google Scholar metadata into dri2xhtml-alt & Mirage themes. Please apply if desired. I didn't want to commit them and disrupt any work being done by the authors of those themes. > 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). > > > > > > > > > > content="http://www.publishername.org/10/1/1.pdf";> > content="http://www.publishername.org/cgi/content/abstract/10/1/1";> > content="http://www.publishername.org/cgi/content/full/10/1/1";> > > > > > > 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 -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
