Skip to content

Latest commit

 

History

History
66 lines (58 loc) · 1.48 KB

filename_conventions.md

File metadata and controls

66 lines (58 loc) · 1.48 KB

Filename conventions

When providing UDD data, supply the data for different entities in separate files, 1 file per entity.

Data must be UTF-8 encoded.

JSON is the preferred file type, but XML or TSV files can also be submitted. Other formats cannot be processed.

Use the following filenames, all lower case. The only difference between the filename groups here is the suffix, json, xml or tsv, as appropriate.

  • assessmentinstance.json
  • course.json
  • courseinstance.json
  • institution.json
  • module.json
  • moduleinstance.json
  • modulevlemap.json
  • period.json
  • staff.json
  • staffcourseinstance.json
  • staffmoduleinstance.json
  • student.json
  • studentassessmentinstance.json
  • studentcourseinstance.json
  • studentcoursemembership.json
  • studentidmap.json
  • studentmoduleinstance.json

or

  • assessmentinstance.xml
  • course.xml
  • courseinstance.xml
  • institution.xml
  • module.xml
  • moduleinstance.xml
  • modulevlemap.xml
  • period.xml
  • staff.xml
  • staffcourseinstance.xml
  • staffmoduleinstance.xml
  • student.xml
  • studentassessmentinstance.xml
  • studentcourseinstance.xml
  • studentcoursemembership.xml
  • studentidmap.xml
  • studentmoduleinstance.xml

or

  • assessmentinstance.tsv
  • course.tsv
  • courseinstance.tsv
  • institution.tsv
  • module.tsv
  • moduleinstance.tsv
  • modulevlemap.tsv
  • period.tsv
  • staff.tsv
  • staffcourseinstance.tsv
  • staffmoduleinstance.tsv
  • student.tsv
  • studentassessmentinstance.tsv
  • studentcourseinstance.tsv
  • studentcoursemembership.tsv
  • studentidmap.tsv
  • studentmoduleinstance.tsv