1. Support of contact information with multiple organization structure in CWIC & IDN Lingjun Kang (lkang3@masonlive.gmu.edu)lkang3@masonlive.gmu.edu Eugene G. Yu (gyu@gmu.edu)gyu@gmu.edu Archie Warnock (warnock@awcubed.com)warnock@awcubed.com

2. Outline Context Dataset contact info in CWIC Harvest/populate contact info – From IDN – From data provider API Challenges Metrics support Expected inputs from data provider during DIF registration

3. Context Dataset level contact info – CWIC currently provides contact info (e.g. responsible parties with different roles) for each dataset Contact info with multiple/hierarchical organization structure – Based on that, CWIC plans to provide metrics being aggregated by dataset ownership (with hierarchical structure)

4. Dataset ownership example Dataset: AVHRR_Pathfinder-NODC-L3C-v5.2 Metadata source: IDN metadata (ISO19115) Dataset ownership related info in metadata Xpath: /gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_Da taIdentification/gmd:pointOfContact/gmd:CI_Responsibl eParty Values: 1)Organization name  DOC/NOAA/NESDIS/NODC > National Oceanographic Data Center, NESDIS, NOAA, U.S. Department of Commerce 2)Role type  resource provider

5. Contact info in CWIC NameScopeDescription “Originator/creator”DatasetParties who creates the dataset “Distributor/publisher”DatasetParties who distributes the dataset “CWIC point of contact” Metadata Party (CWIC) who can be contacted for acquiring knowledge about or acquisition of the resource

6. Contact info in CWIC 1.“ Originator/Creator” (Dataset) 1.1. In CWIC ISO 19115-2 metadata 1) under gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gm d:pointOfContact/gmd:CI_ResponsibleParty (with CI_RoleCode: originator) 2) under /gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_Respon sibleParty 1.2. In CWIC Dublin Core metadata

7. Contact info in CWIC 2.“Distributor/publisher” (Dataset) 2.1. In CWIC ISO 19115-2 metadata 1) under gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfCo ntact/gmd:CI_ResponsibleParty (with CI_RoleCode: originator) 2) under /gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation /gmd:CI_Citation/gmd:citedResponsibleParty/gmd:CI_ResponsibleParty 3) under /gmd:MD_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/gm d:MD_Distributor/gmd:distributorContact/gmd:CI_ResponsibleParty 2.2. In CWIC Dublin Core metadata

8. Contact info in CWIC 3.“CWIC point of contact” (Metadata) In CWIC ISO 19115-2 metadata under /gmi:MI_Metadata/gmd:contact In CWIC Dublin Core metadata

9. Harvest contact info Sources of contact info – IDN metadata (ISO19115) – Data provider API (e.g. NASA ECHO RESTFUL)

10. Harvest/populate contact info Harvest dataset level contact info from IDN

11. Harvest/populate contact info Metadata example From IDN metadata (1) /gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact) Map to contact info elements in CWIC metadata 1.Harvest dataset level contact info 2.Collect detailed contact info 3.Collect hierarchical ownership info (if available) 4.Map to contact info elements based on IDN/CWIC RoleCode mapping (challenges)

12. Harvest/populate contact info Metadata example From IDN metadata (2) /gmd:MD_Metadata/gmd:identificationInfo/ gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:citedResponsibleParty) Map to contact info elements in CWIC metadata 1.Harvest dataset level contact info 2.Collect detailed contact info 3.Map to contact info elements based on IDN/CWIC RoleCode mapping (challenges)

13. Harvest/populate contact info Metadata example From IDN metadata (3) /gmd:MD_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributor/ gmd:MD_Distributor/gmd:distributorContact/gmd:CI_ResponsibleParty Map to contact info elements in CWIC metadata 1.Harvest dataset level contact info 2.Collect detailed contact info 3.Map to contact info elements based on IDN/CWIC RoleCode mapping (challenges)

14. Harvest/populate contact info Harvest contact info from data provider API (e.g. ECHO)

15. Challenges Identification of IDN DIF fields available for contact info during registration: – DIF field for parties who creates the datasets (“Originator/Creator” in CWIC) – DIF field for parties who distributes the dataset (“Distributor/publisher” in CWIC) – How these DIF fields are mapped to IDN ISO metadata (to be harvested by CWIC)

16. Challenges Mapping contact info from IDN ISO metadata to CWIC metadata (ISO + Dublin core) – Role code mapping from IDN ISO to CWIC ISO Reuse IDN ISO roles in CWIC ISO? Map IDN ISO roles to 3 roles in CWIC ISO (information loss)? – Role code mapping from IDN ISO to CWIC Dublin core How to map IDN ISO roles to 3 roles in CWIC Dublin core (information loss)? ISO CI_RoleCode http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_RoleCod e

17. Metrics support Extend CWIC metrics to support metrics aggregation based on hierarchical ownership – Extend metrics collection module – Extend metrics aggregation module – Extend metrics GUI

18. Expected input from data provider during DIF registration The IDN is an important source where CWIC harvests dataset level contact info (e.g. hierarchical ownership). If the contact info is not provided by the data provider from other trusted sources, it is data provider’s responsibilities to register sufficient contact info (i.e. DOC/NOAA/NESDIS/NODC) during IDN DIF registration. Then CWIC is capable to provide metrics aggregation based on hierarchical ownership info. http://gcmd.nasa.gov/learn/keyword_list.html

19. Questions and Discussion