How widely useful is the Learning Registry?
Mimas has been working with a variety of UK collaborators on the JISC-funded JLeRN Experiment, an exploration of the Learning Registry (LR) as an application, as an architecture and as a software toolset. There have been a number of valuable developments, including LR nodes, and a range of use cases has been identified and some tested in areas relating to learning resource discovery, utilization and associated paradata.
The JLeRN project completes at the end of October 2012 and Mimas is authoring a Final Report looking at appetite, demand and sectoral capacity with some use cases and case studies.
To supplement this core work, I’ve been asked to produce a complementary report examining the wider potential affordances of The Learning Registry as an architecture or conceptual approach, looking beyond the core educational technology focus to the broader information environment and the associated JISC community.
This will be a short report – but there will be plenty of room to highlight suggestions and observations. So you may wish to comment here on any of my THREE questions – or to add another! Throughout, bear in mind that we’re interested in the potential of the LR and its reuse as an approach to a problem space, as an application, as an architecture or simply as a bunch of reusable Open Source software.
ONE – What functions should the LR provide to be useful? For example …
- Storage, indexing and retrieval at scale
- Distributed / federated data store management
- Authentication, authorisation and other security features
- Provision of open APIs / service interfaces for ingest, publishing and discovery
- Range of ingest / submission / output data formats
- Reporting and visualisation
- Support for annotation, rating and other user contributions
TWO – In what applications or domains could the LR be useful? For example …
- Library activity data
- Research data
- Profiles of people, places
- General analytics data
- Heterogeneous / specialised metadata
THREE – Are there alternative/complementary approaches to the same requirement/problem space? For example …
- Repositories such as DSpace, Fedora, etc
- California Digital Library Micro-services
- Apache Jackrabbit based document stores
- Enterprise data warehouse applications
- Other approaches using combinations of NoSQL databases and indexing
Any comments via this blog will assist in shaping a presentation of iideas at the JLeRN project closing event on 22 October and my public report due by 31 October. Regardless of whether you wish to comment, thanks for your interest!
PS – My report and anything else coming out of this will be published under a Creative Commons CC0 licence.