[ 
https://issues.apache.org/jira/browse/TAVERNA-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15093665#comment-15093665
 ] 

Alan R Williams commented on TAVERNA-882:
-----------------------------------------

I think the link from 10.1186/s12859-015-0714-x should be to dx.doi.org so 
http://dx.doi.org/10.1186/s12859-015-0714-x rather than direct to 
bmcinformatics.

Yes - I think there is a difference between references and publications.

Those two papers are excellent.

I think the distinction between Apache Taverna and Taverna 2 should be done for 
references. I am not sure about publications.

> Publications page
> -----------------
>
>                 Key: TAVERNA-882
>                 URL: https://issues.apache.org/jira/browse/TAVERNA-882
>             Project: Apache Taverna
>          Issue Type: New Feature
>          Components: Website
>            Reporter: Stian Soiland-Reyes
>            Priority: Minor
>
> It would be good to have a Publications page with academic publications that 
> are about Taverna or use Taverna.
> The older http://www.taverna.org.uk/cite/ refers to the latest canonical 
> citations about Taverna, http://dx.doi.org/10.1093/nar/gkt328
> but even after moving to Apache we have gathered new citations:
> https://scholar.google.co.uk/scholar?hl=en&q=%22Apache+Taverna%22&btnG=&as_sdt=1%2C5&as_sdtp=
> Some searches (must be filtered further):
> https://scholar.google.co.uk/scholar?q=Taverna+workflow&btnG=&hl=en&as_sdt=0%2C5
> https://scholar.google.co.uk/scholar?q=Taverna+workbench&btnG=&hl=en&as_sdt=0%2C5
> Also anything with Taverna on 
> http://dev.mygrid.org.uk/wiki/display/about/myGrid+Publications
> In addition to listing the master citation 
> http://dx.doi.org/10.1093/nar/gkt328 I would propose a single chronological 
> text page along the style we have used on 
> http://www.esciencelab.org.uk/publications/ with links to the DOI and a 
> preprint if it's not Open Access. (I guess those links can be tricky for 
> older papers).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to