Powered by OPF
OPF WIKI STATIC ARCHIVE
2,681 pages · 153 spaces · 776 tags · 4,025 history records · 96.2% of the original wiki recovered
Archived copy. This page was recovered from the Internet Archive snapshot of /display/SPR/SPRUCE Mashup Leeds - Programme, 30th April - 2nd May 2013 taken on 2012-12-17. The original wiki at wiki.opf-labs.org is being decommissioned.

SPRUCE Mashup Leeds - Programme, 30th April - 2nd May 2013

Added by Paul Wheatley · last edited by Paul Wheatley · on Dec 14, 2012 (view change)

Please note: all attendees must be present for all sessions!

Tue 30/4 
 Time
Facilitator Practitioner sessions Developer sessions
1200:1230 PW Welcome! Get set up, activate wifi, eat some lunch.
Plenary session
1230:1250 PW Intro to SPRUCE and SPRUCE Mashups, and the wiki
Plenary session
1250:1300 CW, PW, MdR Example results from a previous mashup event, and the SPRUCE Mashup Manifesto
Plenary session
1300:1400 EF Practitioners lightning talks: describe their collection(s) and issues (2 minutes each)
Developers lightning talks: interests, technologies and experience (2 minutes each)

Outcome: Everyone knows who everyone else is. We have enough information to team up attendees.
Plenary session
1400:1430 MdR + EF Presentation and discussion: Preserving Social Media  
1430:1445   Coffee Break  
1445:1530 PW + CW Introduce Practitioners to Developers. In small groups brainstorm preservation issues with each dataset and select the priority issue to address.
One flipchart sheet per dataset, list the issues, select the priority issue. Discuss possible solutions if there's time.
Outcome: Practitioners and Developers decide what they will be working on during the mashup
Plenary session
1530:1600 PW Report back on brainstorm: lightning talks from the groups
Plenary session
1600:1630 PW Practitioners: Write up Collections and Issues on the wiki
Create Dataset and Issue pages
Outcome: Today's progress on preservation Issues is captured
Brainstorm solutions (led by CW), and introduce Github
Outcome: Developers share ideas on how to solve issues
1630:1730 JD + EF + PW Benefits + objectives alignment session (and introduce Q&A) Hacking begins...
1730:1800 JD + EF + PW
Reporting back on benefits + objectives alignment Hacking
1800   Close  
1900:20:15   Drinks at the Town Hall Tavern which is here. The Town Hall Tavern is a 14 minute walk from Roomzzz, along Burley Road, towards Leeds City Centre.
 
2030   Dinner, Thai Aroy Dee which can be found here.  
Wed 1/5 
Time
Facilitator Practitioner sessions Developer sessions
0900:0945 PW             Welcome back!
Check point: Practioners and Developers share progress with each other
Plenary session
0945:1015 PW Practitioner and Developer partners/groups report back on issues/solutions progress so far Hacking
1015:1115 JD + EF
Stakeholder analysis
Outcome: Stakeholders are identified, analysed and recorded on the wiki
Hacking
1115:1145 JD + EF Reporting back on stakeholder analysis Hacking
1145:1230 PW Peer review of Dataset and Issue pages in pairs (practitioners only)
Wiki pages are reviewed against these criteria, and improvements made where necessary
Outcome: Dataset and Issue pages are refined and updated
Hacking
1230:1315   Lunch  
1315:1330 PW Check point: Practioners and Developers share progress with each other Plenary session
1330:1430 EF + JD Skills gap analysis (what does my team/organisation lack in order to achieve solutions?)
Outcome: Required skills and resources identified by practitioners and recorded
Hacking
1430:1500 EF + JD Reporting back on skills gap analysis
Hacking
1500:1515   Coffee break  
1515:1545 PW Dev review of Issue pages to ensure requirements successfully captured
Issue pages are reviewed by a different dev in conjunction with the Issue owner, and improvements made where necessary (see these hints).
Outcome: Issue pages are honed and devs/pracs learn from interactions
Plenary session
1545:1600 PW Check point: Practitioners and Developers share progress with each other
Outcome: Continue write up on wiki & prepare to give progress report to the group
Plenary session
1600:1645 PW Practitioner and Developer partners/groups report back on progress so far Plenary session
1645:1700 PW Stack Exchange Question and Answer session
Outcome: Everyone has asked a question on Stack Exchange. Some will have answered questions!
Plenary session
1700:2100
  Formal sessions close. Room still available for hacking or other work for anyone who would like to continue working. Facilitators available for further informal  Q&A/discussion as required. Dinner and drinks will be provided in the main room at 1830.
 
Thur 2/5  
Time
Facilitator Practitioner sessions Developer sessions
0900:0920                     Welcome back and Coffee!                                                              
0920:0930 PW Agenda for the day: reminder on what everyone has to have ready by when: wiki write ups, code commits, etc Plenary session
0930:0945 PW
Check point: Practioners and Developers share progress with each other Plenary session
0945:1045 
EF + JD Pulling it all together: The Elevator Pitch
Outcome: Practitioners review business case work so far, summarise it in a one minute Elevator Pitch, and practice delivering it
 
10:45:1100 EF + JD Deliver the Elevator Pitches (part 1) Hacking
1100:1115   Coffee break  
1115:1145 EF + JD Deliver the Elevator Pitches (continued)
Hacking
1145:1230 PW + Crowd sourcing digital preservation Hacking
1230:1315   Lunch  
1315:1345 PW
Check point and finishing off: Practioners and Developers share progress with each other, do any final write ups and prep their presentations
Outcome: Everything we've learnt is written up, code is committed, presentations are ready
Plenary session
1345:1445 PW Practitioner and Developer pairs present results to the group
Plenary session
1445:1500 PW Wrap up and what comes next: Awards, Business Case and other SPRUCE stuff
Plenary session
1500:1515   Coffee and voting on best write up and developer solution Plenary session
1515:1600
Presentation of awards and event evaluation session Plenary session
1600   Close