Item banks and the JISC Information Environment CETIS Metadata and Repositories SIG, Glasgow
Contents <ul><li>an overview of the JISC Information Environment </li></ul><ul><ul><li>the JISC IE technical standards </l...
<ul><li>… the JISC Information Environment… </li></ul>
The JISC Information Environment is… <ul><li>an enabling architecture or framework </li></ul><ul><li>geared towards delive...
The JISC Information Environment… <ul><li>encourages ‘content providers’ to offer machine interfaces (services) that </li>...
JISC IE technical standards <ul><li>encourages ‘content providers’ to offer machine interfaces (services) that </li></ul><...
In a nutshell… the JISC IE <ul><li>shares some similarities with what has now come to be known as Web 2.0… </li></ul><ul><...
JISC IE Architecture JISC-funded content providers institutional content providers external content providers brokers aggr...
The OAI-PMH in more detail <ul><li>OAI Protocol for Metadata Harvesting </li></ul><ul><li>simple protocol for sharing meta...
OAI-PMH (2) <ul><li>simple DC is default (mandatory) record format </li></ul><ul><li>supports any record format provided i...
<ul><li>… item banks… </li></ul>
What is an item? <ul><li>a content package (IMS CP) </li></ul><ul><li>containing </li></ul><ul><ul><li>a QTI XML file </li...
What is an item bank? <ul><li>a repository of ItemCPs </li></ul><ul><li>i.e. a database for storing ItemCPs (in packaged o...
<ul><li>… bringing it all together… </li></ul>
What we need to do – the JISC IE way <ul><li>first and foremost…  assign cool URIs  to every ItemCP (and other significant...
What we need to do – the Web 2.0 way <ul><li>first and foremost…  assign cool URIs  to every ItemCP (and other significant...
Questions… <ul><li>…  and discussion </li></ul>
Upcoming SlideShare
Loading in...5
×

Item Banks and the JISC Information Environment

2,694

Published on

A presentation to the CETIS Metadata and Digital Repositories SIG meeting in Glasgow during October 2006.

Published in: Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,694
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Item Banks and the JISC Information Environment

  1. 1. Item banks and the JISC Information Environment CETIS Metadata and Repositories SIG, Glasgow
  2. 2. Contents <ul><li>an overview of the JISC Information Environment </li></ul><ul><ul><li>the JISC IE technical standards </li></ul></ul><ul><li>an overview of Item Banks </li></ul><ul><ul><li>what is an item? </li></ul></ul><ul><ul><li>what is an item bank? </li></ul></ul><ul><li>bringing it all together </li></ul>
  3. 3. <ul><li>… the JISC Information Environment… </li></ul>
  4. 4. The JISC Information Environment is… <ul><li>an enabling architecture or framework </li></ul><ul><li>geared towards delivery of more seamless interoperability between ‘resource discovery’ services in UK HE and FE </li></ul><ul><li>primarily intended to allow end-users to discover , access , use and publish resources </li></ul><ul><li>heterogeneous – i.e. the JISC IE does not specify what a ‘resource’ is </li></ul><ul><ul><li>bibliographic resources, images, videos, map data, research data, datasets, sounds, etc., etc. </li></ul></ul><ul><ul><li>digital and physical </li></ul></ul>
  5. 5. The JISC Information Environment… <ul><li>encourages ‘content providers’ to offer machine interfaces (services) that </li></ul><ul><ul><li>expose metadata for harvesting </li></ul></ul><ul><ul><li>expose metadata and/or full-text for searching </li></ul></ul><ul><ul><li>expose resources at persistent URIs </li></ul></ul><ul><ul><li>expose news-feeds </li></ul></ul><ul><ul><li>expose context-sensitive links to resources when appropriate </li></ul></ul><ul><li>enables everyone else to </li></ul><ul><ul><li>build user-centric and machine-centric applications on top of those machine interfaces </li></ul></ul>
  6. 6. JISC IE technical standards <ul><li>encourages ‘content providers’ to offer machine interfaces (services) that </li></ul><ul><ul><li>expose metadata for harvesting </li></ul></ul><ul><ul><li>expose metadata and/or full-text for searching </li></ul></ul><ul><ul><li>expose resources at persistent URIs </li></ul></ul><ul><ul><li>expose news-feeds </li></ul></ul><ul><ul><li>expose context-sensitive links to resources when appropriate </li></ul></ul>… use Shibboleth for authentication and access control and register interface details with the IESR OAI-PMH SRU HTTP and cool URIs RSS 1.0 OpenURL
  7. 7. In a nutshell… the JISC IE <ul><li>shares some similarities with what has now come to be known as Web 2.0… </li></ul><ul><li>... though it also has significant differences </li></ul><ul><li>encouraged openness but didn’t engender participation </li></ul><ul><ul><li>too rigid in use of unRESTful standards? </li></ul></ul><ul><ul><li>do we ‘trust our users’ and their ‘right to remix’? </li></ul></ul>http://www.oreillynet.com/pub/a/oreilly/tim/ news/2005/09/30/what-is-web-20.html
  8. 8. JISC IE Architecture JISC-funded content providers institutional content providers external content providers brokers aggregators catalogues indexes institutional portals subject portals learning management systems media-specific portals end-user desktop/browser presentation fusion provision OpenURL link servers shared infrastructure identity providers (IdP) institutional profiling services terminology services service registries identifier services metadata schema registries © Andy Powell, Eduserv Foundation, 2006 This work is licensed under a Creative Commons License Attribution-ShareAlike 2.0 Athens federation services (e.g. WAYF) Content providers are services that make content available… e.g. repositories (of anything, including QTI items) Presentation layer applications now typically delivered thru the browser using Ajax, JSON, etc.
  9. 9. The OAI-PMH in more detail <ul><li>OAI Protocol for Metadata Harvesting </li></ul><ul><li>simple protocol for sharing metadata records between applications </li></ul><ul><li>currently at version 2.0 </li></ul><ul><li>based on HTTP, XML, XML Schema and XML namespaces </li></ul><ul><li>allows a harvester to ask a remote repository for some or all of its metadata records </li></ul>
  10. 10. OAI-PMH (2) <ul><li>simple DC is default (mandatory) record format </li></ul><ul><li>supports any record format provided it can be encoded using XML and XML Schema (e.g. DC, IEEE LOM, MARC, ODRL, …) </li></ul><ul><li>neutral about what kind of resource is described by the metadata Open Archives Initiative http:// www.openarchives.org / </li></ul>
  11. 11. <ul><li>… item banks… </li></ul>
  12. 12. What is an item? <ul><li>a content package (IMS CP) </li></ul><ul><li>containing </li></ul><ul><ul><li>a QTI XML file </li></ul></ul><ul><ul><li>any associated resources such as images, sound clips, etc. </li></ul></ul><ul><ul><li>and some metadata (imsmanifest.xml) </li></ul></ul>Assumption: QTI items are only ever shared in the form of a CP (ItemCP)
  13. 13. What is an item bank? <ul><li>a repository of ItemCPs </li></ul><ul><li>i.e. a database for storing ItemCPs (in packaged or unpackaged form), supporting machine interfaces that allow other applications to </li></ul><ul><ul><li>harvest metadata records (OAI-PMH) </li></ul></ul><ul><ul><li>search metadata and/or item content (SRU) </li></ul></ul><ul><ul><li>obtain copies of the ItemCPs themselves (HTTP and cool URIs) </li></ul></ul><ul><ul><li>grab news feeds (RSS) </li></ul></ul><ul><ul><li>deposit new or updated ItemCPs (??) </li></ul></ul>
  14. 14. <ul><li>… bringing it all together… </li></ul>
  15. 15. What we need to do – the JISC IE way <ul><li>first and foremost… assign cool URIs to every ItemCP (and other significant resources) held in the Item Bank </li></ul><ul><li>map the imsmanifest.xml metadata to simple Dublin Core - expose a simple DC record for every ItemCP in the Item Bank using the OAI-PMH </li></ul><ul><ul><li>dc:identifier should contain the cool URI (above) </li></ul></ul><ul><li>optionally, index the metadata and item content and expose search interface using SRU </li></ul><ul><li>optionally, expose news feeds using RSS </li></ul>
  16. 16. What we need to do – the Web 2.0 way <ul><li>first and foremost… assign cool URIs to every ItemCP (and other significant resources) held in the Item Bank </li></ul><ul><li>generate a Google sitemap for every ItemCP in the Item Bank </li></ul><ul><ul><li>consider browser sniffing/content negotiation to serve an HTML view of every ItemCP to Google and other robots </li></ul></ul><ul><li>optionally, index the metadata and item content and expose search interface using A9 OpenSearch </li></ul><ul><li>optionally, expose news feeds as RSS or Atom </li></ul>
  17. 17. Questions… <ul><li>… and discussion </li></ul>

×