Details
-
Improvement
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
Description
Hi all,
Context: I am currently working on creating some views on top of the ODS v3.4.0 to mimic OneRoster V1.1 standard. This id for a bigger project where we will try to connect Ed-Fi with Clever.
(I could be remembering wrong but I thought I heard or read somewhere that when in doubt regarding Descriptor CodeValues and Descriptions Ed-Fi recommends looking at CEDS first before reinventing the wheel. (Again I could be remembering wrong)
The issue: So I am in the middle of the onerosterv11.getAllClasses view and I hit a little blocker: In the Ed-Fi Descriptor table the values for the GradeLevelDescriptor namespace (CodeValue and Description are the same) OneRoster favors CEDS and mentions that the Grades Served should be in CEDS code values. So I am thinking to myself. "Myself" why didnt we use the edfi.Descriptor.CodeValue like the CEDS.Descriptor.Code?
Example:
EdFi CodeValue | CEDS Code | Both Descriptions Are A-OK |
---|---|---|
... | ... | ... |
Kindergarten | KG | Kindergarten |
First grade | 01 | First grade |
Second grade | 02 | Second grade |
Third grade | 03 | Third grade |
... | ... | ... |
*Just seems a little weird that we (Ed-Fi) has a CodeValue that is equal the Description and not a real codeValue like the ones in CEDS. Thoughts?
My ask: I think (unless I am missing something) that we should align our descriptors as much as possible with CEDS and ensure that the CodeValues map to the Value in CEDS.
Supporting Links:
1) One Roster Class Definition: http://www.imsglobal.org/oneroster-v11-final-specification#_Toc480452010
2) CEDS Grade Levels: https://ceds.ed.gov/CEDSElementDetails.aspx?TermId=7100
Supporting pictures:
CEDS:
Ed-Fi Descriptors:
Tagging people interested: Silvia.Brunet-Jones, Eric.Jansson, Lyria.Zeh
Attachments
Issue Links
- mentioned in
-
Page Loading...