DASWorkshop2011/day3/actionplan

From BioDAS
Jump to: navigation, search

Action plan

ACTION WHO By WHEN STATUS
Security (authentication)
HTTP authentication: Server implementation: Proserver AJ April 2011 DONE (needs testing)
HTTP authentication: Server implementation: MyDas LJG & GAS April 2011 In progress
HTTP authentication: Client implementation: Dalliance TAD May 2011 DONE
HTTP authentication: Client implementation: IGB GH May 2011 In progress
HTTP authentication: Client implementation: Jalview JP June 2011 In progress
Centralized authentication (registry): Specification GAS & JW November 2011 In progress
Centralized authentication (registry): Server implementation: Proserver AJ February 2012 In progress
Centralized authentication (registry): Server implementation: MyDas GAS February 2012 In progress
Centralized authentication (registry): Client implementation: Dasty RJ March 2012 In progress
Alternative Content: one capability using “formats” command
Add specification in BioDAS extension page RCJ April 5th 2011 In progress
Demo: client pointing to static file TAD April 5th 2011 In progress
Registry implemention JW June 2011 In progress
Server implemention: Proserver AJ June 2011 In progress
Server implemention: MyDas LJG & GAS June 2011 In progress
Server implemention: Genoviz? & Trellis GH June 2011 In progress
Pagination for features command
Server implementation: MyDas LJG & GAS April 2011 DONE
Server implementation: Proserver AJ April 2011 DONE
Strategy for Java client library
Stay with JDAS incorporating functionality Dasobert. RCJ, LW, JP, SK, GAS June 2011 In progress
Incompatibility in DAS
For the list of priorities identify provide examples of valid sources implementing all commands JW June 2011 In progress
Report primary error JW June 2011 In progress
Allow no limits on what you can register JW June 2011 In progress
Genomic alignments
Disscuss proposal in the DAS mailing list TAD March 2011 In progress
Binning strategy
Disscuss proposal in the DAS mailing list TAD March 2011 In progress
Next feature
Server implementation: Dazzle TAD April 2011 In progress
Client implementation: Dalliance TAD April 2011 DONE (on nav branch. Should be in release 0.7)
Linking features to rich content
Client implementation: Dalliance TAD June 2011 (subject to server impl.) In progress
Server implementation: Proserver AJ June 2011 In progress
Source demo JW June 2011 In progress
Graphical conventions on feature types
Explore options LJG April 2011 In progress