Unipro UGENE Online User Manual v. 1.14.0
Child pages
  • Shared Database
4 more child pages

Versions Compared

Old Version 8

changes.mady.by.user Ivan Protsyuk

Saved on

compared with

New Version 9

changes.mady.by.user Olga Golosova

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The rational storage of biological data is

the issue that is always around

an ever-present issue. It is not only about large data sizes, but also about the requirement of simultaneous access to them by several scientists. For

example

instance, a few researchers from a lab may need to work on the same data, like a set of primers or data produced by sequencing.

That

 That information has to be updated and synchronized between different users and kept in a common storage.

Some notable implementations of such systems already exist (for example, CLC Bioinformatics Database or Geneious Shared Database), but they are proprietary and quite expensive. Thus, in this UGENE version we have introduced a new functionality – a shared bioinformatics storage. So far, it is represented by an ordinary database (currently we support only MySQL).

That is what UGENE Shared Database is intended for.

HTML
<center>
     <br>
     <img src="/wiki/download/attachments/8093772/Picture1.png"/>
     <br>
</center>

To start sharing data via UGENE users only you need to deploy a public database server. MySQL servers are currently supported. See this paragraph for details about the required server configuration.

After that any UGENE user (who knows the correct login/password, however (smile)) can connect to it and access the stored information, add new objects or delete existed ones. In fact, from the user’s point of view the shared database looks like a usual file opened by UGENE. The entire content of the database can be viewed . The connected database is shown in the Project View as a document exactly the same way as if the data were located on a the local computer. Objects in

As described in this paragraph the users can have a read-only access to the database can be ordered using a folder mechanism as well as moved between folders, other connected databases and local documents using conventional drag’n’drop. The UGENE instance, in turn, or be able to modify its content. A user with a read-only access can:

 Users with write access, in addition, can:

  • Add new objects to the database
  • Create new folders to order the data in the database
  • Modify the folders hierarchy inside the database (using drag'n'drop)
  • Rename objects and folders
  • Delete existed objects
  • Delete folders

All UGENE instances connected to a database constantly monitors the state of the database and shows changes, made by other users.

  HTML<center> <br> <img src="/wiki/download/attachments/8093772/Picture1.png"/> <br> </center>
Tip

UGENE accesses large remote data, such as NGS assemblies, so that only a viewed part of them is loaded to a client computer. So, if you store the assembly data on a server, the data can be browsed in the UGENE Assembly Browser on a local computer almost instantly, without the need to copy the data on the computer or use the hard disk space.


For details see the documentation below:

Children Display
alltrue