The Altair Community is migrating to a new platform to provide a better experience for you. In preparation for the migration, the Altair Community is on read-only mode from October 28 - November 6, 2024. Technical support via cases will continue to work as is. For any urgent requests from Students/Faculty members, please submit the form linked here
mine service tickets
DataFighter
Member Posts: 3 Contributor I
We have an old ticket management system that has very few structured fields.
The only fields where valuable info is, are Summary, Remarks and a Memo field which contains a detailled description of ticket (problem, observable cause, failure modes, planning details, execution details as well as worker's feedback)
I'm looking for a way to spit out the main causes for these tickets as well as other types of information.
Any ideas on how I can do this using RapidMiner?
P.S.: I'm new to machine learning. So please don't be too hard on me!
0
Answers
Hello DataFighter,
This a blog that talks about how to do text mining with Rapidminer.
http://vancouverdata.blogspot.co.uk/2010/11/text-analytics-with-rapidminer-loading.html
Its pretty detailed and should cover all aspects of text mining that will be needed for your case.
please let us know how you progress
Additonally there are dozens of other resources on textmining available when you search. Not seen them, but could be handy.
You can try this sample process. It uses word clustering and association rules.
Thanks TBone,
What format is attribute "label".
WIthout sample data, it's hard for me to understand what's going on and what I should be using in which operators
Sorry, as I mentionned earlier, I'm new to machine learning and text mining
Thanks Bhupendra_patil,
I've looked at some of the videos and I got stuck at stemming.
Our database is in french.
Are there any stemming operators made for french language?
... Nevermind, just found Snowball stemming!
As mentioned start with text mining & clustering to try to get summaries of the problems grouped together in categories.
One thing you don't mention having is timestamps of the tickets if you do maybe you can also use association rules or clustering to see what problems seem to happen around certain times and investigate potential correlations & causes. (for example on humid days the electronics of the computers run slowly and crash more often)
Have a look at the website www.rapidprom.org for inspiration on what you'll be able to do when you have the tickets all cleaned up. It might give you some nice ideas for the next step of your internal ticket management systems.