lims quick start guide - progeny software · progeny lims quick start guide 2 overview - creating a...

Rev 1.22

LIMS QUICK START GUIDE A Multi Step Guide to Assist in the Construction of a LIMS Database

Progeny LIMS Quick Start Guide 1

Contents

Contents ............................................................................................................................................1

Overview - Creating a LIMS Database .................................................................................................2

1.0 Folders .........................................................................................................................................3

2.0 Data Fields ...................................................................................................................................3

2.1 Validations Tab .................................................................................................................................... 4

2.2 Security Tab ......................................................................................................................................... 5

3.0 Sample Datasheets .......................................................................................................................7

3.1 Importing Samples using the Import Module ..................................................................................... 8

3.2 Importing Samples using the Spreadsheet Module .......................................................................... 10

4.0 Containers .................................................................................................................................. 13

4.1 Container Structure........................................................................................................................... 14

4.2 Importing Containers ........................................................................................................................ 15

5.0 Reactions ................................................................................................................................... 17

5.1 Creating New Reactions .................................................................................................................... 18

5.2 Creating “New Sample” Reactions .................................................................................................... 19

5.3 Creating “New Aliquot” Reactions .................................................................................................... 20

6.0 Actions ....................................................................................................................................... 23

6.1 Open vs Closed Actions ..................................................................................................................... 25

7.0 Group Actions ............................................................................................................................ 27

8.0 Workflows ................................................................................................................................. 29

8.1 Moving Samples Through The Workflow .......................................................................................... 31

9.0 Security ...................................................................................................................................... 33

10.0 Queries .................................................................................................................................... 35


Overview - Creating a LIMS Database

The LIMS Quick Start Guide is to assist in the construction of a Progeny LIMS database. Utilizing this

multi-step guide, a user will be able to gain a comprehensive overview of Progeny LIMS and its

functions.

1. Create Folders Create all necessary folders in the Fields, Individuals, Samples and Containers tabs.

Individual Data Fields will include PHI Data and Clinical Folders.

Sample Data Fields will include Sample Info and Lab Info Folders.

2. Create/Import Necessary Fields Create/Import all necessary data fields and store within the target folders.

These fields can then be altered/added to later.

3. Create Sample Datasheets Optionally a Sample can be created so that a datasheet can be constructed and then

populated with the newly created fields.

This Datasheet can then be stored as a template and applied to any other created/imported

Samples

4. Create Necessary Containers All necessary containers are created and configured according to the user specifications.

5. Create Reactions and Actions Reactions as well as Actions are created.

6. Create Workflows Workflows are created.


1.0 Folders

Select the appropriate navigation tab where the folder will be created (Individual, Samples, Containers

and Field tabs), then proceed to select the icon from the Toolbar.

Folders should be created at the Individual, Sample, Containers and Field levels.

2.0 Data Fields

Once the necessary folders have been created, the user can then create or import data fields. When

creating a new field, the user must first navigate to the “Fields” tab, select a folder and then select the

icon from the Toolbar. A pop up window will appear which looks like this:

Figure 2.0


The user then has the option to name the field, enter a default value for the field and select the field

type from the dropdown menu. (Possible Field types include: text, date, image, hyperlink, dropdown

menu, table, lookup table, table summary, number, yes/no, summary, and computed fields). In addition

to fields created/imported by the user, there are a number of system fields which cannot be edited or

deleted. These system fields act like computed fields, in that information cannot be directly entered into

these fields in datasheets, but rather the system will automatically populate these fields.

2.1 Validations Tab The user can also set validations for a field by selecting the “Validations” tab and then choosing from the

options provided. The “Validations” window is displayed in Figure 2.1.

Figure 2.1


The user has the option to choose from the following validations:

Required Field - Selecting this option will require the user to always enter information for

this field when it is included in a datasheet.

User Must Confirm Data Entry - Selecting this option will result in the user being prompted

to re-enter the data into the field before it will be saved.

Unique Value - A unique value must be entered into any field which has this validation

selected.

Within Specific Range - The data which is entered into the field must be within the range set

out in the validation (whether it be text, numbers or dates).

Specific Mask - Defines how you must enter data into the field, can be used to maintain

consistency and to make your database easier to manage. For example, with the underscore

character (_) representing a single character, an input mask of (___) ___-____ would require

a phone number like this: (574)123-4567.

Maximum Number of Characters - Limits the number of characters which can be entered

into a field.

Dependent Validation Settings - These settings are applied at the database level and are

applied at all times (data entry, imports, and so on). When selecting this option the user

must specify the relation that the field must have with another field of the same type.

2.2 Security Tab The security settings of a data field can also be altered so that certain users only have limited access to

certain fields. The administrator can add a class in the “Security” tab and then check/uncheck the

“Read?” or ”Write?” options to determine which users have the ability to alter/view fields and which

users will be restricted in what they can see/edit. The Security tab window will look like Figure 2.2.

Alternatively for more comprehensive security settings the administrator can turn to the “User

Maintenance” options (See section 9.0).


Figure 2.2


3.0 Sample Datasheets

In order to access a Sample datasheet, the user will first have to create a new sample. This can be done

in the “Samples” navigation tab by selecting a folder, right-clicking and then selecting the “New Sample”

option. Once created, the user can double click on the sample to access the datasheet connected with

that sample.

Once the user opens up a sample datasheet he/she will have the option to add/remove the fields he/she

wants to display on the datasheet by selecting the option in the upper panel. Once this

checkbox is selected the user has the option to add fields by clicking the button, located on the

toolbar. A pop-up window will display all available fields and the user can then select the fields he/she

wishes to display on the datasheet by dragging and dropping the fields onto the datasheet. When all

desired fields have been added the user can then select the option and start entering data

into the fields.

The datasheets are fully customizable, allowing users to add text, create multiple tabs and display

document hyperlinks and pictures. The user can create and save an unlimited amount of datasheet

formats, which can then be applied to a wide variety of samples or alternatively the user also has the

option to set a particular format as the default format for an entire folder.

Fields and text can also be customized and formatted to meet the users’ requirements by selecting the

icon from the toolbar. A pop-up window will then display a number of options from which to

choose, such as: Where to position the field name, what type/size font to display, as well as the option

to either display or hide field display icons and names.

Figure 3.0


3.1 Importing Samples using the Import Module A user has the option to not just create samples within the database, but also to import batches of

samples into the database. The import module can be used to import samples into the database from a

.txt file. The import module can be reached by selecting the button from the toolbar. A pop-up

window will open which looks like Figure 3.1.

Figure 3.1

The user can choose which file it is they want to import by clicking the “Browse” button and selecting

the appropriate file. The user must then select the delimiter used in the .txt file.

Samples can be assigned to individuals during the import process by checking the “Assign Samples to

Individuals using:” box, located in the “Import Options” portion of the pop-up window. The user can

then decide which criteria will be used to identify how the samples are to be linked to individuals.

Alternatively, if the individual does not already exist within the database the user has the option to


create this individual and tie the imported sample to it by checking the “Add Individual if no matching ID

is found”. Likewise a new container, where the imported samples are to be stored, can be created by

checking the “Create container if barcode not found” checkbox.

Once the file to be imported has been chosen its’ contents will populate the bottom portion of the pop-

up display window and the user will have the option to select the autobuild function if the file has a

header row. The system will then match existing fields with the headers in the file to populate the

header row in the pop-up window. If however, the headers in the file don’t correlate to any existing

fields, the user can either ignore these columns or check the “File has a Header Row” checkbox and a

new option will appear which looks like this: .

The user can then create new fields for all headers by checking the box and selecting the most

appropriate field type. If the user would prefer to browse through all available fields and select the most

appropriate option this can be done by right-clicking on the header row and selecting the “Choose

Existing Field” option from the list as shown in Figure 3.11.

Figure 3.11

The user can right-click on

the header row and select

the most appropriate field

for each column.

NOTE: “Sample Name” is a

mandatory column header

and as such one column

must include the sample

name for the samples to

be imported


Once all desired header rows have been added the user can click the “Import” button and the file will be

imported.

3.2 Importing Samples using the Spreadsheet Module If the user wishes to import table data for a sample into the database, the sample must first exist in the

database, before the spreadsheet import module can be used to bring the table data into the database.

To use the sample spreadsheet importing option the user must navigate to the “Samples” tab and then

select the button from the toolbar. A new tab will open which looks like Figure 3.2

Figure 3.2

The user can then select the fields which they intend to import data into.

NOTE: All columns in the file to be imported must be in the exact same order as laid out here in the

spreadsheet module. In addition, all column headings must be removed from the file to be imported or

the data will not be imported.

Once the above criteria have been satisfied the user can then run the spreadsheet or save the format.

To run the spreadsheet select the button from the Toolbar. The user will then be redirected to a

new window which looks like Figure 3.21


Figure 3.21

From here the user can import their files by clicking the button located on the Toolbar. A pop-up

window will appear which looks like Figure 3.22.


Figure 3.22

Select the delimiter used in the file to be imported, then specify how many columns are being used to

identify the sample data.

NOTE: The “number of unique identifiers in the import file that match columns in the spreadsheet” must

be the first column of both the spreadsheet and the import file. If more than one column is being used

as an identifying column then these must be the first few columns in both the spreadsheet and the

import file.

Under “Data Options” the user has the option to import table data by checking the box. Additionally the

user can decide to import blank cells over existing data or if the user does not wish to erase all pre-

existing data the “Ignore blank cells” checkbox can be ticked.

Once all of the above has been completed click the “Import” button to import the data.

The “Number of unique identifiers

in the import file that match

columns in the spreadsheet”

refers to the first column(s) in the

spreadsheet/import file which

contain(s) the identifying data for

the samples, eg. Sample Name


4.0 Containers

Containers can be created in both the “Inventory” tab, as well as the “Containers” tab. Just like samples

and individuals, containers can either be created manually or imported into the database.

To create containers in the “Inventory” tab navigate to the “Inventory” tab, right click in the left hand

panel and choose the containers which are to be created from the pop-up menu, as demonstrated in

figure 4.0. Once created and named, containers will automatically be assigned a barcode, which can be

altered based on the preferences of the user.

To create containers in the “Containers” tab navigate to the “Containers” tab and select the

icon from the toolbar. While the user can carry out many of the same functions in the “Inventory” and

“Containers” tabs, there are certain functions which are unique to each one. The main difference

between the two tabs is the way in which containers are displayed in the left hand panel.

In the “Inventory” tab the containers are displayed in a branched out or tree-like format while in the

“Containers” tab the containers are displayed in the traditional folder structure format.

Figure 4.0


4.1 Container Structure When a user wishes to create a new type of container, alter the characteristics of an existing container

or add child (sub) containers to a container, the “Inventory Structure” option will be used to do this.

The structure of containers can only be altered in the “Inventory” tab. The user can access the

“Inventory Structure” by selecting “Container” from the menu and then choosing the “Inventory

Structure” option from the dropdown menu which appears. A pop-up window will appear which will

look like Figure 4.1:

Figure 4.1

The existing container structures are displayed in the “Container Types” pane. By selecting one of these

containers you can alter its structure as well as the child (sub) containers which belong to the parent

container. The “New” option from the side menu can be used to create a new container type. Once the

desired containers have been created, shelves, racks, boxes and plates can then be added to these

containers by using the “Child Containers” pane and selecting “Add” or “Remove”.

The inventory structure display

screen will show all the current

container types and their child

containers. Containers can be added,

removed or altered by highlighting a

container and selecting the most

appropriate option.


4.2 Importing Containers

Navigate to either the “Inventory” tab or the “Containers” tab. Select the button from the

Toolbar. A pop-up window will appear which looks like Figure 4.2.

Figure 4.2

Browse to, and select the file which is to be imported. Select the delimiter used in the import file. The

user has the option to check the “Update Container if found” option, which will update any pre-existing

containers within the database if new information is being imported for that container.

The user will then have the option to autobuild all of their column headers or right-click on each column

header and manually create the headers.


Figure 4.21

NOTE: At least four fields are necessary to import containers: The container name, container type,

parent barcode and container barcode.

Once all relevant headings have been added click “OK” to import.


5.0 Reactions

Reactions form the basis of all actions. These actions then facilitate the movement of samples through

workflows as well as providing other ‘open’ functions which can be carried out outside the confines of a

workflow (For more on “Open” vs “Closed” actions click here). Reactions can be accessed through the

“Samples”, “Workflow”, “Inventory” or “Containers” tabs by selecting the icon from the

toolbar. Once selected a pop-up window will appear which looks like Figure 5.0:

Figure 5.0

The blue reactions are system reactions and so these reactions cannot be deleted. All of the red

reactions however, have been created by the user and so can be altered or deleted by selecting the

appropriate option from the side menu.

Select one of the

options from the side

menu.


5.1 Creating New Reactions When selecting the “New” option, another display window will appear which looks like this:

Figure 5.1

First the user must name the reaction, then the user must select the desired “Reaction Type”. There are

six different options which can be selected for “Reaction type”. These options are displayed in the form

of a dropdown menu and include: Update Value, Decrease Value, Increase Value, Print, Create Sample,

and Create Aliquot. For the vast majority of Reactions the “Reaction Type” will be “Update Value”. The

“Create Sample” and “Create Aliquot” reaction types should only be selected when the user wants to

create an Aliquot/Sample.

When selecting the “Update Value”, “Increase Value” or “Decrease Value” as the “Reaction Type”, the

user must select a field by clicking the icon and then choosing the most appropriate field from the

target folder. If the necessary field doesn’t exist the user must exit the Reactions window and return to

the “Fields” tab to create/import the necessary field before proceeding.

Once the field has been entered the user must then select either “Prompt Text” or “Set Value”. If the

“Prompt Text” option is selected, the user must enter instructions, which will appear onscreen when the

action is being carried out, advising what information must be entered in order to complete the desired

reaction, eg. “Please enter technician name” or “Please enter the new location for your sample”.


If the “Set Value’ option is selected however, the user must enter a value here, which the system will

use to automatically carry out the reaction. Once a valid value is entered for “Set Value”, this reaction

will automatically take place anytime the action which contains it is run.

5.2 Creating “New Sample” Reactions When selecting “Create Sample” as the “Reaction Type”, rather than “Update Value”, “Increase Value”

or “Decrease Value”, the pop-up window will look somewhat different, in that you are presented with

two tabs: “Settings” and “Naming Defaults”. In the “Settings” tab the user has the option to either select

“Prompt Text” or the option to “Accept Default”. An example of this window is shown in Figure 5.2:

If the sample barcodes were not originated in Progeny (that is you are going to scan sample

barcodes as the samples are received), then select “Prompt Text”, and in the “Prompt Text”

field, enter the prompt that is given to a user for adding a new sample.

If the sample barcodes originated in Progeny (that is, the sample barcodes are already in the

Progeny database), then select “Accept Default”.

Figure 5.2

The “Naming Defaults” tab allows the user to choose the naming convention for all samples which will

be created. The user must select one of two options from the “Name Default” dropdown menu: “Prefix,

Auto-increment, Suffix” or “SampleID”. See Figure 5.21.


Prefix, Auto-increment, Suffix - This option allows the user to add either a prefix or suffix or

both to any samples which will be created. The user is also presented with the opportunity to

start the auto-incrementing of samples at a number of their choice (depending on the number

of samples which an institution anticipates it will handle, Progeny normally recommends that

users start auto-incrementing at 100,000 or higher due to the alpha-numerical way the samples

will be displayed in the Progeny database).

SampleID - Will cause all other boxes to grey out, except for the “Preview” box. The system will

use no prefixes or suffixes on any samples, merely auto-incrementing the samples from 1

onwards.

Figure 5.21

5.3 Creating “New Aliquot” Reactions When choosing the “Create Aliquot” option as the “Reaction Type”, the display pane will contain a third

tab in addition to “Settings” and “Naming Defaults” entitled “Advanced” (see Figure 5.3).


Figure 5.3

In this tab, the user has the option of adding fields which will be inherited from the parent sample.

These fields will then be displayed in the aliquot display pane any time the parent sample is selected.

The user can do this by clicking the “Add” button which will then open another display window which

looks like Figure 5.31:


Figure 5.31

The user can then select all fields which are to be inherited from the parent sample and click “OK”.


6.0 Actions

An action is a series of reactions. An action can be carried out on a single sample, a batch of samples or a

container full of samples. Once all necessary reactions have been created/imported, actions can then be

created. To create an action the user must select the icon from the toolbar in one of the

“Workflows”, “Samples”, “Inventory” or “Containers” tabs. A pop-up window will then appear which

looks like Figure 6.0.

Figure 6.0

The side menu provides a number of options from which the user can choose. When creating a new

action the user must select “New” from the side menu. Once selected, another pop-up window will

appear which looks like Figure 6.01.

The user can

import/export Actions

from other databases

which will also

import/export all

Reactions associated with

that Action


Figure 6.01

The user must enter a name for the action. The user is also presented with the option to enter a barcode

and a HotKey for this action.

The user also has the option of configuring the settings of an action by checking or unchecking the

various boxes under the “Settings” header.


Stage Only - The action can only take place within a workflow (See “Open” vs “Closed” actions).

Multiple Samples - This option allows the user to create multiple samples at the same time.

Chain - Choosing this option allows the user to track who carried out what actions and when as

the system will track this through the chain of custody.

Create Multiple Samples - This option will only display if a reaction with “Reaction Type”:

“Create Sample” or “Create Aliquot” has been added to the action. The user will have the

option to create a set number of samples every time the action is run, or can choose to have

the system prompt for number of samples to create each time the action is run.

Reactions can then be added to the action by clicking the “Add” button. The sequence which the

reactions take place in can also be altered by using the “Move Up” and “Move Down” functions. The

user can also choose to add display fields.

6.1 Open vs Closed Actions

Actions can either be ‘open’ or ‘closed’.

Open actions are those which can be carried out outside the confines of a workflow. Examples

of open actions include: To automatically create a sample with predetermined values, to create

a sample kit, to push a sample into a workflow or to assign a sample to an individual.

Closed actions are those which can only be carried out within the confines of a workflow.

Open and closed actions are both created in the same way, but the user can distinguish whether an

action is open or closed by checking or unchecking the “stage only” checkbox in the “New Action”

window (See “Actions”).

If “Stage Only” is checked then the action can only be used within the confines of a workflow.

If “Stage Only” is unchecked then the action can be carried out outside the confines of a

workflow.

In order to carry out an open action the user must first select one of the “Samples”, “Inventory” or

“Container” navigation tabs. If carrying out an open action on a container the user can right-click on the

desired container and select the appropriate action from the pop-up menu which appears. If carrying

out an open action on a sample/batch of samples the user can navigate to the “Samples” tab, select the

sample(s) they wish to carry out the action on, right-click and choose the appropriate action from the

pop-up menu which appears. Certain actions (such as “create sample” actions) can be carried out in the

“Samples” tab without selecting any samples. Simply open a folder and right-click in the blank space in

the right-hand panel to view which actions can be carried out without selecting a particular sample. See

Figure 6.1.

In order to carry out a closed action the user must first navigate to the “Workflows” tab. The user can

then select and right-click on a sample(s) in a workflow, select “Next Stage” from the pop-up list and the

closed action will be carried out on the sample. One closed action is associated with each different stage

of a workflow (See “Workflows”).


Figure 6.1


7.0 Group Actions

A group action is a series of actions (similar to an action being a series of reactions). A group action can

be carried out on a single sample, a batch of samples or a container full of samples. Group actions are

particularly useful where a user would like to run a series of actions during one stage of a workflow on

one sample or a batch of samples, where a user would like to create a sample kit, or where a user would

like to extract two or more sample types (eg. Plasma and DNA) from the one parent sample.

Once all necessary actions have been created/imported, group actions can then be created. To create a

group action the user must select the icon from the toolbar in the “Workflows”, “Samples”,

“Inventory” or “Containers” tabs. A pop-up window will then appear which looks like Figure 7.0.

Figure 7.0

The side menu provides a number of options from which the user can choose. When creating a new

action group the user must select “New” from the side menu. Once selected, another pop-up window

will appear which looks like Figure 7.01.


Figure 7.01

The user must name the action group and to add the desired actions to the new action group the user

must drag actions from the right-hand panel (this is a list of all existing actions within your database) and

then drop the action into the left-hand panel. Once all desired actions have been added, the user can

click “OK” to save the action group.

Similar to actions, action groups can also be run either inside the confines of a workflow or outside the

confines of a workflow.


8.0 Workflows

A workflow is a collection of actions or action groups which have been arranged into a step-by-step

procedure. A workflow is made up of multiple stages, with each stage associated with exactly one action

or group. After a sample is placed into a workflow, the movement of the sample from one stage to the

next can be tracked and recorded until the sample is ultimately exhausted and removed from the

workflow. Managing a workflow includes creating, modifying, and deleting stages, assigning a sample to

a workflow, and moving a sample through a workflow.

To create a new workflow the user must navigate to the “Workflows” tab. In this tab the user can select

the icon from the toolbar. The user must then name the new workflow, eg. “Blood’. Once a

new workflow is created, the user will have the option to select the icon from the toolbar.

After selecting this icon, a pop-up window will appear which looks like Figure 8.0:

Figure 8.0

The user must enter a name for the stage, choose the appropriate action or action group and then check

the “Workflow Entry Stage” checkbox if this stage will be a workflow entry stage. In the “Protocol” box

Choose the appropriate action or

action group from the pop-up

window. All available actions and

action groups from which the user

can choose will be displayed in this

pop-up window when the user clicks

“Change”.


the user has the option to write a brief description of what will take place during this stage of the

workflow. Once all information has been entered for the stage click “Save”.

Once a stage is saved, it will appear on screen as a green box and display the name and brief description

which the user entered for that stage. The box will look like Figure 8.01.

Figure 8.01

When all stages of a workflow have been created the user will be able to connect the various stages of

the workflow, allowing samples to move through the workflow. This can be done by clicking the icon

in the bottom right-hand corner of each of the green dialogue boxes and dragging the arrow to another

stage, as demonstrated below in Figure 8.02.

Figure 8.02


8.1 Moving Samples Through The Workflow Once the workflow has been constructed the user can start moving samples through it. This is done by

going back to the “Samples” tab, right-clicking on a sample/batch of samples and pushing them into a

workflow by selecting the appropriate action, or where a sample/batch of samples already exists within

a workflow, the user can right-click on the sample(s) and select the option “Next Stage” from the pop-up

menu.

Alternatively, if the sample(s) already exists within a workflow, the user has the option to navigate to

the “Workflows” tab, select the workflow which contains the sample(s) and the user will notice that all

samples contained within that workflow will populate on the screen below the workflow (See Figure

8.12). The user can then move the sample to the next stage of the workflow by right-clicking on the

sample(s) and selecting “Next Stage” from the menu.

Once the appropriate next stage is selected a pop-up window will appear which looks like this:

Figure 8.1


The sample name, workflow name, current stage, current action and current reaction will all be

displayed. The user will then follow the onscreen instructions, entering data as required and hitting the

“Enter” key each time to progress to the next reaction. Once all reactions have been run a message will

appear in the window which says “Action Completed”. The user can then close this window and move

the sample on to the next stage and repeat this process until the workflow has been completed.

Figure 8.12


9.0 Security

It’s possible that the administrator may want to restrict access to certain folders/data fields/navigation

tabs within the database for various users. This can be done by navigating to any tab, selecting

“Administration” from the menu and then selecting “User Maintenance”. Once selected a pop-up

window will appear which looks like Figure 9.0.

Figure 9.0


The administrator can enter the names and passwords of the various users by clicking the “Add User”

button. The password must be at least six characters long and contain at least one number. The new

user will then be prompted to reset their password the first time they log into the database. Once all

users have been added, the administrator can decide to restrict the level of access which each user has

to data within the database. This can be done by adding a new class under the “Settings” heading. Once

the “Add Class” option has been selected a pop-up window will appear which looks like this:

Figure 9.01

The administrator can then name the class and select which items are viewable and editable to this class

by checking the various boxes. Once the new user and class are selected the administrator can then go

to the “Licensing”, “Client Interface” and “Formatting” tabs and alter the information which each user

has access to.


10.0 Queries

A user can run a query on the “Pedigree”, “Individual”, “Samples”, “Inventory” and “Markers” tabs by

selecting the icon from the toolbar. This will then open up a spreadsheet generator which

looks like Figure 10.0.

Figure 10.0

In the “Folders” column select the folders which contain the fields to be used in the query. Once a folder

is selected the fields within the folder will display in the “Fields” column to the right of the folders. The

user can then select which fields will be used as column headings and which fields are to be queried by

clicking and dragging a field, placing it under the “Query” or “Column” heading as demonstrated in

Figure 10.01.


Figure 10.01

Once all column headings and query topics have been added the user can select the option from

the toolbar and a spreadsheet will be generated like the one shown in Figure 10.02 below. Alternatively,

the user can choose to load a pre-configured format by selecting the icon from the toolbar and

then selecting the desired format. The user also has the option to save a particular format which they

may want to run again later by selecting the icon from the toolbar.


Figure 10.02

The spreadsheet will then be generated and results can be sorted by clicking on the smart headers and

selecting the desired method of sorting the results. The results can be saved by selecting the “Save” icon

from the toolbar, or the spreadsheet can be rerun by selecting “Edit” from the toolbar and altering some

of the column/query fields. The spreadsheet format and results can also be exported by selecting the

“Export” button on the toolbar.

Additional Information on all topics covered above can be found in the user manual on the Progeny

website or by following this link:

http://www.progenygenetics.com/documentation/userguides/9/Progeny9UserGuide.pdf

http://www.progenygenetics.com/documentation/userguides/9/Progeny9UserGuide.pdf

lims quick start guide - progeny software · progeny lims quick start guide 2 overview - creating a...

Documents