AWOB Preliminary Meetings

MPDL,GAVO

Agend

 * 1) Introduction of all people working on the project together with their scope of duties for the project
 * 2) Organization of the Kick off Meeting:
 * 3) When and where?
 * 4) What (which topics should be on the agenda)?
 * 5) Who will organize the meeting as Hr. Vogler is not officially employed yet?
 * 6) General
 * 7) Will the project language be English or German?
 * 8) Colab for description and specifications
 * 9) JIRA for issues tracking
 * 10) Mailing list for general communication
 * 11) Brief report on a new project(eRosita) at MPE which could be an interesting usecase for the AWOB
 * 12) Presentation preparation for the kick-off (input from Herr Sander)
 * 13) Was ist die Situtation und die Herausforderung bei den Astronomen, die AWoB adressieren soll?
 * 14) Was tut AWoB grundsätzlich und wie fügt sich dies in den wiss. Fachprozess ein?
 * 15) Projektübersicht für Manager (i.e. 3 Arbeitsblöcke/Phasen, Endergebnistyp, welche Projektmitarbeiter, welche Kosten)
 * 16) Stakeholder (Institute/Einrichtungen und operative Hauptansprechpartner und Entscheider/Leiter/Direktoren)

Minutes

 * Introduction
 * The project shall be based as an Open Concept, flexible and dynamic
 * all participants shall speak openly about their ideas
 * results of other communities will be also addressed, so that the project does not reinvent
 * important to establish transparency in communication from this project to other MPDL projects and vice versa, to make sure potentially reusable resuts are indeed reused
 * how close AWOB project now has to stick with what is in the project proposal?
 * the project proposal deliverables would have to be re-addressed again in context of latest developments and results from other (MPDL and external) projects and concrete work & requirements from the scientists
 * Kick-off Meeting
 * there will be a Kick-off meeting with all participants on the AWOB project (including people from the Institutes).
 * this meeting and kick-off presentations would be organized by Wolfgang and Andreas (approximate timeline second week May 2011)
 * the meeting will be in Garching (2 hours for all participants, project people may reserve some more time)
 * Goal: to introduce the stakeholders
 * Kristina will set-up Doodle - will be forwarded to all people of interest (proposals to Wolfgang and Andreas)
 * Ramp-up Meeting separate meeting would be organized already in April to initiate start-up work and provide sufficient level of content for the kick-off
 * agenda/topics to be gathered by Natasa (it is envisioned as a working meeting, so we will have some presentations on the project and related topics)
 * meeting will be held at MPDL
 * Goal: to exchange more substantial content information by direct participants and define/distribute the first actions such as: review of the project proposal, checking for related projects status etc.
 * Kristina will set-up Doodle
 * General
 * Project language: English
 * Colab will be used for specifications, scenario descriptions etc.
 * mailing list will be set-up
 * toDo: check possibility to link the mailing list with Colab (could actually be nice point to address, as it also covers some AWOB workflows)
 * JIRA for issue tracking
 * Note: Colab, JIRA, mailing lists and SVN for code repository are already something which are as standard services offered by MPDL (no need to set-up completely new environment for now)
 * gathering requirements, structuring of information in Colab: experiences from other projects will be used
 * we could exchange a bit more information on the Ramp-Up meeting
 * Working process: technical people meet - or VidConf (as Jaiwon sits at MPE in Garching) - potentially Tuesdays are good for several reasons: dev meetings anyway on this day, also Andreas would be present on Tuesday (due to 50% working hours)
 * Planned availability of Andreas: Tuesday, Thursday (at MPDL), Monday (at MPE)
 * Planned availability of Wolfgang: Monday (at MPE), Thursday (at MPDL)

27.10.2009
Transcription of the whiteboard by Wolfgang, comments in [] by GL:



[Functions of AWOB]


 * Create:
 * Tex
 * Text
 * Upload: [GL Intended was here that we must be able to understand certain kinds of uploaded data]
 * Script
 * FITS
 * JPEG
 * VOTable
 * tabular data
 * Describe uploaded products [in plain text and
 * Apply tools
 * Visualisation (e.g. Aladin)
 * Cross-correlate [catalogues internal and external]
 * Mash-ups (logged)
 * Registry federation [GL AWOB should be a portal to VO: query registry to find IVOA services, act as client to services, etc]
 * Relate/Aggrgate
 * Search
 * Resource Management
 * Statistics
 * Special Plugins
 * SQL Query
 * with results-code inclusion [?]
 * Log book [automated and "hand-written"]
 * database management
 * create table
 * view
 * edit/update
 * schema edit
 * FITS metadata extraction
 * synchronouse tool [?]

[How to describe the main, most important features of AWOB]


 * 1) Collaborative working environment
 * 2) sharing of resources
 * 3) enriched publications
 * 4) enable for DLTP
 * trust
 * support of lifecycle
 * support for cooperation
 * automatic metadata genration
 * auto logbook support
 * provenance
 * service mashups

Entry points [what are the different views that AWOB offers to the users, how will users approach AWOB]


 * publications [users read a paper, wish to get access to actual underlying data]
 * fields/topics [AWOB can provide a view based on common topics, metadata fields (??)]
 * groups [AWOB will show all groups taht exist/are available to a user]
 * login [a user logs in and goes to own home page, from which user can view all projects etc that user is associated to, has access to]

Visibility [authorisation levels]
 * persons
 * groups
 * public

16.10.2009
Screenshots

10.12.2008

 * Discussion about needed resources (see results on MPDL Project).

25.09.2008

 * updated presentation by Gerard/Jaiwon/Wolfgang (see under SVN of MPDL (restricted)
 * outcome:
 * First draft of MPDL project proposal until 10th of oct (Ulla, Natasa), focusing on requirements and approach
 * First draft of eSciDoc HowTo for definition of high-level requirements

15.09.2008

 * first brainstorming at MPDL/Munich

Attached Documents

 * [[Image:VOandMPDL.ppt|slides1]]