Importing Data to QPR ProcessAnalyzer: Difference between revisions

From QPR ProcessAnalyzer Wiki
Jump to navigation Jump to search
(Created page with "== Step 1: Imported File == You can choose whether to import: * '''cases''' or '''case attributes''' * '''events''' or '''event attributes''' * '''.xes''' or '''.pacm''' file....")
 
No edit summary
 
(33 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<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 ==
You can choose whether to import:
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.
* '''cases''' or '''case attributes'''
 
* '''events''' or '''event attributes'''
== Step 2: Import Destination ==
* '''.xes''' or '''.pacm''' file.
Cases and/or events can be imported to an existing QPR ProcessAnalyzer model or the import can create a new model:
With cases or case attributes and events or event attributes, the data needs to be imported from .csv files. A .xes or a .pacm file will contain both case and event data.<br>
* '''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.


== Step 2: CSV File Format ==
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 from a csv file, here you can define in what format the data is in the file:
* 1. column: case ID's
* '''Column delimiter''': Column delimiter is the character that separates data cells in a row. Usually the column delimiter is a semicolon or tab. It's possible to define any character by selecting the "other" option.
* 2. column: event type name
* '''Date format''': Date format is used to interpret date values in the csv file. Default format is: "yyyy-MM-dd HH:mm:ss,fff", where dd = zero-padded day of the month, from 01 through 31; MM = zero-padded month, from 01 through 12; yyyy = year as a four-digit number; HH = zero padded hour, using a 24-hour clock from 00 to 23; mm = zero-padded minute, from 00 through 59; ss = second, from 00 through 59; fff = millisecond. More information about formatting: https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings.
* 3. column: event timestamp
* '''Text qualifier''': Text qualifier is the character used to enclose text (string) values. Sometimes csv files don't contain text qualifiers at all.
* 4. column onward: event attributes
* '''Header row number''': The row number (staring from 1) in the file that contains the headers of the data. Usually the first row contains the headers, but the file may start with rows that need to be skipped.


== Step 3: Import Destination ==
[[Category: QPR ProcessAnalyzer]]
There are following ways to import data:
* '''New model to an existing project''': You need to select an existing project to which the new model is to be created. You also need to define name for the new model.
* '''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.
* '''Existing model''': You need to select the project and model to which the data is to be created. You can click the '''Open''' button to check the model that is currently selected.

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"