AQuA - The Leeds Mashup

Skip to end of metadata
Go to start of metadata

Leeds Mashup Results

Collections, Issues, Contexts and Solutions: all the results from the AQuA Mashups

Leeds Mashup event evaluation

List of attendees

Where to put your Sshhh! bag photo

Some blog posts on the Leeds event from: Paul Wheatley (BL/AQuA/OPF) and Neil Grindley (JISC)

Group photo and misc photos http://www.facebook.com/media/set/fbx/?set=a.10150595988235204.679432.871415203&l=40bd0e1bc0

Photos of brainstorming notes http://www.facebook.com/media/set/fbx/?set=a.10150595985400204.679430.871415203&l=4e8a8c5bf0

#AQuAqa for project tweeting

Leeds Mashup Schedule

Day 1: Understanding the problem

  • 1030 - 1100 Refreshments available
  • 1100 - 1130 Introductions and scene setting
    • Welcome (Bo Middleton) - 2 mins
    • Practical stuff - rooms, toilets, fire safety, permissions to take photos, etc - 2 mins
    • Our goal and outline for the 3 days (Paul Wheatley) - 10 mins
    • Introductions (everyone) - 5 mins
    • AQuA work areas online
  • 1130 - 1215 Collections and QA challenges - lightning talks from collection owners on their collections and initial thoughts on challenges
  • 1215 - 1300 Lunch
  • 1300 - 1345 Problem scoping and solution brainstorming
    • Develop outlines/stories of problems/issues for each sample collection (capture one collection/set of problems per flipchart page). Work in institution groups
    • Develop a list of strategies for tackling the problems/issues (capture one collection and related solution per flipchart page). Brainstorm in mixed groups
  • 1345 - 1430 AQuA Speed Dating: Grab a nerd
    • "Problem market" : content people set out their problems, techies choose from the market!
  • 1430 - 1500 Break
  • 1500 - 1600 Initial AQuA tool/content mashups work
    • A few words on the AQuA approach (Andy Jackson)
    • Begin mashing...

Day 2: Developing the solutions

  • 0900 - 0915 Welcome back
    • Reminders on checking in code, content, problem outlines etc.
  • 0915 - 1200 (Break 1030 - 1100) Tool/content mashup session / Defining the problems with the content owners
    • Optional: Formalise the problem/issue/collection outlines we created on Day 1, using wiki template
    • Optional: Content owners: define the context to their content and problems. How do we turn prototypes into production tools/workflows? Capture on wiki template
  • 1200 - 1245 Lunch
  • 1245 - 1715 (Break 1500 - 1530) Tool/content mashup session with occasional lightning talks.
  • 1715 - 1730 End of day wrap up: Prep for tomorrow.
    • Start thinking about results, visualisations, demos and reporting back for evaluation.

Day 3: Evaluating the results

  • 0900 - 0915 Welcome back - wrapping up the AQuA Mashup
    • Outline where we want to be by 1500
    • Reminders on checking in code, content, problem outlines etc.
  • 0915 - 1100 Tool/content mashup session
    • Includes quick brainstorm for Neil Grindley
  • 1100 - 1130 Break
  • 1130 - 1200 Lightning talks: Cunning code and digitised disasters
  • 1200 - 1245 Lunch
  • 1245 - 1445 Evaluating our mashups: Content owner and peer review
    • Peer review between content owner / techie pairs (reviewing the results)
    • Reviewing the event - gather feedback for shaping the London event
  • 1445 - 1500 Wrap up
    • Thanks, what happens next (Mashup2 or AQuA Project wrapup), reminder to keep in touch via OPF site, thoughts about future work/projects
    • Group photo

Note that this is a proposed outline and is subject to change!

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Mar 28, 2011

    Some topics NANETH wants to bring along to the conference are:

    • OLE Objects – Characterisation, extraction and validation
    • PDF - Characterisation and validation
    • Wrappers – Dealing with problems in creating automated processes using existing tools
    • Tool registry and/or Drools Business Logic integration Platform (http://www.jboss.org/drools), to have more dynamic ways of creating automated processes.
    • AV material – We don’t talk about this too much, is relying on PrestoCentre only a good idea?

    We are looking forward to discuss these topics with you.