Resolve redundancy between PersonCredential and CredentialAward/CredentialDefinition structure.

[jgoodell2]

This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.

Author(s)
Jim Goodell

Authoring Organization(s)
CEDS Team

Email Address
jimgoodell@qi-partners.com

Use Case Title
Resolve redundancy between PersonCredential and CredentialAward/CredentialDefinition structure.

Use Case Overview
This change would either 1. replace PersonCredential by merging properties into CredentialAward or CredentialDefinition and link to StaffCredential, or 2. keep the redundant table but add an optional link to CredentialDefinition.

The decision may be guided by the potential impact and perceived benefit by the OSC. Option 1 would be a breaking change but would resolve the redundancy. Option 2 would not be a breaking change, it would only add a relationship that could be used to provide richer detail with CredentialDefinition linked to PersonCredential.

Pull Request Number(s) (If applicable)

Use Case Background
Provide information related to why these changes/additions are needed.
The IDS currently supports redundant structures for information about a credential held by a person. 1. PersonCredential is an older construct originally designed to support educational staff qualifications for a job with properties for things like license number. It links to the StaffCredential table with statuses such as RefTeachingCredentialBasis and CPR Certification Expiration Date. 2. CredentialAward which links a Person to any kind of credential defined in CredentialDefinition, is a newer construct designed to support any kind of credential and to be compatible with de-facto standards for credentials.

Components Affected
CEDS Integrated Data Store (complete IDS Design Overview Table)
CEDS Data Warehouse (complete DW Design Overview Table)
CEDS Data Migrations (complete Data Migration Impact Analysis Table)

CEDS Element Gap Analysis
No new elements are proposed, only element positions and relationships in the IDS.

---

INTEGRATED DATA STORE DESIGN OVERVIEW

Description of Proposed Changes
Provide a concise description of the proposed changes.

Option 1: Merge properties from PersonCredential into CredentialAward or CredentialDefinition as appropriate. Consider appropriate places for information in tables EarlyChildhoodCredential and StaffCredential, e.g. TeachingCredentialBasis as a criteria metadata that may be associated with a teaching credential.

Option 2: Add a relationship CredentialDefinitionId (nullable) to PersonCredential

As-Is Diagram
Add as an attachment in this issue.
TBD based on option chosen by community.

Proposed To-Be Diagram
Add as an attachment in this issue.
TBD based on option chosen by community.

DATA WAREHOUSE DESIGN OVERVIEW (Includes Dim, Fact, and Report tables)

Description of Proposed Changes
Provide a concise description of the proposed changes.

As-Is Diagram
Add as an attachment in this issue.

Proposed To-Be Diagram
Add as an attachment in this issue.

---

DATA MIGRATION IMPACT ANALYSIS

Description of Proposed Changes
Provide a concise description of the proposed changes.

New Business Rule
Provide a concise and comprehensive description of the new business rule.

Existing Business Rule
Provide a concise and comprehensive description of the existing business rule.

Changed Business Rule
Provide a concise and comprehensive description of the changes to be made to the business rule.