ROADMAP
OiDB
- Until end of 2015: Support, bug-fixing and improvement of
OiDB 1.0
- From early 2016, emphasis on the developments for
OiDB 2.0:
OiDB 2.0 functionnalities
Done:
- Quick-view plots of the uv coverage, phases and visibilities (Datalink), see ticket #579. P0 Coordinate with Myriam-OiFitsExplorer. Inspiration from OHANA? Probably with Java. Start from use-cases.
- Evolution cycle of a granule from L0 to L3. P1 long-term. Work to be linked with duplicates since it uses similar checking tools in the granules. Make sure ids (prog_id, obs_id) are well defined because they are going to be central in the life cycle of data.
- Private access to data enabled for individual granules using the JMMC user accounts (ticket #556). P2. Possibility of re-using the PIONIER collection case for group accounts.
Pending:
- Criterion display that marks if a given granule is suitable for image reconstruction. P1 - short-term Create a ticket. Criteria to be defined with Eric Thiebaut. Info to be deduce from metadata and that we can use to filter the search of data.
- Duplicate detection. P1 long-term. Ticket #615. Duplicated records must be highligthed in the result table.
- DOI management for data citation - Long term P1. Create a ticket from exchange with INIST.
- Possibility to leave comments on a set of granules. P2
OiDB 2.0 contents
Done:
- Improve landpages and listing of facilities. P0
- Add L0 metadata from ESO/VLTI - P0 ticket #747 - mapper les metadata "requete" ESO sur Vizier + mapper les metadata "resultats" avec notre DM.
Pending:
- Update CLIMB/CLASSIC L0 Mail, Mail To Theo fin mars. Need more recent .csv files. P0
- Improve landpages and listing of instruments : send the instrument websites URL to Guillaume. P0
- Add the non-calibrated level (L1 data) and an interface that operates simple calibration schemes. P2 long-term
Environnement
Pending:
- Check GRAVITY/MATISSE format is edible by OiDB , ticket. P0-P1. GRAVITY format to be tested, development in collab. with OiFitsExplorer.
- Better match the ObsCore DM (see meeting notes on 24 march 2015) AND THEN Declaration of OiDB into TAP/VO registry (ticket #553). P1, but lowest priority action for oidb 2.0. to do only if all the previous P0 actions are completed before the end of the year. Status to be checked at the Trieste Interop in october 2016.
- Adaptation for OIFITS 2.0 format P2 long term.
Communication
Done:
- Mail to olbin to get new members: database IOTA + catalog VIZIER + ask feedback. Create a ticket. P0
- RSS flux (http://oidb.jmmc.fr/rss) or news on olbin.vo, other notification mecanisms? P1
Statistics (Dashboard)
Pending:
- How to identify human users /robots on the web pages ?
- Statistics are logged into an XML file. Ask Guillaume this file to prepare SPIE poster/talk.