Scan FME global operation¶
Scan relies on FME to browse data, and therefore requires a license to be available during the process. By default, Scan runs up to 3 instances of FME in parallel, with a single license in use (see Service configuration).
Each instance handles an action associated with a piece of data: for example, signing GEOFLA.DEPARTEMENTS or documenting GEOFLA.COMMUNES. A queue (independent of entry points) starts a new instance as soon as one ends.
The FME license used is available again for other uses once the scan is complete.
Scanning allows two types of inventory to be taken:
- The ordinary scan, which inventories data, detects modifications and synchronizes information in the Isogeo API. The data can then be used by the administrator platform.
- The audit scan, which enables data to be inventoried without detection of modification or synchronization in the Isogeo API.
Scan¶
-
Select an entry point.
-
Click on the "Scan" button. The launched query is displayed.
-
The scan operation is divided into 3 phases:
- Census: the scan lists the data;
- Sign: the scan signs all the data counted in order to deduce whether the data has already been scanned or modified since the last scan (except those ignored);
- Document: scan creates records for newly detected data or updates records for modified data (except for ignored data).
-
When finished, the scan shows you :
- Query statistics ;
- The complete list of data. In this list, each data item is characterized by :
- a unique identifier ;
- its file or table name ;
- its character (geographic, non-geographic) ;
- its type (Database, Vector, Raster, CAD) ;
- its format ;
- its status (new, modified, moved, unchanged, ignored or error) ;
- signing time;
- its documentation time (provided the data is detected as new or modified).
- You can sort this table and search for a table or file.
- You can sort by processing time from longest to shortest by entering the following parameters:
?sign
: sorting by signature time ;?lookup
: sorting by documentation time ;?anyJob
: sort by time of signature and documentation ;?bothJobs
: sort by the sum of the two.
The complete list of data collected during the scan identifies :
- New data added to your inventory ;
- Data unchanged since last scan ;
- Data modified since the last scan ;
- Data moved since the last scan ;
- Data ignored by the last scan.
Go to the inventory to discover these data and browse their metadata.
Audit¶
-
Select an entry point.
-
Click on the "Audit" button. The launched query is displayed.
-
The audit takes place in 2 phases:
- Census: the scan lists the data;
- Document: the scan recovers the metadata of the scanned data or service according to the exclusion parameters. The metadata recovered is the same as for ordinary scanning.
-
Once completed, the scan :
- shows you the complete list of data. In this list, each data item is characterized by :
- its file or table name ;
- its type
- its format ;
- its documentation time (provided the data is not excluded).
- allows you to download the inventory with more information than on the interface
- shows you the complete list of data. In this list, each data item is characterized by :
You can then export the data or statistics to the auditor to gain a clearer overview of your assets.
Scan audit and track changes
The audit scan has no impact on the monitoring of changes to data assets. It does not replace an ordinary scan.
Ignored data
Data ignored by the entry point is inventoried but not documented. To audit this data without modifying the ordinary scan entry point. It is possible to use the entry point duplication feature to create an entry point specific to the audit.
Special cases¶
For both types of scan :
- For databases, FME relies on the user you configure. A table visible from several entry points by several users (different connection strings) will not be duplicated.
- If you copy data without changing the file name, the scan will indicate that it has detected a duplicate, but will still create a new record;
- Attributes whose names start with
fme_
,apic_
andgml_
are considered to be tool-specific technical fields (such as FME) and are not remounted.
Deleting a query¶
You can delete a query by clicking on the "Trash" icon next to the "Scan" button in the query details.
Deleting a request
Please note that this operation deletes the query from the user interface, but does not delete it from the database, so as to preserve the history of operations in case of need.