Difference between revisions of "Database Interop Hackathon"

From Evolutionary Informatics Working Group
Jump to: navigation, search
(New page: <center><big>'''NESCent Hackathon on Evolutionary Database Interoperability'''</big></center> == Synopsis == Even though there is a rich and meticulously curated variety of on-line datab...)
 
(Quick links)
 
(84 intermediate revisions by 9 users not shown)
Line 1: Line 1:
 
<center><big>'''NESCent Hackathon on Evolutionary Database Interoperability'''</big></center>
 
<center><big>'''NESCent Hackathon on Evolutionary Database Interoperability'''</big></center>
  
== Synopsis ==
 
  
Even though there is a rich and meticulously curated variety of on-line databases of phylogenetic data, their holdings are only available in incompatible formats lacking explicit semantics, and programmable APIs for querying the data are often not provided. NESCent seeks to address the resulting obstacle to interoperability and data integration by sponsoring a hackathon that brings together data and metadata experts and developers from a number of  data providers with the developers of the emerging NeXML and CDAO standards.
+
{{HackHead}}
 +
 
 +
== Quick links ==
 +
 
 +
Hackathon-specific:
 +
* [[Hackathon Report]] with notes of our daily sessions and links to resources
 +
* [[Database Interop Hackathon/Use Cases|Use Cases]] (there is also a more general phyloinformatics [https://www.nescent.org/wg_phyloinformatics/Public:UseCases use case list])
 +
* The [[Database Interop Hackathon/Agenda|agenda]] and [[Database Interop Hackathon/Participants|participants list]] for the upcoming meeting
 +
* [[Subgroups]] - Links to all hackathon subgroups.
 +
* [[Database Interop Hackathon/Implementations|Implementations descriptions]] of participating data resources
 +
* Suggested [[Database Interop Deliverables|target projects]] (ideas page)
 +
* Examples of [[Database Interop Hackathon/Metadata Support|metadata support]] in [[NeXML]] using [[CDAO]] and other ontologies
 +
 
 +
Resources and planning:
 +
* Notes on [[Database Interop Hackathon/Teleconferences|teleconferences]] and [[Database Interop Hackathon/Pre-Meeting|organizer's pre-meeting]]
 +
* Home pages for [http://www.nexml.org NeXML] and [http://www.evolutionaryontology.org CDAO]
 +
* [[Database Interop Hackathon/Documentation|Documentation]] archive
 +
* [[Media:Evolution 2009 Poster HL.pdf| Evolutionary Data Leaping to Web 3.0: Some Highlights From NESCent's Third Hackathon]] (Poster presented at the 2009 Evolution Meetings in Moscow, Idaho)
 +
* suggestions for [[Database Interop Hackathon/Provider Overviews|provider overviews]]
 +
 
 +
[[Son of Evoinfo|Proposal page for a follow-up NESCent working group]]
  
 
== Motivation ==
 
== Motivation ==
  
There is a large variety of phylogenetic data resources in the form of on-line databases, providing data ranging from character state matrices (e.g., MorphBank, Morphobank), molecular sequence alignments (e.g., BAliBASE, PANDIT), phylogenetic trees (e.g., TreeBASE), gene or protein trees (e.g., TreeFAM, PhylomeDB), species trees (e.g., Tree of Life), gene families (e.g., PhyloFacts, HOVERGEN), to species taxonomies (e.g., NCBI Taxonomy, ITIS), and to analytic metadata such as divergence times (e.g., TimeTree). There is no common or unifying exchange format in which these data resources are available, and each of the resources boast a variety of meticulously curated or computed metadata for their holdings that require expert knowledge and manual inspection to interpret. Furthermore, there is no common, predictable way for querying and obtaining the data, and in fact most of those resources don't provide any programmable on-line interface (API).  
+
A variety of phylogenetic data resources are available in the form of on-line databases, providing data ranging from character state matrices (e.g., [[MorphBank]], [[MorphoBank]]), molecular sequence alignments (e.g., BAliBASE, [[PANDIT]]), phylogenetic trees (e.g., [[TreeBASE]]), gene or protein trees (e.g., TreeFAM, PhylomeDB), species trees (e.g., [[Tree of Life]]), gene families (e.g., PhyloFacts, HOVERGEN), to species taxonomies (e.g., NCBI Taxonomy, ITIS, [[PaleoDB]]), and to analytic metadata such as divergence times (e.g., [[TimeTree]]).
  
This situation presents a fundamental obstacle to integrating phylogenetic data and service providers into a network of interoperating services that consume and produce data in predictable, verifiable syntax and with explicit machine-interpretable semantics, key prerequisites to applying tools for resource discovery and for constructing or executing complex workflows. It also renders these resources resistant to large-scale data integration, for example for combining and cross-linking some of these resources with other data, such as genomic, phenotypic, or georeferenced specimen data.
+
Even though there is a rich and meticulously curated variety of on-line resources, their holdings are only available in incompatible formats lacking explicit semantics, and programmable APIs for querying the data are often not provided. NESCent seeks to address the resulting obstacle to interoperability and data integration by sponsoring a hackathon that brings together data and metadata experts and developers from a number of data providers with the developers of the emerging [[NeXML]] and [[CDAO]] standards.
  
Recently, the development of the NeXML data exchange format and the CDAO ontology for comparative and phylogenetic data and analysis have provided a window of opportunity to apply both of these emerging standards towards solving some of these obstacles, while at the same time validating their ability to satisfy real-world needs that previously used standards (such as NEXUS) have not. Doing so would benefit the data providers by making their data more broadly useful, end-users by having access to a wide variety of phylogenetic data in a common, predictable format, and ultimately tool developers by defining a uniform way for giving their users instant access to a large swath of data.
+
=== The problem ===
  
NESCent seeks to take advantage of this opportunity by sponsoring a hackathon that brings together data and metadata experts and developers from several phylogenetic data providers with the developers of NeXML and CDAO, as well as with developers of phylogenetic data visualization and database integration projects.
+
There is no existing common or unifying exchange format in which these data resources are available, and each of the resources boast a variety of meticulously curated or computed metadata for their holdings that require expert knowledge and manual inspection to interpret. Furthermore, there is no common, predictable way for querying and obtaining the data, and in fact most of those resources don't provide any programmable on-line interface (API). This situation presents a fundamental obstacle to integrating phylogenetic data and service providers into a network of interoperating services that consume and produce data in predictable, verifiable syntax and with explicit machine-interpretable semantics, key prerequisites to applying tools for resource discovery and for constructing or executing complex workflows. It also renders these resources resistant to large-scale data integration, for example for combining and cross-linking some of these resources with other data, such as genomic, phenotypic, or georeferenced specimen data. This is further exacerbated by the fact that existing commonly used standards for phylogenetic data such as NEXUS cannot fully represent the different data sources and their semantics in a consistent manner, further hindering efforts to overcome this situation because they depend on an exchange standard with sufficient syntactical and semantic expressivity.
  
== Specific objectives ==
+
=== Activities of the EvoInfo working group ===
 +
 
 +
Recently, the development of the [[NeXML]] data exchange format and the [[CDAO]] ontology for comparative and phylogenetic data and analysis have provided a window of opportunity to apply both of these emerging standards towards solving some of these obstacles, while at the same time validating their ability to satisfy real-world needs that previously used standards (such as NEXUS) have not. Doing so would benefit the data providers by making their data more broadly useful, end-users by having access to a wide variety of phylogenetic data in a common, predictable format, and ultimately tool developers by defining a uniform way for giving their users instant access to a large swath of data. Furthermore, the recently started development of PhyloWS provides a first attempt at a uniform specification for a programmable phylogenetic data provider API.
 +
 
 +
=== The hackathon ===
 +
 
 +
NESCent seeks to take advantage of this opportunity by sponsoring a hackathon that brings together data and metadata experts and developers from several phylogenetic data providers with the developers of [[NeXML]] and [[CDAO]]. In addition, developers and end-users of phylogenetic data visualization and database integration projects will build demonstration projects and ensure the utility of the effort for research applications.
 +
 
 +
=== Acknowledgements ===
 +
 
 +
Many of the ideas for this hackathon arose from, and are a continuation of, the activities of NESCent's [[Main Page|Evolutionary Informatics Working Group]]. Specifically, [[Future Data Exchange Standard|NeXML]], [[CDAO]], and [[PhyloWS]] are products of the group, and the motivation for this hackathon is a distillation of the [[CarrotBase]] ideas and concepts, which essentially served as a whitepaper for this event.
 +
 
 +
== Objectives ==
 +
 
 +
For a more specific list of possible deliverables, see [[Database Interop Deliverables]]. We are also [[Database Interop Hackathon/Use Cases|collecting use-cases]].
  
 
The following broad objectives have been identified. Participants of the hackathon will refine these and distill concrete work targets from them in advance of and at the event.
 
The following broad objectives have been identified. Participants of the hackathon will refine these and distill concrete work targets from them in advance of and at the event.
# Define and implement a transformation path from the native data format of the participating data providers to NeXML.
+
# Unify the data format using [[NeXML]]:
# Define comprehensive mappings between the metadata of the participating data providers to CDAO terms.
+
#* Define and implement a transformation path from the native data format of the participating data providers to NeXML.
# Create a database that integrates all participating data providers.
+
#* Document mappings, gaps, and ambiguities, and resolve those at the event as much as possible, or lay out ways for future resolution.
# Create an interactive tool that visualizes and navigates across the breadth of data.
+
# Unify the data semantics using [[CDAO]]
 +
#* Define comprehensive mappings between the metadata of the participating data providers to CDAO terms.
 +
#* Extend CDAO with (possibly provisionary?) terms as much as possible.
 +
#* Identify and document procedure for other data providers with semantics not currently represented within CDAO.
 +
# Unify programmable data provider API
 +
#* Complete the PhyloWS specification for RESTful data access and querying.
 +
#* Document [[NeXML]] and CDAO needs for specifying metadata queries through PhyloWS.
 +
# Create demonstration projects that take advantage of the unified data formats and/or semantics.
 +
#* Database that integrates all participating data providers.
 +
#* PhyloWS implementation on top of an integrated database.
 +
#* Interactive tool that visualizes and navigates across the breadth of data.
  
 
The hackathon concentrates on writing code. All code and documentation will be made available immediately and freely to the community under an  open-source ([http://www.opensource.org/licenses/alphabetical OSI-approved)] license.
 
The hackathon concentrates on writing code. All code and documentation will be made available immediately and freely to the community under an  open-source ([http://www.opensource.org/licenses/alphabetical OSI-approved)] license.
  
== Subgroups ==
+
== Activities ==
 +
 
 +
=== Pre-meeting ===
 +
 
 +
In order to best prepare for the main event, the participating standards are holding a [[Database Interop Hackathon/Pre-Meeting|pre-meeting]] on Feb 20-22, also on-site at NESCent in Durham, NC.
 +
 
 +
=== Conference calls ===
 +
 
 +
;Hackathon participants:
 +
* [[Database Interop Hackathon/Teleconferences#Teleconference June 29, 2009|Teleconference Jun 29, 2009]]
 +
* [[Database Interop Hackathon/Teleconferences#Teleconference June 23, 2009|Teleconference Jun 23, 2009]]
 +
* [[Database Interop Hackathon/Teleconferences#Teleconference Feb 26, 2009|Teleconference Feb 26, 2009]]
 +
* [[Database Interop Hackathon/Teleconferences#Teleconference Feb 20, 2009|Teleconference Feb 20, 2009]]
 +
 
 +
;[[NeXML]]:
 +
* [[Future_Data_Exchange_Standard/Teleconferences#Teleconference.2C_Feb_3.2C_2009| Teleconference Feb 3, 2009]]
 +
 
 +
=== Subgroups ===
 +
 
 +
Participants will split into subgroups at the event. The composition and tasks of the subgroups will be guided by the overall objectives, but will otherwise emerge and be self-determined by the participants prior to and at the event.
 +
 
 +
=== Information gathering ===
 +
 
 +
The form for entering input and output data is on a [[Database_Interop_Hackathon/ResourceIOForm|separate page]].
 +
 
 +
=== Documentation ===
 +
 
 +
''Note: this may eventually become its own subgroup.''
  
 +
* All [[Database Interop Hackathon/Documentation|hackathon-related documentation]]
 +
* Documentation of [[Database Interop Hackathon/Metadata Support|metadata support]] with explicit semantics
  
== Participants ==
+
== Participate ==
  
Participation will be arranged by invitation and by self-nomination followed by review.  
+
* On-site participation was arranged by invitation and by self-nomination through an [http://docs.google.com/Doc?id=dc3k7mhr_43hh8hw2gw Open Call for Participation], followed by review.
* The [[Database Interop Hackathon/Participants|list of participants]] will be available on-line.
+
* The [[Database Interop Hackathon/Participants|list of on-site participants]] has been finalized as of mid-February.
 +
* To better enable remove participation and pre-hackathon interactions, we have created an IRC channel on [http://freenode.net Freenode], named #dbhack1. There are [[Help:Contents#Internet_Relay_Chat_.28IRC.29|instructions for finding and using an IRC client and for connecting]] in the help pages.
 +
** [[Image:Mibbit parameters screen.dbhack1.png|right]] Alternatively to a desktop client, you can use a web-client such as [http://mibbit.com Mibbit], which requires no download or installation of software. For Mibbit, on the front page click 'Start chatting now', and then enter the connection parameters as in the screenshot (substituting your desired nickname for 'your_nick') and hit 'Go'. On the page that opens, click the #dbhack1 tab if it isn't in the front already.
 +
* To enable micro-blogging of the event and as a tool for aggregating content, we have created a [http://friendfeed.com/rooms/dbhack1 Friendfeed room short-named dbhack1]. If you have difficult joining the room or have a content stream we should add let me know. Being Friendfeed, the room also has an RSS feed, in case you want to add it to your favorite feed reader.
 +
* As listed under [[Database_Interop_Hackathon#Links_.26_Resources|resources]], we encourage you to use the tag dbhack1 on social tagging sites (such as [http://connotea.org/tag/dbhack1 Connotea],  [http://citeulike.org/tag/dbhack1 CiteULike],  [http://del.icio.us/tag/dbhack1 Del.icio.us]) to tag online resources or papers relevant to the event.
  
 
== Organization ==
 
== Organization ==
  
'''Organizing Committee:''' [[User:Hlapp|Hilmar Lapp]], [[User:Bco|Arlin Stoltzfus]], [[User:Tjv|Todd Vision]], [[User:RutgerVos|Rutger Vos]]
+
'''Organizing Committee:''' [[User:Hlapp|Hilmar Lapp]], [[User:KatjaSchulz|Katja Schulz]], [[User:ArlinStoltzfus|Arlin Stoltzfus]], [[User:Tjv|Todd Vision]], [[User:RutgerVos|Rutger Vos]]
 +
 
 +
'''Time & Venue:''' The hackathon is scheduled to take place from March 9 to 13, 2009 at NESCent in Durham, North Carolina.
 +
 
 +
'''Agenda:''' The [[Database Interop Hackathon/Agenda|agenda of the event]] will be posted here once developed by the participants.
 +
 
 +
'''Logistics:'''
 +
* Participants stay at the [http://www.duketower.com/ Duke Tower Hotel & Condominiums] in Durham (807 West Trinity Avenue, Durham, NC  27701, telephone:  866-385-3869 or 919-687-4444).
 +
* Breakfast options are the Tower Cafe at Duke Tower (continental breakfast), [http://www.wholefoodsmarket.com/stores/durham/ Whole Foods], [http://www.madhatterbakeshop.com/menu/breakfast/ Mad Hatter's], and [http://www.beantraderscoffee.com/locations.html Bean Trader's] on 9th Street.
  
'''Time & Venue:''' The hackathon is tentatively scheduled to take place from Dec 8-12, 2008 at NESCent.  
+
[[Org:Database_Interop_Hackathon/Agenda|Organizers' notes]]. (''Note: these are for organizers only.'')
 +
 
 +
== Demonstration projects, sample code, ideas ==
 +
 
 +
=== miscellaneous ===
 +
 
 +
* There are some  suggested project ideas from our pre-meetings.
 +
* see [[Database_Interop_Hackathon/Target_Projects]]
 +
 
 +
=== Integrating ToL and TimeTree to get trees with dates ===
 +
 
 +
Rutger Vos has written a mashup showing how to use [[PhyloWS]] services to integrate data from two sources.  Specifically it gets a tree from [[Tree of Life]], and then assigns dates to the nodes using [[TimeTree]].
 +
 
 +
The code for both of these is in the nexml svn repository on
 +
sourceforge in the phylows/ subtree:
 +
 
 +
http://nexml.svn.sourceforge.net/viewvc/nexml/trunk/nexml/phylows/
 +
 
 +
<!--
 +
We're back, baby!
 +
Note that the TimeTree wrapper is currently broken, as it relies on
 +
screen scraping and the TimeTree website has recently changed. This is
 +
no fault of my own, it simply vindicates the argument for machine
 +
readable interfaces :)
 +
-->
 +
 
 +
== Links & Resources ==
 +
 
 +
Help with editing the wiki:
 +
* [http://www.nescent.org/informatics/wiki_tutorial.php Online tutorial] (targeted at Working Groups, but the basics all apply)
 +
* [[Help:Wiki|Collection of wiki editing tips]], with links to further documentation
 +
 
 +
Past NESCent-sponsored hackathons:
 +
* [http://hackathon.nescent.org/Phylohackathon_1 Phyloinformatics Hackathon]
 +
* [http://hackathon.nescent.org/R_Hackathon_1 Comparative Methods in R Hackathon]
 +
 
 +
Relevant reading:
 +
* Lapp et al. (2007) [http://www.la-press.com/the-2006-nescent-phyloinformatics-hackathon-a-field-report-a480 The 2006 NESCent Phyloinformatics Hackathon: A Field Report]. Evolutionary Bioinformatics 3:357-366
 +
 
 +
You can tag online resources, such as citations, articles, or other URLs, using social tagging sites. Please use the dbhack1 tag.
 +
* [http://connotea.org/tag/dbhack1 Connotea]
 +
* [http://citeulike.org/tag/dbhack1 CiteULike]
 +
* [http://del.icio.us/tag/dbhack1 Del.icio.us]
 +
 
 +
== Photos ==
 +
 
 +
<gallery>
 +
Image:IMG_1631.JPG
 +
Image:IMG_1632.JPG
 +
Image:IMG_1634.JPG
 +
Image:IMG_1635.jpg
 +
Image:IMG_1636.JPG
 +
Image:IMG_1637.JPG
 +
Image:IMG_1638.JPG
 +
Image:IMG_1639.JPG
 +
Image:IMG_1640.JPG
 +
Image:IMG_1641.JPG
 +
Image:IMG_1642.jpg
 +
Image:IMG_1643.JPG
 +
Image:IMG_1645.JPG
 +
Image:IMG_1646.JPG
 +
Image:FirstNight.JPG
 +
Image:FirstNight2.JPG
 +
Image:Meeting1.JPG
 +
Image:RogerPresenting.JPG
 +
Image:SheldonPresenting.JPG
 +
</gallery>
  
 
[[Category:DB Interop Hackathon]]
 
[[Category:DB Interop Hackathon]]
 
+
[[Category:NeXML]]
[[Category:Nexml]]
 
 
[[Category:CDAO]]
 
[[Category:CDAO]]
[[Category:DB Interop Hackathon]]
 

Latest revision as of 18:47, 5 February 2011

NESCent Hackathon on Evolutionary Database Interoperability


Quick links

Hackathon-specific:

Resources and planning:

Proposal page for a follow-up NESCent working group

Motivation

A variety of phylogenetic data resources are available in the form of on-line databases, providing data ranging from character state matrices (e.g., MorphBank, MorphoBank), molecular sequence alignments (e.g., BAliBASE, PANDIT), phylogenetic trees (e.g., TreeBASE), gene or protein trees (e.g., TreeFAM, PhylomeDB), species trees (e.g., Tree of Life), gene families (e.g., PhyloFacts, HOVERGEN), to species taxonomies (e.g., NCBI Taxonomy, ITIS, PaleoDB), and to analytic metadata such as divergence times (e.g., TimeTree).

Even though there is a rich and meticulously curated variety of on-line resources, their holdings are only available in incompatible formats lacking explicit semantics, and programmable APIs for querying the data are often not provided. NESCent seeks to address the resulting obstacle to interoperability and data integration by sponsoring a hackathon that brings together data and metadata experts and developers from a number of data providers with the developers of the emerging NeXML and CDAO standards.

The problem

There is no existing common or unifying exchange format in which these data resources are available, and each of the resources boast a variety of meticulously curated or computed metadata for their holdings that require expert knowledge and manual inspection to interpret. Furthermore, there is no common, predictable way for querying and obtaining the data, and in fact most of those resources don't provide any programmable on-line interface (API). This situation presents a fundamental obstacle to integrating phylogenetic data and service providers into a network of interoperating services that consume and produce data in predictable, verifiable syntax and with explicit machine-interpretable semantics, key prerequisites to applying tools for resource discovery and for constructing or executing complex workflows. It also renders these resources resistant to large-scale data integration, for example for combining and cross-linking some of these resources with other data, such as genomic, phenotypic, or georeferenced specimen data. This is further exacerbated by the fact that existing commonly used standards for phylogenetic data such as NEXUS cannot fully represent the different data sources and their semantics in a consistent manner, further hindering efforts to overcome this situation because they depend on an exchange standard with sufficient syntactical and semantic expressivity.

Activities of the EvoInfo working group

Recently, the development of the NeXML data exchange format and the CDAO ontology for comparative and phylogenetic data and analysis have provided a window of opportunity to apply both of these emerging standards towards solving some of these obstacles, while at the same time validating their ability to satisfy real-world needs that previously used standards (such as NEXUS) have not. Doing so would benefit the data providers by making their data more broadly useful, end-users by having access to a wide variety of phylogenetic data in a common, predictable format, and ultimately tool developers by defining a uniform way for giving their users instant access to a large swath of data. Furthermore, the recently started development of PhyloWS provides a first attempt at a uniform specification for a programmable phylogenetic data provider API.

The hackathon

NESCent seeks to take advantage of this opportunity by sponsoring a hackathon that brings together data and metadata experts and developers from several phylogenetic data providers with the developers of NeXML and CDAO. In addition, developers and end-users of phylogenetic data visualization and database integration projects will build demonstration projects and ensure the utility of the effort for research applications.

Acknowledgements

Many of the ideas for this hackathon arose from, and are a continuation of, the activities of NESCent's Evolutionary Informatics Working Group. Specifically, NeXML, CDAO, and PhyloWS are products of the group, and the motivation for this hackathon is a distillation of the CarrotBase ideas and concepts, which essentially served as a whitepaper for this event.

Objectives

For a more specific list of possible deliverables, see Database Interop Deliverables. We are also collecting use-cases.

The following broad objectives have been identified. Participants of the hackathon will refine these and distill concrete work targets from them in advance of and at the event.

  1. Unify the data format using NeXML:
    • Define and implement a transformation path from the native data format of the participating data providers to NeXML.
    • Document mappings, gaps, and ambiguities, and resolve those at the event as much as possible, or lay out ways for future resolution.
  2. Unify the data semantics using CDAO
    • Define comprehensive mappings between the metadata of the participating data providers to CDAO terms.
    • Extend CDAO with (possibly provisionary?) terms as much as possible.
    • Identify and document procedure for other data providers with semantics not currently represented within CDAO.
  3. Unify programmable data provider API
    • Complete the PhyloWS specification for RESTful data access and querying.
    • Document NeXML and CDAO needs for specifying metadata queries through PhyloWS.
  4. Create demonstration projects that take advantage of the unified data formats and/or semantics.
    • Database that integrates all participating data providers.
    • PhyloWS implementation on top of an integrated database.
    • Interactive tool that visualizes and navigates across the breadth of data.

The hackathon concentrates on writing code. All code and documentation will be made available immediately and freely to the community under an open-source (OSI-approved) license.

Activities

Pre-meeting

In order to best prepare for the main event, the participating standards are holding a pre-meeting on Feb 20-22, also on-site at NESCent in Durham, NC.

Conference calls

Hackathon participants
NeXML

Subgroups

Participants will split into subgroups at the event. The composition and tasks of the subgroups will be guided by the overall objectives, but will otherwise emerge and be self-determined by the participants prior to and at the event.

Information gathering

The form for entering input and output data is on a separate page.

Documentation

Note: this may eventually become its own subgroup.

Participate

  • On-site participation was arranged by invitation and by self-nomination through an Open Call for Participation, followed by review.
  • The list of on-site participants has been finalized as of mid-February.
  • To better enable remove participation and pre-hackathon interactions, we have created an IRC channel on Freenode, named #dbhack1. There are instructions for finding and using an IRC client and for connecting in the help pages.
    • Mibbit parameters screen.dbhack1.png
      Alternatively to a desktop client, you can use a web-client such as Mibbit, which requires no download or installation of software. For Mibbit, on the front page click 'Start chatting now', and then enter the connection parameters as in the screenshot (substituting your desired nickname for 'your_nick') and hit 'Go'. On the page that opens, click the #dbhack1 tab if it isn't in the front already.
  • To enable micro-blogging of the event and as a tool for aggregating content, we have created a Friendfeed room short-named dbhack1. If you have difficult joining the room or have a content stream we should add let me know. Being Friendfeed, the room also has an RSS feed, in case you want to add it to your favorite feed reader.
  • As listed under resources, we encourage you to use the tag dbhack1 on social tagging sites (such as Connotea, CiteULike, Del.icio.us) to tag online resources or papers relevant to the event.

Organization

Organizing Committee: Hilmar Lapp, Katja Schulz, Arlin Stoltzfus, Todd Vision, Rutger Vos

Time & Venue: The hackathon is scheduled to take place from March 9 to 13, 2009 at NESCent in Durham, North Carolina.

Agenda: The agenda of the event will be posted here once developed by the participants.

Logistics:

Organizers' notes. (Note: these are for organizers only.)

Demonstration projects, sample code, ideas

miscellaneous

Integrating ToL and TimeTree to get trees with dates

Rutger Vos has written a mashup showing how to use PhyloWS services to integrate data from two sources. Specifically it gets a tree from Tree of Life, and then assigns dates to the nodes using TimeTree.

The code for both of these is in the nexml svn repository on sourceforge in the phylows/ subtree:

http://nexml.svn.sourceforge.net/viewvc/nexml/trunk/nexml/phylows/


Links & Resources

Help with editing the wiki:

Past NESCent-sponsored hackathons:

Relevant reading:

You can tag online resources, such as citations, articles, or other URLs, using social tagging sites. Please use the dbhack1 tag.

Photos