Slide 1: Technical Infrastructure for Open Content JISC CETIS OER Session 26/11/08 v0.1
Amber Thomas, JISC amber.thomas@jisc.ac.uk
Joint Information Systems Committee
Slide 2: Outline
technical requirements for projects
then
some issues and ideas to get us thinking
Joint Information Systems Committee
Slide 3: Technical Requirements for Projects
All content should be stored in Institutional Repositories All content should be IMS Content Packaged All content should be released under a custom JISC licence All content should be tagged with full UK Lom metadata
Joint Information Systems Committee
Slide 4: Requirements: 1 All content should be stored in Institutional Repositories Content can be anywhere (and in JorumOpen) BUT consider:
how easily discoverable is the content? [public VLEs? slideshare?] how stable are the URLs? how easily can you update and manage it? how can you track usage? [google analytics? social bookmarking?]
Joint Information Systems Committee
Slide 5: Requirements: 2 All content should be IMS Content Packaged Content can be in any format BUT consider:
how accessible is the content? how easy is it to edit the content? [youtube? slideshare? flash player?] how long/how well will the format be supported? [msoffice versions?]
Joint Information Systems Committee
Slide 6: Requirements: 3 All content should be released under a custom JISC licence Content can be released under a creative commons licence (or similar) BUT consider:
how will authors know whether they own the content they create? how will third party content use be identified, checked and permitted? how will the appropriate licences be chosen and communicated? how will service providers handle the rights issues? [service T&Cs] how will other legal issues be addressed? [performance rights? consent for filming lectures?]
Joint Information Systems Committee
Slide 7: Requirements: 4 All content should be tagged with full UK Lom metadata Content can be minimally tagged BUT consider:
how will you ensure attribution if you don’t include the author name and licence terms? how will you describe the content to a learner and/or a teacher? how will you tag the content by subject/topic? [controlled vocabularies? user-generated tags?]
Joint Information Systems Committee
Slide 8: Requirements: 5 Deposit of objects/links to JorumOpen
BECAUSE JorumOpen will showcase current practices in the UK We need to ensure that all content produced under this programme is surfaced to the open web, with no excuses HEFCE investment needs visible results There’s potential for building rich services on top of an aggregation, so we need to find out what the aggregation looks like It’s better to start with a central model and move to distributed rather than start with distributed and hope to aggregate it later
Joint Information Systems Committee
Slide 9: Some issues and ideas
Stewardship in the web2.0 world My stuff on the web Rights chains Persistence and linked content Network-level stuff Aggregating metadata Collections registries Measures and metrics
Sustainability and business models Who can pay for the effort and technologies to do this? What evidence do they need to prove its worth doing?
It’s not just about content Pulling metadata down from the cloud Content in social networks
Joint Information Systems Committee
Slide 10: Approaches to Socio-Technical Design
Do we design … Top down Bottom up Elegant architectures Evolutionary models Maybe … stitching together what works common workflows commonly used tools and services 80/20 rule
Joint Information Systems Committee
Slide 11: So … Scope for technical infrastructure work
Identify minimum requirements for releasing content into the wild (metadata, persistent identities) Work with existing tools, platforms and practices and identify ways to improve them (easier to use, easier to integrate, more consistent metadata, more informed implementations) Track and monitor release of content and its use (for accountability, for understanding effective release methods, benefits to authors) Identify gaps and opportunities Collate support and good practice in all of the above
… Get involved!
Joint Information Systems Committee
