The UK Crop Plant Bioinformatics Network

BrassicaDB Tutorial

Database access


[Previous | Contents | Next]

Access to the database is available through a range of methods:

  1. Direct access using xace, tace or WinAce.
  2. Remote access. Using xaceclient, aceclient or winClient.
  3. Form based Web access (e.g. Webace or AceBrowser).
  4. Java based Web access (e.g. CITA clients).

Each of these methods has its, own strengths and weaknesses.

  1. Direct access.

    This requires access to a system that holds a copy of the database locally and a copy of the database software. This method provides access to all of the features of the database software, but not the value-added features of the other interfaces. This can be difficult to setup and maintain, and is not recommended for most users.

  2. Remote access.

    Using special versions of the database software, it is possible to use the database data from a remote site. This method has the advantage of avoiding the problem of data synchronisation, but is slower than using a local data set. It does however allow access to most of the features of the database software.

    Note: at this time, the Windows and UNIX versions of this system are not compatible.

  3. Form based web interfaces

    These are traditional form based web access methods. They have good support for database browsing and can support cross-linking to external data sources. However many of the more sophisticated abilities of the database software are not available. Most of the missing capabilities are related to the built in analysis tools available in the ACEDB software, and should not affect most users. There is also the issue of speed. These interfaces can be very slow, although they do their best to be as quick as possible given the limitations of the medium (AceBrowser seems to have the edge here).

    Note: these are the database interfaces used on the public mirrors of BrassicaDB.

  4. Java interfaces

    The platform independence of Java and its availability in most modern web browsers makes it ideal for the next generation of web interfaces. However while Java is a standard many of the current implementations do have flaws. Most of the currently available interfaces avoid this by being quite simple and using a common subset of the Java specification.

Generally you will not use methods 1 & 2, and they are only mentioned here for completeness. So we will concentrate on the web methods, and the interfaces they provide. So let's go look at them...

[Previous | Contents | Next]