mummies on rails

16
Mummies On Rails A system for recoding mummy data using a modern development framework. Ahmad Alam, Ian Dunlop, Robert Stevens, Andrew Brass (Comp. Sci.) Jenefer Cockitt, Rosalie David, Ryan Metcalfe (KNH) Bio-Health Informatics Group

Upload: ahmad-alam

Post on 17-Jan-2015

102 views

Category:

Technology


2 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Mummies on rails

Mummies On Rails

A system for recoding mummy data using a modern development framework.

Ahmad Alam, Ian Dunlop, Robert Stevens, Andrew Brass (Comp. Sci.)Jenefer Cockitt, Rosalie David, Ryan Metcalfe (KNH)

Bio-Health Informatics Group

Page 2: Mummies on rails

Objective:

•Develop a system for recoding comprehensive mummy data

•The system would be on the World Wide Web – hence sharable

•Use of a modern framework –Ruby on Rails

Page 3: Mummies on rails

Why document electronically?

•Access being limited

•Ageing Edwardian Records

•Difficult to analyse on paper

•Very difficult to share

Page 4: Mummies on rails

The primary dataset

•Dakhleh Mummy Records Selected

•Best example that could be found

•Extremely detailed 13 pages long

•Unique and cannot be re-produced

Page 5: Mummies on rails
Page 6: Mummies on rails

• Ruby on Rails selected as development framework – Twitter runs on it

• Contemporary evolving framework

• Based on Model–View-Controller approach

• Drives :-• Reusability – Code re-use• Modularity• Modification• Maintainability

Page 7: Mummies on rails
Page 8: Mummies on rails

• Rails, database agnostic

• Manages own schema and model

• Backend database selection : MySQL

• Open source

• Most widely used (hence best supported)

• Scalable

Page 9: Mummies on rails

MEPR•Introducing:

Mummy Electronic Patient Record

•Built using Rails ‘re-use’ philosophy on :-

• Active Admin – Versapay runs on it• Formtastic• Devise• Inherited Resources

Page 10: Mummies on rails
Page 11: Mummies on rails

Mepr•Benefits:

•Filtered Searches possible, based on multiple criterion

•Extensible/Modifiable, with relative ease

•Encourages a re-think of the meta-data being recorded

•Increased longevity – easy to store backups on media and ‘cloud’

Page 12: Mummies on rails
Page 13: Mummies on rails

Evolving Mepr

•Improving record structure through feedback from archaeologists

•Improving the query engine to allow for better ‘reasoning’

•Holy grail : a working Ontology based system to achieve better data integration using semantic-web methodologies

Page 14: Mummies on rails

Challenges

•Ontologies: not yet main stream, performance issues, languages still developing, i.e. OWL, Sparqle.

•Open data: too many data ‘silos’ e.g. Outlook (Hotmail), Google, facebook, Amazon

•XML for formalising data – some success, Microsoft Office.

Page 15: Mummies on rails

Near term Mepr development

•Project to be Open Sourced shortly

•To be placed on a GitHub repository

•Will enable other programmers to work in collaboration on the project

•Possible inclusion of other mummified records, i.e. non-Egyptian

Page 16: Mummies on rails

Mepr

•Available right now:-

http://mepr.herokuapp.com/admin/[email protected] (password:password)

•Current development version:-

http://heroku.cs.man.ac.uk:3000/admin/login

•Contact [email protected]