|
News 2008/05/28
| | | |
Conference call minutes: 2006-12-01 (incorporating 2006-11-20,24,27))
 

Attendees (aggregated over all days, alphabetised)

Tim Booth, Ryan Brinkman, Oliver Fiehn, Dawn Field, Jennifer Fostel, Graeme Grimes, Eugene Kolker, Ruth McNally, Norman Morrison, Don Robertson, Phillippe Rocca-Serra, Susanna-Assunta Sansone, Chris Taylor, Stefan Wiemann.

Minutes (summarised, reordered)
  • Update by Chris on activities to date, setting up telcons in the future
    • Positive discussion with NBT on MICheck paper, we should press on and get the paper back to them: NBT says the issue will be out in Feb / March or later, so there is a period in which we could still build the website and no significant change to paper except small tweaks; if we don't have the content by then, they would 'downgrade' it to a different category publication.
    • Brief discussion of the three recent papers in NBT 'critical' of standards ([1],[2],[3]).
    • Chris will soon be able to spend a lot more time on MICheck (essentially now an FTE).
    • Website should be more actively developed soon by Chris now that MIAPE paper has been resubmitted.
    • Website now has project registration form (excel and XML), list of registered projects, MIACA, MIRIAM, MIAPE, MIMix, GSC, MIAME/Env.
    • Telecons - suggested bi-weekly, a cluster now because of paper and feel out the situation - two in Dec.
       
  • Feedback on the reviews - what to do with the paper
    • Reviewed suggestions to date; make it very short; submit later; proceed.
    • Could take into account the recent NBT papers.
    • Resubmit by end of year, more or less as is, after some work on website.
       
  • Name change (MICheck is another project) - how about "MIChecklist"? Other suggestions?
    • Required because MICheck project already exists.
    • Alternatives include: MIcatalog, MIlog, MIchecklist (no, owned by a bank).
    • OBRA - Open Biological Reporting Anthology - I'd also prefer something like "OBRA template". Although MIMI is absolutely correct, it sounds weird.
    • MIBI Standards, or MIBI for short: Minimum Information for Biomedical Investigations. The "s" on standards I thought may be import to get the idea that this is not just one, but a collection - or better Biological - top contender - currently the front runner - on how about "Life Sciences"
    • MIgistry
    • MI Core Set
    • Final consensus - MIB*I - "MIBI" - to get around biological / biomedical - with Bio*
       
  • Registering projects with MIcheck - Excel template for MIMI ("Minimum Information about a Minimum Information") form available
    • XML schema available, but excel seems a more practical approach for now
    • Really need input from micheck community
    • Not really a standard per se, but a mechanism for MICheck to catalogue the checklists in a useful form - call it 'project registration instead' and don't make too big a deal of it
    • Defining MIMI is valuable - a project in itself
    • Issue of whether specifications should use 'must' and 'should' or 'may' and could', MIAPE tending more towards the former, what stance should MICheck take?
    • Checklists should be about science, developed and used by scientists
    • How prescriptive should we actually be? without an explicit level of detail, the data still can't be processed
    • 15 total extant projects 'registered' by intent through authorship on paper
      • (N.B. two additional documents listed in paper, but subsequently subsumed by CIMR [MIAMet, SMRS])
    • Should we set a deadline?
    • Need to consider how to manage a large list in the future (Chris looking at javascript for navigation according to categories)
    • PSI, GSC, and Env have been MIMI-in-Excel testers - any other group willing to give it a test run welcome!
       
  • The website (Chris to make a start, the group to advise?), what about a wiki? Mailing lists (communication and co-ordination)
    • As a priority, add a description of MIMI, the excel template - DONE
    • Yes, enough of a need for interaction in MICheck members to warrant a mailing list
    • Set up public wiki and two mailing lists (all, coordinators)
    • Static webpages and some kind of search facility over guidelines we have
    • List of coordinators and communities to go up in wiki
    • News to be added in a blog
    • Support for using the OBO (obo.sourceforge.net) site as a 'template' - list of checklists could be organized / browsed in a similar fashion (yes / no whether Foundry etc)
    • Bit of history (PSI meeting session), FAQ - who we are, how different from others, etc
    • Turn venn in header into a real example of overlap
    • Add meeting notes to website
    • By Dec 1, growing content available! positive feedback
       
  • Charter - promised in paper
    • Will start a draft this week (Ruth, Norman, Dawn to do a preliminary read through) - base on extracts from paper plus a bit more - a mission statement, what is our purpose, what do we hope from people who sign up; also more meaningful Foundry sign-up pledge
    • Primary community is really composed of the MIxxx coordinators
    • Any group can register a checklist without further commitment to MICheck
       
  • Linkages (relevant meetings, information to the web in the short-term)
    • No mode for inviting people not in a specific community but with general interest /expertise yet, could be useful
       
  • The scope of MICheck (Linkages between MIcheck, OBO/OBI, and FuGE; RSBI)
    • Some discussion that people have different ideas of the scope
    • Further discussion is needed
    • Good suggest to people 'best practice' is the use of GO, OBI, FuGE etc, but not as a 'must' more a should
    • MIcheck (content, checklist), OBI (ontology), and FuGE (syntax) is a useful construct
    • No a priori limit on scope (anytime of checklist to be initial investigations)
       
  • MICheck Foundry - future MICheck workshops (face-to-face meetings)
    • Yes, positive about the need for workshops
    • Susanna is putting in a BBSRC bid to fund workshops for multi-omic workshops - including one for MICheck (OBI, FuGE also)
    • Chris exploring potential funding routes with BBSRC T&R in support of their new data sharing policy (which promotes standards uptake)
    • Come up with a memorandum of understanding if others significantly change guidelines
    • Need future discussion of what the products of the Foundry will be
       
  • Wrap up and volunteers (what are people willing to do)
    • Poll for telcon dates - key to have one in early Dec and one in middle (a paper discussion before it goes back) Friday 8th, Friday 15th - final draft out from Chris by 11th - Chris
    • Start to write some guidelines for new MIxxx groups
    • Ask Amelia (at EBI) about practical aspects of OBO tree (collapsible) view on website - could we easily do the same - Chris
    • Ryan to put in EI on Dec 1 for a 'standards summit' (can take cv's etc from Susanna's bid) - 25k for flights (CIHR funding; http://www.cihr-irsc.gc.ca/e/30812.html)
    • Connotea - bibliography, website: Ryan (after Dec 15), Dawn

Item last updated on 2006-12-07. Chris Taylor (chris.taylor[@]ebi.ac.uk)