How yurkovskiy/dtapi works
d-tester is a Kohana-based JSON API for academic records, user administration, and student quizzes. The main workflow is a student starting an eligible test, receiving question/answer data, submitting answers for checking, and accessing results; administrators maintain users and academic/test data through CRUD APIs. The graph also shows shared entity access and question-type checking. Several controller/model implementations are unsampled, so documented endpoints establish API capabilities, while uncertain internal links are omitted or dashed.
Main entry points: Log.php Test eligibility · Model/Student.php Student records · database.php MySQL database · Controller/Student.php Student API
Components 20
API controllers
- Admin CRUD
application/classes/Controller/BaseAdmin.php - Student API
application/classes/Controller/Student.php - Entity lookup
application/classes/Controller/EntityManager.php
Quiz runtime
- Test start API
application/classes/Controller/Log.php - Test eligibility
application/classes/Model/Log.php - Test player API
application/classes/Controller/TestPlayer.php - Answer checking
application/classes/Controller/SAnswer.php - Question types
application/classes/NumericalQuestion.php
Academic data
- Question API
application/classes/Controller/Question.php - Answer API
application/classes/Controller/Answer.php - Results API
application/classes/Controller/Result.php - Academic APIs
application/classes/Controller/Group.php - Timetable API
application/classes/Controller/TimeTable.php
Identity and access
- Login API
application/classes/Controller/Login.php - Admin user API
application/classes/Controller/AdminUser.php - User accounts
application/classes/Model/User.php
Persistence
- Entity operations
application/classes/Model/Common.php - Student records
application/classes/Model/Student.php - MySQL database
application/config/database.php
Other components
- API client
Connections 23
- API client → Admin CRUD: manages records
- API client → Student API: manages students
- API client → Login API: authenticates
- API client → Admin user API: manages admins
- API client → Entity lookup: fetches entities
- API client → Test start API: starts test
- API client → Test player API: plays test
- API client → Question API: fetches questions
- API client → Answer API: fetches answers
- API client → Answer checking: checks answers
- API client → Results API: reads results
- API client → Academic APIs: reads academic data
- API client → Timetable API: reads schedules
- Admin user API → User accounts: uses accounts
application/classes/Controller/AdminUser.php - Student API → Student records: registers students
application/classes/Controller/Student.php - Student records → User accounts: creates account
application/classes/Model/Student.php - Entity lookup → Entity operations: loads entity model
application/classes/Controller/EntityManager.php - Entity operations → MySQL database: queries records
application/classes/Model/Common.php - Test start API → Test eligibility: starts eligibility check
- Test eligibility → MySQL database: writes test log
application/classes/Model/Log.php - Test eligibility → Student records: reads student
application/classes/Model/Log.php - Answer checking → Question types: checks type
- Question types → MySQL database: reads answers
application/classes/NumericalQuestion.php