Laserfiche WebLink
<br />Page 36 of 58 <br /> <br />Import all associated videos and still images of <br />inspections. Media files must be linked to their <br />corresponding inspections for easy reference and <br />retrieval. <br />R <br /> <br />Import all relevant metadata, including, but not <br />limited to: <br />a. Inspection dates and times. <br />b. Inspection locations, e.g., GPS coordinates <br />and pipe segment identifiers. <br />c. Inspector details, e.g., name and ID. <br />d. Equipment used, e.g., camera model and <br />calibration data. <br />R <br /> <br />Import any other related and associated data from <br />the CUES GraniteNET system necessary for <br />comprehensive inspection records. <br />R <br /> <br />Support importing data in formats generated by <br />CUES GraniteNET, such as database backups, export <br />files, or XML/CSV files. <br />R <br /> <br />Import process must include a mapping interface <br />that allows users to align CUES GraniteNET data <br />fields with corresponding fields in the target system. <br />Field mappings must be saved as templates to reuse. <br />R <br /> <br />Validate data before import to identify missing or <br />inconsistent information. All errors detected during <br />the import process must be logged, with detailed <br />error messages to facilitate troubleshooting. <br />R <br /> <br />Create detailed logs of each import process, <br />including: <br />a. Start and end times of the import. <br />b. Number of records imported successfully. <br />c. Number and details of records with errors. <br />R <br /> <br />Generate reports summarizing issues encountered <br />during the import process for review. R <br />Provide an intuitive interface for configuring import <br />settings, viewing logs, and resolving errors. R <br />