JACoW Conference Coordination: Continuity for Sustainability - Examining the JACoW ModelSpeaker: Christine Petit-Jean-Genaz (CERN) In 2016 JACoW celebrated its 20th anniversary - a good time to review what has been achieved and take stock. For newcomers, a little history ... Accelerator Conferences and Electronic PublicationPAC'95 and EPAC'96 were the first accelerator conferences to attempt electronic publication of proceedings, at a time when contributions were submitted on 1MB diskettes (figures hand drawn ...), plus paper copies just in case .... and Acrobat was in its infancy, not to say embryonic ... PAC'95 experienced considerable difficulties:
EPAC'96 editors (John Poole and Christine) were the first to "sample" the PAC'95 exercise, and decided to introduce:
EPAC'96 (Sitges, Spain) was the first event when editors processed contributions during the conference. The team looked like this: John Poole, CERN (who later became the first JACoW Chair)
Publication of around 800 papers on a server at CERN was achieved around three months after the conference - a time frame now reduced to 3 weeks for IPACs with 1300 or more papers. JACoW Was BornIlan Ben-Zvi, BNL (SPC Chair of PAC'99) was at the origin of the idea to publish PAC and EPAC proceedings at the same site, such that all proceedings would be searchable across the same site. APAC (first event in Japan in 1998) was welcomed to this infant Collaboration. This representation is shown in the list of editors at EPAC'96. Read more about it at: https://www.jacow.org/uploads/About/Article_KASOKUKI.pdf Post-Mortem Reports from 1996: https://www.jacow.org/Team/Post-MortemReports Team Meetings from 2001: https://www.jacow.org/Team/PreviousTMAndWorkshops Software Development for Programme ManagementUntil around 2000, there was no standard software for programme management, registration, etc.
PAC and EPAC joined forces to develop a common application, "SPMS"
The JACoW Model, for Continuity and SustainabilityToday the JACoW Model offers continuity across all conference series via the training of new editors:
Newcomers gradually acquire expertise, and in turn share this with the future newcomers. Since there are no "permanent" JACoW staff, every effort has been made to support this model in order not to lose expertise. Conference series, especially the smaller ones, benefit from the Central Repository, mailing lists and experienced advice in conference and scientific programme management, as well as online help. The JACoW site is open access, so free of charge to all. But, publication on JACoW does have a cost: training of editors, their attendance at TMs and conferences, rental of a proceedings office, of soft- and hardware, organising the editorial/IT effort during a conference, etc. This cost should be included in the budget of all conferences. Before the electronic era paper proceedings and mailing them represented more than 30% of the budget of a conference ... Several attempts have been made over the years to estimate the cost of outsourcing the publication of proceedings for the same quality product as on jacow.org. Each time it could be demonstrated that producing JACoW quality proceedings resulted in a higher cost when the work was outsourced to commercial companies. Continuity and sustainability via the JACoW model remains thus for the time being the key to maintaining the status quo of JACoW, relying on support from:
This year's Kickoff Session had a dual aim:
The next presentation scheduled during this TM describes the experience of a relative newcomer to JACoW: MEDSI. We must note the concerns regarding the cost of JACoW, and weigh them against the options for each conference or series. The discussions during this Team Meeting will be brought before the Stakeholders during IPAC'19 in Melbourne. |