To prevent spam users, you can only post on this forum after registration, which is by invitation. If you want to post on the forum, please send me a mail (h DOT m DOT w DOT verbeek AT tue DOT nl) and I'll send you an invitation in return for an account.
Repair/assign correct Originator to log
Hi,
I do have a couple of datasets including the column 'Person' indicating the person responsible for that particular event in the log. However, ProM does not recognize this column as the Originator column meaning that I can not analyze the log (on for example segregation of duties) using the LTL checker in prom 5.2. Does anyone have an idea how to make ProM recognize this column as the Originator column or how to 'repair' the log so that this column 'Person' is marked as the originator column?
I really hope someone can help me out here! Thanks!
Comments
-
Dear 'KKoopen',
I think the easiest and most pragmatic solution is to open the event log (not the 'gzipped' version but the raw XES or MXML file), and rename the attribute name.
In the case of XES rename the attribute to 'org:resource'.
My preferred editor is Notepad++, but most editor have a 'replace all' function
Joos Buijs
Senior Data Scientist and process mining expert at APG (Dutch pension fund executor).
Previously Assistant Professor in Process Mining at Eindhoven University of Technology -
Thanks JBuijs! This solved my problem
Howdy, Stranger!
Categories
- 1.6K All Categories
- 45 Announcements / News
- 225 Process Mining
- 6 - BPI Challenge 2020
- 9 - BPI Challenge 2019
- 24 - BPI Challenge 2018
- 27 - BPI Challenge 2017
- 8 - BPI Challenge 2016
- 68 Research
- 1K ProM 6
- 394 - Usage
- 288 - Development
- 9 RapidProM
- 1 - Usage
- 7 - Development
- 54 ProM5
- 19 - Usage
- 187 Event Logs
- 32 - ProMimport
- 75 - XESame