Skip to main content

Mapping the Hidden Connections in the National Teaching Repository

The National Teaching Repository (NTR) has just won a prestigious national award for teaching and learning — the Collaborative Award for Teaching Excellence 2026. Good timing, then, to bring together two things I've been enjoying lately: being part of the NTR board, and playing with AI to solve problems.

I wanted to see what happened if I pointed some vibe-coding and some AI-assisted analysis at the repository itself. Could I surface patterns in the NTR that aren't obvious just from browsing it — the invisible web of who has worked with whom, and what the collective body of work is actually about? Two small activities, one feeding into the other.

Activity 1: Mapping co-author connections

The first idea was simple: go through the NTR's FigShare listing and map the links between authors, to see the inter-connectedness that has organically built up over the years.

The prompt I used was:

I would like to go through the https://figshare.edgehill.ac.uk/The_National_Teaching_Repository articles to show links between authors. Produce code to do this before generating the final code ask questions for clarity

The "ask questions for clarity before generating the final code" part matters — it's a small habit that saves a lot of wasted effort, and it meant the resulting code actually matched what I wanted rather than a guess at it.


shows authors and links between them
co-author map

The output was a co-author map — nodes for authors, edges for shared articles — showing at a glance who tends to cluster together and where the bridges between clusters sit.

The only hiccup was a genuinely minor one: one of the libraries the code needed wasn't mentioned in the setup instructions. I've fixed that in the repo itself, so if you want to run this yourself, the README has the fix for the missing import.

Code is here if you want to play with it: git@github.com:scottturnercanterbury/NTRAI.git

Activity 2: What is the NTR actually about?

With the edge data from Activity 1 already containing the titles of every piece in the repository, the obvious next question was: what are the themes? Not a deep dive into abstracts and descriptions — just titles — so treat this as indicative rather than exhaustive. Even so, it throws up some genuinely interesting patterns.

I asked for a proper thematic analysis, following Braun and Clarke's well-known method (V. Braun, V. Clarke, Using thematic analysis in psychology, Qualitative Research in Psychology, 3(2), 2006, pp. 77–101, DOI: 10.1191/1478088706qp063oa):

From the uploaded file using shared titles, carry out a thematic analysis. Before doing the analysis, please ask any questions you need, then do the analysis. Please use the steps in Braun and Clarke (V. Braun, V. Clarke, Using thematic analysis in psychology, Qualitative Research in Psychology, 3(2), 2006, pp. 77–101, DOI: 10.1191/1478088706qp063oa) to do this. Constraints Scope: All titles Depth of data: All available data Analytical lens: What are the themes in the repoistory this is data from https://figshare.edgehill.ac.uk/The_National_Teaching_Repository Target themes: Look for semantic themes and then provide a separate analysis of latent themes Please ask any clarification questions before starting the analysis.

Eight themes came out of it, covering all 324 titles:

  1. Designing, Assessing and Structuring the Curriculum (≈53 titles) — assessment design, feedback, module and curriculum development, employability.
  2. Digital, Technological and AI-Mediated Teaching (≈57 titles) — the largest cluster, spanning online/VR tools through to a fast-growing sub-cluster on generative AI in teaching.
  3. Equity, Belonging and Student Wellbeing (≈52 titles) — inclusive practice, decolonising the curriculum, mental health, personal tutoring.
  4. Active, Playful and Creative Pedagogy (≈19 titles) — gamification, escape rooms, zines and other creative/ludic methods.
  5. Discipline-Specific and Practice-Based Teaching (≈34 titles) — heavily health, nursing, bioscience and lab/fieldwork skills.
  6. Scholarly Identity, Recognition and the SoTL Community (≈45 titles) — Fellowship and NTF applications, SoTL identity and career development.
  7. Internationalisation and Cross-Border Partnership (≈27 titles) — international collaboration projects and support for international students.
  8. The Repository as Infrastructure (≈29 titles) — a reflexive cluster about the NTR itself: how to submit, how it's governed, its own history.

Two themes are worth a closer look. Digital, Technological and AI-Mediated Teaching is the single largest grouping — no surprise, but it's striking how much of that growth is very recent generative-AI content, from prompt templates to critique pieces on AI and racialised gender. And The Repository as Infrastructure is a nice reminder that a repository like this doesn't just accumulate content by accident — there's a whole meta-layer of guidance, governance and conference presentations keeping it alive, submitted by the same community that's building the co-author network in Activity 1.

So what?

Two different uses of AI, chained together: collect the data from the repository, visualise the links between authors, then hunt for themes in the titles.

There's plenty of refining still to do on Activity 1 — this was done quickly and should be seen as a starting point rather than a finished tool. The obvious issue is the same author sometimes showing up as two different nodes because of how their name was entered. And for Activity 2, capturing more information — abstracts, for instance — rather than just titles would sharpen the thematic analysis considerably.

Still, as a quick way of turning an award-winning repository into a map and a set of themes, it's a nice example of what a bit of vibe-coding and an afternoon can do.



All opinions in this blog are the Author's and should not in any way be seen as reflecting the views of any organisation the Author has any association with. Twitter @scottturneruon

Comments

Popular posts from this blog

Programming Anki's Vector robot

With the sad news that Anki is shutting down ( https://www.vox.com/2019/4/29/18522966/anki-robot-cozmo-staff-layoffs-robotics-toys-boris-sofman ) I thought it was time I start playing with the SDK for the Vector robot. In this short post, I providing a quick overview of getting going with this with a simple program based on the tutorials Anki provide. Installation I am using a Mac (more details are available here  https://developer.anki.com/vector/docs/install-macos.html ) but there are instructions for Windows and Linux. - You need the Vector to have been set-up previous on a tablet, and an account set-up on the Anki Cloud. - Install Homebrew - available here  https://brew.sh/ - Using Homebrew to install Python3  brew install python3 -Now install the SDK  python3 - m pip install -- user anki_vector - Lst but not least configure the set-up  python3 - m anki_vector . configure - that is it. The configuration tool tells you where the serial...

Speech Recognition in Scratch 3 - turning Hello into Bonjour!

The Raspberry Pi Foundation recently released a programming activity Alien Language , with support Dale from Machine Learning for Kids , that is a brilliant use of Scratch 3 - Speech Recognition to control a sprite in an alien language. Do the activity, and it is very much worth doing, and it will make sense! I  would also recommend going to the  machinelearningforkids.co.uk   site anyway it is full of exciting things to do (for example loads of activities  https://machinelearningforkids.co.uk/#!/worksheets  ) . Scratch 3 has lots of extensions that are accessible through the Extension button in the Scratch 3 editor (see below) which add new fun new blocks to play with. The critical thing for this post is  Machine Learning for Kids  have created a Scratch 3 template with their own extensions for Scratch 3 within it  https://machinelearningforkids.co.uk/scratch3/ . One of which is a Speech to Text extension (see below). You must use this one ...

Robot Software

In the previous blog posts for this 'series' "It is a good time...."  Post 1  looked at the hardware unpinning some of this positive rise in robots; Post 2  looked at social robots; Post 3  looked at a collection of small robots; Post 4 looked at further examples of small robots Robots, such as the forthcoming Buddy and JIBO, will be based some established open sourceand other technologies. Jibo will be based around various technologies including Electron and JavaScript (for more details see:  http://blog.jibo.com/2015/07/29/jibo-making-development-readily-accessible-to-all-developers/ ). Buddy is expected to be developed around tools for Unity3d, Arduino and OpenCV, and support Python, C++, C#, Java and JavaScript (for more details see http://www.roboticstrends.com/article/customize_your_buddy_companion_robot_with_this_software_development_kit ).  This post contin ues with some of the software being used with the smaller robots.  A number ...