Make certain fields nullable

[CJ-Gilbert-CEPI]

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) CJ Gilbert

Authoring Organization(s) CEPI, Michigan

Email address GilbertC6@Michigan.gov

Use Case Title
Make certain fields nullable

Use Case Overview
Michigan asks that the following fields (properties) be nullable in the IDS and Ontology:

• ProfessionalDevelopmentRequirementId in the StaffProfessionalDevelopmentActivity table
• CredentialIssuerId in the CredentialAward table
• Name in the FinancialAccount table
• OrganizationPersonRoleId in the K12StaffAssignment

Use Case Background
We ask that the following fields (properties) be nullable in the IDS and Ontology because we don’t collect the data needed to populate them 100% of the time:

• ProfessionalDevelopmentRequirementId in the StaffProfessionalDevelopmentActivity table
  Michigan does not currently collect data about Professional Development Requirements in the same collection as where we store the fact records for Staff Professional Development.
• CredentialIssuerId in the CredentialAward table
  In some cases, Michigan only asks LEAs to report details about a credential and not necessarily who issued the credential.
• Name in the FinancialAccount table
  Michigan needs to be able to link a StaffEmployment record with a FinancialAccountLocal record. The only way to do that is to pass through the FinancialAccount table, but we do not intent to populate this table as it’s own entity.
• OrganizationPersonRoleId in the K12StaffAssignment
  Michigan can have an assignment associated with a vacant job position. We need OrganizationPersonRole to be nullable in these cases since we don’t have a ‘person’ in the role.

Components Affected
• CEDS Integrated Data Store
• CEDS Ontology