Date: Fri, 29 Mar 2024 07:09:23 +0700 (NOVT) Message-ID: <485249959.88280.1711670963323@ugene.net> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_88279_1991457788.1711670963322" ------=_Part_88279_1991457788.1711670963322 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The rational storage of biological data is an ever-present issue. It is = not only about large data sizes, but also about the requirement of simultan= eous access to them by several scientists. For 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 information has to be updated and synchr= onized between different users and kept in a common storage. That is what U= GENE Shared Database is intended for.
To start sharing data via UG= ENE you need to deploy a public database server. MySQL servers are currentl= y supported. See thi= s paragraph for details about t= he required server configuration.
After that any UGENE user (w= ho knows the correct login/password, however) can connect to the database. The c= onnected database is shown in the Project View as a document exactly the same way as if the data were located on the local computer.= span>
As des= cribed in this parag= raph the users can have a read-only access to the database or be able t= o modify its content. A user with a read-only acce= ss can:
Us= ers with write access, in addition, can:
All UGENE instances connected to a databa= se constantly monitors the state of the database and shows changes, made by= other users.
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 a= ssembly data on a server, the data can be browsed in the UGENE Assembly Bro= wser on a local computer almost instantly, without the need to copy the dat= a on the computer or use the hard disk space.
Fo= r details see the documentation below: