Importing Data to QPR ProcessAnalyzer: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
This page describes how to import data to QPR ProcessAnalyzer using the Data Import view | <div style="border:1px solid #dfdfdf;padding:0.5em 1em 0.5em 1em;background-color:#E7EAEC;margin:10px 0px 0px 10px;"> | ||
This import functionality is deprecated, and it has been replaced by the new import to datatables, that is part of the [[QPR_ProcessAnalyzer_Project_Workspace|Workspace]]. | |||
</div> | |||
This page describes how to import data to QPR ProcessAnalyzer using the Data Import view. | |||
== Step 1: Imported File == | == Step 1: Imported File == | ||
Choose a file to be imported from your disk drive. It's possible to import '''.csv''', '''.pacm''' and '''.xes''' files. If importing from a .csv file, define also whether the data contains cases, events or other data to be loaded into a data table. ''Pacm'' and ''xes'' files contain an entire QPR ProcessAnalyzer model. | |||
== Step 2: Import Destination == | == Step 2: Import Destination == | ||
Cases and/or events can be imported to an existing QPR ProcessAnalyzer model or | Cases and/or events can be imported to an existing QPR ProcessAnalyzer model or the import can create a new model: | ||
* '''Import to Existing Model''': Select a project and model which the data will be import to. You can click the '''Open''' button to check the model that is currently selected. | * '''Import to Existing Model''': Select a project and model which the data will be import to. You can click the '''Open''' button to check the model that is currently selected. | ||
* '''Create New Model''': Select a project to which the new model will be created, and define a name for the new model. | * '''Create New Model''': Select a project to which the new model will be created, and define a name for the new model. | ||
When importing a data table, the target project and data table name needs to be defined. | When importing a data table, the target project and data table name needs to be defined. When importing to an existing datatable, specify the name of the datatable similar to creating a new datatable. | ||
When '''Add to existing data''' is checked, the existing data in a datatable is not deleted and the new data is added to the existing data. | |||
== Step 3: CSV File Format == | == Step 3: CSV File Format == | ||
When importing from a csv file, you need to define in which format the data is stored in the file. If uncertain, open the file | When importing from a csv file, you need to define in which format the data is stored in the file. If uncertain, open the file in a text editor. Following settings are available: | ||
* '''Column Delimiter''': | * '''Column Delimiter''': Character that separates data columns within a row. Usually the column delimiter is a semicolon or tab. It's possible to define any character by selecting the ''Other'' option. | ||
* '''Date Format''': Date format is used to interpret date values in the csv file. Default format is | * '''Date Format''': Date format is used to interpret date values in the csv file. Default format is ''yyyy-MM-dd HH:mm:ss,fff''. More information about formatting: https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings. | ||
Csv files need to be UTF-8 encoded | Csv files need to be UTF-8 encoded. | ||
When importing cases from a csv file, the first column must contain case ID and the rest of the columns are case attributes. When importing events, the column order in the csv file must be the following: | When importing cases from a csv file, the first column must contain case ID and the rest of the columns are case attributes. When importing events, the column order in the csv file must be the following: | ||
| Line 22: | Line 28: | ||
* 2. column: event type name | * 2. column: event type name | ||
* 3. column: event timestamp | * 3. column: event timestamp | ||
* 4. column | * 4. column onward: event attributes | ||
[[Category: QPR ProcessAnalyzer]] | [[Category: QPR ProcessAnalyzer]] | ||
Latest revision as of 15:43, 23 September 2021
This import functionality is deprecated, and it has been replaced by the new import to datatables, that is part of the Workspace.
This page describes how to import data to QPR ProcessAnalyzer using the Data Import view.
Step 1: Imported File
Choose a file to be imported from your disk drive. It's possible to import .csv, .pacm and .xes files. If importing from a .csv file, define also whether the data contains cases, events or other data to be loaded into a data table. Pacm and xes files contain an entire QPR ProcessAnalyzer model.
Step 2: Import Destination
Cases and/or events can be imported to an existing QPR ProcessAnalyzer model or the import can create a new model:
- Import to Existing Model: Select a project and model which the data will be import to. You can click the Open button to check the model that is currently selected.
- Create New Model: Select a project to which the new model will be created, and define a name for the new model.
When importing a data table, the target project and data table name needs to be defined. When importing to an existing datatable, specify the name of the datatable similar to creating a new datatable.
When Add to existing data is checked, the existing data in a datatable is not deleted and the new data is added to the existing data.
Step 3: CSV File Format
When importing from a csv file, you need to define in which format the data is stored in the file. If uncertain, open the file in a text editor. Following settings are available:
- Column Delimiter: Character that separates data columns within a row. Usually the column delimiter is a semicolon or tab. It's possible to define any character by selecting the Other option.
- Date Format: Date format is used to interpret date values in the csv file. Default format is yyyy-MM-dd HH:mm:ss,fff. More information about formatting: https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings.
Csv files need to be UTF-8 encoded.
When importing cases from a csv file, the first column must contain case ID and the rest of the columns are case attributes. When importing events, the column order in the csv file must be the following:
- 1. column: case ID's
- 2. column: event type name
- 3. column: event timestamp
- 4. column onward: event attributes