|
New Session |
|
A Session is the container for a set of MRR records within P5. A Session can only contain records for a single Project Code, but most other fields can be different for each record in the Session. A Session can be empty or contain thousands of records, encompass one day of marking or several months of marking, however it is not recommended to cross calendar year boundaries in a Session. When submitted to PTAGIS, a Session is written to File and that file is received by PTAGIS, processed into the database, and stored in the file archive.
|
Profile |
|
|
Select the Profile to associate with the new Session. Existing values in the New Session Defaults section of the Profile will be used to complete the rest of the form. Settings and devices specified in the selected Profile will be active while the Session is open. |
|
Project Code |
|
|
Select the Project Code (which used to be known as the Coordinator ID) for the new Session. |
|
File |
|
|
The File name will be automatically generated based on the Project Code, the current date, and the default value for UDF specified in the selected Profile. If a Project Code has not been selected, the File name will remain blank. If a default value for UDF has not been specified, it will use incremental numbers, starting with 001. |
|
Session |
|
|
Enter a name for the Session. Defaults to the File name, if it is generated, but can be changed. |
|
Session Folder |
|
|
Select an existing folder or enter a name to create a new folder into which the Session will be saved. If left blank, the Session will not be placed into a folder. |
|
Repeating Values |
|
|
Select a Repeating Value to use with this Session. |
|
Data Entry Layout |
|
|
Select a custom Data Entry Layout to use with this Session. If left blank, the default data entry form will be used. |
|
Project Defined Session Fields |
|
|
All session-level Project Defined Fields will be displayed here. Enter a value to be saved in those fields for this Session. |
