A Conference to Launch the Discovery Programme
Wellcome Collection
Thursday, May 26, 2011
AGENDA
10.00 Refreshments & Registration
10.30 Discovery - Introduction by Prof David Baker, Deputy Chair JISC Board
Introducing the Discovery programme and its purpose to create a metadata ecology for UK education and research
Part 1: The Demand Side – User Expectations in teaching, learning and research
Key question: What do UK educators and researchers need from content collections and services in order to excel and push new boundaries in discovery? What are the motivations arising for Libraries, Archives, Museums and their partners?
10.50 Keynote 1 (filmed) – Dr Stuart Lee, Director, Computing Systems and Services, at Oxford University's Computing Services
11.10 Keynote 2 – Prof Peter Murray-Rust, Reader in the Unilever Centre for Molecular Science Informatics, Cambridge University
11.30 The Research Conversation (whole conference debate)
11.50 Coffee
12.10 Keynote 3 – Drew Whitworth, Programme Director, MA: Digital Technologies, Communication and Education, University of Manchester
12.30 The Teaching & Learning Conversation (whole conference debate)
12.50 Summing up – David Baker
13.00 Lunch
During lunch there will be a display of the eight RDTF Discovery projects in the lunch area with representatives on hand to field queries.
Part 2: The Supply Side – Opportunities to Expand Access and Visibility
Key question: What are practical next steps that Libraries, Archives and Museums can take to make their collections more available, enhance audiences and add value? What are the immediate challenges, the early wins and the available tools?
The afternoon sessions will focus on debate and discussion with the audience rather than presentations – speakers below will introduce themes and facilitate discussion
13.45 Welcome back & intro to the afternoon – Nick Poole, CEO of Collections Trust
14.00 The Art of the Possible: Special Collections – Veronica Adamson, Director, Glenaffric
Opportunities around Special Collections identified in a series of interviews
14.15 The Art of the Possible: Aggregation Services – Peter Burnhill, Director of EDINA
Aggregation as a tactic for improving resource discovery
14.30 Tea and Action Planning: Special Collections & Aggregation Services (whole conference activity)
Tea break during which delegates will be asked to form small groups to discuss next steps with the aim of producing two suggested actions per group to feed back into a plenary session after 20 minutes. Suggestions will be posted up onto a projected timeline.
15.05 The Big Event: A catalyst for collaboration – Nick Poole
Balloon debate format to select potential option for a collaboration theme
Discussion exploring how the selected option might act as a catalyst for collaboration
15.40 Licensing: Announcement of a new agreement – David Baker
15.50 Summing Up – David Baker
16.00 Conference Close
Coordinated by SLIC, MMITS, SCURL, SALCTG & the JISC RSC’s (Scotland)
Playfair Library, Edinburgh
21 October 2010
Live-notes taken by guest contributor Nicola Garwood, Eduserv
Presentation One:
Books are going e!
Catherine Nicholson, Head of Learning Resources, Glasgow School of Art
Presentation Two:
The Digital Landscape: You, me and us!
Caren Milloy, Head of Projects, JISC Collections
Presentation Three:
The Google Generation, Professor David Nicholas, Department of Information Studies, UCL
Presentation Four:
The Springer / SHEDL ebooks project
Helen Ellis, Licensing Manager, Springer
Presentation Five:
Mobile Learning
Jon Trinder, Glasgow University
Presentation Six:
LoveBytes: Digital Literacy
Debbie Boden, Director of Library Services, Glasgow Caledonia University
Presentation Seven:
Bloomsbury Public Library Online
Jonathan Davidson, Area Manager, Bloomsbury
Presentation Eight:
Digital Economy Act
Janice McFarlane, Head of Partnerships, National Library of Scotland
Presentation Nine:
Swets Showcase
Tamsyn Wymer, Swets
Presentation 10:
Acquisitions, but not as we know it
Elize Rowan, Acquisitions Manager, University of Edinburgh
(Note: that Nicola had to leave at this point so tail end of the presentation/day was missed).
JIBS-Eduserv Seminar
School of Oriental and African Studies, University of London
16 June 2010
Aeonian Training Centre, London
25 November 2009
University of London Student Union
October 2009
Brief notes on the first three talks at the CETIS Widgetmeetup this morning. Note that this meeting was not live-blogged due to lack of a working wifi network at the start of the meeting.
The purpose of this CETIS activity is to:
Apache Software Foundation
An overview of the ASF by Ross Gardler (OSS Watch)
An Apache Incubator is a place for new projects, each of which must be championed by a member and have 3 mentors.
The incubator leads to a working community (and possibly some working code though the community is seen as much more important).
Incubators can last anywhere between 3 months to 18 months.
At the end of the incubator, IP must be in a state where it is able to be managed properly. That means that when industry gets involved in an ASF project their risks are minimised.
Typical activity story for an ASF member goes something like this...
Note that all committers can veto code changes by any other committer. Being a committer means that the contribution workflow is smoother but it doesn't really give you any additional rights/ownership.
The whole ASF operation runs for something like $180,000(US) per year.
Lots of the projects are based on standards - their aim is to provider working implementations of standards.
ASF projects are typically quite visible - which is one advantage of going down that route.
Note that new projects can join existing projects as a sub-project of an existing project (but a lightweight incubation period is still required).
Overall ethos is that the community is more important than the code - "community over code"
Wookie and Widgets
A presentation about the Wookie project by Scott Wilson of CETIS.
Scott started by saying why the Wookie project had chosen to implement thru an ASF project.
Wookie is not an acronym
Wookie is an ASF Incubator project.
Wookie is a Java Servlet running in Tomcat or Jetty and offering:
The REST API allows you to get a list of available widgets, to instantiate a new widget instance and to associate participants with that instance.
Typical lifecycle goes like this...
Plugins are available for LAMS, Moodle, Wordpress and ELGG 1.0 (though the latter two need more work).
A plugin is a bit of code that implements the Wookie lifecycle above.
What widget APIs are supported?
The W3C Widget Object is the default but at the point a new widget is instantiated you can also ask for optional other APIs to be supported - e.g. the Google Wave Gadget API
There has been some integartion with Shindig (which is another ASF incubator for OpenSocial).
Wookie handles getPref/setPref but doesn't handle the Shindig data interface.
Intention to work on inter-widget comms and more support for Bondi/DAP APIs.
What does a widget look like?
Four things:
All of this gets zipped together and the file extension is changed to .wgt.
That's it!
Widget instances can share data but only when they have been instantiated from the same location.
Business model for hosting Wookie widgets not clear yet. Will there be a UK widget 'app' store? Or an EU one?
How do you find widgets?
Widget config.xml file gives you title, description, icon , category (tag) and author. Can browser/search based on these.
Widgets can interact with external services using HTTP (e.g. Ajax) but must do so via a proxy hosted at the Wookie server (which can maintain a white list of allowed services). This prevents widgets opening abitrary connections to remote services.
For more info [email protected]
Google Wave and widgets
Wilbert Kraan (CETIS) gave an overview of Google Wave and the way it handles widgets...
Widgets were originally designed to do one thing for one user - they were typically accessed thru the desktop of a personal computer.
Wookie has changed that - widgets now do one thing for many users - they are typically social in some way.
Google Gadget API provides an alternative platform for doing this kind of thing.
Can fairly easily port Google Wave gadgets into Wookie.
The Wave platform is significantly more complex than Wookie - however, that doesn't necessarkily make it better.
I stopped taking notes when the phrase "wiki widget for wookie and wave" was used. Sorry :-(
Lakeside Centre, Aston University
21 September 2009
A series of live-blogs from meetings about the Web, cloud infrastructure, linked data, big data, open access, digital libraries, metadata, learning, research, government, online identity, access management and anything else that takes our fancy by by Pete Johnston and Andy Powell.
All views expressed here are personal.
Recent Comments