The Shared project is pre-configured as part of the default LabKey Server installation. Resources to be shared site-wide, such as assay designs, can be placed here to be made available in the other projects or folders you create. Resources shared within subfolders of a single project can generally be shared by placing them at the local project level.

Changing the folder type of the Shared project, although allowed by the user interface, can produce unexpected behavior and is not supported.
The following table guides you to some of the ways the Shared project can be used:

Shared Definitions

When defined in the Shared project, the following features and definitions will be available in any other project or folder of the requisite type.

FeatureFolder TypeDocumentation
List DefinitionsAnyManage Lists
Assay DesignsAssaySet Up Folder For Assays
Plate TemplatesAssayCustomize Plate Templates
Panorama QC Annotation TypesPanorama QCPanorama QC Annotations
Sample TypesAnyCreate Sample Type
Source TypesSample ManagerUse Sample Manager with LabKey Server
Data Classes (including Bioregistry Entities)Any/BiologicsCustomize the Bioregistry
Wikis*AnyWiki Admin Guide

*Wikis are generally available site-wide, depending on permissions. From any container, you can see and use wikis from any other container you have permission to read. A permission-restrictive project can choose to make wikis available site-wide by defining them in the Shared project and accessing them from there.

In addition, some features, including Issue Definitions will not be automatically shared across the site, but will be available site-wide by creating a local definition of the same name.

Features Using Shared Definitions

The following features will include definitions from the Shared project when providing user selection options. There is no hierarchy; the user can select equally any options offered:

Assay Request TrackerAssay DefinitionsPremium Resource: Assay Request Tracker Administration

Resolving Targets by Name

When referring to any of the features in the following table, the hierarchy of searching for a name match proceeds as follows:

    1. First the current folder is searched for a matching name. If no match:
    2. Look in the parent of the current folder, and if no match there, continue to search up the folder tree to the project level, or wherever the feature itself is defined. If there is still no match:
    3. Look in the Shared project (but not in any of its subfolders).
Sample TypesLink Assay Data to Samples
Experimental Annotations for MS2 Runs
Issue DefinitionsIssue Tracker: Administration

Related Topics

Was this content helpful?

Log in or register an account to provide feedback

expand allcollapse all