Wiki Working Group

Contact: Charlie Horak, Oak Ridge National Laboratory

The purpose of the working group is to improve the site by involving more team members in the development. This includes setting priorities, developing revised structure, recruiting content owners, brainstorming, and following up on input from team.

8 Nov 2016 meeting

Minutes

  • Decided on overall structure and set some priorities
  • Began developing a Gant/swim lane chart to show roles, tasks, and timelines in one view
  • Began assigning/requesting content owners for specific topics

Next tasks:

  • Complete details on structure and continue recruiting content owners
  • Write up instructions and expectations for content owners
  • Create a cheat sheet for wiki markup
  • Check on better search options
  • Create site map

For discussion during meeting

Tasks

1. Decide on top-level structure

As this is developed, consider possible content owners.

SPMS Manual

  • Possible organization: by sections, then screens; include topical index.
  • Review & consolidate information; will require review of most pages.
    • Sources in addition to current wiki: TM presentations (Todd, specifically--TM Monday "JACoW overview"; Info on roles; starting ~slide 11); Christine's bible (2013 TM) and other items from her (papers, presentations, etc.).
  • From Monday discussion: specifically mentioned hard-to-find items
    • Documentation on second industry email (Todd says okay for vendors, can also use non-SPMS email)
    • Second abstract reminder--usually a message to institution admins to remind people
    • How to put together synoptic table
    • Session chair information
    • editorial room setup
    • Additional sessions page is outdated
  • From Monday discussion: items to add
    • Second abstract reminder--usually a message to institution admins to remind people
    • What is purpose of accept/reject contributions at abstract level--didn't know what this means
    • Setup server item: use regional servers if possible
    • Would be nice to have samples of emails
    • Printed program isn't always used --up to conference
    • What is purpose of accept/reject contributions at abstract level--didn't know what this means

Proceeding Production Chronology

Critical part of this is narrative to explain process and create a flow from section to section and plenty of links to detailed information, especially SPMS manual
  • Review & consolidate information; will require review of most pages.
  • Sources in addition to wiki: TM presentations; Christine's bible (2013 TM) and other items from her (papers, presentations, etc.).

Tracks by Roles

  • See Todd's TM Monday presentation; roles laundry list

Scientific Program Information

This will probably be most applicable to large conferences
  • "Upper-level information on Committees/roles
  • SP interaction with SPMS

2. After structure is decided

  • Add:
    • Short introduction to site organization and how to use
    • Site map
    • High-level overview of proceedings process for Jacow conferences (lots of links to other pages)
    • More cross-referencing links where appropriate
    • Expanded/revised tutorial section and topical index