E-MERGE: File List View (E-Merge) [22762]

File List View

The File List view is displayed on the right side of the application display below the toolbar. The File List view displays the names of the individual files contained within the folder opened in the Folder Tree view. Columns may be sorted in ascending or descending order by clicking on the column header. Specific files may be selected by clicking on the name of the file in the File Name column. The File List view includes information specific to the individual files such as the size of the file, and information pertaining to the creation, modification, or merge status of the file.

Icons
To the left of the filename for each file in the File List view is an icon indicating the status of the file.

	Unmerged, unaltered E-Prime data file
	Unmerged E-Prime data file containing altered data.
	E-Prime data file that has been merged to another file.
	E-Prime data file that has been merged, and contains altered data.
	E-Prime data file selected as target file.
	E-Prime data file containing more than one session of data.
	All non-E-Prime data files.

File Name
The File Name column displays the filename without the path for each file contained within the folder selected in the Folder Tree view.

Experiment
The Experiment column lists the name of the experiment with which the data file is associated. For merged data files, the Experiment column displays dashes, because data from different experiments may be contained within the same file. This column is left empty for all non-E-Prime data files.

Status
The Status column contains one of three values for E-Prime files: Single Session, Merged data, or Target. The Status column remains blank for non-E-Prime files.

Single Session
Single session files are E-Prime data files generated by the E-Run application, which contain data from a single session. Single Session files have the .edat3 file extension.

Merged Data
Merged data files are E-Prime data files which contain data from more than one session, and which are not designated as the target file. Merged data files have the .emrg3 extension. Merged data files may be merged into other files (i.e., act as a source file) or receive data from other files (i.e., act as a target file).

Target File
The target file is the file into which sessions of data are to be merged during a particular merge operation. Single session files may not be named as target files because data may not be merged into them. Target files may or may not be located in the same directory as the source files, and may or may not exist prior to the merge operation. If the target does not exist prior to the merge operation, it will be created by E-Merge during the operation.

If the file contains modifications to the data, three asterisks are added to the Status column value. When a source file containing data alterations is merged into a target file, E-Merge carries all data alteration flags from the source file to the target file. Therefore, when merging a source file with data alterations into a target file without data alterations, the target file will contain data alterations at the conclusion of the merge operation. After the merge operation is completed, the Status column value for the target file will be updated to include “***”, indicating altered data.

Subject
The Subject column displays the subject number assigned within an E-Prime data file. For merged E-Prime data files, this column displays three dashes because merged data files may contain data for more than a single subject. For files other than E-Prime data files, this column remains empty.

Session
The Session column displays the session number assigned within an E-Prime data file. For merged E-Prime data files, this column displays dashes because merged data files may contain more than a single session of data. For files other than E-Prime data files, this column remains empty.

Last Merged
The Last Merged column contains the date the file was last merged into another file. This column is blank if the file was never merged into another file or if the file is not an E-Prime data file.

Last Modified
The Last Modified column displays the last date any changes were made to the file. The column remains blank if the file was never modified or if the file is not an E-Prime data file. Modifications to the file need not include altering the data. For example, saving a new comment to a file will change the Last Modified date but will not alter the data.

Created
The Created column displays the creation date for E-Prime data files, and remains blank for all other files. The creation date refers to the date a single session data file was generated by E- Run, or the date a merged data file was created by E-Merge during a merge operation.

Size in KB
The Size in KB column displays the size of the file in kilobytes.

Filtering the File List View

The set of files displayed in the File List view may be filtered according to file name to limit the number of files listed. The filter is applied to include all files fitting a designated pattern. The Filter on File Name dialog may be displayed using the Filter tool button, or the Filter option under the View menu.

Four filters are supplied in the Filter on File Name dialog: all files (*.*), single session files (*.edat3), merged data files (*.emrg3), and all E-Prime data files (*.edat, *.emrg, *.edat2, *.emrg2). The default setting displays all files (*.*).

The default may be changed by typing directly in the Select a Filter field, or by choosing an option from the drop-down menu. Any filter pattern entered by the user is added to the list of available filters in the drop-down box until the application has been exited. Multiple filters may be entered using a semi-colon as a separator.

NOTE: Do not include spaces in addition to the semi-colon separating filters.

Because the file name filter examines both long filenames and aliases during the search, some wildcard searches may yield unexpected results. For example, if the system has generated the alias LONGFI~1 for LongFileName, a filter on a *1 pattern would return LongFileName even though the actual file name does not contain a 1.