Issue
The IMS OneRoster 1.1 spec defines 10 columns for enrollments.csv:
sourcedId, status, dateLastModified, classSourcedId, schoolSourcedId, userSourcedId, role, primary, beginDate, endDate
The current implementation generates 11 columns with an additional courseSourcedId column. This was added in v2.1.1-beta (changelog: "Add missing courseSourcedId column to enrollments.csv").
Spec Reference
https://www.imsglobal.org/oneroster-v11-final-csv-tables (Section 3.9 - enrollments.csv)
Current Model
EnrollmentFile.cs has 11 properties including courseSourcedId.
Recommendation
Verify whether courseSourcedId should be in enrollments.csv per the IMS spec, or if this is an intentional extension. If it's an extension, consider making it configurable or documented as non-standard.
Related
- NemesisApp also validates against 11 headers
- DailyOneRosterFile now validates against the spec's 10 headers
Issue
The IMS OneRoster 1.1 spec defines 10 columns for
enrollments.csv:The current implementation generates 11 columns with an additional
courseSourcedIdcolumn. This was added in v2.1.1-beta (changelog: "Add missing courseSourcedId column to enrollments.csv").Spec Reference
https://www.imsglobal.org/oneroster-v11-final-csv-tables (Section 3.9 - enrollments.csv)
Current Model
EnrollmentFile.cshas 11 properties includingcourseSourcedId.Recommendation
Verify whether
courseSourcedIdshould be in enrollments.csv per the IMS spec, or if this is an intentional extension. If it's an extension, consider making it configurable or documented as non-standard.Related