Curriculum: standard data model

The overview of the root objects is shown below. The name shown behind brackets is the internal used name and can also be used in configuring calculated fields and expressions. The name before the brackets is the standard naming at first install, but might be different for each installation due to changing these names use the Label edit function to the internal used naming convention.

The overview is not shown in alphabetical order, but in a hierarchy based order (top -> down), and ended with the more generic objects that contribute to the structure.

‍

Faculty (faculty)

Object to model the Faculty information of the institute, e.g. Faculty of Law, Faculty of Science

• Faculty (faculty)
  The faculty root that will hold the standard (identifying) curriculum fields like code, external Id, multi-lingual names, abbreviation, start and end date, etc.
• Additional (additional)
  The additional object is the standard object used to extend the data model with self-defined custom-fields.
• Description (description)
  The description object is an internal (technical) object that is used to manage and maintain the multi-lingual descriptive texts. The supported descriptive texts are configured using the Element.
• Method parameter (method-parameter)
  The method-parameter object is an internal (technical) object used for Workload Management. It will contain the different workload calculation rules for the individual teaching and assessment methods.
• Relation/person (relation)
  The relation object is used to hold the relation with the assigned persons with the configured relation-types for the root object.  Additional fields to specify or add to the relation can be configured, or standard fields can be made invisible to limit specific functionality (e.g. usage of 'virtual / vacancy' persons).

Organisation (organisation)

Object to model the HR organisations of the institute, e.g. Department of business Law

• Organisation (organisation)
  The organisation root that will hold the standard (identifying) curriculum fields like code, external Id, multi-lingual names, abbreviation, start and end date, etc.
• Additional (additional)
  The additional object is the standard object used to extend the data model with self-defined custom-fields.
• Description (description)
  The description object is an internal (technical) object that is used to manage and maintain the multi-lingual descriptive texts. The supported descriptive texts are configured using the Element.
• Relation/person (relation)
  The relation object is used to hold the relation with the assigned persons with the configured relation-types for the root object.  Additional fields to specify or add to the relation can be configured, or standard fields can be made invisible to limit specific functionality (e.g. usage of 'virtual / vacancy' persons).

Specification (specification)

Object to model the accredited programs, e.g. Bachelor of Law, Master of Science

• Specification (specification)
  The specification root that will hold the standard (identifying) curriculum fields like code, external Id, multi-lingual names, abbreviation, start and end date, etc.
• Additional (additional)
  The additional object is the standard object used to extend the data model with self-defined custom-fields.
• Capacity (capacity)
  The capacity object used to define the number of students and standard providing minimum, optimum and maximum capacity.
• Credits (credits)The credits object used to define the number of credits and standard providing minimum, optimum and maximum capacity. Don't rename the field names, only labels, since these three fields are used in the curriculum structure to identify if the amount of required minimum, optimum (standard) and/or maximum is met in the underlying module-groups and modules.
• Description (description)
  The description object is an internal (technical) object that is used to manage and maintain the multi-lingual descriptive texts. The supported descriptive texts are configured using the Element.
• Document (document)
  The document object will hold the uploaded documents and their related information like type, date, etc.
• Subject/Learning outcome (subject)
  The subject object will hold the learning outcomes the student can obtain with the specification. At study level, the actual learning outcomes for the 'offered program' are derived from this set and configured.
• Relation/person (relation)
  The relation object is used to hold the relation with the assigned persons with the configured relation-types for the root object.  Additional fields to specify or add to the relation can be configured, or standard fields can be made invisible to limit specific functionality (e.g. usage of 'virtual / vacancy' persons).

Qualification (qualification)

Object to model the obtainable qualification, e.g. Bachelor of Law, Certificate of Arts and Science

• Qualification (qualification)
  The qualification root that will hold the standard (identifying) curriculum fields like code, external Id, multi-lingual names, abbreviation, start and end date, etc.
• Additional (additional)
  The additional object is the standard object used to extend the data model with self-defined custom-fields.
• Description (description)
  The description object is an internal (technical) object that is used to manage and maintain the multi-lingual descriptive texts. The supported descriptive texts are configured using the Element.
• Link (link)
  The link object is used to manage the link(s), e.g. required, excludes between the qualification, specification and study objects.
• Relation/person (relation)
  The relation object is used to hold the relation with the assigned persons with the configured relation-types for the root object.  Additional fields to specify or add to the relation can be configured, or standard fields can be made invisible to limit specific functionality (e.g. usage of 'virtual / vacancy' persons).

Study (study)

Object to module the offered program, e.g. Bachelor of Law (full-time), Bachelor of Business Law (part-time), Master of Arts (Rotterdam)

• Study (study)
  The study root that will hold the standard (identifying) curriculum fields like code, external Id, multi-lingual names, abbreviation, start and end date, etc.
• Additional (additional)
  The additional object is the standard object used to extend the data model with self-defined custom-fields.
• Advice (advice)
  The advice object is an internal object used to manage the different advices given to proposed changes in the curriculum structure
• Award qualification (award-qualification)
  The award-qualification object is used to relate the study and its obtainable qualifications.
• Capacity (capacity)
  The capacity object used to define the number of students and standard providing minimum, optimum and maximum capacity.
• Credits (credits)The credits object used to define the number of credits and standard providing minimum, optimum and maximum capacity. Don't rename the field names, only labels, since these three fields are used in the curriculum structure to identify if the amount of required minimum, optimum (standard) and/or maximum is met in the underlying module-groups and modules.
• Description (description)
  The description object is an internal (technical) object that is used to manage and maintain the multi-lingual descriptive texts. The supported descriptive texts are configured using the Element
• Document (document)
  The document object will hold the uploaded documents and their related information like type, date, etc.
• Effort (effort)
  The effort object will hold the calculated Workload management effort that is required to deliver the object
• Subject/Learning outcome (subject)
  The subject object will hold the learning outcomes the student can obtain with the specification. At study level, the actual learning outcomes for the 'offered program' are derived from this set and configured
• Link (link)
  The link object is used to manage the link(s), e.g. required, excludes between the study and other educational objects in the system.
• Offering period (offering-period)
  The offering-period object defines the start moments the program is offered, e.g. September start, February start.
• Relation/person (relation)
  The relation object is used to hold the relation with the assigned persons with the configured relation-types for the root object.  Additional fields to specify or add to the relation can be configured, or standard fields can be made invisible to limit specific functionality (e.g. usage of 'virtual / vacancy' persons).
• Route (route)
  The route object is used to hold the different routes and related qualifications a student can follow within the program. E.g. all modules in year 1 will provide a Certificate or February start should start with these X modules in semester 2
• Structure (study-module-group)
  The study-module-group object is the foundation for the curriculum tree direct from the study downwards. It will hold the module-groups directly related to the study, including its relation related fields such as phase or required information.

Module group (module-group)

Object to model the clusters of modules that are part of offered programs. E.g., Year 1, Propedeuse, Specialisation Civil Law

• Module group (module-group)
  The module-group root that will hold the standard (identifying) curriculum fields like code, external Id, multi-lingual names, abbreviation, start and end date, etc.
• Additional (additional)
  The additional object is the standard object used to extend the data model with self-defined custom-fields.
• Capacity (capacity)
  The capacity object used to define the number of students and standard providing minimum, optimum and maximum capacity.
• Credits (credits)
  The credits object used to define the number of credits and standard providing minimum, optimum and maximum capacity. Don't rename the field names, only labels, since these three fields are used in the curriculum structure to identify if the amount of required minimum, optimum (standard) and/or maximum is met in the underlying module-groups and modules.
• Description (description)
  The description object is an internal (technical) object that is used to manage and maintain the multi-lingual descriptive texts. The supported descriptive texts are configured using the Element
• Document (document)
  The document object will hold the uploaded documents and their related information like type, date, etc.
• Effort (effort)
  The effort object will hold the calculated Workload management effort that is required to deliver the object
• Subject/Learning outcome (subject)
  The subject object will hold the learning outcomes the student can obtain with the specification. At study level, the actual learning outcomes for the 'offered program' are derived from this set and configured.
• Link
  The link object is used to manage the link(s), e.g. required, excludes between the module-group and other educational objects in the system.
• Offering period (offering-period)
  The offering-period object defines the start moments the program is offered, e.g. September start, February start.
• Relation/person (relation)
  The relation object is used to hold the relation with the assigned persons with the configured relation-types for the root object.  Additional fields to specify or add to the relation can be configured, or standard fields can be made invisible to limit specific functionality (e.g. usage of 'virtual / vacancy' persons).
• Structure (module-group-module-group)
  The module-group-module-group object is the foundation for the curriculum tree direct from the module-group downwards. It will hold the module-groups directly related to the module-group, including its relation related fields such as sequence or required information.
• Structure (module-group-module)
  The module-group-module object is the foundation for the curriculum tree direct from the module-group downwards. It will hold the modules directly related to the study, including its relation related fields such as sequence or required information.

Module (module)

Object to model the modules that are part of offered programs. E.g. Introduction to Law, Basic analytics.

• Module  (module)
  The module root that will hold the standard (identifying) curriculum fields like code, external Id, multi-lingual names, abbreviation, start and end date, etc.
• Additional (additional)
  The additional object is the standard object used to extend the data model with self-defined custom-fields.
• Appraisal (appraisal
  The appraisal object is an internal object that is used to model the assessment tree and enable use of assessment in different modules. E.g. a test is used in module A and module B, and in module A its weighting is 50% and in module B its weighting is 20%.
• Capacity (capacity)
  The capacity object is used to define the number of students and standard providing minimum, optimum and maximum capacity.
• Delivery (delivery)
  The delivery object is used to manage the delivery plan for assets, e.g. deliver 23 times book A in week 4 from stock.
• Credits (credits)
  The credits object used to define the number of credits and standard providing minimum, optimum and maximum capacity. Don't rename the field names, only labels, since these three fields are used in the curriculum structure to identify if the amount of required minimum, optimum (standard) and/or maximum is met in the underlying module-groups and modules.
• Description (description)
  The description object is an internal (technical) object that is used to manage and maintain the multi-lingual descriptive texts. The supported descriptive texts are configured using the Element
• Division (division)
  The division object is used in Workload management to maintain the hour/cost division of a module against the organisation structure.
• Document (document)
  The document object will hold the uploaded documents and their related information like type, date, etc.
• Education week (module-week)
  The module-week is an internal object to hold the activity required sequence information, e.g. in week 4 the order of activities should be lecture A, workgroup C, workgroup B
• Effort (effort)
  The effort object will hold the calculated Workload management effort that is required to deliver the object
• Subject/Learning outcome (subject)
  The subject object will hold the learning outcomes the student will learn with the module. At module level, the actual learning outcomes are derived from the 'offered program' and configured.
• Link (link)
  The link object is used to manage the link(s), e.g. required, excludes between the module and other educational objects in the system.
• Material (asset)
  The material object is used to manage the required material/resources to deliver the module
• Method schema (method-schema)
  The method-scheme object is an internal object that is used to model the method tree and enable use of assessment in different modules. E.g. a test is used in module A and module B, and in module A its required and in module B its optional.
• Offering period (offering-period)
  The offering-period object defines the start moments the module is offered, e.g. Period 1, Quarter 2, Semester 2.
• Relation/person (relation)
  The relation object is used to hold the relation with the assigned persons with the configured relation-types for the root object.  Additional fields to specify or add to the relation can be configured, or standard fields can be made invisible to limit specific functionality (e.g. usage of 'virtual / vacancy' persons).
• Resource (module-resource)
  The module-resource object is an internal object used to relate module resource information to specific offering periods.

Assessment (assessment)

Object to module the assessment and its delivery, e.g. Oral, Digital, Portfolio

• A
  The assessment root that will hold the standard (identifying) curriculum assessment fields like code, external Id, multi-lingual names, abbreviation, duration, minimal grade, type, etc.
• Activity (activity)
  The activity object is used to hold the lecturers (persons) that are related to the individual assessment activities
• Activity planning (activity-planning)
  The activity-planning object is used to hold the weeks the assessments are planned during the offering period
• Activity serie (activity-serie)
  The activity-serie object is used to hold the activity series (sets of activities and activity-planning) defined for a module, e.g. cumulative test serie in week 1, 4, and 8 and a final test in week 10
• Appraisal (appraisal)
  The appraisal object is an internal object that is used to model the assessment tree and enable use of assessment in different modules. E.g. a test is used in module A and module B, and in module A its weighting is 50% and in module B its weighting is 20%.
• Subject/Learning outcome (subject)
  The subject object will hold the learning outcomes the student will be tested in the assessment.

Teaching method (method)

Object to module the assessment and its delivery, e.g. Oral, Digital, Portfolio

• Teaching method (method)
  The teaching method root that will hold the standard (identifying) curriculum teaching method fields like code, external Id, multi-lingual names, abbreviation, duration, nr. of groups, type, etc.
• Activity (activity)
  The activity object is used to hold the lecturers (persons) that are related to the individual assessment activities
• Activity planning (activity-planning)
  The activity-planning object is used to hold the weeks the assessments are planned during the offering period
• Activity serie (activity-serie)
  The activity-serie object is used to hold the activity series (sets of activities and activity-planning) defined for a module, e.g. cumulative test serie in week 1, 4, and 8 and a final test in week 10
• Subject/Learning outcome (subject)
  The subject object will hold the learning outcomes the student will be tested in the assessment.
• Method schema (method-scheme)
  The method-scheme object is an internal object that is used to model the method tree and enable use of assessment in different modules. E.g. a test is used in module A and module B, and in module A its required and in module B its optional.

The above mentioned objects are used to structure and manage the core curriculum. The next objects can be considered as more generic objects that contribute to many objects are are used to steer processes.

The above mentioned objects are used to structure and manage the core curriculum. The next objects can be considered as more generic objects that contribute to many objects are are used to steer processes.

‍

Academic year (academic_year)

Object to module the academic year, used to version the year and its related processes and data

• Academic year (academic-year)
  The academic-year object is a fully internal object that is used to hold the academic years and its calendar information.
• Relation/person (relation)
  The relation object is used to hold the relation with the assigned persons with the configured relation-types for the root object.  Additional fields to specify or add to the relation can be configured, or standard fields can be made invisible to limit specific functionality (e.g. usage of 'virtual / vacancy' persons).

Learning objective (objective)

Object to model the learning objectives the student will get taught/learn in a module. E.g. create a pivot table in Excel, write a paper in academic English.

• Learning objective (objective)
  The objective root that will hold the standard (identifying) curriculum fields like code, external Id, multi-lingual names, description.
• Appraisal (appraisal)
  The appraisal object is an internal object and is used to relate the learning objective to the assessment it will be assessed with. This relationship supports the assessment plan including the assessments and the related objectives tested in the different assessments.
• Subject/Learning outcome (subject)
  The subject object is an internal object and is used to relate the learning objective to the subject it contributes to. This relationship is used in the different matrix reports in Curriculum Mapping.

Resource (resource)

Object to model the resources in the system. Resources are managed using the resource management functionality and are used in module context.

• Resource (resource)
  The resource object is an internal object used to define and manage resources to be used in the context of other objects (e.g. module).
• Resource version (resource-version)
  The resource version object is an internal object that support management of resource versions

Rule (rule)

Object to model rules in the system. Rules are used to define relations between objects, including the applied rule, e.g. a qualification can be obtained via (Module A and B) or(Module A and Module-group C)

• Rule (rule)
  The rule object is an internal object used to define and manage rules to be used in the context of other objects (e.g. module), e.g. requires, excludes.
• Link (link)
  The link object is used to manage the rule's relations with the educational objects, e.g. Module E requires module A

Person (person)

Object to model the users / persons in the system. The person object is at the heart of the system and is used for authorisation, process management, stakeholder definition, responsibilities, etc.
In a workload management context the relation is using the assignment that can be considered a wrapper around person.

• Person (person)
  The person object represents the actual person (user / login) that will have access to the system and can be used to define relationships with the other objects.
• Availability preference (availability-preference)
  The availability-preference object is an internal object that holds the weekly availability pattern per offering period of the user
• Availability request (availability-request)
  The availability-request object is an internal object that is used in Workload management context to hold and manage the ad-hoc (un)availability requests of the user, including approval status.

Assignment (assignment)

Object to model the person assignment, e.g. 50% FTE for the Department of Erasmus studies.
In a Workload management context the relationships from objects (study, module-group, module, ...) are against the assignment where workload calculations are required. The authentication and authorisation layer will use the person bound to the assignment.

• Assignment (assignment)
  The assignment object will hold the assignment, in the above example it is the assignment with the Department of Erasmus studies.
• FTE (fte)
  The fte object will hold the FTE percentage per year for the different assignments, in the above example this is 50%.
• Task (task)
  The task object will hold the assigned non-educational task to the person, including the allocation value. E.g., paper reader for 5 students, 35% module coordinator for Module A
  ‍

Team (team)

Object to model and manage teams of persons, e.g. Exam Committee has team members John and Jane Doe.

• Team (team)
  The team object is used to define and manage teams and its team members (persons)

Next to Person and Assignment, a Team can be used in relationship configuration. This means a study director can f.i. be:

• a Person (John Doe)
• an Assignment (John Doe's contract of 50% with Department of Science)
• a Team (John and Jane Doe)