Priorities
OiDB
v2.0
P0
-
Fix some technical issues that prevent new collections to appear.
- Quick-view plots of the uv coverage, phases and visibilities (Datalink), see ticket #579
, #773 (with samples)
and this meeting
- PDF PIONIER
- Check GRAVITY/MATISSE format is edible by OiDB , ticket. GRAVITY format to be tested, development in collab. with OiFitsExplorer.
- Adaptation for OIFITS 2.0 format. Feedback sur le validateur.
- Update CLIMB/CLASSIC L0. Need more recent .csv files. (last ones are from Dec 2015)
- Add L0 metadata from ESO/VLTI ticket #747 - mapper les metadata "requete" ESO sur Vizier + mapper les metadata "resultats" avec notre DM.
- Improve landpages and listing of instruments/facilities : send the instrument websites URL to Guillaume.
P1
- Dashboard cleaning
- DOI management for data citation - Decision de l'OSUG pour la definition du prefix du DOI (+ doi non opaques)?
- Healthchecks/alertes pour suivre le bon fonctionnement de la base.
- Lien des abstracts des proposals CHARA aux granules L0.
- Criterion display that marks if a given granule is suitable for image reconstruction. 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.
- Evolution cycle of a granule from L0 to L3. 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.
- Duplicate detection. Ticket #615.
- Complete some management interfaces to edit content (e.g. DataPI informations)
P2
- Quelle suite donner à la timeline ? P2 pour le moment
- Add the non-calibrated level (L1 data) and an interface that operates simple calibration schemes. Long-term
- Private access to data enabled for individual granules using the JMMC user accounts (ticket #556). Possibility of re-using the PIONIER collection case for group accounts.
- Better match the ObsCore DM (see meeting notes on 24 march 2015) AND THEN Declaration of OiDB
into VO registry (ticket #553), TAP declaration is done.
- Possibility to leave comments on a set of granules.
- Mail to olbin to get new members: database IOTA + catalog VIZIER + ask feedback.
- RSS flux (http://oidb.jmmc.fr/rss
) or news on olbin.vo, other notification mecanisms?
- How to identify human users /robots on the web pages ?
To classify
This topic: Jmmc/Software
> WebHome >
OiDb > Priorities20
Topic revision: r5 - 2018-12-05 - GuillaumeMella