I have never used UIMA, but I have heard good things. All the analytics processes I run are in Hadoop Mapreduce and there are cascading jobs that do many different things. However, this sounds like a good idea for a "solution wrapper," and I understand and agree with your concern about creating classes which combine components. I would like to try it in UIMA, sounds great, where in the UIMA project do I start?
On Tue, Oct 22, 2013 at 2:29 PM, Jörn Kottmann <[email protected]> wrote: > On 10/05/2013 11:58 PM, Mark G wrote: > >> 4. provide a "solution wrapper" for the Geotagging capability >> >> In order to make the GeoTagging a bit more "out of the box" functional, I >> was thinking of creating a class that one calls find(MaxentModel, doc, >> sentencedetector, EntityLinkerProperties) to abstract the current impl. I >> know this is not standard practice, just want to see what you all think. >> This would make it "easier" to get this thing running. >> > > > What do you think about using a solution like UIMA to do this? I am not > sure how you > are intending to run your NLP pipelines but in my experiences that has > worked out > really well. UIMA can help to solve some production problems like > scalability, error handling, > etc. > > If you are interested in this you could write an Analysis Engine for the > Entity Linker and add > it to opennlp-uima. > > I still believe it is not a good idea to make classes which combine > components to use them out of > the box, because that never really suits all of our users, and it is easy > to implement inside a user project. > > Anyway we should add command line support and implement a class which can > demonstrate how the entity linker > works in a similar fashion as our other command line tools. > > Jörn >
