1. DM_PPT_NP_v01 Configuration Management of UMM Models January 2016

2. DM_PPT_NP_v01 2 Sources of change requests MMT users –Alpha and beta testers –Eventually, all metadata providers (includes GCMD providers and DAACs) –Metadata curators ESDIS ESO Reviews CMR and MMT developers CMR SE group ISO

3. DM_PPT_NP_v01 3 High Level Change Cycle Community Input Yearly ESO Review* Workoff Post Updated Documentation Implementation UMM As CMR schema As MMT form ESDIS Periodic review boards + ERBs *A model’s first ESO review is an approval gate prior to implementation. Afterwards, ESO reviews are reviewing an As-Built UMM model which will also include several recommendations for the ESO body to approve/reject.

4. DM_PPT_NP_v01 4 Who Approves Changes? Change Request Approvals fall into two categories based on the severity of the change –ERB Approval Level Changes – these are change requests represented by JIRA tickets in the UMM, CMR and MMT projects, which can be approved by the existing ERB (Andy/Luther/Katie) –ESDIS+ Approval Level Changes – these are change requests represented by JIRA tickets in the ECSE project which require the ESDIS + (Optional) Community Members approval. The ESDIS group could reject tickets, approve them for implementation or approve them to be presented to the ESO community as “recommendations” only. Recommendations are listed in a separate section of the UMM-x document.

5. DM_PPT_NP_v01 5 Change Approval Examples Type of ChangeESDIS+ Approval Required?Examples Correct clerical mistakes or cosmetic issuesNotypo, misspelling, grammar Update field descriptionsNoupdate descriptions to provide better help text Add new optional fieldNoadd ISO function code to Related URL Change name of fieldYesEntryId > Shortname Remove field or subfieldYes Remove title and version from Resource Citation? (already under Collection Information) Split field into multiple parts Yes for required fields No for non-required fieldsFile size > File Size, File Units Change whether field is required (add/delete)YesDOI and Related URL are 'one or the other' for Resource Citation Change cardinality of fieldYes TilingIdentificationSystem > Systems; multiple URLs to single URL for Resource Citation; DOI and Related URL are 'one or the other' for Resource Citation Change from free text to controlled vocabularyYesMime Type Add or remove values from controlled vocabulary picklistYesProcessing Level; Collection Progress Change mapping of field to ISO, ECHO, DIFNo?? Normalize a set of fieldsNoOrganization, Personnel, Platform, Instrument, Sensor

6. DM_PPT_NP_v01 6 Create corresponding implementation tickets, linked together in JIRA Detailed Change Cycle JIRA:ECSE Tickets JIRA: MMT Tickets ESDIS Approval Board Existing ERB Perform Analysis / Provide Recommendation Reject Approve for Recommendation Only Approve for Implementation Add Recommendation in Jama UMM-x Project for ESO Review JIRA: CMR Tickets JIRA: UMM Tickets Reject Approve for Implementation MMT: Update MMT Forms CMR: Update Schema + CMR Translation Code UMM: Update Field Information in Jama UMM-x Project Move ticket to ECSE bucket for additional analysis JIRA: UMM Ticket JIRA: CMR Ticket JIRA: MMT Ticket

7. DM_PPT_NP_v01 7 Change Impacts Source DocumentRepositoryPropose changes via: Approve implemented changes via: End Product UMM-x documentJamaCMR JIRA ticket / ERB Jama peer reviewBaselined Jama version of UMM document (e.g. v1.5) UMM-x schemaStashCMR JIRA ticket / ERB Stash Peer reviewBaselined version of the schema to match the document (e.g. v1.5) MMT formStashMMT JIRA ticket / ERB Stash Peer reviewMMT form in Operations to match a specified version of the schema Metadata records in CMR CMRTBD Metadata records in native format, but able to be converted into any specified UMM version When the UMM-x model changes, there may be corresponding changes to the following ‘source’ documents Impact to clients and providers will be minimized by versioning the UMM

8. DM_PPT_NP_v01 8 UMM-x Document in Jama Recommend Jama be THE source repository for UMM. –Current most recent Word docs should be uploaded into Jama –Changes made in Jama concurrently by multiple different authors –UMM “baselined” as needed to match the UMM schema versions –Reviews conducted as needed out of Jama –Any UMM “baseline” can be exported to a Word document when we want to post it on the wiki

9. DM_PPT_NP_v01 REFERENCE MATERIALS FROM CMR OPERATIONS PLAN (DRAFT OUTLINE)

10. DM_PPT_NP_v01 10 CMR Configuration Management - excerpt from CMR Operations Plan Draft Outline RepositoryCM Board / Review ProcessChange Process Document Update Cycle SoftwareStash / GitSprint ProcessESEC EED Agile Processes continuous Metadata Standards, Schemas, and Models NASA extension of ISO 19115EMFDBarry Weiss document As needed Metadata Schemas (includes UMM- JSON) CMR Stash*TBD (ECSE-49)As needed UMM-* documentsJama*ESO Review (in Jama)CMR Life-Cycle Document As needed Requirements High Level (Contractual) Requirements (e.g. 423-RQMT-00x) COMET (RQMT)ESDIS CCBESDIS Project Configuration Management Procedures (423- PG-1410.2.1) As needed User StoriesJama (CMR project)Jama Review ERB (for one offs) CMR Life-Cycle Document As needed

11. DM_PPT_NP_v01 11 CMR Process and Procedures Documents CMR Life-Cycle Document (Rev 1, 3 Feb 2015) – Recommendation: review and revise to put in alignment with Operations Plan; possibly embed in Operations Plan CMR Metadata Quality Assurance Review Process – Recommendation: Evolve this process for CMR curation GCMD Keyword Community Guide