Description

DF_ICimages checks that the CRF image name contained in each database record can be found in the study pages directory (where all documents are stored), and conversely, that each file in the study pages directory is referenced by exactly one database record.

Each database record contains the unique CRF image name corresponding to the submitted CRF page for that data record. DF_ICimages retrieves these image names from all data records and also retrieves the names of all documents stored in the study pages directory. It then compares these 2 lists looking for any cases where there is no one-to-one correspondence between the lists. The result is that this report identifies any database records for which the corresponding image is missing, and any images stored in the study pages directory for which there is no corresponding database record.

DF_ICimages processes the data records first and thereafter processes the CRF images. If the database is receiving new documents at the time that the report is run, it is possible that the results of these two sequential steps will not accurately reflect the database status. To account for this, you may chose to use -x.

Without -x, the database remains read-write for the duration of the report, and DF_ICimages can erroneously report an inconsistency where there is none. This can occur when new documents are being received at the instant that DF_ICimages is running and the timing of the new pages and data interleaves the execution of DF_ICimages. You may hence choose to ignore inconsistencies that deal with documents received, say today or this week, or run the report with -x which will guarantee consistency of results.

With -x, DF_ICimages will attempt to place the database server into a read-only state for the duration of the report. If successful, other tools that modify the database, such as DFexplore and incoming document processing, will not work until read-write access is restored by DF_ICimages.

Options