Meeting with James 30th march - hamstar/Braincase GitHub Wiki

Agenda

Get some basic requirements.

Talk about scope in proposal
- is quite large
- defined chunks of functionality
- discussed potential priorities with client
Deliverables
- reqs
- architecture
- github
- sufficient artifacts to allow future dev
- allow to add further functionality
- acceptance tests
Deployment options
- virtual appliance
- LAMP
- RPM
- online installer
it should act as a mind expanding device
- follows academic throughout career
- hold data that has real value to the academic
James recommended using the rational unified process

Screw FTP
More fine grained access control
- per page access
- group and individual access
Revisions of wiki pages (idempotence)
No chance to lose more that one days work (backup)
- automatic backups!
- to cloud (dropbox/amazon s3 etc)
- to fileshare
Portable
- application (open source with deployment options)
- data (export/import of data)
Export to LaTeX
Export to BibTex
Canonical heirarchy
- child pages or browse history
- breadcrumbs
Publication Database (to store publication info/references)
- allow addition of notes to publication entries
- references are cit-able in wiki pages
- PDF storage
Versioned repository for each user of the system
- holds files for the user
Multiuser
Upload images
User centric front page
Global front page