22 | | * Establish the internal IS-ENES2 metadata organisation |
23 | | * Need to make sure it is cross-cutting wrt IS-ENES2 work packages (JRA, NA etc). |
24 | | * May take some advantage of es-doc cog, and/or telcos, as well as internal mechanisms. |
25 | | * Re-establish the European network to feed into es-edoc |
26 | | * Establish and document priority actions for IS-ENES2 activities |
27 | | * Begin a programme of external communication |
28 | | * Identify an external user group and a set of beta testers. |
29 | | * Consider what training is needed. |
30 | | * Formalise links with other projects (EU, US where necessary (and not already covered by es-doc). |
31 | | * Liaise with CMIP6 preparation. |
| 22 | 0. Establish the internal IS-ENES2 metadata organisation |
| 23 | a. Need to make sure it is cross-cutting wrt IS-ENES2 work packages (JRA, NA etc). |
| 24 | a. May take some advantage of es-doc cog, and/or telcos, as well as internal mechanisms. |
| 25 | 0. Re-establish the European network to feed into es-edoc |
| 26 | 0. Establish and document priority actions for IS-ENES2 activities |
| 27 | 0. Begin a programme of external communication |
| 28 | a. Identify an external user group and a set of beta testers. |
| 29 | a. Consider what training is needed. |
| 30 | a. Formalise links with other projects (EU, US where necessary (and not already covered by es-doc). |
| 31 | a. Liaise with CMIP6 preparation. |
| 32 | |
| 33 | Metadata Management Issues ([[span(style=color: #FF0000,these are the most time critical activities)]]): |
| 34 | 0. Quality control the existing CMIP5 documentation. |
| 35 | 0. Update existing CMIP5 documentation in the light of new knowledge acquired for the IPCC AR5. |
| 36 | 0. Communicate with modelling groups accordingly. |
| 37 | |