About
This article described describes how to interprete the csv results migration report which can be gained by migration summary view. The migration report is provided as zip archive containing a text file in CSV format (semicolon-separated).
Content
| Table of Contents | ||||
|---|---|---|---|---|
|
...
Export_M04_MW_banane6_2621601885127550154.csv
...
Interpretation of CSV files
The files conaines containes of a head and a table.
Head
The head is self explaining. e.g.:containes general information about the migration.
...
Table
The table have this has these columns:
Column Name | Description |
|---|---|
ID | incrementing number |
STATUS | 3 means ok |
DOCID | the document id |
DATESOURCE | date |
from source archive | |
DATEMIGRATED | date and time of migration |
COMPIDS | the |
component id’s migrated | |
COMPIDCOUNT | the amount of components migrated |
CHECKSUM_SRC | if configuration item CheckSrcHashValues is enabled, the hash |
transfered from source archive (only KGS CS) and hash built in migration tool is compared. If comparison |
was sucessful, the hash value |
appears in this column. | |
CHECKSUM_DST | if configuration item CheckDstHashValues is enabled, |
a hash is generated by the migration tool |
and |
sent to destination CS as HTTP header. If the destination CS is an KGS CS it can compare the sent hash with an own generated one. If this comparison |
fails, it will send an error response. If it is successful the CS will send an 201 |
HTTP status (“Created”) and the migration tool will write the hash into the column CHECKSUM_DST. | |
ERROR | If an error occures during migration the error is written here. |
EXTRACOUNT | |
SORTKEY | |
SIZE | document size |
READTIME | time consumed while reading the document |
WRITETIME | time consumed while writing the document |
