1. JACoW Website J. Poole

2. Review the objectives of the web pages. Review the contents of the website (other than the conference proceedings). Proposal for the future content of the site. 2 Aim of this Talk Technical Issues, TM KEK, November 2008, J. Poole

3. 3 JACoW Website, TM KEK, November 2008, J. Poole

4. Primary function is to provide access to the conference proceedings. Secondary function is to provide information to help authors in the preparation of JACoW conference papers. Tertiary function is communication with the JACoW Team and the accelerator community. 4 Website Purpose JACoW Website, TM KEK, November 2008, J. Poole

5. 5 The Central Frame JACoW Website, TM KEK, November 2008, J. Poole The help page has not been updated since 2003 and has a bad return link. It needs to be updated with some more up-to-date examples and checked to see that the information is still relevant for the FAST search engine. The hit counter only counts hits on this page. The number of papers being served is far more than this would indicate (in October 2008 the number of papers per annum is about 400,000) so this counter could be removed.

6. 6 Contents Today JACoW Website, TM KEK, November 2008, J. Poole

7. The templates are the first step in enabling the authors to produce conforming papers. The analysis of problems encountered at conferences shows us where ‘help’ is needed. There is also a level of background information which it is useful for authors to know about – SPMS repository, library data, JACoW conferences etc. 7 Author Education JACoW Website, TM KEK, November 2008, J. Poole

8. Incomplete author list in SPMS Format errors A4 printed on US letter and vice-versa PDF, not PS submitted Loss of colour 8 Problems to Attack JACoW Website, TM KEK, November 2008, J. Poole

9. 9 Current Help Frame and the Problems to Attack JACoW Website, TM KEK, November 2008, J. Poole Incomplete author list – not addressed Format errors (columns, margins, styles …) - not addressed A4 on US – making the PS Submitting PDF Loss of colour

10. 10 JACoW Website, TM KEK, November 2008, J. Poole General background to the process but does not reflect the current status of JACoW. Needs updating to underline the role of PostScript. Too much emphasis on Type 3 fonts, given today’s Acrobat capabilities. Contains quite a lot of obsolete information. Basically OK but need updating. Basically OK but need updating with the latest information and tips.

11. Basic description is OK – explains what affiliations and profiles are. Historical information could be removed as it is not really relevant any more. Creation of profiles is mixed with the privacy policy. 11 Author Profiles JACoW Website, TM KEK, November 2008, J. Poole

12. Collaboration conferences maintained by Christine and is up-to-date. PRSTAB seems out of place. 12 The Rest of Author Info. JACoW Website, TM KEK, November 2008, J. Poole

13. Steering Committee link leads to a page which also defines the Team membership. Terms of Ref. – give prominence to sanctions on conferences which do not adhere to them Requirements for membership – first paragraph could be reworded to explain the requirement that the conference should send a stand-alone set of files and JACoW does not publish links. ‘Meetings’ is for the Team and Steering Committee ( ≠ editors) Documentation is for the Team. 13 ‘For Editors’ JACoW Website, TM KEK, November 2008, J. Poole

14. ‘Meetings’ is messy Documentation is lacking in structure. –Are Post Mortem reports a thing of the past ? –The editor training may be the most useful link but is buried at the end –Shouldn’t we have a new poster ? 14 Pages Under ‘Editors’ JACoW Website, TM KEK, November 2008, J. Poole

15. Website updates (perhaps only 2 people ever look at this). Critical to the operation of the mirror site, but is this the right place for it ? SPMS Terms and Conditions – essential source material for organisers wishing to use SPMS or JACoW Software licenses. SPMS – still has links to the old documentation (such as it is). 15 JACoW Team Items JACoW Website, TM KEK, November 2008, J. Poole

16. Library data is useful and should be there, but does it need to have its own sub-heading ? About JACoW - useful and it should be on the website. Award for the collaboration is nearly 5 years old and could be removed (maybe include the text in the above). Future Accelerator Projects – only needs one link from the index. –Is this a core JACoW Activity – the link goes to EPAC ? –Should it have more explanation 16 Other Links in the Index JACoW Website, TM KEK, November 2008, J. Poole

17. Apart from the more obvious errors, editors spend a lot of time fixing: –Fonts not available to distiller substituted with Type3 – simple to fix but hard to avoid –Title to upper case –Sub-section headings to initial caps –Figure and table captions (single and multi-line) –Figures with paragraph indent –Tables wider than the column –Removing hyperlinks 17 Editor’s time JACoW Website, TM KEK, November 2008, J. Poole

18. Papers which will perform well on JACoW Papers which have a reasonable appearance Make it easy for authors to deliver what we need Educated authors Minimise editorial effort 18 What do we want to achieve ? JACoW Website, TM KEK, November 2008, J. Poole

19. Provision of templates Simpler guidelines (more drill-down instructions) Clarity and ease of use Clear instructions for editors 19 How can the Website Help JACoW Website, TM KEK, November 2008, J. Poole

20. Recall that priority on the website should be given to certain specific problems : –Incomplete author list –Format errors –A4 printed on US letter and vice-versa –PDF, not PS submitted –Loss of colour 20 Planning a New Version JACoW Website, TM KEK, November 2008, J. Poole

21. Basically have structured information for: –Authors How to avoid common problems Templates General help information –Organisers Terms and Conditions JACoW Structure and roles Using SPMS –JACoW Team Meetings Editor Training Documentation 21 Secondary and Tertiary Objectives JACoW Website, TM KEK, November 2008, J. Poole

22. There are several aspects to this: Technical requirements for publication on JACoW JACoW Membership conditions JACoW activities – steering committee and team meetings Technical information for team members (‘editors’) like SPMS/JPSP GPL download site, post mortem reports, editor training and instructions etc. 22 JACoW Team Information JACoW Website, TM KEK, November 2008, J. Poole

23. The basic site needs modernisation. The structure is too flat (often a confusing amount of information on each page). The majority of the information on the existing pages is valid but needs updating and tidying up. Information specifically targeting the author errors which cause red and yellow dots to be attributed should be given some prominence (perhaps a page which conferences can link to from their author instructions). The Team information needs to be re-structured and clarified. 23 Overall Assessment JACoW Website, TM KEK, November 2008, J. Poole

24. The file structure could be cleaned up. Obsolete information should be removed. What is the impact for the mirror site at KEK ? 24 Physical Implementation JACoW Website, TM KEK, November 2008, J. Poole

25. Keeping in mind the three levels of the objectives Find a young web engineer to propose a better way to present the basic structure (not just relying on frames) – but the requirements of the search engine must not be overlooked. Find a volunteer to make a new JACoW poster – the collaboration does much more than it used to and it would be good to tell the World Update the existing information following what was discussed/agreed in this meeting. 25 Proposal JACoW Website, TM KEK, November 2008, J. Poole