User Guide

User Guide

This guide will teach you how to use AkademiTrack to automatically register your STU attendance.

Getting Started

Before using AkademiTrack, make sure you've completed the First Time Setup to configure your Feide credentials.

Main Window Overview

When you open AkademiTrack, you'll see:

• AkademiTrack - Application title with your school name
• Start automatisering - Button to begin monitoring
• Stopp automatisering - Button to stop monitoring (appears when running)
• Innstillinger - Settings button
• Gjeldende status - Current status display showing what the application is doing
• Activity Log - Scrollable log of all actions (if enabled in settings)

Starting Automation

Manual Start

1. Open AkademiTrack
2. Click "Start automatisering" (Start Automation)
3. The application will:
   • Log in to iSkole using your saved credentials
   • Fetch today's schedule
   • Find all STU sessions for today
   • Check for conflicts with other classes
   • Begin monitoring registration windows

Auto-Start (Optional)

Enable auto-start in Settings to have automation begin automatically when you launch AkademiTrack:

1. Click "Innstillinger"
2. Go to "Automatisering" section
3. Enable "Auto-start automatisering"
4. Save settings

Now automation will start immediately when you open the app.

What Happens During Automation

Phase 1: Authentication

AkademiTrack logs in to iSkole using your Feide credentials. You'll see status updates like:

• "Logger inn..." (Logging in...)
• "Innlogging vellykket" (Login successful)

Phase 2: Schedule Fetching

The application retrieves your schedule for today:

• "Henter timeplan..." (Fetching schedule...)
• "Timeplan hentet" (Schedule fetched)

Phase 3: STU Session Detection

AkademiTrack identifies STU sessions:

• "Fant X STU-økter for i dag" (Found X STU sessions for today)
• Lists each session with time and details

Phase 4: Conflict Checking

The application checks if STU sessions overlap with other classes:

• "Sjekker for konflikter..." (Checking for conflicts...)
• "STU-økt overlapper med [Fag] - hopper over" (STU session overlaps with [Subject] - skipping)
• Sessions with conflicts are automatically skipped to avoid issues

Phase 5: Registration Window Monitoring

For each valid STU session, AkademiTrack:

• Calculates when the registration window opens
• Waits until the window is available
• "Venter på registreringsvindu for [Økt]..." (Waiting for registration window for [Session]...)

Phase 6: Automatic Registration

When a registration window opens:

• "Registreringsvindu åpnet for [Økt]" (Registration window opened for [Session])
• "Registrerer oppmøte..." (Registering attendance...)
• "Oppmøte registrert!" (Attendance registered!)
• System notification appears confirming registration

Phase 7: Completion

Once all sessions are handled:

• "Alle økter for i dag er behandlet" (All sessions for today are handled)
• "Automatisering fullført" (Automation completed)
• Automation stops automatically

Stopping Automation

To stop automation before it completes:

1. Click "Stopp automatisering" (Stop Automation)
2. The application will:
   • Cancel all pending registrations
   • Stop monitoring
   • Return to idle state
3. You can restart automation anytime by clicking "Start automatisering" again

Understanding Status Messages

Info Messages

Normal operation messages:

• Login successful
• Schedule fetched
• Session found
• Registration completed

Warning Messages

Important notices that don't prevent operation:

• STU session has conflict with another class
• Session skipped due to overlap
• Registration window not yet open

Error Messages

Problems that may require attention:

• Login failed
• Network connection lost
• Unable to fetch schedule
• Registration failed

Debug Messages

Detailed technical information (only visible if "Detaljert logging" is enabled):

• API requests and responses
• Internal processing steps
• Timing calculations

Notifications

AkademiTrack shows system notifications for important events:

Registration Success

• Appears when attendance is successfully registered
• Shows the session name and time
• Confirmation that you don't need to do anything

Automation Complete

• Appears when all sessions for the day are handled
• You can close AkademiTrack or let it run

Error Notifications

• Appear if something goes wrong
• Check the activity log for details
• May need to restart automation

Activity Log

The activity log shows all actions taken by AkademiTrack:

Viewing the Log

• Visible by default in the main window
• Can be hidden in Settings → Generelt → "Vis aktivitetslogg"

Log Information Each log entry shows:

• Timestamp
• Message type (INFO, WARNING, ERROR, DEBUG)
• Description of what happened

Using the Log

• Scroll through to see what AkademiTrack has done
• Useful for troubleshooting issues
• Can be copied for support requests

Tips for Best Results

Run Early in the Day

Start AkademiTrack when you arrive at school or start your study session. This ensures it's ready when registration windows open.

Keep App Running

Don't close AkademiTrack while it's monitoring. It needs to stay open to register attendance automatically.

Check Notifications

Pay attention to notifications to confirm registrations are happening successfully.

Enable Auto-Start

For a hands-off experience, enable both "Start with system" and "Auto-start automatisering" in settings.

Monitor on First Use

Watch the activity log during your first few uses to understand how it works and verify everything is functioning correctly.

Keep Internet Connected

AkademiTrack needs continuous internet access to communicate with iSkole.

Common Scenarios

Scenario: No STU Sessions Today

If you start automation and have no STU sessions scheduled:

• "Ingen STU-økter funnet for i dag" (No STU sessions found for today)
• Automation stops immediately
• This is normal - you only need to run it on days with STU

Scenario: All STU Sessions Have Conflicts

If all your STU sessions overlap with other classes:

• Each conflicting session is logged with details
• "Alle økter har konflikter - ingen registreringer nødvendig" (All sessions have conflicts - no registrations needed)
• Automation completes without registering anything
• This is correct behavior - you shouldn't register for conflicting sessions

Scenario: Mixed Sessions (Some Conflicts, Some Valid)

• Conflicting sessions are skipped
• Valid sessions are monitored and registered
• Each decision is logged clearly

Scenario: Registration Window Already Passed

If you start automation after a registration window has closed:

• "Registreringsvindu har stengt for [Økt]" (Registration window has closed for [Session])
• That session is skipped
• Future sessions are still monitored

Using Multiple Devices

You can install AkademiTrack on multiple devices, but:

• Each device needs its own setup
• Credentials are not synced between devices
• Running on multiple devices simultaneously is not recommended
• Registration may happen multiple times if run on multiple devices

Updating Your Schedule

AkademiTrack fetches your schedule fresh each day:

• No need to manually refresh
• Schedule changes are reflected automatically
• Stop and restart automation if your schedule changes during the day

Privacy During Use

While running, AkademiTrack:

• Only accesses your own iSkole data
• Only registers attendance for your account
• Does not interact with other students' data
• Operates within iSkole's normal usage patterns

---

Next Steps

Now that you know how to use AkademiTrack:

• Explore Settings & Configuration for customization options
• Check Troubleshooting if you encounter any issues
• Visit FAQ for answers to common questions

---

Need Help?

If something isn't working as expected:

• Check the activity log for error messages
• Visit the Troubleshooting page
• Check the FAQ page
• Create an issue on GitHub
• Contact the developers directly