A Closer Look …

… with added diagram goodness.

I thought I’d write a quick post, giving you a bit more detail on what we’re looking to do, technically, with the project – not too technical (although if you do want lots more info on that then please do let us know).

Essentially, what we’re going to do is:

  • Identify where the content we’re covering lives.
  • Pull in the metadata – titles, descriptions, copyright, etc – and aggregate it all.
  • Generate that into a searchable index.
  • Map the resources to curriculum and enhance the metadata with this added information.
  • Develop an API (Application Programming Interface) to enable flexibility and variety when it comes to creating the tools you can use to search and discover.

Which looks like this

Project Architecture Diagram

There are two key parts – well, ok, three if you count the metadata aggregation. Obviously, mapping the resources to FE curriculum is hugely important as this is right at the core of creating better paths to the content. The API is the other key bit.

This will enable us (or anyone else for that matter) to create different tools for searching and finding Jisc digital content. We can have a webpage with search bar and lovely blocks of content displayed according to where it lives, but we can also integrate with existing sites that already give you access to content collections. For example the Re:Source site for FE practitioners in Scotland. We can also look at developing plugins for VLEs, like a Moodle Block (similar to what the Caboodle project have done) or mobile apps. This will, of course, be driven by your feedback and requirements … so if you would like to contribute do get in touch. Or help us out by filling in our survey! 🙂

If you’re a bit lost at the whole “API” thing, then worry not! This short video gives you a nice explanation of what they enable apps and software to do.