Importing Data to QPR ProcessAnalyzer: Difference between revisions

From QPR ProcessAnalyzer Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(19 intermediate revisions by 3 users not shown)
Line 1: Line 1:
This page describes how to import data to QPR ProcessAnalyzer using the Data Import view in the [[QPR_ProcessAnalyzer_Deployment_Package_for_QPR_UI|QPR ProcessAnalyzer Deployment Package]].
<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 ==
First choose the file to be imported from you local disk drive. It's possible to import '''csv''', '''pacm''' and '''xes''' files. If importing from a csv file, you need to define, whether the data contains cases or events. Pacm and xes files contain the entire QPR ProcessAnalyzer model, so with those formats no further selections are needed.
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 ==
There are following ways to store data to a model:
Cases and/or events can be imported to an existing QPR ProcessAnalyzer model or the import can create a new model:
* '''Create a new model to an existing project''': You need to select an existing project to which the new model will be created. You also need to define a name for the 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 a new model to a new project''': You need to define the name of the new project and new model. Note that you can't define different names for the new project and the new model, but you can rename the project and model after the import.
* '''Create New Model''': Select a project to which the new model will be created, and define a name for the new model.
* '''Import to an existing model''': You need to select the project and model which the data will be import to. You can click the '''Open''' button to check the model that is currently selected.
 
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.


== Step 3: CSV File Format (Optional) ==
Csv files need to be UTF-8 encoded.
When importing from a csv file, you need to define in what format the data is stored in the file. If uncertain, open the file and see its contents. Following settings can be set:
* '''Column delimiter''': Column delimiter is the character that separates data cells 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.
* '''Text qualifier''': Text qualifier is the character used to enclose text (string) values. Sometimes csv files don't contain text qualifiers at all.
* '''Header row number''': The row number (starting from 1) in the file that contains table headers. Usually the first row contains the headers, but the file may start with rows that need to be skipped.


When importing cases from a CSV file, the first column must contain case ID's and the rest of the columns contain 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:
* 1. column: case ID's
* 1. column: case ID's
* 2. column: event type names
* 2. column: event type name
* 3. column: event timestamps
* 3. column: event timestamp
* 4. column and onwards: event attributes
* 4. column onward: event attributes


[[Category: QPR UI]]
[[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:

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
Retrieved from "https://wiki.onqpr.com/pa/index.php?title=Importing_Data_to_QPR_ProcessAnalyzer&oldid=19043"