[ Show as SlideShow ]

JACoW Conference Coordination: Continuity for Sustainability - Examining the JACoW Model

Speaker: Christine Petit-Jean-Genaz (CERN)

Presentation Updated for TM'21 in Trieste

This year JACoW celebrates its 25th anniversary. In the past couple of years we took stock of what we had achieved as a Collaboration, and we set in motion a number of initiatives that will be implemented in the coming couple of years.

Throughout these years JACoW has developed tools, techniques and procedures. Its "model" relies on the training of newcomers to the Collaboration in the use of our conference management tools, and in publication techniques, with hands-on editing experience during conferences. These skills are gradually assimilated, and then passed on to future newcomers.

The quality of published proceedings has improved considerably over the years. The JACoW Archive is highly appreciated by the whole community. But since JACoW is based on good will, there are times when the fragility of the model may jeopardise its continuity and sustainability.

For newcomers, here is a little history to better understand the JACoW model ...

Accelerator Conferences and Electronic Publication

PAC'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:

  • 80% failure rate on post-conference processing
  • a student was hired to re-process almost all contributions and final publication was over a year after the conference.

EPAC'96 editors (John Poole and Christine) were the first to "sample" the PAC'95 exercise, and decided to introduce:

  • author education via templates, and improved guidance and written instructions,
  • hands on editing during each conference, the past, current and future editors working together at each event to share experience and knowledge,
  • a "dotting board" (with paper dots) for feedback to authors during the conference.

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)
Christine Petit-Jean-Genaz, CERN, EPAC/IPAC Scientific Secretariats/Editor
Andreu Pacheco, U. Barcelona, EPAC'96 Local Editor
Martin Comyn, TRIUMF, PAC'99 Editor
Leif Liljeby, MSI, EPAC'98 Local Editor - to whom we owe JACoW paper size ...
Yong Ho Chin, KEK, APAC'98 Editor

  • An 80% successful processing rate was achieved during the conference
  • Problem papers, QA, post-processing activities (creation of table of contents, insertion of page numbers, links from these to the pdf files) was completed during a 10 week period at CERN

Publication of around 800 papers on a server at CERN was achieved around three months after the conference, similar to the time it took to compile several 1000 page volumes from camera-ready paper and send to Singapore for reproduction (EPAC). Today editing typically starts around 3 days before the start of the conference and many events regularly publish "pre-press" (without author lists, etc.) at the close of the conference, and on JACoW.org around 2 to 3 weeks after the event.

JACoW Was Born

Ilan 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 Management

Until around 2000, there was no standard software for programme management, registration, etc.

  • EPAC: FileMaker Pro until 2000; in 2002 a first Oracle application, with an associated Central Repository (5000 profiles) was used
  • PAC: Oracle for PAC'99, 01 and '03, without any Central Repository, but with an e-mail utility and other nice features.

PAC and EPAC joined forces to develop a common application, "SPMS"

  • Matt Arena, Fermilab (the developer) and Christine Petit-Jean-Genaz, CERN (functionality/specification/user interface) developed the first SPMS application, associated with a Central Repository, used first for EPAC'04
  • Functionality was gradually improved and extended to become a complete conference management tool for the accelerator community covering scientific programme and delegate registration activities, export of data to websites, industrial exhibition management, the editorial module
  • The JPSP scripts (Volker Schaa) were later developed to produce the final publication package from data exported from SPMS
  • Very many new features are still being introduced by Volker Schaa, GSI, with ISBN numbers, doi's
  • Better references and citations contribute to improve JACoW's impact factor via the Reference Search and Catscan apps introduced at IPAC'19.

The JACoW Model, for Continuity and Sustainability

Today the JACoW Model offers continuity across all conference series via the training of new editors:

  1. Theoretical and practical training at annual Team Meetings since 2001: editing, IT, soft- and hardware, tools such as SPMS, Indico, JPSP, etc.,
  2. Hands on editing training at IPAC
  3. Hands on editing training at non-IPAC events

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:

  • Stakeholders: JACoW SPC Chairs, past, current and future in each series - supporting the JACoW model within their own laboratories and providing feedback to the annual Stakeholders Meetings to keep JACoW on track and continuously improving,
  • Stakeholders: JACoW Editors, past, current and future in each series - who learn, and then pass on and share their experience in the production of high quality proceedings,
  • Stakeholders: Representatives of Institutes - who have an overview of JACoW, and who have a voice in ensuring JACoW gets the necessary support within the managements of organizations, in particular:
  1. Hosting SPMS Instances in Asia and Europe: KEK and CERN. Fermilab withdrew its support in 2020, the Instances hosted at Fermilab were moved to KEK
  2. Hosting the servers for the upload/download of contributions to proceedings: PSI, JLAB: With the introduction of Indico for scientific programme management in the coming years, there will be no need for the upload/download servers at PSI and JLAB
  3. Hosting websites/documentation: Elettra (the wiki), CERN and KEK (the Proceedings)
  4. Allowing "core" staff to contribute to the JACoW effort in particular of the JACoW Officers: ANSTO, CERN, Elettra, GSI, JLAB, ORNL, PSI, and lastly
  5. Allowing "core" staff to join the editorial effort at major conferences - while a small conference could possibly manage all editing activities with "in house" staff, the larger events with anything from 400 to 1400 contributions most certainly could not.

The Kickoff Session is for the time being a necessary regular feature with the dual aim to:

  • Improve the initiation of new members into the Collaboration
  • Improve awareness of the JACoW model and ensure it is well understood and supported