The old user/password method stopped working for me a week or so ago. However I was able to use the api key method after checking out the latest (as of last week) source code from subversion and building locally. The only changes I had to make was to set the environment variables ctakes.umlsaddr to https://utslogin.nlm.nih.gov/cas/v1/api-key (otherwise the old url was used) and ctakes.umls_apikey to my api key.
Roberto if you need more detailed instructions I can post them. a Le mer. 16 déc. 2020 à 06:37, Miller, Timothy < timothy.mil...@childrens.harvard.edu> a écrit : > Hi Roberto, > The existing mechanism should be functional until January 15. After > that point changes to the cTAKES code are required to use the new UMLS > authentication mechanism. We are working on this and will release patches > and/or new releases. > > Tim > > > On Wed, 2020-12-16 at 10:12 +0100, Roberto Zanoli wrote: > > * External Email - Caution * > > > > > > Dear All, > > > > I'm new to cTAKES and I'd like to analyze some texts by using > > AggregatePlaintextUMLSProcessor that requires the UMLS resource. > > > > According to the runctakesCVD file, to enable the use of the UMLS > > resources you have to set your UMLS credential, i.e., > > Dctakes.umlsuser, Dctakes.umlspw > > > > Since, UMLS Terminology Services accounts have been migrated to a > > service that allows you to sign in to UTS using Google, Microsoft, > > ... I don't have any username and password with which to set the > > variables above. Do you have any suggestions? > > > > Thanks in advance > > Roberto > > > > > > > > > > -- > > Le informazioni contenute nella presente comunicazione sono di > > natura privata e come tali sono da considerarsi riservate ed > > indirizzate esclusivamente ai destinatari indicati e per le finalità > > strettamente legate al relativo contenuto. Se avete ricevuto questo > > messaggio per errore, vi preghiamo di eliminarlo e di inviare una > > comunicazione all’indirizzo e-mail del mittente. > > -- > > The information transmitted is intended only for the person or entity > > to which it is addressed and may contain confidential and/or > > privileged material. If you received this in error, please contact > > the sender and delete the material. >
