1. IPY Data Management Archival and Data Access Status Catalogue Interoperability Status WIS-relation Øystein Godøy

2. The IPY operational snapshot  Still working on cataloguing WMO essential data (and to a certain extent data access) ‏  ECMWF and HIRLAM NWP (METNO) with online access (OpeNDAP, HTTP, WMS) ‏  OSISAF data with online access  THORPEX data sets in the North Atlantic winter 2008 mainly available  METNO surface observations added  Working on drifters, POPs, ITPs, IMBBs,...

3. Constraints  Limited funding requires prioritising  The full funding of METNO IPY-activities is unlikely to be received, implies a change in time plan/ambitions  Focus on ECMWF access and transformation  Done  Focus on Metadata exchange  Advantage OAI-PMH, easier/cheaper to implement  CIP is ISO23950 related, needed in the future, but too resource consuming within the current funding scheme

4. Exchange of metadata  Various technologies  OAI-PMH  IPY, CEOS WGISS  CSW 2.0.2/ISO23950  INSPIRE, WIS, GEOSS, CEOS WGISS CIP  OAI-PMH  Low cost/easy to implement  Recommended for harvesting metadata by CEOS WGISS Interoperability Handbook 1.1  http://wiki.ieee-earth.org/Documents/CEOS_WGISS_Interoperability_Handbook http://wiki.ieee-earth.org/Documents/CEOS_WGISS_Interoperability_Handbook

5. OAI-PMH  Software developed and tested  Norwegian project involving NP, HI, NILU, METNO  International Operational Data Coordination  Using DIF for exchange  Gaining experience with controlled vocabularies  Setting up run time rules  Regular (daily) export/import at 3 sites, to be extended  Evaluated for NDACC-AVDC-EVDC-GEOMON-GECA- EARLINET interoperability

6. Catalogue interoperability  DOKIPY do harvest IPY-metadata from GCMD  Working adaptions to local structures requried  DOKIPY will link with NSIDC  DAMOCLES will link with CADIS  IPY in Sweden is using the Open Source system for metadata developed by METNO, will implement OAI-PMH support  http://wiki.met.no/metamod/ http://wiki.met.no/metamod/  ArcticNet asked for exchange of metadata  AADC to be asked

7. Catalogue interoperability continued  Mark Parsons coordinating efforts with others  PANGEA, AADC,... ???  IPY Discussion Forum have been used to highlight problems  Insufficient ISO Topic Categories  Harmonisation of controlled vocabularies  Community developed like CF versus single institution controlled like GCMD  How to handle changes, updates, backwards compatibility, etc...  IPY is interdisciplinary...

8. Catalogue interoperability continued  Main show stoppers so far has not been implementation of the software  But rather handling various controlled vocabularies and mapping between these  The main reason being that IPY is interdisciplinary and data centres need to maintain existing commitments and catalogues  Controlled vocabularies are essential for smooth catalogue interoperability

9. Remote Sensing data sets  No dialogue with space agencies since last meeting  Software implementation required first  Experience with exchange mechanisms required to set up a proper system  Transformations of vocabularies needed  RAMP added at metadata level  IDN and eoportal added at metadata level  In principle exchange with other OAI-PMH systems should be easier now

10. Remote Sensing data sets continued  Adding support for CIP does not seem feasible in the present situation  More likely to be added after IPY after GEOSS, INSPIRE and WIS harmonisation of systems

11. IPY Operational Data Coordination Technology  http://ipycoord.met.no/ http://ipycoord.met.no/  METAMOD 2.x DAR -> WIS DCPC  To integrate IPY or scientific needs more seamless with the WMO community  Archives  OAI-PMH (adding CSW/ISO23950 in time) ‏  Shopping basket in time  THREDDS Data Server  HTTP/OpeNDAP  Better support for WMO formats  Although trouble experienced with the BUFR format used  OGC WMS (focusing at high latitudes) ‏

13. WIS-relation  VGISC project temporarily stranded  Different needs within consortium (GISC/DCPC) ‏  The focus for METNO in support of IPY is DCPC, not GISC functionality  VGISC as a discussion forum still exist and attempts to find a solution  METNO has discussion with EU-funded BALTRAD-project concerning possible SIMDAT- use

14. WIS-relation  VGISC partners examine possible software solutions to fulfil WIS requirements  Gap analyses based upon what the individual partners have got and the required functionality have been and is being performed by partners  Integration and adaptation of existing components  In most cases a mix of internal and external software

16. User Requests I3 User Role Assignment Procedure Applicable Data Policy I2 I1 Observations, Products and Associated Metadata Reference Information (WIGOS, IOC, etc)‏ Authorized Requests for Information Information Search Requests Catalogue Browse Requests Subscription Information « Ad Hoc » metadata Monitoring Data From all functions Control Actions to All functions O2 Reports of Performance against Requirements Delivered Information via « Push » Services (time-critical & non-time-critical)‏ Delivered Information via « Pull » Services (time-critical & non-time-critical)‏ O1 Information Search Results Information Services Dissemination Metadata DAR Metadata Catalogue POSSIBLE CHOICES SIMDAT base Sun OpenSSO base Geonetwork base MSS SMART / GEMS A3 Maintain and Expose Catalogue of Services and Information Manage Requests Catalogue Access « Ad Hoc » Routine « Push » Cache A6 Manage System Performance Monitoring Administration Assign User Role & Authorise Access to Information A2 & A4 Authentication Authorisation User & Data Policies Portal Make / Follow Request Browse / Search DAR Admin / Monitoring Portal A1 Collect Observations, Create Products and Archive Information Synchro & Harvesting Replication A5 Deliver Information to Users Legacy Databases Collection Retrieval