• 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. Final Thoughts
  • 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

  • Reflections on Journey
  • Looking Ahead: The Future of Graph at Universities

Final Thoughts

As I reflect on this project, I am struck by my progress in realising the original objectives I set out to achieve and what it took to get here. Through a combination of perseverance, problem-solving, and a relentless drive to deliver a tangible solution, I am proud to say that I have successfully:

  1. Designed an extensible, system-agnostic graph data model for university timetables, providing a flexible and adaptable foundation for capturing the complex relationships inherent in timetabling data.

  2. Developed a configurable ETL (extract, transform, load) pipeline to seamlessly transition from relational database representations to a graph database, unlocking new possibilities for timetable analysis and optimisation.

  3. Discussed how graph-based approaches to timetabling analysis can contribute to measuring and improving the overall quality of university timetables, a critical aspect of enhancing the student experience and institutional efficiency.

But I could not have done it without others. I am grateful for the support, guidance and encouragement I have received from many people along the way.

Reflections on Journey

This journey has had a little bit of everything: challenges, setbacks, breakthroughs, and moments of clarity. It has tested my limits, pushed me to grow, and allowed me to create something that I believe can make a meaningful impact. I have learned a lot about myself, my capabilities, and the power of perseverance; I have gained new skills and insights; I have developed a deeper understanding of where I want to go from here.

Admittedly, the project was ambitious, and I found myself struggling with to navigate the ever-expanding scope, not knowing when to ‘stop.’ But, I am proud of what I have achieved and learned, as well as where I am right now - when I can comfortably draw a line under this project as a proof-of-concept, knowing that it provides a foundation for future work and exploration.

In short, it has been fulfilling and I did what I wanted to do - something exploratory, practical, new, challenging, and impactful.

But it is especially rewarding to receive feedback from subject matter experts, such as the timetabling data manager at UWE1, who said:

  • Opens new reporting and analytics opportunities

  • Very useful graphical representation of the relations within the database

  • Huge time saving comparing to current SQL methods

  • Easily adjustable and scalable

  • Date and time represented in much better way

  • Makes reporting of timetable clashes such an easy task

Looking Ahead: The Future of Graph at Universities

Looking ahead, I am confident that the potential of graph databases in the realm of timetabling analysis has only begun to be explored. My project has only scratched the surface but there is a vast reserve of untapped opportunity. By continuing to explore and refine the concepts introduced in this project, Higher Education Institutions can unlock new levels of insight to improve efficiency, agility, and student satisfaction.

And it does not only apply to timetabling datasets.

Universities hold a significant amount of interconnected data that can be leveraged to improve the student experience, make more informed decisions, and drive positive change. The possibilities are endless - to illustrate, I have included some blue-skies thinking in the Appendix.

Footnotes

  1. Personal communication with Wojciech Lewicki, 19 August 2024 - when reviewing and discussion the project.↩︎

TQI Summary
Random Graph Generator

Copyright 2024, Petter Lövehagen

 

Built with Quarto