1 / 15

JISC DEVELOPMENT PROGRAMMES

JISC DEVELOPMENT PROGRAMMES. Development Programmes. Information Environment Learning Environment Building and linking systems for the delivery of learning & teaching Middleware Networking Preservation Research Environment JCALT Programme. Learning Environment.

stephanie-snider
Download Presentation

JISC DEVELOPMENT PROGRAMMES

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. JISC DEVELOPMENT PROGRAMMES

  2. Development Programmes • Information Environment • Learning Environment • Building and linking systems for the delivery of learning & teaching • Middleware • Networking • Preservation • Research Environment • JCALTProgramme

  3. Learning Environment • Managed Learning Environments for Lifelong Learning: Building MLEs across FE and HE • Facilitating the seamless movement of learners across sectors and institutions • 2 large scale projects (NIIMLE and Shell) • Supporting studies surveying MLE activity and building learner profiles • Managed Learning Environments for Lifelong Learning 2 • Build on the outcome of the two current projects • Make initial explorations of the wider aspects of linking MLEs

  4. Learning Environment • Scotland, Wales and Northern Ireland (SWaNI) • More later ….. • Building MLEs in HE • Demonstrating the potential of MLEs to support learning and teaching • Linking Digital Libraries with Virtual Learning Environments (DiVLE) • 10 projects • Pedagogical and organisational issues • Technical exploration and curriculum focussed pilots

  5. Update on SWaNI • MIS-VLE-MIS (Enterprise) • 4 projects • 3 VLE vendors • Granada Learnwise • Teknical • WebCT • 4 MIS vendors • Capita Dita • FD Learning • Microcompass • SITS

  6. Update on SWaNI • LIP (Learner Information Profile) • 2 projects • Scottish UFI and SITS • UFI and Teknical • Content interop and packaging • 1 project (large consortium) • Intrallect (digital repository) • FD • Learnwise • Teknical • Digital Brain • producers of some of the best NLN materials

  7. What’s being tested with Enterprise spec? • TEKNICAL • Capita Dita • Sits • FD • Granada Learnwise • Capita Dita • Microcompass • WebCT • Capita Dita

  8. What’s being tested with LIP spec? • Personal Development Planning • Updating the lifelong learning record • Commonality with the NIIMLE and Shell projects • Integration with SUfI and UfI • Allowing for complete learner log • Vertical MLE • Cross institution • Cross sector

  9. How? • Transport mechanism • IMS have recommended the use of SOAP with attachments • Not all vendors are ready for this • Application Profiles • Need to ensure that the agreed profiles are appropriate for the different sectors • Regional FE extensions where necessary

  10. Where we’re up to • MIS/VLE • Agreed the application profiles • What we’re sending • In what format • Currently testing the app profiles • Agreed the transport mechanism • A number of different models • For testing purposes • All vendors committed to SOAP in future

  11. Where we’re up to • Personal Development Planning • Ongoing process • Working with CRA • Content • Currently testing and reporting • Consortium have secured funding to continue this work

  12. And the content? • Content packaging and metadata • Content produced by 5 different institutions in different formats and within different VLEs • Simple learning objects • Export/Import from vle to vle • Test results • Modify • Report • Export/Import from digital repository • Effectiveness of consortium approach

  13. Issues arising • The projects’ perspective • Time • Projects too short – too much lead time • Money • There’s never enough  • Working with multiple vendors • Time consuming - herding cats  • Strengthened relationships • How was it for them? • Underestimated the complexity • Use to kick start further work at institutional level • Raised senior management awareness

  14. Issues arising • The JISC perspective • Need to better plan the timing of projects • Need to work with vendor partners at planning stage • Differences between FE and HE • In terms of capacity for such projects • In terms of expectations of projects • Horse and cart ……..

  15. CART – HORSE - CART • Why are you doing this? • For the experience • Absolutely valid • As long as the experience leads to recognition of the need to change • A perceived need • Technology driving the change • Need to consider what you want to do and then consider the available AND appropriate technology/ies • Institutional buy-in • Business process re-engineering involves absolutely everyone • Top down and bottom up

More Related