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.
CSV Import timestamp issue
Hello everyone,
I tried to convert a CSV file to XES using the CSV Import Plugin but the outcome is unexpected. I hope the following example illustrates my problem:
The date is in german format dd.mm.yyyy.
On the "Configure Conversion from CSV to XES" the plugin states it can't autodetect the date format. I shall be given in SimpleDateFormat fashion, therefore I type "d.M.y".
After conversion is done the Log inspector activity A occured on 16.01.0201. This is not the expected. What can I do?
I tried to convert a CSV file to XES using the CSV Import Plugin but the outcome is unexpected. I hope the following example illustrates my problem:
startdate, event, trace
16.11.2017, A, Case1
The date is in german format dd.mm.yyyy.
On the "Configure Conversion from CSV to XES" the plugin states it can't autodetect the date format. I shall be given in SimpleDateFormat fashion, therefore I type "d.M.y".
After conversion is done the Log inspector activity A occured on 16.01.0201. This is not the expected. What can I do?
Answers
-
P.s. I am using ProM Lite 1.2
-
Could you try "dd.MM.yyyy" instead?
-
The output is still wrong... day and month are correct, year is inexplicable.
-
If possible, please replace the dots by another character. As an alternative, add an additional trailing dot to the timestamp ("16.11.2017.").The problem is caused with a 'fix' for the milliseconds in a timestamp: If the trailing milliseconds have more than 3 digits (like 1.2345), this is truncated to three digits (like 1.234). Your date format suffers from this fix, as now the year (xxx.2017) gets truncated (xxx.201).
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
- 393 - Usage
- 287 - Development
- 9 RapidProM
- 1 - Usage
- 7 - Development
- 54 ProM5
- 19 - Usage
- 187 Event Logs
- 32 - ProMimport
- 75 - XESame