LigandScout uses a “
two-level
” file storing strategy, the
Shared Repository (or Central Repository) and the Local Repository.
If a PDB code is entered in the
PDB 4-letter code
field of the
PDB Panel
,
LigandScout tries to find the associated files in the first level Local Repository.
If unsuccessful, LigandScout will check the Shared Repository which represents the second level. The
Shared Repository is usually installed at a central location and
every licensee can take advantage of it by specifying the correct
path to this repository in
Preferences/Program & Network Settings
.
As the second level repository is
intended to be shared among all licensed users, it is not modifiable
using LigandScout (the only exception is if a new repository is
installed to be the new Shared Repository). Hence, there is the
first level repository which contains all of
the changes that were performed on a structure locally (if the
user decides to save them). Also, recently downloaded and interpreted
PDB structures will be stored there for faster retrieval later on.
You can store changes to your current active site to the Local Repository with
File
>
Save to Repository
(CTRL+S). If you do not use this command and you load new
data or quit LigandScout, a
Save changes
dialog
reminds you to store or discard the modified data.
The
Export Repository
command (CTRL+ALT+SHIFT+E) in the
File
>
Repository
menu
enables the export of your PDB data storage. To allow
sharing your Local and Shared Repository you can choose to store it as a single compressed
archive. Choose
Local Repository
for your local storage. If the repository is located on a server and
is to be shared with other users, select
Shared Repository
.
Make sure that you have writing privilege for this location.
The path to your
Shared Repository
is specified
in the
Preferences/Program & Network Settings
whereas the
Local Repository
will be managed by LigandScout.