dm_ppt_np_v01 configuration management of umm models january 2016
DESCRIPTION
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.TRANSCRIPT
DM_PPT_NP_v01
Configuration Management of UMM Models
January 2016
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
DM_PPT_NP_v01
3
High Level Change CycleCommunity
Input
Yearly ESO Review*
WorkoffPost Updated Documentati
on
Implementation
UMMAs CMR schemaAs 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.
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.
DM_PPT_NP_v01
5
Change Approval ExamplesType of Change
ESDIS+ Approval Required? Examples
Correct clerical mistakes or cosmetic issues No typo, misspelling, grammarUpdate field descriptions No update descriptions to provide better help textAdd new optional field No add ISO function code to Related URLChange name of field Yes EntryId > Shortname
Remove field or subfield YesRemove title and version from Resource Citation? (already under Collection Information)
Split field into multiple partsYes for required fieldsNo for non-required fields File size > File Size, File Units
Change whether field is required (add/delete) Yes DOI and Related URL are 'one or the other' for Resource Citation
Change cardinality of field Yes
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 vocabulary Yes Mime TypeAdd or remove values from controlled vocabulary picklist Yes Processing Level; Collection ProgressChange mapping of field to ISO, ECHO, DIF No ??
Normalize a set of fields No Organization, Personnel, Platform, Instrument, Sensor
DM_PPT_NP_v01
6
Create corresponding implementation tickets, linked together in JIRA
Detailed Change Cycle
JIRA:ECSE Tickets
JIRA: MMT Tickets
ESDIS Approv
al 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 TicketJIRA: MMT
Ticket
DM_PPT_NP_v01
7
Change Impacts
Source Document
Repository
Propose changes via:
Approve implemented changes via:
End Product
UMM-x document
Jama CMR JIRA ticket / ERB
Jama peer review Baselined Jama version of UMM document (e.g. v1.5)
UMM-x schema Stash CMR JIRA ticket / ERB
Stash Peer review Baselined version of the schema to match the document (e.g. v1.5)
MMT form Stash MMT JIRA ticket / ERB
Stash Peer review MMT form in Operations to match a specified version of the schema
Metadata records in CMR
CMR TBD TBD 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
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
DM_PPT_NP_v01
REFERENCE MATERIALS FROM CMR OPERATIONS PLAN (DRAFT OUTLINE)
DM_PPT_NP_v01
10
CMR Configuration Management - excerpt from CMR Operations Plan Draft Outline
Repository CM Board / Review Process Change Process Document
Update Cycle
Software Stash / Git Sprint Process ESEC EED Agile Processes
continuous
Metadata Standards, Schemas, and ModelsNASA extension of ISO 19115 EMFD Barry Weiss document Barry Weiss
documentAs needed
Metadata Schemas (includes UMM-JSON)
CMR Stash* TBD (ECSE-49) As needed
UMM-* documents Jama* ESO Review (in Jama) CMR Life-Cycle Document
As needed
RequirementsHigh Level (Contractual) Requirements (e.g. 423-RQMT-00x)
COMET (RQMT) ESDIS CCB ESDIS Project Configuration Management Procedures (423-PG-1410.2.1)
As needed
User Stories Jama (CMR project) Jama ReviewERB (for one offs)
CMR Life-Cycle Document
As needed
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