Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Definitions for Courses and Classes #4

Open
kyukyukyu opened this issue Sep 5, 2013 · 2 comments
Open

Definitions for Courses and Classes #4

kyukyukyu opened this issue Sep 5, 2013 · 2 comments
Labels

Comments

@kyukyukyu
Copy link
Member

  • Course (과목): An entity which is identified with course_no. Semantically, a course is a unit of teaching that typically lasts one academic term, is led by one or more instructors (teachers or professors), and has a fixed roster of students. (Source: Wikipedia)
  • Class (강좌): An entity which is identified with class_no. There are one or more classes for one course. Semantically, a class is a group of pupils or students who are taught together. (Source: Naver Dictionary)
  • Placement Required Course (필수 배치 과목): A course which the placement of at least one class of is required for the combination.
  • Placement Optional Course (선택 배치 과목): A course which the placement of at least one class of is optional for the combination.
  • Fixed Class (확정 강좌): A class that should be placed for every combination, which means any other class of the same subject should not be placed.
@kyukyukyu
Copy link
Member Author

I think we should get rid of 'Fixed Class', because users can get the same result by just adding only one class of the course.

Instead, 'Preferred Class (우선 배치 강좌)' can be suggested. 'Preferred Class' is a class which timetables with should be listed first in the result.

The difference from 'Fixed Class' is that the classes that are of same course with a 'Preferred Class' can be placed. However, the timetables with other classes of the course is listed later than the timetables with a 'Preferred Class'.

@kyukyukyu
Copy link
Member Author

Don't define 'Preferred Class'. Instead, just follow the order of classes and courses in the class cart when creating new timetables, so that users can set the overall priorities of classes and courses by sorting them in the class cart UI.

kyukyukyu added a commit that referenced this issue Sep 20, 2013
* I deleted `fixed` property from class entities of class carts.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant