This document summarizes a meeting of the JISC Coursedata Technical Working Group. It provides an agenda for sharing experiences and tools related to implementing XCRI course data feeds. Attendees are encouraged to discuss their progress, plans, and issues. Project presentations are given on tools developed at Loughborough and Lincoln universities. Future actions and events are planned to continue supporting the adoption of standard course data feeds.
2. Rob Englebright Ruth Drysdale
JISC
JISC
Ian Ibbotson Verena Wiegert
Aggregator team JISC
Alan Paull Craig Hawker
Validator team Validator Team
Scott Wilson Kirstie Coolin
CETIS Coursedata team
3. Wireless, Fires etc
• No planned fire drills, if you hear the alarm
leave and congregate outside.
• Wireless might hold up, might not, don’t
download any ISOs...codes are:
4. Aims of the day
• To support needs of developers/techies implementing xcri-cap
feeds in #coursedata projects. We asked you what you wanted:
• Making contacts with devs at other institutions with common
interests,
• Showing tools, validator, aggregator etc
• Sharing experiences, code etc
• drinking lots of coffee.
• Agenda: bit.ly/coursedata-tech-event -TBC
5. Why are we doing this?
• OLTF @DaveOwhite:
• "Information about online programmes is lacking and often
difficult to find, both for distance courses and for the
online learning elements in blended programmes. This has a
significant impact on student choice, domestically and
internationally. Only with better information can
prospective students find what they want, judge value for
money and make more accurate decisions about where and how to
study. Better information will give institutions
competitive edge" Report to HEFCE by the Online Learning Task
Force January 2011.
6. What exactly is being
done?
• Sept 2011 - Dec 2011 SAF (93)
• Jan 2012 - March 2013
• Review internal course data handling
processes and revise
• ...as a minimum, create a system-
generated course advertising feed in XCRI
CAP 1.2 format with a COOL URI...
• JISC Coursedata Programme: bit.ly/coursedata
7. Who?
Arts University College at Bournemouth London Metropolitan University University of Bedfordshire
Aston University London School of Economics University of Birmingham
Bath Spa University Loughborough College University of Bolton
Birkbeck, University of London Loughborough University University of Cambridge
Bishop Burton College Middlesex University University of East London
Blackpool & The Fylde College Myerscough College University of Essex
Bournemouth and Poole College New College Durham University of Exeter
Bradford College North Lindsey College University of Greenwich
Brunel University Oxford Brookes University University of Hertfordshire
Burton and South Derbyshire College Plymouth College of Art University of Hull
City College Norwich Royal Holloway University of London University of Kent
City of Bristol College St Georges University of London University of Leicester
Cornwall College St Mary's University College University of Lincoln
Coventry University Staffordshire University University of Nottingham
Cranfield University Teesside University University of Oxford
Edge Hill University The Arts University College at Bournemouth University of Salford
Grimsby Institute for HE & FE The Courtauld Institute of Art University of Sheffield
Harper Adams University College University of Central Lancashire Univeristy of Sussex
Lancaster University University College Falmouth University of Sunderland
Leeds Metropolitan University University of the West of England
Leeds Trinity University College University of West London
Leicester College Wigan & Leigh College
10. What does XCRI-CAP
look like?
• http://www.xcri.org/wiki/index.php/
XCRI_CAP_1.2 becoming BS8581-
conformant profile of BS EN 15982
(MLO)
• http://www.xcri.org/wiki/index.php/
XCRI_Feeds
• http://www.xcri.co.uk/data-definitions-
and-vocabulary-framework.html
11. cool URIs
• Requirement for feeds to have a cool URI to
help aggregation:
• data.foo.ac.uk/courses.xml
• foo.ac.uk/data/courses.xml
• foo.ac.uk/courses.xml
• http://lncn.eu/toolkit
12. Licence
• From the Data definitions doc.
• “It is a principle of XCRI-CAP feeds produced under the Course Data
Programme that the data should be freely available to any aggregator or
other user, organisation or individual to copy, re-distribute, share, adapt
and exploit commercially or otherwise.
This document recommends that all such feeds are explicitly licensed
under an Open Government Licence (OGL).
This licence grants to the user a worldwide, royalty-free, perpetual, non-
exclusive licence to use the information, while providing for
acknowledgement of the source of the information. This licence contains
no warranty or liability on the provider, and importantly also includes
specific non-endorsement clauses. “
16. Round Table
discussions
• Get some coffee, Introduce yourselves
• Share your progress, plans and issues
• 3 Questions:
• How far have you got?
• What do you need to do next?
• What actions are there for JISC?
24. Action Planning
• Actions for you...
• Actions for JISC? -future events?
• webinars vs face to face? topics? tools?
25. Adverts
• DEVCSI- mailing list
• Dev8D event, DevXS event
• http://devcsi.ukoln.ac.uk/
• UCLAN elevator feedback
http://bit.ly/uclan-elevator
Notes de l'éditeur
Good morning-\nThis is the JISC coursedata-tech event.\nIf you are here for something else, now is the time to leave.\n\n\n
Rob Englebright\nProgramme Manager with JISC Elearning team.\nI'm looking after part of the #coursedata programme, \nworking with BSI on standardisation of xcri-cap, \nLooking after the tail end of the DVLE programme,\nThe JISC Online conference - in November\n\nRuth Drysdale is in charge of the wider Coursedata programme\nVerena works with Ruth & I, and collates the newsletter, and makes sure stuff happens.\nIan is a Director at Knowledge Integration, and is from the Aggregator team\nAlan Paull is part of the validator team, and has a comprehensive knowledge of XCRI-CAP\nCraig built the validator\nScott wrote a lot of XCRI-CAP\nKirstie is supporting projects, and has done all this before...\n\n\n
\n
The aim of the day is to support those doing the implementation side of things.\n\nWe have tried to pitch it right, but there is a wide range of folk here,\n\nWe have stuff to tell you, we want to gather your thoughts, issues, successes,\nwe want to help you get in touch with each other, and share the joy and pain.\nThis will be better if you join in... \n\nTo give you something to do if you’ve heard a particular bit before, or it’s particularly dulll..\nBingo -there are 10 activities on the card, if you want to have a chance of winning a big(ish) prize (It’s only biggish, as I’ve coughed up for it), scribble down your name, tick off the activities as you do them... add URLS etc..and hand to me by 3.20ish pm.\n[HAND OUT CARDS]\n\nWe’ll pull a winner out of a hat.\n\nWe have breaks in the day, but feel free to nip out for a coffee, or crafty fag whenever.\n\nWe are happy to take questions as we go, if we don’t have answers immediately we’ll work on it and get back to you. If you think of something but don’t want to slow the flow of the presentation or the discussion has moved on, write it down on a post it and stick it on the wall. We will provide feedback through the coursedata-tech page.\n\nLET me tell you a story...\n\n\n
This is our prime driver.\n\nThe Online Learning Task Force (OLTF) published its final report 'Collaborate to compete: Seizing the opportunity of online learning for UK higher education' in January 2011.\n\nIt makes six recommendations to institutions and the wider HE sector. including:\n\nusing online learning to enhance student choice\ndeveloping and exploiting open educational resources.\n\nit found that it was tricky to find some types of course. [read slide]\n\nor to Quote Douglas Adams: on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying 'Beware of the Leopard'\n\n.\n\n
The JISC #coursedata programme..\nstage 1 ran from September- Dec 2011 -and provided small amount of funding to 93 institutions to undertake self review and develop a plan to revise internal systems and implement xcri-cap 1.2\nStage 2 runs from Jan 2012 - March 2013\nOutworking of the plans from stage 1, -Review internal course data handling processes and revise\n\ncreate an xcri-cap1.2 feed with a cool URI- As a minimum the feed generated should include part time, online/distance, post graduate and CPD courses. It is not necessary to include closed courses, although additional feeds for internal consumption could be a useful output\n\nJISC Coursedata Programme: bit.ly/coursedata.\n\n16...as a minimum, create a system-generated course advertising feed in a XCRI CAP 1.2 format with a COOL URI. \n\n
STAGE 2\n\n63 institutions, \n16 FE (400 FTES)\n\nHave a look, \nyou may know some colleagues in these institutions, it may be that some of the projects are working together, as projects are allowed to run “assemblies” using project funding, to gather together, and discuss issues.. there has been a Unit-e assembly, a SITS assembly...\nyou may wish to organise a .NET assembly, a sharepoint assembly, a PHP, or Plone assembly (I saw a couple of folk using Plone- didn’t even realise it was still about)\nI guess it all depends on your particular team structure.\n\n\n
England (Hefce capital fund)\nAgain, have a look there may be folk close by who you can call upon.\n\nThere are folk certainly in Wales who have worked on previous xcri- mini projects, and it’s worth maybe doing a quick trawl of the JISC projects database to see if there’s anything that might be of use.\n\nJISC PIMS: https://pims.jisc.ac.uk/ JISC Programme information management system... there’s even an API, default xml response... \n\n\n\n
Lets look at that output requirement again: \n...as a minimum, create a system-generated course advertising feed in XCRI CAP 1.2 format with a COOL URI for online, distance, CPD, some projects are doing ALL courses.\n\nxcri-cap is an xml representation of course advertising information\ncore elements - (4)\nCommon elements, common descriptive elements, \nspecific elements used by other elements such as <start> and <end>\n\n5.3 Common Elements\n5.3.1 the <contributor> element\n5.3.2 the <description> element\n5.3.3 the <identifier> element\n5.3.4 the <title> element\n5.3.5 the <subject> element\n5.3.6 the <type> element\n5.3.7 the <url> element\n5.3.8 the <image> element\n\n5.4 Common Descriptive Elements\n5.4.1 the <abstract> element\n5.4.2 the <applicationProcedure> element\n5.4.3 the <assessment> element\n5.4.4 the <learningOutcome> element\n5.4.5 the <objective> element\n5.4.6 the <prerequisite> element\n5.4.7 the <regulations> element\n\n5.5 Elements used in the provider element\n5.5.1 the <location> element\n\n5.6 Elements used in the course element\n5.6.1 the <qualification> element\n5.6.2 the <credit> element\n\n5.7 Elements used in the qualification element\n5.7.1 the <abbr> element abbreviated form of the title of the qualification\n5.7.2 the <educationLevel> element\n5.7.3 the <awardedBy> element\n5.7.4 the <accreditedBy> element\n\n5.8 Elements used in the presentation element\n5.8.1 the <start> element\n5.8.2 the <end> element\n5.8.3 the <duration> element\n5.8.4 the <applyFrom> element\n5.8.5 the <applyUntil> element\n5.8.6 the <applyTo> element\n5.8.7 the <engagement> element\n5.8.8 the <studyMode> element\n5.8.9 the <attendanceMode> element\n5.8.10 the <attendancePattern> element\n5.8.11 the <languageOfInstruction> element\n5.8.12 the <languageOfAssessment> element\n5.8.13 the <places> element\n5.8.14 the <cost> element\n5.8.15 the <age> element\n5.8.16 the <venue> element\n\n\n
http://www.xcri.org/wiki/index.php/XCRI_CAP_1.2 becoming BS8581- conformant profile of BS EN 15982 (MLO)\n\nhttp://www.xcri.org/wiki/index.php/XCRI_Feeds\n\nhttp://www.xcri.co.uk/data-definitions-and-vocabulary-framework.html\n\nwychwolf.com/moodle/wychwolf-moodle.xml\n\nlook at this doc:\nhttp://www.xcri.co.uk/technical-implementation/272-sample-xcri-cap-12-instance-file-for-the-open-university.html\n\n\n\n
The aim of the #coursedata programme is that institutions should review and streamline their processes for course data generation, and maintenance. To exemplify this each institution should include plans to generate an XCRI-CAP 1.2 feed with a COOL URI.(http://www.w3.org/TR/cooluris/)\nTo facilitate the ease of discovery the feed should be placed at one of the following publicly accessible locations:\ndata.foo.ac.uk/courses.xml \nfoo.ac.uk/data/courses.xml \nfoo.ac.uk/courses.xml \nUseful Information on institutional URIs was collected in the Lincoln University Linking You Toolkit: http://lncn.eu/toolkit.\nPlease note the advice around how to mint the above URIs and then redirect them to the current URLs is a plausible method that can be used, however careful consideration should be made for the long term maintenance of these URLs.\nIf there is a better "more cool" logic for a different URI syntax, or sound reasons for not using the format this should be discussed with the JISC Programme Manager. Please consult the Lincoln You toolkit or project team for further guidance\n
Unless there is a compelling reasons not to, which is agreed with the JISC Programme manager, the XCRI-CAP feed should include an open licence outlining the permitted use of the file, it is suggested that the OGL is used.\nLicensing of XCRI-CAP feeds\n1It is a principle of XCRI-CAP feeds produced under the Course Data Programme that the data should be freely available to any aggregator or other user, organisation or individual to copy, re-distribute, share, adapt and exploit commercially or otherwise. This document recommends that all such feeds are explicitly licensed under an Open Government Licence (OGL). This licence grants to the user a worldwide, royalty-free, perpetual, non-exclusive licence to use the information, while providing for acknowledgement of the source of the information. This licence contains no warranty or liability on the provider, and importantly also includes specific non-endorsement clauses. The OGL licence is similar to a Creative Commons licence, but attribution is only needed if the copyright holder makes it a requirement. Where multiple providers are involved, an optional generic statement that 'public sector information' is included, rather than a specific attribution, can be used.\n2It is important that data publishers are familiar with the terms of the OGL for the avoidance of doubt about how the information may be used and the constraints placed on any user. The JISC sponsored document &#x201C;Licensing Open data: A Practical Guide&#x201D; June 2011 provides a sound overview of the licence landscape.\n3The following information about the licence attached to the data should be included in the description element of the catalog element:\nName of the licence, for example &#x2018;Open Government Licence (OGL)&#x2019;\nVersion number of the licence\nOwner of the licence, for example &#x2018;University of Test&#x2019;\nhttp://www.nationalarchives.gov.uk/doc/open-government-licence/\n http://discovery.ac.uk/files/pdf/Licensing_Open_Data_A_Practical_Guide.pdf \n
\n
use the sample OU file, copy and paste into the validator window:\nhttp://www.xcri.co.uk/technical-implementation/272-sample-xcri-cap-12-instance-file-for-the-open-university.html\n\n
An aggregator that manages feeds, the SOLR index can be interrogated by an API, and has SDKs for PHP, Java and such like. will look at these later today.\n\n
\n\n\n\n\n\n
\n
\n
\n
\n
More funds... for interesting ideas.\n
\n
hand out photocopies of iphone outline.\n\nSearch screen... and results screen...\n\nwhat they build will be made available for re-purposing \n