ACeDB2000 conference proceedings: Day 4

> ##### Back to conference overview

> ## ACeDB2000: Day 3

> ### Summaries from task groups:

> Curators: There were some more volunteers to work on the comparative map display stuff. Mummi will talk about his use of the Clone grid in the afternoon if time allows. Richard has abandonded the Wiki-idea for now and setup a simple CGI-script page to accept doc-text.

> Programmers: ZAce is in its beginning stages,the programmers have a primitive running version now. The XML-discussion is getting really close to what a standard should look like.

> Middleware: Steven Jones has been working on a new version of Efetch that fetches seqs from an external SRS-server

> ### Ed Griffiths: Client/server tutorial

> Socket layer:

> - Handles new connections
> - multiple connections
> - non-blocking IO at any stage
> - handles errors and timeouts

> ACeDB layer:

> - Handles authentication and write access
> - Does requests like queries and stuff
> - Slices large requests into smaller bits

> (some nice diagrams of the schema), and now we're talking low-level code description and socket stuf. I'll ask him for some text on this..

> Summary:

> 1. The server is now well layered: connecting code in one layer, the ACeDB code in another, and no impact on the 'core' Ace.
> 2. The server is easier to port, since TCP/IP sockets are everywhere.
> 3. Easier to connect to server with Perl/JAVA etc.
> 4. Truly networked with new password/user system.
> 5. Better control of shutdowns and crashes.
> 6. Easier to administer with the new user commands.

> ### Hamish McWilliam: Java clients, CORBA servers

> Here are Hamish's slides from the talk.

> ### Robin Dowell:DAS, a Distributed Annotation System

> Often times many groups are working on annotating of a particular piece of a genome, and this can often lead to multiple databases spread all over, and the user that needs the data contained in them has to go to many different places to get the data.
> One solution is to have centralized databases like GenBank, but this poses problems of ownership and organization in itself.

> Another solution is to link all those databases to each others, but then the user needs to learn how to use all the databases.

> So, a system that automatically gathers the data from the different databases. Requirements of system:

> 1. Handle multiple levels of relative coordinates<
> 2. Easily generated and parsed
> 3. Extensible
> 4. Functional groupings of annotations

> now she's showing some slides that I can't see very well. Must ask her for copies.The URL is http://stein.cshl.org/das

> ### Dave Matthews: Quick queries on the web using AceBrowser

> The subject is premade queries (by curator) that can be offered on AceBrowser homepages. For example, finding all loci within a certain distance from a locus we are interested in... See Dave's homepage for the examples: (somewhere at the Cornell site,get URL from Dave..)

> If the (power) user is not satisfied with using the default distance, he can modify the table definition. But the idea is that the basic query is provided and the user can play with that and even save it to disk for later use.
> I'll leave the details to Dave, see if he has a written tutorial lying around, or in the making.

> ### Maria Nemchuk: AcePerl version of WebAce

> See website with installation instructions