Embed Size (px)
DESCRIPTION
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. - PowerPoint PPT Presentation
Citation preview
From InDiCo to JACoWin one (well maybe a few) click(s)
J. Poole
• 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.
2
Introduction
From InDiCo to JACoW, TM KEK, November 2008, J. Poole
• 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.
3
The Prototype
From InDiCo to JACoW, TM KEK, November 2008, J. Poole
• 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.
4
Setting up InDiCo
From InDiCo to JACoW, TM KEK, November 2008, J. Poole
• 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
5
Basic Process
From InDiCo to JACoW, TM KEK, November 2008, J. Poole
6
http://indico.cern.ch/conferenceOtherViews.py?view=jacow&fr=no&confId=15495
From InDiCo to JACoW, TM KEK, November 2008, J. Poole
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>
7
Software ‘Problem’
From InDiCo to JACoW, TM KEK, November 2008, J. Poole
• 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.
8
Software Features
From InDiCo to JACoW, TM KEK, November 2008, J. Poole
9From InDiCo to JACoW, TM KEK, November 2008, J. Poole
• Data quality !!
- difficult to see why in InDiCo author index …
10
Case Sensitivity
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
<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>
13
XML Reveals More
From InDiCo to JACoW, TM KEK, November 2008, J. Poole
<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>[email protected]</email> </emails>
14
JPSP Result
From InDiCo to JACoW, TM KEK, November 2008, J. Poole
A quick fix in the XML(changing the case) gives:
• 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.
15
Co-authors
From InDiCo to JACoW, TM KEK, November 2008, J. Poole
• 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
16
Paper ID
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
• Append a conference acronym to the number
… or suppress this output on the page
18
Proposal
From InDiCo to JACoW, TM KEK, November 2008, J. Poole
• 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 spmsbatch against a new XML dump– Replace the new banner.htm with your saved version.
19
Methodology
From InDiCo to JACoW, TM KEK, November 2008, J. Poole
† See http://cern.ch/poole/erl07 for the current production version
• 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.
20
Conclusion
From InDiCo to JACoW, TM KEK, November 2008, J. Poole
