Notice: This application will enforce Multi-factor authentication (MFA) for NIH users beginning the evening of Wed Aug 3rd.
NIH | National Cancer Institute | NCI Wiki  

Document Information

Author: Denise Warzel
Email: warzeld@mail.nih.gov
Team: caDSR
Contract: [Contract number]
Client: NCI CBIIT
National Institutes of Heath
US Department of Health and Human Services

Contents of this Page
 

Sign off

Date

Role

CBIIT or Stakeholder Organization

Sherri de Coronado

---

Section Chief Semantic Infrastructure and Operations

CBIIT

Dianne Reeves

--

Data Standards and Metadata Conent

CBIIT

Denise Warzel

---

Metadata and Models Software Engineering

CBIIT

Sima Padya

--

Technical Project Manager

Leidos

The purpose of this document is to collect, analyze, and define high-level needs and features of the National Cancer Institute Center for Biomedical Informatics and Information Technology (NCI CBIIT) curator caDSR Metadata cleanup activities. This document focuses on the cleanup activities that have and are being done by development team in conjunction with Curators from the end user perspective. A supplementary wiki page will be developed for the dev team perspective pertaining to actually running/rerunning the scripts and reports created as a result of this effort.

Vision and Needs

The objective of this initiative of the Metadata Cleanup is to [brief statement of the release theme, for example, improve usability for creating and maintaining value meanings].

This release will address [detailed description of the problem statements to be resolved by the release, such as fixes, usability improvements, functional improvement, and performance improvements for an incremental release.

This set of cleanup activities was first recorded in 2010.  In 2016 we are preparing for a modernized infrastructure and want to clean up the content in preparation.

Current Solution

Due to the original business rules and tool functionality, in addition to the maintenance activities ongoing in EVS around concept used in caDSR content development, semantically duplicate metadata objects occur in different contexts. Also, prior to Value Meanings becoming administered items and having EVS concepts related to them, duplicate text/string based VMs were created if the spelling or case (mixed vs lower/upper) of the text strings were slightly different. EVS performs monthly maintenance on concepts that may have been used in caDSR, name changes, definition changes, retire/split/merge actions. These actions have an impact on content that has been curated based on these concepts.

Proposed Solutions

Develop cleanup scripts and user reports that can be run iteratively to remove the duplicates described in functional requirements below, reassign related components to the remaining harmonized content and suggest new features to support this activity better in the future.

Functional Requirements

Each major piece of work related to Metadata Cleanup activities is listed below.

GForge number
(hyperlinked)

Brief description of functional requirement
(enhancement or new feature)

Status
(Active/Pended/Completed)

Iteration

GF 23756

CADSRMETA-2 - Getting issue details... STATUS

Eliminate Duplicate Value Meanings - See Value Meaning Cleanup (login required)

--

---

 

Add script to report unused Value Domains in the nightly Sentinel Audit Report

--

 

---

Revive/rerun old concept cleanup utility - See caDSR Metadata Cleanup Task Summary

---

---

GF 11350

Create Concept Cleanup Report - See caDSR Metadata Cleanup Task Summary

  • Convert Concept Cleanup utility to use current LexEVS API
  • Update Java Utility for Matching EVS Concepts to LexEVS API

---

---

---

Create feature requests to allow Curators to find and fix data errors

---

---

GF 11351

- Eliminate Duplicate Object Class Administered Items in different contexts - See caDSR Metadata Cleanup Task Summary

  • Eliminate Duplicate Property Administered Items in different contexts - See caDSR Metadata Cleanup Task Summary
  • Eliminate Duplicate DECs (based on Object Class and Property cleanup)

---

---

GF 11352

Eliminate Duplicate Representations Classes

---

---

GF 16754

Retire caDSR Metathesaurus Concepts (Part 2A)

  • Concept Name Matches Script and Report (2A)
  • Review Name Matches Feedback and Process changes (2A)
  • Process Synonym Changes (2A Version 2)

---

---

---

Processes Changes for Content Migration (2B)

---

---

GF 16754

Synchronize caDSR Concepts with EVS (Part 3)

---

---

---

Generate Discrepancy Reports

---

---

---

Reconciliation Routine

--

---

Functional Bug Fixes

Each bug fix included in this release is described in detail below.

GForge number
(hyperlinked)

Brief description of bug

Status
(Approved or Proposed)

Iteration

---

---

---

---

Non-Functional Requirements

This section describes in detail all the related requirements which must be met for this release but do not add functionality. These requirements are included in the scope and project plan due to level of effort or relative importance to the overall success of delivery of the release.

GForge number (hyperlinked)

Brief description of non-functional requirement

Status
(Approved or Proposed)

Iteration

---

Example, "Although there are no functional changes to the product for this requirement, the team must migrate the existing software to Hibernate 4.1 to be compatible with the caCORE technology stack."

---

---

General Support Activities

This section describes in detail all the related activities which must be performed for this release but do not add functionality. These activities are included in the scope and project plan due to level of effort or relative importance to the overall success of delivery of the release.

GForge number (hyperlinked)

Brief description of general support activity

Status
(Approved or Proposed)

Iteration

---

Example, "Level 2 Support, integration of help and training to the user community."

---

---

Stakeholder Summary

Customer Name

Role

Interest/Need

[Name]

[Title or role]

---

CBIIT Staff/Contractor Name

Role

Responsibilities

[Name]

[Role in this project]

---

Technical Environment

This product uses the following technical components which have been derived from the current CBIIT Technology Stack.

Client Interface

  • [Example, Internet Explorer 6.0 and above]
  • [Example, Mozilla v. 1.5.0.3 and above]

Application Server

[Example, Apache Tomcat 5.5.9]

Database Server

[Example, Oracle 9i]

Operating System

  • [Example, Windows 2000. XP, Vista]
  • [Example, Unix (Sun Solaris)]

[Other]

Product Dependencies

This release is dependent on the caCORE components or products documented in the CORE Product Dependency Matrix.

[Provide additional explanation as applicable. For example, "The EVS vocabulary systems are used by the Java client to retrieve and validate concept information for naming and defining meanings."]

Out of Scope Items

Items that are out of scope were evaluated as part of the initial scoping activities for this release, and subsequently not included in the final approved scope. These items are also documented in the cumulative backlog of requirements found on the product GForge site. They include out-of-scope functional requirements (enhancements or new features), bug fixes, non-functional requirements, and general support activities.

GForge number (hyperlinked)

Brief description of item moved from the in-scope section
with brief explanation added of why it was not included in this release

Iteration during which the item
was removed from in-scope

---

---

---

Document History

Document Version:

Click the Info tab. View the Recent Changes or click the link to view the page history.

Last Modified:

Refer to the first line displayed in the document window.

Project GForge site:

[Project GForge site link]

Most current version:

Unless the display includes a notice that you are viewing a previous version, you are viewing the most current version of this Scope Document for the release indicated in the title.

Revision history:

Click the Info tab. In the Recent Changes area, click the link to view the page history.

Review history:

Click the Info tab. In the Recent Changes area, note the developer who made each change and the date and time. Refer to the Key People Directory for their roles. Click the link to view any page or to view the page history, and then click the link for a page. When the page opens, view the comments and changes made in that version.

Related documents:

[Name and URL of each related document]

 

 

  • No labels