1. Advanced ISO Topics ISO for Data Documentation

2. Contents Content Updates – gmx:Anchor for text – Codelists NCEI Component Registry – Resolved Records – Unresolved Records Related Standards – ISO 19110 – ISO 19111 Status of Standards

3. Special Problem: I have an element that is a free text domain. How can I restrict this field to a set of defined terms?

4. gmx:Anchor for text anchor (gmx:Anchor) can be used as a substitute for a CharacterString when you want to restrict the free text to a controlled vocabulary. Ex: Pearl Harbor, HI can be replaced by Pearl Harbor, HI In this implementation example, the gmx:Anchor points to a vocabulary that containing a specific vocabulary entry.

5. Special Problem: Codelists I have an element that uses a codeList but the codeList values do not contain the information I need. How can I extend the codeList or can I use my own? Creators can supply your own codeList anywhere in the Standard by pointing to a custom location instead of the standard location. Of course, this could cause interoperability problems, so it should not be done without careful consideration of the implications.

6. NCEI Component Registry - Docucomp

7. Example CI_ResponsibleParty

8. Unresolved Records Record Services Sample record

9. Resolve Records

10. Ideally, you have a single component with a default role that you can “overwrite”. When you resolve the component, the specified role will override and replace the default component role value. Special Problem: How do I change the default role value of a responsible party component?

11. Example of ‘role’ Ex: National Coastal Data Development Center (pointOfContact)"> originator

12. Example of ‘role’ Ex: The component National Coastal Data Development Center (pointOfContact)"/> Has a default role of pointOfContact

13. Related Standards -19110 This is a separate document that can be used to describe the ‘content’ of your dataset,when appropriate. It is similar to the CSDGM Section 5 Entity and Attributes A “data dictionary”

14. Content Information

16. FC_FeatureCatalogue

17. Future ISO 19110 Feature Catalog use

18. Related Standards -19111 How do I document the Spatial Referencing?

19. ISO 19111 Spatial Referencing Use

20. Use citation and identifier to reference to external 19111 Use components to reference to external registries – EPSG http://www.epsg-registry.org/http://www.epsg-registry.org/ – spatialreference.org http://www.spatialreference.org/http://www.spatialreference.org/

21. Related Standards -19119 How do I use ISO 19119 to document Services?

22. ISO 19119 Service Metadata use

24. Special Problem: How can I document biological data? The ISO 19115 and -2 can be used to describe biological data. Use the metadata extension information provided in the ISO 19115 standard as needed. Extended ISO Biological schema available via ftp://ftp.ncddc.noaa.gov/pub/Metadata/NOS_CD/schemas/ISObio/ See Biological Workbook

25. http://service.ncddc.n oaa.gov/rdn/www/met adata- standards/documents/ BIO-Metadata.pdf Biological Profile Additions

26. MD_DataIdentification

27. Dataset Series How do I build hierarchical relationships using metadata?

28. Datasets, Aggregates and their Metadata – Hierarchical Metadata

30. Hierarchical Metadata

31. Subsets

32. Building Relationships Platform Data type/sensor

33. Cruise 1Cruise2Cruise 1 Building Relationships Program Platform Data type/sensor

35. Status of Standards

36. Is 19110 still going to be separate in 19115-2? 19139 XML schema implementation 1911019111 MI_ MD_ FC_ 19119 Services SV_

37. QUESTIONS ncddcmetadata@noaa.gov