Skip to content
Laravel

Programs Management

Introduction

Here is an ERD for programs management and the tables related to it,

Programs

The ERD for program management in OTAS details the relationships between various educational components and the users within the system:

  • Institutions: This entity is central to program management and is associated with several other entities.

  • Programs: Programs are the educational offerings provided by the institutions. Each program is linked to an institution, indicating a one-to-many relationship.

  • Fields: Represents broad academic disciplines or areas of study. Each field may contain multiple specialities, indicating a one-to-many relationship.

  • Specialities: Specialties are more specific areas of study within each field. They are associated with programs, showing that each program focuses on a particular specialty.

  • Levels: Denotes the academic levels, such as undergraduate or postgraduate. Each level is associated with various programs, suggesting a one-to-many relationship.

  • Languages: This entity represents the languages in which the programs are offered. There is a one-to-many relationship between languages and programs.

  • Titles: Indicates the official titles or qualifications conferred upon completion of the programs. Each program has a title, creating a one-to-many relationship.

  • OC_Users: These are the users involved in creating or managing the programs. There is a "create" relationship from oc_users to programs, indicating that users in the system are responsible for creating and updating program details.

In summary, the diagram illustrates that institutions have programs, which in turn are linked to specific levels, fields, specialities, and languages. Programs also have titles and are created by users in the system.

Tables

The program management within OTAS involves a series of interconnected tables, each serving a unique role in cataloging the various aspects of educational programs:

  • Fields: Stored in spotlayerteam_institutionsprograms_field, this table includes names of educational fields in seven languages, such as Engineering & Technology, Aviation, Architecture & Design, etc.

  • Specialities: The spotlayerteam_institutionsprograms_speciality table contains the titles of specialities in seven languages and holds a reference to the related field through a field ID.

  • Levels: The spotlayerteam_institutionsprograms_level table lists academic levels, like Bachelor and Master, and provides their names in seven languages.

  • Languages: Found in spotlayerteam_institutionsprograms_language, this table records the languages in which programs are offered, with the language names presented in seven different languages, including English and Turkish.

  • Titles: The spotlayerteam_institutionsprograms_title table includes names of academic titles in seven languages, such as Bachelor of Accounting, Bachelor of Advertising, etc.

  • OC_Users: This is the previously defined users table from the User Management section, detailing the users responsible for creating and managing the programs.

  • Programs: Identified as spotlayerteam_institutionsprograms_program, this table houses the program details within the system, linking to titles, levels, creators (users), languages, and specialities.

Each table features multilingual support to cater to a diverse user base and ensures comprehensive coverage of program-related data.

Program Quota

program-quota

The ERD you've presented illustrates the structure for managing program quotas within OTAS, connecting programs to academic years and semesters. Here’s how the entities interact:

  • Programs: This entity represents the various academic programs offered by institutions.

  • Academic Years: This entity represents the various academic cycles during which these programs are offered.

  • Semesters: This entity represents the subdivisions of the academic years, such as Fall, Spring, or Summer.

  • Program_Quota: This is the junction table that ties programs to specific academic years and semesters. The presence of a program's ID in this table, alongside an academic year and semester, signifies that the quota for that particular program has been filled for the specified time period.

The relationships operate as follows:

  • Programs can have quotas for multiple academic years and semesters.
  • Academic years have various programs each with their own quotas.
  • Semesters are linked to different programs, also with distinct quotas.

program-quota-form

When an entry is made in the program_quota table, it indicates that no more students can enroll in that specific program for the given academic year and semester because it has reached its full capacity. This system allows the administration to control and monitor the number of students in each program to ensure they do not exceed the available resources or capacity.