How ciwga/atilimu works
Project type and purpose
• This is a Python-based CLI tool (“ATILIM UNIVERSITY STUDENT SYSTEM”) that aggregates and downloads data from multiple university web services (ATACS, Moodle, UNACS, curriculum, profile, KVKK forms) and persists it on the local filesystem. It is not a full-stack web app but a modular command-line client.
File structure
• Top-level:
• main.py: the CLI entry point and orchestrator
• requirements.txt & LICENSE
• tools/ package (modular service clients and support code):
• atacs.py, moodle.py, unacs.py, curriculum.py, profile.py, kiyos_auth.py
• config.py: app configuration (API endpoints, credentials, storage paths)
• helpers.py & exceptions.py: shared routines (HTTP session management, error classes)
README for additional insights
• Describes eight “features” (personal info, ATACS messages, Moodle announcements & docs, electives, pay table, KVKK, graduation photos)
• Persists data under atilim_data/<service> directories
• Uses HTTP sessions, cookie management, and supports many file types
Main components
a. CLI Layer:
• main.py
• User Input / Menu System
b. Core Modules:
• tools/config.py
• tools/helpers.py & tools/exceptions.py
c. Service Connectors:
• tools/kiyos_auth.py (shared authentication)
• tools/atacs.py
• tools/moodle.py
• tools/unacs.py
• tools/curriculum.py
• tools/profile.py
d. External Systems:
• ATACS Web Service
• Moodle LMS
• UNACS Course Catalog
• KVKK Form Service
e. Local Data Store:
• atilim_data/ (with subfolders: university_profile, atacs, moodle, unacs, …)
Relationships and interactions
• User → CLI (main.py)
• main.py reads config → initializes HTTP session via helpers & kiyos_auth
• service modules call external APIs (ATACS, Moodle, UNACS, etc.)
• responses are parsed, exceptions handled, then saved into atilim_data/
• helpers handle file I/O and request retries, exceptions manage error flows
Architectural patterns and design principles
• Modular service-connector pattern: each “tools/*.py” handles one API
• Single responsibility: config, auth, HTTP helpers separated
• File-system persistence layer: all outputs normalized under atilim_data
• CLI application pattern: menu → command → service call → save
Relevant technologies
• Python 3.x
• requests (HTTP client, cookie management)
• argparse or simple input() loops in main.py
• Local filesystem I/O (os, pathlib)