Latest revision as of 09:01, 14 April 2025

The goal of GraphIT is to develop and evaluate a dependency graph of learning contents. This graph enables faculties to develop better study programs, teachers to structure their courses better and students to find the best way to achieve their personal goals.

💡 On each interactive visualization on this page, you can click on the "GraphIT Query Service" link in the lower left corner. This opens a new tab which shows you the SPARQL query and allows you to modify it.

The Dependency Graph

Learning contents connect to each other to form a learning path

A dependency graph is a collection of nodes (or items), connected with each other using edges (or properties), to show which nodes depend on others. For GraphIT the nodes represent a topic of study.

At the lowest level our graph is structured by linking learning contents to their prerequisite(s). Students can use these links to determine how topics depend on each other, and what knowledge is required to understand a specific item. Materials (such as tutorials and articles) or exams can also be linked to each learning content.

In the end the graph turns into a big interconnected structure:

A snippet of the dependency graph

In order to make this amount of data useable, several Structure-Items have been defined to help group items together. For example learning contents of similar topics are included in a category, that can later be referenced when putting a course together. Courses include Session-Items (representing an actual session of a course), that also include all items that are being discussed in person.

Items being discussed in a session on 3D-Graphics of the CGBV-course	All items included in the category 3D-Graphics

The User-Item of a student and all items connected to it

Every item can further include existing properties. This allows for specifying information such as a date, expressing interest, people responsible and URLs.

People can interact with the graph by creating a User-Item (example: Max Mustermann), that they can use to link back to items in different ways.

For a more detailed explanation of the entire underlying structure go to GraphStructure or take a quick look at these following diagrams:

The base structure
Connection of courses

Using the Graph

The graph itself is just a versatile data structure. In order to make it usable, we are developing tools and visualizations. The SPARQL query language offered by WikiBase allows for retrieving relevant parts of the graph and visualizing it in different ways. This can offer insights on about the contents of the graph, but also the graph itself and it's underlying structure.

We combine different visualization to create a course page (see for example: WissArb and CGBV), where a collection of information is contained in one place.

Such as a timeline of all course sessions:

All sessions of the CGBV course

Or an overview of students knowledge and interests:

Students self defined interests and prior knowledge for learning contents of the WissArb-Course

Such a graph is possible by allowing students to modify their personal user-item and use it to link to items with the properties: has completed and interested in.

Or

Learning paths to show the step-by-step path towards learning a topic (here: Virtual Cameras)	The most important categories the course talks about

Custom Frontends

A visual editor for graph exploration and marking items

A tabular editor for modifiying and connecting items

For an easier and more direct way of interaction some custom frontends have been developed.

Students can interact with the graph using a visual editor. It shows a specific course and all items it includes. It allows students to explore the graph, see learning paths towards specific topics and quickly mark items as prior knowledge or a topic that they are interested in.

Admins can interact with a tabular editor, that can modifiy items dependently and independently of each other. They can move, copy or delete statements (property-item-pairs) between items and create new connections.

Plans for the Future

We want to implement:

Evaluation and implementation of a suitable infrastructure (based on Wikibase)
Structuring the content of a course of study as a dependency graph
Continuous evaluation of the usage through pilot projects in courses, in the planning/revision of a degree program and for individual learning paths, e.g. for career changers
Integration of OER
Analysis of the course of study aggregated and in person
Development of tools for visualizing and processing the data
Preparation for scaling the concept to university / national / international level

Cooperation with other partners is planned, in particular with developers in the area of Wikibase / graph databases and application partners from the public sector.

@@ Line 24: / Line 24: @@
 [[GraphStructure#Course|Courses]] include [[GraphStructure#Session|Session]]-Items (representing an actual session of a course), that also [[Property:P14|include]] all items that are being discussed in person.
-<div style="border: solid 5px #d2d6e0; background-color:#eaecf0;">
+{| class="wikitable"
-{{#widget:SPARQLquery|code=
+! Items being discussed in a '''[[Item:Q940|session]]''' on 3D-Graphics of the ''CGBV''-course
+! All items included in the '''category''' ''[[Item:Q8|3D-Graphics]]''
+|-
+| style="width: 64%" | {{#widget:SPARQLquery|code=
 #defaultView:Graph
 PREFIX wdt: <https://graphit.ur.de/prop/direct/>
@@ Line 40: / Line 43: @@
    service wikibase:label { bd:serviceParam wikibase:language "en".}
 } LIMIT 100
-|caption=Items being discussed in a session on 3D-Graphics of the ''CGBV''-course
 }}
-</div>
+| style="width: 36%" | {{#widget:SPARQLquery|code=
+#defaultView:Table
+PREFIX wdt: <https://graphit.ur.de/prop/direct/>
+PREFIX wd: <https://graphit.ur.de/entity/>
+select distinct ?item ?itemLabel
+where {
+  BIND (wd:Q8 as ?category)
+  ?category wdt:P14 ?item.
+  service wikibase:label { bd:serviceParam wikibase:language "en".}
+}
+}}
+|}
+</br>
 {| class="wikitable" style="float:right; width:40em; margin-left:5px"
-! The User-Item of a student and all items connected to it
+! The '''User-Item''' of a ''[[Item:Q157|student]]'' and all items connected to it
 |-
 |
@@ Line 54: / Line 69: @@
 PREFIX wd: <https://graphit.ur.de/entity/>
-SELECT ?item1 ?image ?item1Label ?item2 ?image2 ?item2Label ?edgeLabel ?rgb WHERE {
+SELECT ?item1 ?item1Label ?item2 ?item2Label ?edgeLabel ?rgb ?shape WHERE {
    VALUES ?item1 {wd:Q157}
@@ Line 68: / Line 83: @@
            if(?prop = wdt:P23, "ffeec2", # interested in (orange)
         "FFFFFF" ))) as ?rgb).
+  # Shape Coding:
+    BIND (if(?prop = wdt:P25, "text", # participates in
+          if(?prop = wdt:P12, "ellipse", # has completed
+          if(?prop = wdt:P23, "box", # interested in
+        "text" ))) as ?shape).
 SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
@@ Line 88: / Line 108: @@
 = Using the Graph =
 The graph itself is just a versatile data structure. In order to make it usable, we are developing tools and visualizations. The [https://www.w3.org/TR/sparql11-query/ SPARQL] query language offered by WikiBase allows for retrieving relevant parts of the graph and visualizing it in different ways. This can offer insights on about the contents of the graph, but also the graph itself and it's underlying structure.
 We combine different visualization to create a course page (see for example: [[Courses/WissenschaftlichesArbeiten|WissArb]] and [[Courses/CGBV_SS24|CGBV]]), where a collection of information is contained in one place.
@@ Line 145: / Line 166: @@
 </div>
-Such a graph is possible by allowing students to modify their personal user-item and use it to link to items with the properties: [[Property:P12|has completed]] and [[Property:P23|interested in]].
+<small>Such a graph is possible by allowing students to modify their personal user-item and use it to link to items with the properties: [[Property:P12|has completed]] and [[Property:P23|interested in]]. </small>
-Or '''learning paths''', to show the step-by-step path towards learning a specific topic:
+Or
-{{Learning Path2|item=Q149}}
+{| class="wikitable"
+! '''Learning paths''' to show the step-by-step path towards learning a topic (here: [[Item:Q149| Virtual Cameras]])
+! The most important ''categories'' the course talks about
+|-
+<!-- Linke Spalte -->
+| style="width: 60%" | {{#widget:SPARQLquery|code=
+#defaultView:Graph
+# prerequisite -> topic -> postrequisite
+PREFIX wd: <https://graphit.ur.de/entity/>
+PREFIX wdt: <https://graphit.ur.de/prop/direct/>
+SELECT distinct ?v ?vLabel ?rgb ?link ?linkLabel
+WHERE {
+{
+  { SELECT * WHERE {
+  { SELECT ?goal ?goalLabel ?topic ?topicLabel WHERE {
+    {
+    BIND (wd:Q149 as ?goal).
+    ?goal wdt:P1+ ?topic.
+    } UNION {
+      VALUES ?topic { wd:Q149 } # we also want to include the root node itself
+    }
+  }
+  }
+  ?topic wdt:P1 ?pre.
+  BIND (?topic as ?v). # + add all ?pre that are not yet in ?topic
+  BIND (?pre as ?link).
+  bind (if(?v = wd:Q149, "FBBC74", "FFEDD8") as ?rgb).
+  }
+  }
+  Union
+  { SELECT * WHERE {
+  { SELECT ?topic ?topicLabel ?goal ?goalLabel WHERE {
+    {
+      BIND (wd:Q149 as ?topic).
+      ?goal wdt:P1+ ?topic.
+    } UNION {
+      VALUES ?topic { wd:Q149 } # we also want to include the root node itself
+    }
+  }
+  }
+  ?post wdt:P1 ?topic.
+  BIND (?post as ?v).
+  BIND (?topic as ?link).
+  bind ("F68C13" as ?rgb).
+  }
+  }
+  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
+}
+}
+}}
+<!-- Rechte Spalte -->
+| style="width: 40%" | {{#widget:SPARQLquery|code=
+#defaultView:BubbleChart
+PREFIX wd: <https://graphit.ur.de/entity/>
+PREFIX wdt: <https://graphit.ur.de/prop/direct/>
+SELECT DISTINCT ?category ?categoryLabel ?items
+WHERE {
+  wd:Q932 wdt:P14 ?category.
+  ?category wdt:P3 wd:Q169.
+  {
+  SELECT ?category ?categoryLabel (COUNT(DISTINCT ?item) as ?items) WHERE {
+    ?category wdt:P14 ?item.
+  } GROUP BY ?category ?categoryLabel
+  }
+  filter (?items>=8)
+  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
+}
+}}
+|}
 == Custom Frontends ==
-[[File:Visual-Editor-screenshot.png|thumb|right|400px|A visual editor for graph exploration and marking items]]
+[[File:Visual-Editor-screenshot.png|thumb|right|460px|A '''visual editor''' for graph exploration and marking items]]
-[[File:Table-Editor-Screenshot2.png|thumb|right|400px|A tabular editor for modifiying and connecting items]]
+[[File:Table-Editor-Screenshot2.png|thumb|right|460px|A '''tabular editor''' for modifiying and connecting items]]
 For an easier and more direct way of interaction some custom frontends have been developed.
 Students can interact with the graph using a '''[https://test.graphit.ur.de/app/src/pages/selectionTools/ visual editor]'''.
-It shows a specific course and all items it includes. It allows students to explore the graph, see learning paths towards specific topics and quickly mark items as prior knowledge or a topic that they are interested in.
+It shows a specific course and all items it includes. It allows students to explore the graph, see learning paths towards specific topics and quickly mark items as [[Property:P12|prior knowledge]] or a topic that they are [[Property:P23|interested in]].
 Admins can interact with a '''tabular editor''', that can modifiy items dependently and independently of each other. They can move, copy or delete ''statements'' (property-item-pairs) between items and create new connections.

Quick Overview: Difference between revisions

Latest revision as of 09:01, 14 April 2025

The Dependency Graph

Using the Graph

Custom Frontends

Plans for the Future