Author(s) CJ Gilbert
Authoring Organization(s) CEPI, Michigan
Email address GilbertC6@Michigan.gov
Proposal
Add the Job Detail class (C200178) to the domain of Has Evaluation Required Indicator (P002194)
Background
The original proposal for the Evaluation Required Indicator was written based on the Domain Entity Schema and so it requested that this element be part of a 'Job'
However, in the ontology, the Job class actually has a subclass called Job Detail. This subclass is where elements that can change over time (like Local Job Function Code) are placed so that it is possible to track the dates when those aspects of the Job changed.
Whether or not an evaluation is required would be the kind of element that should be a part of Job Detail.
We propose adding Job Detail to the domain of Has Evaluation Required Indicator so that organizations can choose to store that indicator once (at the Job level) or over time (in the Job Detail level)
Author(s) CJ Gilbert
Authoring Organization(s) CEPI, Michigan
Email address GilbertC6@Michigan.gov
Proposal
Add the Job Detail class (C200178) to the domain of Has Evaluation Required Indicator (P002194)
Background
The original proposal for the Evaluation Required Indicator was written based on the Domain Entity Schema and so it requested that this element be part of a 'Job'
However, in the ontology, the Job class actually has a subclass called Job Detail. This subclass is where elements that can change over time (like Local Job Function Code) are placed so that it is possible to track the dates when those aspects of the Job changed.
Whether or not an evaluation is required would be the kind of element that should be a part of Job Detail.
We propose adding Job Detail to the domain of Has Evaluation Required Indicator so that organizations can choose to store that indicator once (at the Job level) or over time (in the Job Detail level)