Hi Sean, When we try to deploy cTAKES as web application, it always looks for sno_rx_16ab.xml by default on server start. So do you mean we should also have sno_rx_16ab.xml as well as custom xml file in the resources folder all the time?
Regards, Gandhi -----Original Message----- From: Finan, Sean [mailto:sean.fi...@childrens.harvard.edu] Sent: Tuesday, November 21, 2017 8:42 PM To: dev@ctakes.apache.org Subject: RE: Use of custom Dictionary Descriptor file [EXTERNAL] Hi Sandeep, Adding a custom dictionary should never require code modification. The dictionary creator gui will create a custom dictionary and its .xml configuration file and place them in your ctakes resources/ directory. No code changes necessary. https://cwiki.apache.org/confluence/display/CTAKES/Dictionary+Creator+GUI If you search the ctakes devlist emails you should find some threads discussing custom dictionaries and bsv files. (bar separated value, aka pipe-delimited). For smaller custom dictionaries those can be created. The emails should include information on creating the .xml dictionary configuration files. Sean -----Original Message----- From: Sandeep Byatha Gururaja rao [mailto:sandeep...@arisglobal.com] Sent: Tuesday, November 21, 2017 9:40 AM To: dev@ctakes.apache.org Subject: Use of custom Dictionary Descriptor file [EXTERNAL] Hi, Is there currently any way to use a custom dictionary descriptor file without making changes to the code or by rebuilding the ctakes-dictionary-lookup-fast jar file. Regards, Sandeep This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender or system manager by email immediately if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited and against the law. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender or system manager by email immediately if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited and against the law.