1. 2.2 Data Group Membership: Reeves (chair), Lloyd, Morse. Reports to SSC. This group will be responsible for preparation of the AMMA-UK Data Protocol, which will be agreed and signed by all Partners and Associates of the consortium and all members of the SSC. This Data Protocol will be finalised by 1 April 2005. The Data Group will also be responsible for liaison with BADC. Data stewardship will be conducted primarily by BADC for which costs have been awarded (through Leeds).

2. Data Protocol AMMA-UK DP to cover all data collected by UK participants of AMMA Would copy of NERC UTLS DP be suitable ? NERC proposal 6 months submission, 2 years public NERC Consortium Agreement ? –Intellectual Property, Confidentiality (marked), Publication (30 days notification, 30 days response, 6 months delay) Is it suitable for both Partners and Associates? AMMA-EU data policy? –Intellectual Property, Confidentiality (marked), Publication (6 weeks response, 6 months delay) AMMA ISSC Data Base Transversal Centre?

3. Data collected on the BAe-146 aircraft will be covered by the FAAM Data Protocol (DP) –core and non-core data, the latter which can be covered by a separate agreement (i.e. AMMA DP) Raw data (+meta data) ? Preliminary data (BADC workspace) ? Freedom of Information Act – all data should be accessible QA/QC recommendations – e.g. error flags Satellite data accessed through CEH ? Model data ?

4. BADC Project Web Page Similar to http://badc.nerc.ac.uk/data/itop/. This explains how data can be submitted to and accessed from BADC.http://badc.nerc.ac.uk/data/itop/ BADC Project Workspace Place where files (documents, preliminary data etc) can be shared between project participants. BADC Archive File naming conventions

5. 1. Data to be produced Platform (e.g. 146, site name), Instruments, Data type (e.g. time series, 3-D data, frequency), File frequency and number (e.g. daily, per flight), Preferred format, (e.g. NetCDF, NASA Ames, jpeg), Expected size (Mb) 2. Data required Nature (e.g. model, satellite), Source (UKMO, ECMWF, NASA), Data type (e.g. time series, 3-D data, frequency), File frequency and number (e.g. daily, per flight), Preferred format, (e.g. NetCDF, NASA Ames, jpeg), Expected size (Mb), Can you already get this via BADC ?

6. Time scale EOP measurements start when ? Dry run for operational planning in 2005 Real-time data for flight planning

7. UTLS OZONE Data Protocol The aims of the Data Protocol are: to encourage rapid dissemination of scientific results from UTLS OZONE. to protect the rights of the individual scientists funded by UTLS OZONE. to have all the involved researchers treated equitably. to ensure the quality of the data in the UTLS OZONE data archive. These aims conflict at times, and it is hoped that the provisions of the protocol resolve these conflicts fairly. It is recognised that this cannot always be achieved to everyone's complete satisfaction; there are bound to be cases where individual interests clash with those of the UTLS OZONE programme. Therefore to try to meet these aims, all PIs involved in UTLS OZONE, in accordance with and on behalf of their co-investigators, must agree to abide by the following conditions:

8. 1.Preliminary data must be made available to other UTLS OZONE scientists as soon as possible. There are 2 advantages to quick release a) planning of the future phases of the mission can be greatly improved, and b) scientific evaluation of the data can occur in a timely manner. 2.Any corrections or amendments to the preliminary data should be announced as soon as possible. 3.Validated data must be made available to other UTLS OZONE scientists via the BADC within 6 months of creation. The data will then be made available to the public domain 18 months after its submission to the BADC. Exceptions to these times will be outlined in the Implementation plan. 4.Results of model studies using data acquired during UTLS OZONE must be made available to other UTLS OZONE scientists via the BADC. The time scale for submission is the same as that for validated data, as outlined in point 3. 5.Data submitted to the BADC must be in the data format agreed between UTLS OZONE PIs and the BADC. All agreed metadata describing the data must also be supplied.

9. 6.It is each PI’s responsibility to ensure that the data used in publications are the best available at that time. 7.All scientists involved in UTLS OZONE are to have equal and complete access to measurements and model results produced during UTLS OZONE. 8.If measurements or model results from other research groups within UTLS OZONE are used in a publication, joint authorship must be offered. This does not necessarily have to be accepted, particularly in cases where due credit and acknowledgement can be given in other, possibly more appropriate, ways. 9.Whilst the data is restricted from the public domain (see point 3), each PI has the right to refuse to allow his/her work, whether measurement or calculation, to be used in a publication or presentation prior to the PI’s own publication of that work. 10.Whilst the data is restricted from the public domain (see point 3), no data should be transferred to a third party without the originator’s consent. 11.In the event of dispute the final decision rests with the UTLS OZONE Scientific Steering Committee.

10. ITOP-UK Conditions of Use Applying to Forecasts and Non-Core Flight Data Should ITOP-UK data be used to support a research study, it is essential that the ITOP-UK Principal Investigator will be made aware that the data are being used. It is imperative that the ITOP-UK Principal Investigator be consulted when suspicious data is encountered or when interpretation of data becomes dependent upon understanding the underlying technique. Should a study using ITOP-UK data lead to some publication, it is expected that the relevant ITOP investigators will be offered co-authorship and the opportunity to comment on the manuscript prior to submission for publication. Whilst the data are restricted from the public domain (i.e. during a period of time of 18 months following submission to the BADC), the Prinicipal Investigator has the right to refuse to allow his work to be used in a publication or presentation prior to his own publication of that work.