1 / 20

From InDiCo to JACoW

From InDiCo to JACoW. in one (well maybe a few) click(s) J. Poole. Introduction. JACoW has been promoting the links between InDiCo and JACoW tools for many years. At the 2006 Team Meeting we agreed to try and build an interface between them.

kipling
Download Presentation

From InDiCo to JACoW

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. From InDiCo to JACoW in one (well maybe a few) click(s) J. Poole

  2. Introduction • JACoW has been promoting the links between InDiCo and JACoW tools for many years. At the 2006 Team Meeting we agreed to try and build an interface between them. • The basic idea is to run the conference using InDiCo, which is much lighter than SPMS, but to feed some output into the JACoW Proceedings Script Package (JPSP) in order to produce JACoW compatible proceedings. From InDiCo to JACoW, TM KEK, November 2008, J. Poole

  3. The Prototype • It was agreed to use the 2007 Energy Recovery Linac Workshop (ERL07) as a guinea pig. • Unfortunately it has taken a long time to complete the process but the proceedings are now ready. • It was a small workshop, where the emphasis was on working in groups rather than presentations. There were some formal presentations and the main talks and conclusions have been written up. From InDiCo to JACoW, TM KEK, November 2008, J. Poole

  4. Setting up InDiCo • The basic rule that the quality of the final result is critically dependent on the quality of the data entered, is even more important when using InDiCo. • Because the InDiCo repository is not managed or maintained to the same level that the SPMS is, it is very easy for errors to creep in. • Errors or bad information become very apparent when the website is built. From InDiCo to JACoW, TM KEK, November 2008, J. Poole

  5. Basic Process • Run conference using InDiCo • Process the contributions and upload JACoW compatible PDF files • Get an XML dump from InDiCo • Run the scripts • Fix the problems • Loop until OK From InDiCo to JACoW, TM KEK, November 2008, J. Poole

  6. http://indico.cern.ch/conferenceOtherViews.py?view=jacow&fr=no&confId=15495http://indico.cern.ch/conferenceOtherViews.py?view=jacow&fr=no&confId=15495 From InDiCo to JACoW, TM KEK, November 2008, J. Poole

  7. Software ‘Problem’ InDiCo appends ‘-1’ to the session abbreviation in the XML file • <name abbr="PLENARY-1">PLENARY</name> • <name abbr="WG1-1-1">First Session of Working Group 1</name> From InDiCo to JACoW, TM KEK, November 2008, J. Poole

  8. Software Features • InDiCo will allow a ‘/’ in a session name or abbreviation • This is not acceptable to the scripts • ERL had many such session names where two working groups met together in a session. From InDiCo to JACoW, TM KEK, November 2008, J. Poole

  9. From InDiCo to JACoW, TM KEK, November 2008, J. Poole

  10. Case Sensitivity • Data quality !!- difficult to see why in InDiCo author index … From InDiCo to JACoW, TM KEK, November 2008, J. Poole

  11. InDiCo Author Details From InDiCo to JACoW, TM KEK, November 2008, J. Poole

  12. InDiCo Profile Search From InDiCo to JACoW, TM KEK, November 2008, J. Poole

  13. XML Reveals More <contributor type="Author"> <lname>HAJIMA</lname> <fname>Ryoichi</fname> <mname></mname> <institutions> <institute> <full_name abbrev="" type="">Japan Atomic Energy Agency (JAEA)</full_name> <name1/> <department/> <URL/> <town/> <postal_code/> <zip_code/> <country_code abbrev=""/> </institute> </institutions> <emails> <email></email> </emails> • <contributor type="Author"><lname>Hajima</lname> <fname>Ryoichi</fname> <mname></mname> <institutions> <institute> <full_name abbrev="" type="">JAEA</full_name> <name1/> <department/> <URL/> <town/> <postal_code/> <zip_code/> <country_code abbrev=""/> </institute> </institutions> <emails> <email>hajima.ryoichi@jaea.go.jp</email> </emails> From InDiCo to JACoW, TM KEK, November 2008, J. Poole

  14. JPSP Result A quick fix in the XML (changing the case) gives: From InDiCo to JACoW, TM KEK, November 2008, J. Poole

  15. Co-authors • The XML dump does not seem to contain co-author listings. • From the previous slides can see that Hajima was co-author on 3 other papers in InDiCo. From InDiCo to JACoW, TM KEK, November 2008, J. Poole

  16. Paper ID • InDiCo assigns a unique ID to each contribution and the downloaded PDF is given this ID as a filename. • The unique IDs are numbers and this leads to some confusion. • The numbers appear in the table of contents From InDiCo to JACoW, TM KEK, November 2008, J. Poole

  17. Top and Bottom of the Published Paper From InDiCo to JACoW, TM KEK, November 2008, J. Poole

  18. Proposal • Append a conference acronym to the number … or suppress this output on the page From InDiCo to JACoW, TM KEK, November 2008, J. Poole

  19. Methodology • Read the manual ! • Run through the process • If there are problems, they will almost certainly come from bad data, so go back and fix the original and try again. • Once it is ~working†and it is necessary to fix small errors • Customise INDEXLOC.HTM and save as INDEX.HTM • Modify html/banner.htm and save a copy (make the links to the conference home relative and point to this instance, remove link to classification index etc.) • Re-run spmsbatchagainst a new XML dump • Replace the new banner.htm with your saved version. †Seehttp://cern.ch/poole/erl07for the current production version From InDiCo to JACoW, TM KEK, November 2008, J. Poole

  20. Conclusion • The InDiCo to JPSP process is a valuable addition to the JACoW suite of tools and can be considered to be in production. • Some improvements have been suggested, but they are not necessary for the current functionality. • This development opens the door for smaller conferences who do not have the resources to implement an SPMS to publish on JACoW • The cost however, is in the manpower required for quality control of the data (which is automatically taken care of in SPMS by the repository). However, there are substantial overall gains. From InDiCo to JACoW, TM KEK, November 2008, J. Poole

More Related