Discussions

Donellen lab wiki Requirements

1. Steve Donnellan & team have a whole heap of needs mostly arising from running a service across multiple institutions with material coming from many sources.
2. As such, they are a microcosm of the greater taxonomic community in Australia & a good test bed for the things that we wish to attempt.
3. Requirements (which they believe can be done by the wiki) are
   1. Collaborative writing. (currently done through Google doc tho' they found limitations in this file size and edits).
   2. sharing copyright protected material. (Access needs to be controlled).
   3. distributing images (currently done through morphobank. May be large files. possibly sort.)
   4. managing data (currently done adhoc through excel on a not so common fileshare. Also need to unambigiuosly identify specimens and samples.)
   5. managing specimens (currently done adhoc through excel on a not so common fileshare)
   6. Annotation of images and data (they have no current solution)
   7. distribution of files (across firewalls & distance. They have no current solution)
   8. distance collaboration (video conferences +)

GJR will

i) look into how the wiki can be adapted to meet these needs. They have a lot to be gained from centralizing onto one system. As well economies of scale and practice and new capabilities will emerge. On the face of it, I think some quite minor enhancements to the wiki will give them what they need.

ii) set up kyle as wiki master

iii) Design a populate a wiki for acad along the lines of the one used by Andy Austin.

iv) This design will be a useful template for other taxonomic wiki's in trin and beyond.

v) Subject to a reality check with Jim, Design and Lab resolver service.

vi) perhaps set up a lsid resolution service for acad (with appropiate plans to move custody of such a system onto ACAD.. taxonomy.org as a lsid resolver?).

ACAD collaboration space

Possible Design for prototype

• restricted access (password controlled)
• evo for Steve Donellan
• file sharing using khoi's php file lister.
• dna sequences
• image sharing ( and annotation)
• metadata into images.
• multiple images of type specimens (morphospace)
• ?voucher database?
• ?loans?
• copyright material (e.g pdf's ) on a theme
• templates
• reference list linked to pdf's (bibtext)?
• blogs
  
  Views crafted for different lab members.
• post docs
• pHd's
• Managers

Kyle Armstrong on Laboratory Information Management Requirements

Version 1.(Lab accession resolver)

gaols

• to 'allow ownership and provenance to be revealed as required'.

1. lsid domain for adelaide?
2. lsid resolver / creator
3. ACAD number.

1. Gallery installation of trin wiki serevr
2. file browser install (php Khoi) or twiki addon
3. mysql <=> twiki
4. LSID Resolver? (Based on institutions Accession no.'s or other uids)

Micro Lims. (Lab accession resolver)

1. Project id; Lsid;
2. Specimen: bar code/accession; project; lsid;
3. Sample: Lab process; accession; acad no, project; result
4. Result;
5. templates for excel or other results files attached as blobs

• acad no's are uid easily translated into lsids
• ditto for accession no's. though 1 degree of abstraction req'd
• possible hosting of lab resolver lsid service on taxonomy.org.au?
• Portability of Applications is an important consideration - easily dealt with by use of institution independant domain names.

acad no's are uid easily translated into lsids

ditto for accession no's. though 1 degree of abstraction req'd

possible hosting of lab resolver lsid service on taxonomy.org.au?

Andy Austin. re PBI wiki & co

Andy Austin's wiki model - good model for wiki structure.
Elements that Andy thinks is valuable

• notification of new entries in sidebar
• thematics and specific titles - crafted for taxonomy
• images (adove image libraries and co - simple image keys)
• Database links (?lims?)
• forums & Blogs

- MargaretC - 28 Oct 2008