1. 1 Processing Picked up in 2007 J. Poole

2. Processing, TM Knoxville, October 2007, J. Poole 2 Uploading When an editor has processed a file and is ready to upload the PDF, you can get a strange message from the SPMS if you still have the file open in Acrobat. –Needs an update in the instructions to editors Some PostScript files could not be uploaded Still a mystery as it was possible for some people to upload a particular file and not others –Needs some discussion around the table.

3. Processing, TM Knoxville, October 2007, J. Poole 3 PitStop Version PitStop 7 works better than 6.5 with Acrobat 7 –You can edit files after the banner, footer and hidden fields have been done –Recommend not to use 6.5 again

4. Processing, TM Knoxville, October 2007, J. Poole 4 Optimizer On some occasions PDF Optimizer was unable to flatten transparency –Solution was to run it manually with flattening of transparency suppressed. Batch job can cause memory overflow (2.8GHz machine with 1Gbyte memory) –Solution was to split the job into chunks (around 100 files at a time)

5. Processing, TM Knoxville, October 2007, J. Poole 5 Deleted Files A user can ‘delete’ files but they are not removed from the server – it is just the entry in SPMS that is removed. –It is therefore possible for an editor to download the files because the interface is generated from the file server. –This created some problems in the final stages – explanation from Volker

6. Processing, TM Knoxville, October 2007, J. Poole 6 Unprintable files A file which looked fine on the screen was total rubbish when printed There was a similar problem when Christine tried to print a version of the Proposal for a New Organisation Structure of JACoW which had been concatenated inside one of her documents. In the PAC case it was a Mac produced PDF file (WEPMS090 in PAC07) printing from a PC. In this case the generation of the PDF as was uploaded looks bizarre.

7. Processing, TM Knoxville, October 2007, J. Poole 7 Printed Version

8. Processing, TM Knoxville, October 2007, J. Poole 8 On Screen

9. Processing, TM Knoxville, October 2007, J. Poole 9 The offending file

10. Processing, TM Knoxville, October 2007, J. Poole 10 WEPMS090

11. Processing, TM Knoxville, October 2007, J. Poole 11 The Log File Uploaded [John Poole 01-AUG-07 04:40 PM (UTC +01:00)] WEPMS090.PDF Email: [06-JUL-07 04:47 PM (UTC +01:00)] PAC 2007 Proceedings Final QA Passed [Christine Petit-Jean-Genaz 03-JUL-07 07:56 PM (UTC +01:00)] QA OK Poster Police [William Roybal 27-JUN-07 10:51 PM (UTC +01:00)] Poster Posted, Poster Manned, Poster Satisfactory. File Uploaded [Jana Leah Thomson 25-JUN-07 11:09 PM (UTC +01:00)] WEPMS090.PDF Edit Complete [Luce Salas 25-JUN-07 10:09 PM (UTC +01:00)] File Uploaded [Luce Salas 25-JUN-07 10:08 PM (UTC +01:00)] WEPMS090.doc File Uploaded [Luce Salas 25-JUN-07 10:06 PM (UTC +01:00)] WEPMS090.PDF Copyright form Received [Jean N. Trujillo 25-JUN-07 04:50 PM (UTC +01:00)] Paper Copy Received [Jean N. Trujillo 25-JUN-07 04:50 PM (UTC +01:00)] Dot Reassignment [Jean N. Trujillo 25-JUN-07 04:50 PM (UTC +01:00)] Edit Complete [Luce Salas 23-JUN-07 05:53 PM (UTC +01:00)] Opened source file to fix font problems and recreated PS file. Font Problems File Uploaded [Luce Salas 23-JUN-07 05:53 PM (UTC +01:00)] WEPMS090.PDF Paper Assigned [Luce Salas 23-JUN-07 05:41 PM (UTC +01:00)]

12. Processing, TM Knoxville, October 2007, J. Poole 12 Analysis of this problem In this case it looks as if a ‘user’ produced PDF was uploaded after the editor’s version which was perfectly OK. Although the bad file looks fine on the screen and the font list looks OK, it is obviously screwed.

13. Processing, TM Knoxville, October 2007, J. Poole 13 Web Server Case Sensitivity This can cause problems at many stages –Full download for JPSP –Running JPSP –Web links Suggestions from the floor ?

14. Processing, TM Knoxville, October 2007, J. Poole 14 Slow Figures in LaTeX I used this method when not all of the source files were available Take a screen dump of the figures (at maximum zoom) and paste it into word. Make a PDF from the word file Open the PDF made from the screen dump and copy the graphics part (CTRL+C) using PitStop Open the bad file, delete the bad figures with PitStop and then paste and scale the new image.

15. Processing, TM Knoxville, October 2007, J. Poole 15 Final Steps - I The link to the ‘Home’ page from the proceedings website generated by JPSP should point to the JACoW version of the home page, not the conference website (use a relative link ?). The link appears in only one file (BANNER.HTM) so it is easy to fix but it needs to go into the instructions.

16. Processing, TM Knoxville, October 2007, J. Poole 16 Keywords and library data JPSP generates keywords for each paper by scanning the text in the PDF file, comparing it to a list of keywords and selecting the five highest scoring words Publication of library catalog data for citation indexes (e.g. CERN (CDS) and SLAC (SPIRES)) is achieved through a package in the SPMS. In order to produce the output, the keywords have to be stored in the conference database.

17. Processing, TM Knoxville, October 2007, J. Poole 17 Library Data Production - I The script keyword-sql.pl is used to generate a procedure file keywords_plsql.txt to load the keywords for each paper into SPMS. The script reads the file keyword-count.txt which is produced by JPSP Each line in the output file looks like: exec keywords.add ('FRXAPA01', 'target'); This part of the procedure is done by the person responsible for running JPSP

18. Processing, TM Knoxville, October 2007, J. Poole 18 Library Data Production - II The script keywords-regexps-sql.pl is used to generate a procedure file keyword_regexp_sql.txt to load the keywords and their corresponding regular expression into SPMS. It uses the file keywords.list which is part of JPSP but customisable by each conference. Each line in the file looks like: exec keywords.set_regexp('target', 'target.{0,1}') This part of the procedure is also done by the person responsible for running JPSP

19. Processing, TM Knoxville, October 2007, J. Poole 19 Uploading Keyword Data The conference database manager performs the following steps: Run the file keywords_plsql.txt in SQL*Plus Run the file keyword_regexp_sql.txt in SQL*Plus Ensure that the system parameter ‘Proceedings TOC Base URL’ is pointing to the appropriate place at JACoW.org The JACoW Repository database manager performs the following steps (using EPAC06 as an example): wget http://oraweb.cern.ch/pls/EPAC06/Library_Data.OAI wget http://oraweb.cern.ch/pls/EPAC06/Library_Data.SPIRES Post the resultant files on the JACoW site

20. Processing, TM Knoxville, October 2007, J. Poole 20 SPMS Packages Some modification to the SPMS package (LIBRARY_DATA) and the underlying tables is necessary to allow correct functionality for library data publication. The development has been done and installed and tested on EPAC06 but it remains to be implemented generally.

21. Processing, TM Knoxville, October 2007, J. Poole 21 Repatriation It was agreed at the last TM that once proceedings had been published and catalog data published, then the link to the central repository would be cut and no further central maintenance would be applied. The final step for a conference was also supposed to be the repatriation of a certain amount of data to the central repository. There is perhaps a slight conflict between these previous two statements. This repatriation step has still never been executed or even tested. Should we test this soon, or should we abandon it ?