In the last post I described OSCAR, which can review and extract chemical data from published articles. Here is how I used it to review the Beilstein Journal of Organic Chemistry
The BJOC unlike most other chemistry journals encourages reader’s comments, so I thought OSCAR would like to add some. Since I did this on a Saturday none of the comments have been moderated (or at least none have appeared). I first added comments to the journal announcement about what I intended to do, and gave links to the OSCAR home page. I then started at the first paper and found the “Additional File 1” which contains a pointer to the chemical data. (The process seems overly convoluted, and I have commented on this). I first downloaded OSCAR (the adventurous among you can try this and the following), started it (click the jar file), opened the BJOC (Word) file with the data, selected all of it and pasted it into OSCAR.
This is a very well presented file (and worthy of the authors’ orgnaisations – GSK and Leeds) – not all chemical manuscripts are as well prepared. OSCAR reveals only two errors, which are missing commas. (These are more important than they sound as we rely on them for the parsing). Typical results can be seen in the previous post. I therefore added this to the comments section for the paper. I assume the comments will appear in a day or two. I don’t know whether the authors will be automatically informed – I expect so – and whether the deposited data can then be corrected either by authors or editorial staff. If so, this is a real mechanism for cleaning up the current literature. Of course if the authors use OSCAR in future they will get a clean sheet!
I then applied OSCAR to all the papers in the Journal that contained chemical synthetic data – about 27. There is no standard place for the data – sometimes they occur in free text and sometimes in “Additional File n” (this name is not very helpful and I have suggested it should be changed to something with chemical semantics). I commented on the variability in navigation which made it difficult for me (and very difficult for OSCAR if it wished to review the journal systematically). OSCAR discovered several important errors – for example a chemical formula was wrong (this matters) and many suggestions about style improvements. (I did not comment on these as OSCAR’s rules don’t yet include BJOC policy). I also noted that some papers didn’t include data. I did not comment on the chemistry at all – its merit or its correctness – as I am not a specialist except on data. But perhaps this will stimulate expert readers to do so in future.
OSCAR raised concerns in almost all papers – ranging from punctuation to incorrect formula. I stress that this is common in ALL chemistry papers – and should not be used to measure BJOC against others. They all need cleaning up.
I made addiitonal comments on the accessibility of crystallographic data – these were not added as supplemental data and I argue strongly that they should be. I’ll write later about this.
I am hoping this will be seen as positive critiquing – it would be in compsci or crystallography. Certainly the adoption of data standards will make an enormous impact in the standard and re-usability of chemistry.
(Note: Our two summer students this year- Richard Moore and Justin Davies – again financed by RSC, have been refactoring OSCAR – we call this OSCAR-Data. OSCAR-Data uses OPSIN (OSCAR3) and allows for several inputs – SciXML, HTML, converts them into CML and then applies a set of custom rules (which could be publisher-specific). )
-
Recent Posts
-
Recent Comments
- pm286 on ContentMine at IFLA2017: The future of Libraries and Scholarly Communications
- Hiperterminal on ContentMine at IFLA2017: The future of Libraries and Scholarly Communications
- Next steps for Text & Data Mining | Unlocking Research on Text and Data Mining: Overview
- Publishers prioritize “self-plagiarism” detection over allowing new discoveries | Alex Holcombe's blog on Text and Data Mining: Overview
- Kytriya on Let’s get rid of CC-NC and CC-ND NOW! It really matters
-
Archives
- June 2018
- April 2018
- September 2017
- August 2017
- July 2017
- November 2016
- July 2016
- May 2016
- April 2016
- December 2015
- November 2015
- September 2015
- May 2015
- April 2015
- January 2015
- December 2014
- November 2014
- September 2014
- August 2014
- July 2014
- June 2014
- May 2014
- April 2014
- March 2014
- February 2014
- January 2014
- December 2013
- November 2013
- October 2013
- September 2013
- August 2013
- July 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- December 2006
- November 2006
- October 2006
- September 2006
-
Categories
- "virtual communities"
- ahm2007
- berlin5
- blueobelisk
- chemistry
- crystaleye
- cyberscience
- data
- etd2007
- fun
- general
- idcc3
- jisc-theorem
- mkm2007
- nmr
- open issues
- open notebook science
- oscar
- programming for scientists
- publishing
- puzzles
- repositories
- scifoo
- semanticWeb
- theses
- Uncategorized
- www2007
- XML
- xtech2007
-
Meta
Pingback: Decoding IUPAC Names With OPSIN