So, finally, the day is approaching that my baby gets the “1.0” label. But, before I dare to put it out there, I would like to have it tested, and not only by me.
So, what (/who) is XESame?
XESame started as XESma during my Master’s project. The goal of XESame is to extract event logs from data sources. The input format can be database tables, text files or even XML files. The output is an eventlog in the XES or MXML format.
A good slogan for XESame would be: “Opens the cave of process mining wonders”, but that would be a bit bragging.
Err, sounds great but then what?
This event log can be used in ProM to apply process mining analysis (which is sometimes called ‘magic‘ (Dutch article), it also produces very colorful and nice pictures…). More about ProM and process mining can be found at processmining.org.
But why do you want to test it now?
In September 2010, at the BPM’10 conference in New York, the ProM 6 framework will be officially released. Included in this framework is XESame. The next few days and weeks ProM 6 will be tested (internally) for the release. Since XESame will be released for the first time and I’m the only one working on it, I would really like some thorough testing and feedback.
Okay, so, how can I help?
Well, you can do several things, depending on what you like to do and how much time you can/will spend. First of all, I would suggest that you download XESame and try to extract an event log from data you have available. Then report back to me if XESame was useful and why (not).
XESame uses JDBC to connect to the data source. Since I can not test XESame on ‘all’ data source types out there, I’m interested in how it works on different types of data sources (e.g. different databases such as MySQL, Oracle, MS SQL, etc.)
Furthermore, if you encounter any errors, please let me know so I can try to fix them.
I’m also very interested in what features are missing and how XESame can provide better guidance in defining an extraction of event log data.
But I already looked at XESMa, do you need my help?
Well, yes, for two reasons: First, what did you think of XESMa when you tried it? Second: the graphical user interface of XESame is completely different from the (rudimentary and bloated) interface of XESMa. So I always need (and will appreciate) your help.
Okay, so how do I get started?
Good question (and I’m glad that you want to get started).
First of all, you need to download XESame of course and run it. Go to the ProM 6 BPM’10 release page and download the latest version of the framework and XESame. This should be under the section ‘Download’ or otherwise ‘History’.
For Windows users there is an xesame.exe file that you can start. For Mac/Linux/… users start the MainFrame class in the org.processminning.mapper.ui package from xesame.jar.
If you didn’t try XESame or XESMa before, it might be a good idea to read my Master’s thesis (PDF, 8Mb), especially chapters 5 and 6 with all the examples. (Not in any way suggesting that chapters 1, 2, 3, 4 and 7 are not interesting to read of course.) Although the thesis talks about XESMa a lot, everything should also be applicable for XESame.
And if you’re really interested, look at the XESame source code via http://prom.win.tue.nl:8000/Tracsites/browser/public/XESame/src/org/processmining/mapper or point your SVN client to svn://prom.win.tue.nl/public/XESame (you can use “anonymous/anonymous” for anonymous access, although you cannot commit of course).
Once you’re done fiddling around or when you encounter a serious error or bug or get stuck, contact me and I’ll try to help you. The best way to contact me is to go to my employee page and see if you want to come by my office, give me a call or send me an e-mail (or contact me through Office Communicator on my tue mail address).
Unfortunately, I’m only human so on occasion I might be at the restroom, having lunch or even on holiday (from August 9 until (and including) 20).
So, even if you don’t plan to click on any of the above links, I would like to thank you for reading this post. I hope to hear from you soon and until next time,
Update 28-7-2010 16:50 (CET): I forgot to mention that the ‘official home’ of XESame is http://prom.win.tue.nl/research/wiki/xesame/start (I was too exited…).
P.S. huge disclaimer follows:
Please note that the author, the department or the university can not be held responsible for any damage caused by direct or indirect usage of XESame (or XESMa). It is recommended that XESame will only be provided read access to the data source and that you run XESame on a copy of the data an not on (the only instance of) the original data source. And of course, XESame is not extensively tested (yet) so it might do strange things to you or your computer. But rest assure, me and my computer survived all months of development.