Final Developer Workshop Ideas

Page to capture ideas of things that could be worked on at the Final Developer Workshop.

Demonstrations

Ideas for demos at DL event, the final review, and for the Demonstration WP.

• Identify who will be attending/presenting demos at DL conference
• Prepare information/advice for creating demos (in advance)
• Detail the demo story to be told
  • What is the workflow to be used?
  • What are the steps?
  • What are the main points to disseminate?
• DL Conference dissemination
  • Leaflets?
  • stickers?
  •  
• Posters?
  • Unified look?
  • Use at review
• Overlap with Demonstration WP?
  • Web based demos running locally might be useful
  • Standardised powerpoints for tools?

End-2-end demo ideas to show...

At the DL conference there will be 3 tables for showing demonstrations. The suggested plan is to use these 3 to show different things:

• Integration - A round trip demo from identifying a preservation risk, planning, through to execution of the plan, storing the results and re-evaluating
• Scalable execution - show how the plan from the round-trip demo can be executed at scale
• Selection of tools - show what tools SCAPE has worked on and that can be used to build up preservation plans

...Integration:

Demo: PW Lifecycle/Roundtrip: Scout (monitor source, notification)-> Plato planning -> Plan in DOR -> execute on Taverna Server -> store results -> re-assess.

Notes:

• Identify what needs doing to complete this roundtrip?
  • Taverna Server (Enactment workflow status?)
  • Link back to Scout (for example, report API feedback)
• Possibility to make this a standalone demo/without internet?
  • Vagrant Machines?

Questions/Considerations:

1.   Can we do this demo without an internet connection?
   

...Scalable Execution:

This demo will show how a Preservation Plan can be executed at scale. To assist understanding across the demos, the plan should be the same (i.e. do the same thing) as that used for the Integration demo.

Demo: Same Plan translated to Pig Script -> execute on Hadoop platform (eventually wrapping tools with ToMaR?)

Questions/Considerations:

1. How will a scalable platform be demonstrated at the DL conference? What if there's no (reliable) internet connection?

...Tools:

Small part of workflow. Variety of tools.

• Identify tools to show (at DL, at EC review)
  • Choose by SCAPE leaflets?
• Flesh out demos
  • What are main points to demo?
  • How can these be shown clearly?
  • What are the demo steps?
• Can some be presented as posters instead?

Ideas:

• KrakeN
• Component generation/register in Catalogue -> notification via Scout Catalogue Adaptor?
• Medical Data Scenario (tools)?
• Policy?
  • Perhaps as a poster

Demo Selection:

At DL Conference: Pagelyzer, Matchbox, xCorrSound, Jpylyzer

At EC Review: Pagelyzer

e-Packs

Electronic dissemination material, could be downloadable or distributed on pre-loaded USB sticks

Content ideas

• Preload with VMs/tools
• Powerpoints about the tools (standardised template)

Sustainability, Integration & Productization

Microsites/Readme Templates

• Identify what is missing/left to complete for each tool and create wall chart task lists [in advance]
• Intro on adaptations to templates and why
• Complete technical/remaining details in readme's as per task lists

Other User documentation?

Demo Sites

• Documentation and Work Examples
  • Explain what tool does
  • Host test data
  • Provide a worked example
• Rebranding demo sites

• Use these for conference/review demos?
  • Demo site can run on a standalone machine
  • Test data would need to be hosted alongside the demo

Executable Plan Integration

• What can we do to help executable plan to Hadoop conversion? documentation / best practice
  • Taverna->Pig Examples

Project Housekeeping

• Archiving github projects
  • Create a list of projects [in advance]
  • Identify status of each project
  • Discuss and work out what to do
• Public API Documentation
  • Status of all APIs?[API Status]
  • Update API Github page
• Fixes
• Other Project Artefacts

Component Generation

• Component Generation Workshop/Tutorial

Tool Testing/Bug Detection

• Identifying bugs/tasks that need working on

Packaging

• apt packages & apt repo for tools
• Man Files (for packaging)
  • Work out best way to create Man files [in advance]
  • Creating Man files for cmd line tools, e.g. xcorrSound, etc.

VM’s

• Vagrant demonstrators
• Getting Started guides
• examples

Prototypes

Scout Adaptors

• Component Catalogue
• Github projects (open source preservation software)
• PRONOM signature files

Platform integration tool prototypes? (help manual integration aspects)

• List of tool dependencies in Component Catalogue?

C3PO

• SRU-query for content profiles in Preservation Action Plans

Data Publication Platform

• DPP prototype using testbed evaluation data
  • Discuss with Rune

Other

• Integration Roundup (what’s done? status? how to show it?)
•  
• WP23 (Data Center Testbed) meeting: discuss MS102, MS100, MS94