• Home
  • Project
    Introduction
    • Introduction
    • Background and Motivation
    • What is a Good Timetable?
    • Project Aims and Scope
  • Graph Data
    Model
    • Graph vs Relational Data Models
    • Graph Data Model for Timetabling
    • Early Insights
    • Model Expansion
    • Graphing Time
  • Data
    Pipeline
    • ETL Overview
    • Approach
    • Configuration and Logging
    • Extract
    • Transform
    • Google Drive Load
    • Neo4j Load
    • Reflection
  • Timetable
    Metrics
    • Timetable Metrics
    • Metric Aggregations
    • Implementing Metrics
    • TQI Summary
  • Final
    Thoughts
  • Appendices
    & Extras
    • Appendix Table of Contents
    • References
    • Acknowledgements
  • Word
  1. Supervision
  2. Notes Example 2
  • Home
  • Project Introduction
    • Introduction
    • Background and Motivation
    • What is a Good Timetable?
    • Project Aims and Scope
  • Graph Data Model
    • Graph vs Relational Data Models
    • Graph Data Model for Timetabling
    • Early Insights
    • Model Expansion
    • Graphing Time
  • Data Pipeline
    • ETL Overview
    • Approach
    • Configuration and Logging
    • Extract
    • Transform
    • Google Drive Load
    • Neo4j Load
    • Reflection
  • Timetable Metrics
    • Timetable Metrics
    • Metric Aggregations
    • Implementing Metrics
    • TQI Summary
  • Final Thoughts
  • Appendices
    • Random Graph Generator
    • Technology Stack
    • Configuration
    • Anonymisation
    • ETL Summary and Code
      • ETL Summary
      • ETL Code
      • Config and Misc
      • Extract-SQL
      • Extract
      • Google Drive Load
      • Transform
      • Neo4j Load
    • Neo4j & Cypher Code
      • Cypher Queries
      • Creating Nodes and Relationships
      • Deleting Nodes and Relationships
      • General Queries
      • Count Queries
      • Hard (timetabling) Constraints
      • Student Clashes
      • Soft Constraints
      • Rooms and Spaces
      • Perspectives
      • Blue Skies Opportunities
  • Supervision
    • Supervision
    • Notes Example 1
    • Notes Example 2
    • Notes Example 3
  • References
  • Acknowledgements

On this page

  • Summary
  • Accomplishments
  • Next Steps
    • Weekly Goal: What is goal of next fortnight?
  • Issues/Blockers
  • Post-Meeting Notes
  1. Supervision
  2. Notes Example 2

Fortnightly Update - 2024-06-24

Summary

Significant progress in the backend and more proof-of-concept in front end.

Accomplishments

  • Project Management
  • Data Collection:
      • modularised, scalable, configurable, efficient pipeline
      • More than half way completed - same principles
      • need to add staff, student, activity nodes and test outcomes
      • need to add relationships and test.
  • Analysis / Wrangling:
  • Model Development:
  • Results:
  • Pipeline development
  • Cypher queries for version 1
  • conversation with business owners to validate work

Next Steps

Weekly Goal: What is goal of next fortnight?

  • write up and benchmark v1 notes
  • finish developing and testing pipeline:
    • extract
    • transform
    • load
  • document pipeline - written and visual (mermaid?)
  • develop cypher queries for version 2
  • design (theory) timetable quality index
  • consider scaling dataset
  • start writing project notes

Issues/Blockers

  • Technical:
    • Digital certificates on machines preventing load
    • Neo4j Aura (free) limitations - loading issues
  • Methodological: Concerns about approach or analysis?
    • Spending a lot of time getting ETL ‘right’
    • Not sure about balance of project and what I will deliver at the end
  • Data-Related: Issues with data quality, access, or quantity?
    • Working on pipelines which will mean I can scale accordingly (within constraints of free instance)

Post-Meeting Notes

My supervisor and I spoke about where I am at in the project at the moment and next steps. We discussed what I am attempting to do and why, including graph data structures, proof-of-concept, etc. and that it is becoming a data engineering project. I stated that my timeline looks to complete a robust data ETL pipeline by the middle of July, with a view to shifting towards more work within Neo4j from the end of July to the middle of August.

We agreed to meet in two weeks.

Notes Example 1
Notes Example 3

Copyright 2024, Petter Lövehagen

 

Built with Quarto