1. Conferences - Hosting/co-hosting science conferences - Exhibit and present project output and services at community conferences Training Workshops - Data analysis workshops - Science review workshops - Fellowship workshops - Instrument/proposal workshops Visitor Support - Support individual visitors to the data center for training - Support data center personnel visits to community institutions for colloquia and workshops Helpdesk - Proposal support – observations, archival science, theory - Data analysis support

2. Web pages - Repository for supporting documentation, FAQs, software, guides, links - Repositories for community follow-up data (e.g. CFOP) - Citizen Science --- planethunters.org has positives and drawbacks News delivery (Notification of events, proposal solicitations, resources etc) - Newsletters and blogs (through email and websites) - Telegram services (e.g. GCN, ATel) - Social Media (email, Facebook, Twitter, Tumblr…..) Support Users’ Groups - Provides for community participation in developing data center operations and policy - selected to cover broad disciplines from community (not insiders) - more focused groups are required for specific, often technical, problem solving

3. Points raised: - Develop community support infrastructure before first light, not after, e.g. the XMM- Newton OM and Kepler were slow out of the blocks because support wasn’t ready. - How can PI-led teams evolve into community teams and PI team knowledge propagate into the community? - Kepler specific – Kepler requires interaction with a community (ground based observers) that do not use or need the project data directly. Can Kepler learn from e.g. Swift how to engage that community? - Is the international community being supported effectively? Would missions benefit from greater international participation? - Should NASA and the missions be fostering a culture where scientific productivity/impact has the same importance as running the mission?

4. Archive Services - Validation and verification of archived data - Provision of raw, calibrated, higher-level data - Provision of engineering and calibration data - Synergizing mission data content and formats with other missions and existing software - Aligning the different interests and services of mission and archive to best support the community Develop and support data analysis tools - Create open source projects - Avoid re-invention where possible - Synergize software with other missions - Don’t delay – be software-ready for launch and commissioning - Avoid software licenses – the cost to the community is wasteful and resented - Avoid writing proprietary code for pipelines – archived data becomes a black box for the community