Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS]
Ok Peter. Thanks for the update. On Wed, Nov 25, 2020 at 9:08 PM Peter Abramowitsch wrote: > Hi Gandhi > > If you hang on a bit for some of it, it will save you having to revise. > Yesterday I attached the instructions I had given for using the new code in > the trunk environment and that will give you a good overview. But there > may be some minor differences in the backport. This is because the > infrastructure for exposing environment vs system vs desc*xml variables is > a bit different and I'm still in testing mode. > > The bit that you could start with is about how to obtain your API key. > > Peter > > On Wed, Nov 25, 2020 at 3:47 PM gandhi rajan > wrote: > > > Hi Sean, > > > > Can pick up wiki update if I could get some guidance on what exactly need > > to be updated and will proceed from there. > > > > On Tue, Nov 24, 2020 at 11:53 PM Finan, Sean < > > sean.fi...@childrens.harvard.edu> wrote: > > > > > Hi Gandhi, > > > > > > That would be great! > > > > > > I think that an additional test would be useful and putting Peter's > > > documentation on the wiki is important. > > > Can you take one of those tasks? > > > Or would you like to handle something else like point release prep, web > > > site disclaimer, web site link update (to 4.1), etc.? > > > > > > Peter, is your documentation available only on your private (web) > > > directory or do you have it someplace publicly available? > > > > > > Many thanks, > > > Sean > > > > > > > > > > > > From: gandhi rajan > > > Sent: Tuesday, November 24, 2020 1:06 PM > > > To: dev@ctakes.apache.org > > > Subject: Re: Changes to UTS Authentication for Authorized Content > > > Distributors [EXTERNAL] [SUSPICIOUS] > > > > > > * External Email - Caution * > > > > > > > > > Hi Sean, > > > > > > I can take up a few things if you can guide me on the same. > > > > > > On Tue, Nov 24, 2020 at 9:59 PM Finan, Sean < > > > sean.fi...@childrens.harvard.edu> wrote: > > > > > > > Hi Tim and all, > > > > > > > > Peter kindly checked this into trunk last week. > > > > I tested that version and it seemed to work. > > > > > > > > Another question might be "how do we get this into the/a release? > > > > > > > > I haven't looked into whether or not Apache svn servers have a > locking > > > > mechanism on release branches, but if not I think that a patch of 4.0 > > > using > > > > the version that you and Greg tested should be a simple checkin. > > > > > > > > I am sure that everybody is tired of hearing me say this, but I would > > > like > > > > to get out a version 5 asap and disclaim that it is required for the > > new > > > > umls authentication. That would make patching v4 a non-issue. > > > > > > > > Regardless of repository inclusion, the documentation (also written > by > > > > Peter) needs to get to the ctakes wiki - and probably the main > ctakes > > > web > > > > site. On that note, the web site needs to be redone asap. > > > > > > > > Anyway, cheers to Peter for taking upon himself this update! > > > > We do still have a few things left to do. > > > > Volunteers? > > > > > > > > Sean > > > > > > > > > > > > From: Miller, Timothy > > > > Sent: Tuesday, November 24, 2020 11:07 AM > > > > To: dev@ctakes.apache.org > > > > Subject: Re: Changes to UTS Authentication for Authorized Content > > > > Distributors [EXTERNAL] [SUSPICIOUS] > > > > > > > > * External Email - Caution * > > > > > > > > > > > > Peter, > > > > I was able to try your changes and get this new authentication > > > > mechanism to work in the default pipeline. Peter, Sean, et al, what > are > > > > the next steps for getting this in to trunk? If you're not > comfortable > > > > checking in directly maybe you can share the patch for review. > > > > Tim > > > > > > > > On Sun, 2020-11-15 at 20:54 +0100, Peter Abramowitsch wrote: > > > > > * External Email - Caution * > > > > > > > > > > > > > &g
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS]
Hi Gandhi If you hang on a bit for some of it, it will save you having to revise. Yesterday I attached the instructions I had given for using the new code in the trunk environment and that will give you a good overview. But there may be some minor differences in the backport. This is because the infrastructure for exposing environment vs system vs desc*xml variables is a bit different and I'm still in testing mode. The bit that you could start with is about how to obtain your API key. Peter On Wed, Nov 25, 2020 at 3:47 PM gandhi rajan wrote: > Hi Sean, > > Can pick up wiki update if I could get some guidance on what exactly need > to be updated and will proceed from there. > > On Tue, Nov 24, 2020 at 11:53 PM Finan, Sean < > sean.fi...@childrens.harvard.edu> wrote: > > > Hi Gandhi, > > > > That would be great! > > > > I think that an additional test would be useful and putting Peter's > > documentation on the wiki is important. > > Can you take one of those tasks? > > Or would you like to handle something else like point release prep, web > > site disclaimer, web site link update (to 4.1), etc.? > > > > Peter, is your documentation available only on your private (web) > > directory or do you have it someplace publicly available? > > > > Many thanks, > > Sean > > > > > > ____________ > > From: gandhi rajan > > Sent: Tuesday, November 24, 2020 1:06 PM > > To: dev@ctakes.apache.org > > Subject: Re: Changes to UTS Authentication for Authorized Content > > Distributors [EXTERNAL] [SUSPICIOUS] > > > > * External Email - Caution * > > > > > > Hi Sean, > > > > I can take up a few things if you can guide me on the same. > > > > On Tue, Nov 24, 2020 at 9:59 PM Finan, Sean < > > sean.fi...@childrens.harvard.edu> wrote: > > > > > Hi Tim and all, > > > > > > Peter kindly checked this into trunk last week. > > > I tested that version and it seemed to work. > > > > > > Another question might be "how do we get this into the/a release? > > > > > > I haven't looked into whether or not Apache svn servers have a locking > > > mechanism on release branches, but if not I think that a patch of 4.0 > > using > > > the version that you and Greg tested should be a simple checkin. > > > > > > I am sure that everybody is tired of hearing me say this, but I would > > like > > > to get out a version 5 asap and disclaim that it is required for the > new > > > umls authentication. That would make patching v4 a non-issue. > > > > > > Regardless of repository inclusion, the documentation (also written by > > > Peter) needs to get to the ctakes wiki - and probably the main ctakes > > web > > > site. On that note, the web site needs to be redone asap. > > > > > > Anyway, cheers to Peter for taking upon himself this update! > > > We do still have a few things left to do. > > > Volunteers? > > > > > > Sean > > > > > > > > > From: Miller, Timothy > > > Sent: Tuesday, November 24, 2020 11:07 AM > > > To: dev@ctakes.apache.org > > > Subject: Re: Changes to UTS Authentication for Authorized Content > > > Distributors [EXTERNAL] [SUSPICIOUS] > > > > > > * External Email - Caution * > > > > > > > > > Peter, > > > I was able to try your changes and get this new authentication > > > mechanism to work in the default pipeline. Peter, Sean, et al, what are > > > the next steps for getting this in to trunk? If you're not comfortable > > > checking in directly maybe you can share the patch for review. > > > Tim > > > > > > On Sun, 2020-11-15 at 20:54 +0100, Peter Abramowitsch wrote: > > > > * External Email - Caution * > > > > > > > > > > > > Hi Greg > > > > > > > > I've got the modifications finished for the new UMLS authentication > > > > method > > > > using API keys. If you're game, I'd like you to be next to test it. > > > > Contact me at pabramowit...@gmail.com and I'll get you a new > > > > ctakes-dictionary-lookup-fast.4.0,1,x,jar and Readme. > > > > > > > > If it's smooth for you, I'll talk with Sean about checking it in and > > > > what > > > > wiki locations need to be updated. > > > > > > > > To get your key you'll need to log i
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS]
I will be done with the UmlsUserApprover 4.0.0 backport by tomorrow. It's working already but I need to try all the ways of setting the auth params. A bit of the infrastructure around CLI and Envvars in the UimaContext is different. Peter On Wed, Nov 25, 2020 at 3:08 PM Miller, Timothy < timothy.mil...@childrens.harvard.edu> wrote: > That link doesn't say anything there about incremental update releases, > but even with the normal process I think we can get 4.0.1 out faster > than usual because it is such a small change and there are unlikely to > be multiple RCs to get one that works for everyone. > Does anyone want to volunteer to be release manager? It needs to be > someone on the PMC, so Sean, myself, Gandhi, or Chen probably. > > Tim > > > On Tue, 2020-11-24 at 18:10 +, Finan, Sean wrote: > > * External Email - Caution * > > > > > > > > I haven't looked into whether or not Apache svn servers have a > > > > locking mechanism ... > > > I think it's worth checking -- if we're allowed to just branch off > > > the > > > 4.0.0 tag we can get a 4.0.1 distribution that just has this one > > > change, and we could have it built and uploaded quickly so we're > > > ready > > > for the UMLS change. How would we find out? > > > > A 4.0.1 made directly from 4.0 with only the authentication update is > > probably the way to go. > > I suppose that for people with dependencies, downloads etc. fixed at > > 4.0 would have to get their new umls key and change their ctakes > > config anyway, so telling them to update any coded version numbers > > doesn't involve too much extra effort. > > > > The main apache org how to release documentation is at > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__infra.apache.org_release-2Dpublishing.html=DwIF-g=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=Heup-IbsIg9Q1TPOylpP9FE4GTK-OqdTDRRNQXipowRLRjx0ibQrHEo8uYx6674h=QVEto_k7Ovh16r4YjW7Uelv9_lDmvjxRwoI2r7_6qBk=fjMkpO1i2FXprtFbQ-XJ1cvVlSQ8-uz3gSOBojxNMI8= > > I am not sure of anything specifically regarding patches. > > I don't know if we need to go through the full process for a point > > release ... > > > > > > ____ > > From: Miller, Timothy > > Sent: Tuesday, November 24, 2020 12:45 PM > > To: dev@ctakes.apache.org > > Subject: Re: Changes to UTS Authentication for Authorized Content > > Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] > > > > * External Email - Caution * > > > > > > On Tue, 2020-11-24 at 16:29 +, Finan, Sean wrote: > > > * External Email - Caution * > > > > > > > > > Hi Tim and all, > > > > > > Peter kindly checked this into trunk last week. > > > I tested that version and it seemed to work. > > > > > > Another question might be "how do we get this into the/a release? > > > > > > I haven't looked into whether or not Apache svn servers have a > > > locking mechanism on release branches, but if not I think that a > > > patch of 4.0 using the version that you and Greg tested should be a > > > simple checkin. > > > > I think it's worth checking -- if we're allowed to just branch off > > the > > 4.0.0 tag we can get a 4.0.1 distribution that just has this one > > change, and we could have it built and uploaded quickly so we're > > ready > > for the UMLS change. How would we find out? > > > > Tim > > > > > I am sure that everybody is tired of hearing me say this, but I > > > would > > > like to get out a version 5 asap and disclaim that it is required > > > for > > > the new umls authentication. That would make patching v4 a non- > > > issue. > > > > > > Regardless of repository inclusion, the documentation (also written > > > by Peter) needs to get to the ctakes wiki - and probably the main > > > ctakes web site. On that note, the web site needs to be redone > > > asap. > > > > > > Anyway, cheers to Peter for taking upon himself this update! > > > We do still have a few things left to do. > > > Volunteers? > > > > > > Sean > > > > > > > > > From: Miller, Timothy > > > Sent: Tuesday, November 24, 2020 11:07 AM > > > To: dev@ctakes.apache.org > > > Subject: Re: Changes to UTS Authentication for Authorized Content > > > Distributors [EXTERNAL] [SUSPICIOUS] > > > > > > * External Email - Caution *
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS]
Hi Sean, Can pick up wiki update if I could get some guidance on what exactly need to be updated and will proceed from there. On Tue, Nov 24, 2020 at 11:53 PM Finan, Sean < sean.fi...@childrens.harvard.edu> wrote: > Hi Gandhi, > > That would be great! > > I think that an additional test would be useful and putting Peter's > documentation on the wiki is important. > Can you take one of those tasks? > Or would you like to handle something else like point release prep, web > site disclaimer, web site link update (to 4.1), etc.? > > Peter, is your documentation available only on your private (web) > directory or do you have it someplace publicly available? > > Many thanks, > Sean > > > > From: gandhi rajan > Sent: Tuesday, November 24, 2020 1:06 PM > To: dev@ctakes.apache.org > Subject: Re: Changes to UTS Authentication for Authorized Content > Distributors [EXTERNAL] [SUSPICIOUS] > > * External Email - Caution * > > > Hi Sean, > > I can take up a few things if you can guide me on the same. > > On Tue, Nov 24, 2020 at 9:59 PM Finan, Sean < > sean.fi...@childrens.harvard.edu> wrote: > > > Hi Tim and all, > > > > Peter kindly checked this into trunk last week. > > I tested that version and it seemed to work. > > > > Another question might be "how do we get this into the/a release? > > > > I haven't looked into whether or not Apache svn servers have a locking > > mechanism on release branches, but if not I think that a patch of 4.0 > using > > the version that you and Greg tested should be a simple checkin. > > > > I am sure that everybody is tired of hearing me say this, but I would > like > > to get out a version 5 asap and disclaim that it is required for the new > > umls authentication. That would make patching v4 a non-issue. > > > > Regardless of repository inclusion, the documentation (also written by > > Peter) needs to get to the ctakes wiki - and probably the main ctakes > web > > site. On that note, the web site needs to be redone asap. > > > > Anyway, cheers to Peter for taking upon himself this update! > > We do still have a few things left to do. > > Volunteers? > > > > Sean > > > > > > From: Miller, Timothy > > Sent: Tuesday, November 24, 2020 11:07 AM > > To: dev@ctakes.apache.org > > Subject: Re: Changes to UTS Authentication for Authorized Content > > Distributors [EXTERNAL] [SUSPICIOUS] > > > > * External Email - Caution * > > > > > > Peter, > > I was able to try your changes and get this new authentication > > mechanism to work in the default pipeline. Peter, Sean, et al, what are > > the next steps for getting this in to trunk? If you're not comfortable > > checking in directly maybe you can share the patch for review. > > Tim > > > > On Sun, 2020-11-15 at 20:54 +0100, Peter Abramowitsch wrote: > > > * External Email - Caution * > > > > > > > > > Hi Greg > > > > > > I've got the modifications finished for the new UMLS authentication > > > method > > > using API keys. If you're game, I'd like you to be next to test it. > > > Contact me at pabramowit...@gmail.com and I'll get you a new > > > ctakes-dictionary-lookup-fast.4.0,1,x,jar and Readme. > > > > > > If it's smooth for you, I'll talk with Sean about checking it in and > > > what > > > wiki locations need to be updated. > > > > > > To get your key you'll need to log into UMLS, If you've not been > > > there > > > recently you'll need to go through their profile upgrade process > > > where user > > > details will be rerouted through one of the public authentication > > > mechanisms. > > > Once in, go to your profile section and you'll find the API_KEY. > > > > > > All of you will need to do this eventually. > > > > > > Regards > > > Peter > > > > > > Regards, Peter > > > > > > On Wed, Nov 11, 2020 at 10:13 PM Greg Silverman > > > wrote: > > > > > > > Hi Peter, > > > > Thanks, that would be great. I like the backwards compatible > > > > method. Our > > > > issue is that we have custom configurations for use in Docker and > > > > Kubernetes with UIMA-AS, so this would be ideal. > > > > > > > > Greg-- > > > > > > > > > > > > On Wed, Nov 11, 2020 at 3:
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS]
That link doesn't say anything there about incremental update releases, but even with the normal process I think we can get 4.0.1 out faster than usual because it is such a small change and there are unlikely to be multiple RCs to get one that works for everyone. Does anyone want to volunteer to be release manager? It needs to be someone on the PMC, so Sean, myself, Gandhi, or Chen probably. Tim On Tue, 2020-11-24 at 18:10 +, Finan, Sean wrote: > * External Email - Caution * > > > > > I haven't looked into whether or not Apache svn servers have a > > > locking mechanism ... > > I think it's worth checking -- if we're allowed to just branch off > > the > > 4.0.0 tag we can get a 4.0.1 distribution that just has this one > > change, and we could have it built and uploaded quickly so we're > > ready > > for the UMLS change. How would we find out? > > A 4.0.1 made directly from 4.0 with only the authentication update is > probably the way to go. > I suppose that for people with dependencies, downloads etc. fixed at > 4.0 would have to get their new umls key and change their ctakes > config anyway, so telling them to update any coded version numbers > doesn't involve too much extra effort. > > The main apache org how to release documentation is at > https://urldefense.proofpoint.com/v2/url?u=https-3A__infra.apache.org_release-2Dpublishing.html=DwIF-g=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=Heup-IbsIg9Q1TPOylpP9FE4GTK-OqdTDRRNQXipowRLRjx0ibQrHEo8uYx6674h=QVEto_k7Ovh16r4YjW7Uelv9_lDmvjxRwoI2r7_6qBk=fjMkpO1i2FXprtFbQ-XJ1cvVlSQ8-uz3gSOBojxNMI8= > > I am not sure of anything specifically regarding patches. > I don't know if we need to go through the full process for a point > release ... > > > ____ > From: Miller, Timothy > Sent: Tuesday, November 24, 2020 12:45 PM > To: dev@ctakes.apache.org > Subject: Re: Changes to UTS Authentication for Authorized Content > Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] > > * External Email - Caution * > > > On Tue, 2020-11-24 at 16:29 +, Finan, Sean wrote: > > * External Email - Caution * > > > > > > Hi Tim and all, > > > > Peter kindly checked this into trunk last week. > > I tested that version and it seemed to work. > > > > Another question might be "how do we get this into the/a release? > > > > I haven't looked into whether or not Apache svn servers have a > > locking mechanism on release branches, but if not I think that a > > patch of 4.0 using the version that you and Greg tested should be a > > simple checkin. > > I think it's worth checking -- if we're allowed to just branch off > the > 4.0.0 tag we can get a 4.0.1 distribution that just has this one > change, and we could have it built and uploaded quickly so we're > ready > for the UMLS change. How would we find out? > > Tim > > > I am sure that everybody is tired of hearing me say this, but I > > would > > like to get out a version 5 asap and disclaim that it is required > > for > > the new umls authentication. That would make patching v4 a non- > > issue. > > > > Regardless of repository inclusion, the documentation (also written > > by Peter) needs to get to the ctakes wiki - and probably the main > > ctakes web site. On that note, the web site needs to be redone > > asap. > > > > Anyway, cheers to Peter for taking upon himself this update! > > We do still have a few things left to do. > > Volunteers? > > > > Sean > > > > > > From: Miller, Timothy > > Sent: Tuesday, November 24, 2020 11:07 AM > > To: dev@ctakes.apache.org > > Subject: Re: Changes to UTS Authentication for Authorized Content > > Distributors [EXTERNAL] [SUSPICIOUS] > > > > * External Email - Caution * > > > > > > Peter, > > I was able to try your changes and get this new authentication > > mechanism to work in the default pipeline. Peter, Sean, et al, what > > are > > the next steps for getting this in to trunk? If you're not > > comfortable > > checking in directly maybe you can share the patch for review. > > Tim > > > > On Sun, 2020-11-15 at 20:54 +0100, Peter Abramowitsch wrote: > > > * External Email - Caution * > > > > > > > > > Hi Greg > > > > > > I've got the modifications finished for the new UMLS > > > authentication > > > method > > > using API keys. If you're game, I'd like you to be next to test > > > it. > > >
Re: ctakes 5.0.0 warranted ? Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS]
I agree with Sean. Its high time to churn out ctakes 5.0.0 and move forward. On Wed, Nov 25, 2020 at 3:28 AM Finan, Sean < sean.fi...@childrens.harvard.edu> wrote: > I think that trunk has enough new stuff to warrant a major release. > > I am sure that I am missing quite a few things, but some clumps of new > goodies include: > > New Modules (and components): > ctakes-fhir > ctakes-rest > ctakes-dockhand > > > New (reader, writer, AE) Components: > Case-Sensitive Dictionary Lookup > optional faster Cleartk-Assertion engines > document attribute adjusters > new JDBC writer api > - various sundry > > New Facilities, Utilities: > Builders for Annotations, CAS > Accessors for Annotations, CAS > Time normalization > - and more > > New Abstractions, "Paradigms" > Semantic Group, Type focus > Patient (grouped document) focus > Simple extendable File Readers, Writers > Stores for cross-document efforts > > Other features: > JCas Views usable via piper files > New examples (code, pipers, documents) > > ... and undoubtedly many updates to models and code that I am forgetting > or don't even know about. > > > I don't know about major incompatibilities. A few classes have been > moved, data has changed, maybe a default or two. Anybody using ctakes > 4.0.0 as a dependency may have to modify their code on a switch to trunk - > as you noticed with the relocation of DotLogger. > > Another change for a major release could be removing ytex from the main > package and making it a separate build (and deprecated). Anything that > people love in ytex can be moved elsewhere in ctakes. There is a lot to > discuss here and I might be one of only a few that feel a weaker coupling > is useful, but that would be a big change. > > > Sean > > > ____________ > From: Peter Abramowitsch > Sent: Tuesday, November 24, 2020 4:19 PM > To: dev@ctakes.apache.org > Subject: Re: Changes to UTS Authentication for Authorized Content > Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] > > * External Email - Caution * > > > Sounds reasonable, but just a thought: Are the changes in trunk > sufficient to warrant a new major release? Are there major structural or > compatibility issues between 4.0 and trunk? - it doesn’t strike me that > there areHow about 4.0.0 going to 4.0.1 and trunk becoming > 4.1.0-SNAPSHOT? I.e. a new feature release... when it comes. > > Peter > > Sent from my iPad > > > On Nov 24, 2020, at 22:10, Finan, Sean > wrote: > > > > Webapp email is killing me ... that email was sent prematurely. > > > >> ctakes-4.0.0-rc3to ctakes-4.0.1 > > > > I think that is certainly one way to do it. > > > > One could checkout the branch > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__svn.apache.org_repos_asf_ctakes_branches_ctakes-2D4.0.0_=DwIFaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=xeFeUaJNuo194Tf0hhctytlRcvlCCK5kSTbEov9k7fI=L-tssYfMezM1lM2e5BDWecnnc0VXLcfLBNju58Nabsc= > > and make the changes to that code. > > > > Would the method be: > > 1. Checkout 4.0.0 branch > > 2. Apply the patch > > 3. Continue with the full release process, checkin and tag 4.0.1 ? > > 4. Keep working on trunk for the next release > > 5. Change the version numbers in trunk to ctakes-5.0.0-SNAPSHOT > > ^- this would force all external projects using trunk to update their > dependency version. > > > > Let us keep this rolling, > > Sean > > > > From: Finan, Sean > > Sent: Tuesday, November 24, 2020 4:02 PM > > To: dev@ctakes.apache.org > > Subject: Re: Changes to UTS Authentication for Authorized Content > Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] > > > > * External Email - Caution * > > > > > >> ctakes-4.0.0-rc3to ctakes-4.0.1 > > > > I think that is certainly one way to do it. > > > > One could checkout the branch > > > > Would the method be: > > 1. Checkout 4.0.0-rc3 > > 2. Apply the patch > > 3. Continue with the full release process, checkin and tag? > > 4. Keep working on trunk for the next release > > > > > > > > From: Miller, Timothy > > Sent: Tuesday, November 24, 2020 2:22 PM > > To: dev@ctakes.apache.org > > Subject: Re: Changes to UTS Authentication for Authorized Content > Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS]
>the hope (at least my hope!) was that if we could get out a 4.0.0.0.0.1 release with just this change Agreed. I don't want to force refactoring upon any 4.0.0 users if they only need the authentication update. From: Miller, Timothy Sent: Tuesday, November 24, 2020 4:22 PM To: dev@ctakes.apache.org Subject: Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] * External Email - Caution * There's no doubt, maybe even 5.0.0 could be justified, but the hope (at least my hope!) was that if we could get out a 4.0.0.0.0.1 release with just this change, it would satisfy anyone who just wants to make sure their setup still works when the NLM switches off the REST server. Tim On Tue, 2020-11-24 at 22:19 +0100, Peter Abramowitsch wrote: > * External Email - Caution * > > > Sounds reasonable, but just a thought: Are the changes in trunk > sufficient to warrant a new major release? Are there major > structural or compatibility issues between 4.0 and trunk? - it > doesn’t strike me that there areHow about 4.0.0 going to 4.0.1 > and trunk becoming 4.1.0-SNAPSHOT? I.e. a new feature release... > when it comes. > > Peter > > Sent from my iPad > > > On Nov 24, 2020, at 22:10, Finan, Sean < > > sean.fi...@childrens.harvard.edu> wrote: > > > > Webapp email is killing me ... that email was sent prematurely. > > > > > ctakes-4.0.0-rc3to ctakes-4.0.1 > > > > I think that is certainly one way to do it. > > > > One could checkout the branch > > https://urldefense.proofpoint.com/v2/url?u=https-3A__svn.apache.org_repos_asf_ctakes_branches_ctakes-2D4.0.0_=DwIFaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=Heup-IbsIg9Q1TPOylpP9FE4GTK-OqdTDRRNQXipowRLRjx0ibQrHEo8uYx6674h=m8k3ufZy2nG7f3SJkq_l7KQvGiWF_Z2l4hcEJkYLGP0=k_mq8OPmtWdlvyj5tITQHfONr0GiO2Akx-eyT6FbVdQ= > > and make the changes to that code. > > > > Would the method be: > > 1. Checkout 4.0.0 branch > > 2. Apply the patch > > 3. Continue with the full release process, checkin and tag 4.0.1 ? > > 4. Keep working on trunk for the next release > > 5. Change the version numbers in trunk to ctakes-5.0.0-SNAPSHOT > > ^- this would force all external projects using trunk to update > > their dependency version. > > > > Let us keep this rolling, > > Sean > > ____ > > From: Finan, Sean > > Sent: Tuesday, November 24, 2020 4:02 PM > > To: dev@ctakes.apache.org > > Subject: Re: Changes to UTS Authentication for Authorized Content > > Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] > > [SUSPICIOUS] > > > > * External Email - Caution * > > > > > > > ctakes-4.0.0-rc3to ctakes-4.0.1 > > > > I think that is certainly one way to do it. > > > > One could checkout the branch > > > > Would the method be: > > 1. Checkout 4.0.0-rc3 > > 2. Apply the patch > > 3. Continue with the full release process, checkin and tag? > > 4. Keep working on trunk for the next release > > > > > > > > From: Miller, Timothy > > Sent: Tuesday, November 24, 2020 2:22 PM > > To: dev@ctakes.apache.org > > Subject: Re: Changes to UTS Authentication for Authorized Content > > Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] > > > > * External Email - Caution * > > > > > > Specifically, is the way to go to branch from the tag at: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__svn.apache.org_repos_asf_ctakes_tags_ctakes-2D4.0.0-2Drc3=DwIGaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=FQFm_YbfeRux_ry1zWBtjd3hgCIPEZvQqmrh1W9UAVE=F1goCJ3-zDm3bXn-8Z-aBDBSeOhu6U8vMwtDGnmxTE4= > > > > (the latest release candidate before release I believe) > > into > > https://urldefense.proofpoint.com/v2/url?u=https-3A__svn.apache.org_repos_asf_ctakes_tags_ctakes-2D4.0.1=DwIGaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=FQFm_YbfeRux_ry1zWBtjd3hgCIPEZvQqmrh1W9UAVE=5acAKSY9--DM3OWA_Kl4H7Uwt7AGhttmPYKUzdnYLEY= > > > > ? > > > > Tim > > > > > On Tue, 2020-11-24 at 20:14 +0100, Peter Abramowitsch wrote: > > > * External Email - Caution * > > > > > > > > > Right, then. > > > I'll get that done. > > > > > > Peter > > > > > > On Tue, Nov 24, 2020 at 7:53 PM Finan, Sean < > > > sean.fi...@childrens.harvard.edu>
ctakes 5.0.0 warranted ? Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS]
I think that trunk has enough new stuff to warrant a major release. I am sure that I am missing quite a few things, but some clumps of new goodies include: New Modules (and components): ctakes-fhir ctakes-rest ctakes-dockhand New (reader, writer, AE) Components: Case-Sensitive Dictionary Lookup optional faster Cleartk-Assertion engines document attribute adjusters new JDBC writer api - various sundry New Facilities, Utilities: Builders for Annotations, CAS Accessors for Annotations, CAS Time normalization - and more New Abstractions, "Paradigms" Semantic Group, Type focus Patient (grouped document) focus Simple extendable File Readers, Writers Stores for cross-document efforts Other features: JCas Views usable via piper files New examples (code, pipers, documents) ... and undoubtedly many updates to models and code that I am forgetting or don't even know about. I don't know about major incompatibilities. A few classes have been moved, data has changed, maybe a default or two. Anybody using ctakes 4.0.0 as a dependency may have to modify their code on a switch to trunk - as you noticed with the relocation of DotLogger. Another change for a major release could be removing ytex from the main package and making it a separate build (and deprecated). Anything that people love in ytex can be moved elsewhere in ctakes. There is a lot to discuss here and I might be one of only a few that feel a weaker coupling is useful, but that would be a big change. Sean From: Peter Abramowitsch Sent: Tuesday, November 24, 2020 4:19 PM To: dev@ctakes.apache.org Subject: Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] * External Email - Caution * Sounds reasonable, but just a thought: Are the changes in trunk sufficient to warrant a new major release? Are there major structural or compatibility issues between 4.0 and trunk? - it doesn’t strike me that there areHow about 4.0.0 going to 4.0.1 and trunk becoming 4.1.0-SNAPSHOT? I.e. a new feature release... when it comes. Peter Sent from my iPad > On Nov 24, 2020, at 22:10, Finan, Sean > wrote: > > Webapp email is killing me ... that email was sent prematurely. > >> ctakes-4.0.0-rc3to ctakes-4.0.1 > > I think that is certainly one way to do it. > > One could checkout the branch > https://urldefense.proofpoint.com/v2/url?u=https-3A__svn.apache.org_repos_asf_ctakes_branches_ctakes-2D4.0.0_=DwIFaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=xeFeUaJNuo194Tf0hhctytlRcvlCCK5kSTbEov9k7fI=L-tssYfMezM1lM2e5BDWecnnc0VXLcfLBNju58Nabsc= > and make the changes to that code. > > Would the method be: > 1. Checkout 4.0.0 branch > 2. Apply the patch > 3. Continue with the full release process, checkin and tag 4.0.1 ? > 4. Keep working on trunk for the next release > 5. Change the version numbers in trunk to ctakes-5.0.0-SNAPSHOT > ^- this would force all external projects using trunk to update their > dependency version. > > Let us keep this rolling, > Sean > > From: Finan, Sean > Sent: Tuesday, November 24, 2020 4:02 PM > To: dev@ctakes.apache.org > Subject: Re: Changes to UTS Authentication for Authorized Content > Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] > > * External Email - Caution * > > >> ctakes-4.0.0-rc3to ctakes-4.0.1 > > I think that is certainly one way to do it. > > One could checkout the branch > > Would the method be: > 1. Checkout 4.0.0-rc3 > 2. Apply the patch > 3. Continue with the full release process, checkin and tag? > 4. Keep working on trunk for the next release > > > ________________ > From: Miller, Timothy > Sent: Tuesday, November 24, 2020 2:22 PM > To: dev@ctakes.apache.org > Subject: Re: Changes to UTS Authentication for Authorized Content > Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] > > * External Email - Caution * > > > Specifically, is the way to go to branch from the tag at: > https://urldefense.proofpoint.com/v2/url?u=https-3A__svn.apache.org_repos_asf_ctakes_tags_ctakes-2D4.0.0-2Drc3=DwIGaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=FQFm_YbfeRux_ry1zWBtjd3hgCIPEZvQqmrh1W9UAVE=F1goCJ3-zDm3bXn-8Z-aBDBSeOhu6U8vMwtDGnmxTE4= > > (the latest release candidate before release I believe) > into > https://urldefense.proofpoint.com/v2/url?u=https-3A__svn.apache.org_repos_asf_ctakes_tags_ctakes-2D4.0.1=DwIGaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=FQFm_YbfeRux_ry1zWBtjd3hgCIPEZvQqmrh1W9UAVE=5acAKSY9--DM3OWA_Kl4H7Uwt7AGh
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS]
There's no doubt, maybe even 5.0.0 could be justified, but the hope (at least my hope!) was that if we could get out a 4.0.0.0.0.1 release with just this change, it would satisfy anyone who just wants to make sure their setup still works when the NLM switches off the REST server. Tim On Tue, 2020-11-24 at 22:19 +0100, Peter Abramowitsch wrote: > * External Email - Caution * > > > Sounds reasonable, but just a thought: Are the changes in trunk > sufficient to warrant a new major release? Are there major > structural or compatibility issues between 4.0 and trunk? - it > doesn’t strike me that there areHow about 4.0.0 going to 4.0.1 > and trunk becoming 4.1.0-SNAPSHOT? I.e. a new feature release... > when it comes. > > Peter > > Sent from my iPad > > > On Nov 24, 2020, at 22:10, Finan, Sean < > > sean.fi...@childrens.harvard.edu> wrote: > > > > Webapp email is killing me ... that email was sent prematurely. > > > > > ctakes-4.0.0-rc3to ctakes-4.0.1 > > > > I think that is certainly one way to do it. > > > > One could checkout the branch > > https://urldefense.proofpoint.com/v2/url?u=https-3A__svn.apache.org_repos_asf_ctakes_branches_ctakes-2D4.0.0_=DwIFaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=Heup-IbsIg9Q1TPOylpP9FE4GTK-OqdTDRRNQXipowRLRjx0ibQrHEo8uYx6674h=m8k3ufZy2nG7f3SJkq_l7KQvGiWF_Z2l4hcEJkYLGP0=k_mq8OPmtWdlvyj5tITQHfONr0GiO2Akx-eyT6FbVdQ= > > > > and make the changes to that code. > > > > Would the method be: > > 1. Checkout 4.0.0 branch > > 2. Apply the patch > > 3. Continue with the full release process, checkin and tag 4.0.1 ? > > 4. Keep working on trunk for the next release > > 5. Change the version numbers in trunk to ctakes-5.0.0-SNAPSHOT > > ^- this would force all external projects using trunk to update > > their dependency version. > > > > Let us keep this rolling, > > Sean > > ____ > > From: Finan, Sean > > Sent: Tuesday, November 24, 2020 4:02 PM > > To: dev@ctakes.apache.org > > Subject: Re: Changes to UTS Authentication for Authorized Content > > Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] > > [SUSPICIOUS] > > > > * External Email - Caution * > > > > > > > ctakes-4.0.0-rc3to ctakes-4.0.1 > > > > I think that is certainly one way to do it. > > > > One could checkout the branch > > > > Would the method be: > > 1. Checkout 4.0.0-rc3 > > 2. Apply the patch > > 3. Continue with the full release process, checkin and tag? > > 4. Keep working on trunk for the next release > > > > > > > > From: Miller, Timothy > > Sent: Tuesday, November 24, 2020 2:22 PM > > To: dev@ctakes.apache.org > > Subject: Re: Changes to UTS Authentication for Authorized Content > > Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] > > > > * External Email - Caution * > > > > > > Specifically, is the way to go to branch from the tag at: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__svn.apache.org_repos_asf_ctakes_tags_ctakes-2D4.0.0-2Drc3=DwIGaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=FQFm_YbfeRux_ry1zWBtjd3hgCIPEZvQqmrh1W9UAVE=F1goCJ3-zDm3bXn-8Z-aBDBSeOhu6U8vMwtDGnmxTE4= > > > > (the latest release candidate before release I believe) > > into > > https://urldefense.proofpoint.com/v2/url?u=https-3A__svn.apache.org_repos_asf_ctakes_tags_ctakes-2D4.0.1=DwIGaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=FQFm_YbfeRux_ry1zWBtjd3hgCIPEZvQqmrh1W9UAVE=5acAKSY9--DM3OWA_Kl4H7Uwt7AGhttmPYKUzdnYLEY= > > > > ? > > > > Tim > > > > > On Tue, 2020-11-24 at 20:14 +0100, Peter Abramowitsch wrote: > > > * External Email - Caution * > > > > > > > > > Right, then. > > > I'll get that done. > > > > > > Peter > > > > > > On Tue, Nov 24, 2020 at 7:53 PM Finan, Sean < > > > sean.fi...@childrens.harvard.edu> wrote: > > > > > > > I think so. Whether we can 'release' it or not, branching code > > > > from the > > > > 4.0 release is probably a first step. > > > > > > > > From: Peter Abramowitsch > > > > Sent: Tuesday, November 24, 2020 1:23 PM > > > > To: dev@ctakes.apache.org > > > > Subject: Re: Changes to UTS Authentication f
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS]
Sounds reasonable, but just a thought: Are the changes in trunk sufficient to warrant a new major release? Are there major structural or compatibility issues between 4.0 and trunk? - it doesn’t strike me that there areHow about 4.0.0 going to 4.0.1 and trunk becoming 4.1.0-SNAPSHOT? I.e. a new feature release... when it comes. Peter Sent from my iPad > On Nov 24, 2020, at 22:10, Finan, Sean > wrote: > > Webapp email is killing me ... that email was sent prematurely. > >> ctakes-4.0.0-rc3to ctakes-4.0.1 > > I think that is certainly one way to do it. > > One could checkout the branch > https://svn.apache.org/repos/asf/ctakes/branches/ctakes-4.0.0/ > and make the changes to that code. > > Would the method be: > 1. Checkout 4.0.0 branch > 2. Apply the patch > 3. Continue with the full release process, checkin and tag 4.0.1 ? > 4. Keep working on trunk for the next release > 5. Change the version numbers in trunk to ctakes-5.0.0-SNAPSHOT > ^- this would force all external projects using trunk to update their > dependency version. > > Let us keep this rolling, > Sean > > From: Finan, Sean > Sent: Tuesday, November 24, 2020 4:02 PM > To: dev@ctakes.apache.org > Subject: Re: Changes to UTS Authentication for Authorized Content > Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] > > * External Email - Caution * > > >> ctakes-4.0.0-rc3to ctakes-4.0.1 > > I think that is certainly one way to do it. > > One could checkout the branch > > Would the method be: > 1. Checkout 4.0.0-rc3 > 2. Apply the patch > 3. Continue with the full release process, checkin and tag? > 4. Keep working on trunk for the next release > > > ____________ > From: Miller, Timothy > Sent: Tuesday, November 24, 2020 2:22 PM > To: dev@ctakes.apache.org > Subject: Re: Changes to UTS Authentication for Authorized Content > Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] > > * External Email - Caution * > > > Specifically, is the way to go to branch from the tag at: > https://urldefense.proofpoint.com/v2/url?u=https-3A__svn.apache.org_repos_asf_ctakes_tags_ctakes-2D4.0.0-2Drc3=DwIGaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=FQFm_YbfeRux_ry1zWBtjd3hgCIPEZvQqmrh1W9UAVE=F1goCJ3-zDm3bXn-8Z-aBDBSeOhu6U8vMwtDGnmxTE4= > > (the latest release candidate before release I believe) > into > https://urldefense.proofpoint.com/v2/url?u=https-3A__svn.apache.org_repos_asf_ctakes_tags_ctakes-2D4.0.1=DwIGaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=FQFm_YbfeRux_ry1zWBtjd3hgCIPEZvQqmrh1W9UAVE=5acAKSY9--DM3OWA_Kl4H7Uwt7AGhttmPYKUzdnYLEY= > > ? > > Tim > >> On Tue, 2020-11-24 at 20:14 +0100, Peter Abramowitsch wrote: >> * External Email - Caution * >> >> >> Right, then. >> I'll get that done. >> >> Peter >> >> On Tue, Nov 24, 2020 at 7:53 PM Finan, Sean < >> sean.fi...@childrens.harvard.edu> wrote: >> >>> I think so. Whether we can 'release' it or not, branching code >>> from the >>> 4.0 release is probably a first step. >>> >>> From: Peter Abramowitsch >>> Sent: Tuesday, November 24, 2020 1:23 PM >>> To: dev@ctakes.apache.org >>> Subject: Re: Changes to UTS Authentication for Authorized Content >>> Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] >>> >>> * External Email - Caution * >>> >>> >>> Sean >>> >>> In the meantime, I think I have the 4.0.0 source somewhere. I can >>> take my >>> copy which is early 4.0.1 and make whatever small changes are >>> needed (if >>> any) to get it to build in 4.0.0. Would that be useful? >>> >>> Peter >>> >>> On Tue, Nov 24, 2020 at 6:46 PM Miller, Timothy < >>> timothy.mil...@childrens.harvard.edu> wrote: >>> >>>>> On Tue, 2020-11-24 at 16:29 +, Finan, Sean wrote: >>>>> * External Email - Caution * >>>>> >>>>> >>>>> Hi Tim and all, >>>>> >>>>> Peter kindly checked this into trunk last week. >>>>> I tested that version and it seemed to work. >>>>> >>>>> Another question might be "how do we get this into the/a >>>>> release? >>>>> >>>>> I haven't looked into whether or not Apache svn s
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS]
Webapp email is killing me ... that email was sent prematurely. > ctakes-4.0.0-rc3to ctakes-4.0.1 I think that is certainly one way to do it. One could checkout the branch https://svn.apache.org/repos/asf/ctakes/branches/ctakes-4.0.0/ and make the changes to that code. Would the method be: 1. Checkout 4.0.0 branch 2. Apply the patch 3. Continue with the full release process, checkin and tag 4.0.1 ? 4. Keep working on trunk for the next release 5. Change the version numbers in trunk to ctakes-5.0.0-SNAPSHOT ^- this would force all external projects using trunk to update their dependency version. Let us keep this rolling, Sean From: Finan, Sean Sent: Tuesday, November 24, 2020 4:02 PM To: dev@ctakes.apache.org Subject: Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] * External Email - Caution * > ctakes-4.0.0-rc3to ctakes-4.0.1 I think that is certainly one way to do it. One could checkout the branch Would the method be: 1. Checkout 4.0.0-rc3 2. Apply the patch 3. Continue with the full release process, checkin and tag? 4. Keep working on trunk for the next release From: Miller, Timothy Sent: Tuesday, November 24, 2020 2:22 PM To: dev@ctakes.apache.org Subject: Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] * External Email - Caution * Specifically, is the way to go to branch from the tag at: https://urldefense.proofpoint.com/v2/url?u=https-3A__svn.apache.org_repos_asf_ctakes_tags_ctakes-2D4.0.0-2Drc3=DwIGaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=FQFm_YbfeRux_ry1zWBtjd3hgCIPEZvQqmrh1W9UAVE=F1goCJ3-zDm3bXn-8Z-aBDBSeOhu6U8vMwtDGnmxTE4= (the latest release candidate before release I believe) into https://urldefense.proofpoint.com/v2/url?u=https-3A__svn.apache.org_repos_asf_ctakes_tags_ctakes-2D4.0.1=DwIGaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=FQFm_YbfeRux_ry1zWBtjd3hgCIPEZvQqmrh1W9UAVE=5acAKSY9--DM3OWA_Kl4H7Uwt7AGhttmPYKUzdnYLEY= ? Tim On Tue, 2020-11-24 at 20:14 +0100, Peter Abramowitsch wrote: > * External Email - Caution * > > > Right, then. > I'll get that done. > > Peter > > On Tue, Nov 24, 2020 at 7:53 PM Finan, Sean < > sean.fi...@childrens.harvard.edu> wrote: > > > I think so. Whether we can 'release' it or not, branching code > > from the > > 4.0 release is probably a first step. > > > > From: Peter Abramowitsch > > Sent: Tuesday, November 24, 2020 1:23 PM > > To: dev@ctakes.apache.org > > Subject: Re: Changes to UTS Authentication for Authorized Content > > Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] > > > > * External Email - Caution * > > > > > > Sean > > > > In the meantime, I think I have the 4.0.0 source somewhere. I can > > take my > > copy which is early 4.0.1 and make whatever small changes are > > needed (if > > any) to get it to build in 4.0.0. Would that be useful? > > > > Peter > > > > On Tue, Nov 24, 2020 at 6:46 PM Miller, Timothy < > > timothy.mil...@childrens.harvard.edu> wrote: > > > > > On Tue, 2020-11-24 at 16:29 +, Finan, Sean wrote: > > > > * External Email - Caution * > > > > > > > > > > > > Hi Tim and all, > > > > > > > > Peter kindly checked this into trunk last week. > > > > I tested that version and it seemed to work. > > > > > > > > Another question might be "how do we get this into the/a > > > > release? > > > > > > > > I haven't looked into whether or not Apache svn servers have a > > > > locking mechanism on release branches, but if not I think that > > > > a > > > > patch of 4.0 using the version that you and Greg tested should > > > > be a > > > > simple checkin. > > > > > > I think it's worth checking -- if we're allowed to just branch > > > off the > > > 4.0.0 tag we can get a 4.0.1 distribution that just has this one > > > change, and we could have it built and uploaded quickly so we're > > > ready > > > for the UMLS change. How would we find out? > > > > > > Tim > > > > > > > I am sure that everybody is tired of hearing me say this, but I > > > > would > > > > like to get out a version 5 asap and disclaim that it is > > > > required for > > > > the new umls authen
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS]
> ctakes-4.0.0-rc3to ctakes-4.0.1 I think that is certainly one way to do it. One could checkout the branch Would the method be: 1. Checkout 4.0.0-rc3 2. Apply the patch 3. Continue with the full release process, checkin and tag? 4. Keep working on trunk for the next release From: Miller, Timothy Sent: Tuesday, November 24, 2020 2:22 PM To: dev@ctakes.apache.org Subject: Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] * External Email - Caution * Specifically, is the way to go to branch from the tag at: https://urldefense.proofpoint.com/v2/url?u=https-3A__svn.apache.org_repos_asf_ctakes_tags_ctakes-2D4.0.0-2Drc3=DwIGaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=FQFm_YbfeRux_ry1zWBtjd3hgCIPEZvQqmrh1W9UAVE=F1goCJ3-zDm3bXn-8Z-aBDBSeOhu6U8vMwtDGnmxTE4= (the latest release candidate before release I believe) into https://urldefense.proofpoint.com/v2/url?u=https-3A__svn.apache.org_repos_asf_ctakes_tags_ctakes-2D4.0.1=DwIGaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=FQFm_YbfeRux_ry1zWBtjd3hgCIPEZvQqmrh1W9UAVE=5acAKSY9--DM3OWA_Kl4H7Uwt7AGhttmPYKUzdnYLEY= ? Tim On Tue, 2020-11-24 at 20:14 +0100, Peter Abramowitsch wrote: > * External Email - Caution * > > > Right, then. > I'll get that done. > > Peter > > On Tue, Nov 24, 2020 at 7:53 PM Finan, Sean < > sean.fi...@childrens.harvard.edu> wrote: > > > I think so. Whether we can 'release' it or not, branching code > > from the > > 4.0 release is probably a first step. > > > > From: Peter Abramowitsch > > Sent: Tuesday, November 24, 2020 1:23 PM > > To: dev@ctakes.apache.org > > Subject: Re: Changes to UTS Authentication for Authorized Content > > Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] > > > > * External Email - Caution * > > > > > > Sean > > > > In the meantime, I think I have the 4.0.0 source somewhere. I can > > take my > > copy which is early 4.0.1 and make whatever small changes are > > needed (if > > any) to get it to build in 4.0.0. Would that be useful? > > > > Peter > > > > On Tue, Nov 24, 2020 at 6:46 PM Miller, Timothy < > > timothy.mil...@childrens.harvard.edu> wrote: > > > > > On Tue, 2020-11-24 at 16:29 +, Finan, Sean wrote: > > > > * External Email - Caution * > > > > > > > > > > > > Hi Tim and all, > > > > > > > > Peter kindly checked this into trunk last week. > > > > I tested that version and it seemed to work. > > > > > > > > Another question might be "how do we get this into the/a > > > > release? > > > > > > > > I haven't looked into whether or not Apache svn servers have a > > > > locking mechanism on release branches, but if not I think that > > > > a > > > > patch of 4.0 using the version that you and Greg tested should > > > > be a > > > > simple checkin. > > > > > > I think it's worth checking -- if we're allowed to just branch > > > off the > > > 4.0.0 tag we can get a 4.0.1 distribution that just has this one > > > change, and we could have it built and uploaded quickly so we're > > > ready > > > for the UMLS change. How would we find out? > > > > > > Tim > > > > > > > I am sure that everybody is tired of hearing me say this, but I > > > > would > > > > like to get out a version 5 asap and disclaim that it is > > > > required for > > > > the new umls authentication. That would make patching v4 a > > > > non- > > > > issue. > > > > > > > > Regardless of repository inclusion, the documentation (also > > > > written > > > > by Peter) needs to get to the ctakes wiki - and probably the > > > > main > > > > ctakes web site. On that note, the web site needs to be redone > > > > asap. > > > > > > > > Anyway, cheers to Peter for taking upon himself this update! > > > > We do still have a few things left to do. > > > > Volunteers? > > > > > > > > Sean > > > > > > > > > > > > From: Miller, Timothy > > > > Sent: Tuesday, November 24, 2020 11:07 AM > > > > To: dev@ctakes.apache.org > > > > Subject: Re: Changes to
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS]
Right, then. I'll get that done. Peter On Tue, Nov 24, 2020 at 7:53 PM Finan, Sean < sean.fi...@childrens.harvard.edu> wrote: > I think so. Whether we can 'release' it or not, branching code from the > 4.0 release is probably a first step. > > From: Peter Abramowitsch > Sent: Tuesday, November 24, 2020 1:23 PM > To: dev@ctakes.apache.org > Subject: Re: Changes to UTS Authentication for Authorized Content > Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] > > * External Email - Caution * > > > Sean > > In the meantime, I think I have the 4.0.0 source somewhere. I can take my > copy which is early 4.0.1 and make whatever small changes are needed (if > any) to get it to build in 4.0.0. Would that be useful? > > Peter > > On Tue, Nov 24, 2020 at 6:46 PM Miller, Timothy < > timothy.mil...@childrens.harvard.edu> wrote: > > > On Tue, 2020-11-24 at 16:29 +, Finan, Sean wrote: > > > * External Email - Caution * > > > > > > > > > Hi Tim and all, > > > > > > Peter kindly checked this into trunk last week. > > > I tested that version and it seemed to work. > > > > > > Another question might be "how do we get this into the/a release? > > > > > > I haven't looked into whether or not Apache svn servers have a > > > locking mechanism on release branches, but if not I think that a > > > patch of 4.0 using the version that you and Greg tested should be a > > > simple checkin. > > > > I think it's worth checking -- if we're allowed to just branch off the > > 4.0.0 tag we can get a 4.0.1 distribution that just has this one > > change, and we could have it built and uploaded quickly so we're ready > > for the UMLS change. How would we find out? > > > > Tim > > > > > > > > I am sure that everybody is tired of hearing me say this, but I would > > > like to get out a version 5 asap and disclaim that it is required for > > > the new umls authentication. That would make patching v4 a non- > > > issue. > > > > > > Regardless of repository inclusion, the documentation (also written > > > by Peter) needs to get to the ctakes wiki - and probably the main > > > ctakes web site. On that note, the web site needs to be redone > > > asap. > > > > > > Anyway, cheers to Peter for taking upon himself this update! > > > We do still have a few things left to do. > > > Volunteers? > > > > > > Sean > > > > > > > > > From: Miller, Timothy > > > Sent: Tuesday, November 24, 2020 11:07 AM > > > To: dev@ctakes.apache.org > > > Subject: Re: Changes to UTS Authentication for Authorized Content > > > Distributors [EXTERNAL] [SUSPICIOUS] > > > > > > * External Email - Caution * > > > > > > > > > Peter, > > > I was able to try your changes and get this new authentication > > > mechanism to work in the default pipeline. Peter, Sean, et al, what > > > are > > > the next steps for getting this in to trunk? If you're not > > > comfortable > > > checking in directly maybe you can share the patch for review. > > > Tim > > > > > > On Sun, 2020-11-15 at 20:54 +0100, Peter Abramowitsch wrote: > > > > * External Email - Caution * > > > > > > > > > > > > Hi Greg > > > > > > > > I've got the modifications finished for the new UMLS authentication > > > > method > > > > using API keys. If you're game, I'd like you to be next to test > > > > it. > > > > Contact me at pabramowit...@gmail.com and I'll get you a new > > > > ctakes-dictionary-lookup-fast.4.0,1,x,jar and Readme. > > > > > > > > If it's smooth for you, I'll talk with Sean about checking it in > > > > and > > > > what > > > > wiki locations need to be updated. > > > > > > > > To get your key you'll need to log into UMLS, If you've not > > > > been > > > > there > > > > recently you'll need to go through their profile upgrade process > > > > where user > > > > details will be rerouted through one of the public authentication > > > > mechanisms. > > > > Once in, go to your profile section and you'll find the API_KEY. > > > > > > > > All of you will need to do this eventually. > > > > >
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS]
I think so. Whether we can 'release' it or not, branching code from the 4.0 release is probably a first step. From: Peter Abramowitsch Sent: Tuesday, November 24, 2020 1:23 PM To: dev@ctakes.apache.org Subject: Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] * External Email - Caution * Sean In the meantime, I think I have the 4.0.0 source somewhere. I can take my copy which is early 4.0.1 and make whatever small changes are needed (if any) to get it to build in 4.0.0. Would that be useful? Peter On Tue, Nov 24, 2020 at 6:46 PM Miller, Timothy < timothy.mil...@childrens.harvard.edu> wrote: > On Tue, 2020-11-24 at 16:29 +, Finan, Sean wrote: > > * External Email - Caution * > > > > > > Hi Tim and all, > > > > Peter kindly checked this into trunk last week. > > I tested that version and it seemed to work. > > > > Another question might be "how do we get this into the/a release? > > > > I haven't looked into whether or not Apache svn servers have a > > locking mechanism on release branches, but if not I think that a > > patch of 4.0 using the version that you and Greg tested should be a > > simple checkin. > > I think it's worth checking -- if we're allowed to just branch off the > 4.0.0 tag we can get a 4.0.1 distribution that just has this one > change, and we could have it built and uploaded quickly so we're ready > for the UMLS change. How would we find out? > > Tim > > > > > I am sure that everybody is tired of hearing me say this, but I would > > like to get out a version 5 asap and disclaim that it is required for > > the new umls authentication. That would make patching v4 a non- > > issue. > > > > Regardless of repository inclusion, the documentation (also written > > by Peter) needs to get to the ctakes wiki - and probably the main > > ctakes web site. On that note, the web site needs to be redone > > asap. > > > > Anyway, cheers to Peter for taking upon himself this update! > > We do still have a few things left to do. > > Volunteers? > > > > Sean > > > > ____ > > From: Miller, Timothy > > Sent: Tuesday, November 24, 2020 11:07 AM > > To: dev@ctakes.apache.org > > Subject: Re: Changes to UTS Authentication for Authorized Content > > Distributors [EXTERNAL] [SUSPICIOUS] > > > > * External Email - Caution * > > > > > > Peter, > > I was able to try your changes and get this new authentication > > mechanism to work in the default pipeline. Peter, Sean, et al, what > > are > > the next steps for getting this in to trunk? If you're not > > comfortable > > checking in directly maybe you can share the patch for review. > > Tim > > > > On Sun, 2020-11-15 at 20:54 +0100, Peter Abramowitsch wrote: > > > * External Email - Caution * > > > > > > > > > Hi Greg > > > > > > I've got the modifications finished for the new UMLS authentication > > > method > > > using API keys. If you're game, I'd like you to be next to test > > > it. > > > Contact me at pabramowit...@gmail.com and I'll get you a new > > > ctakes-dictionary-lookup-fast.4.0,1,x,jar and Readme. > > > > > > If it's smooth for you, I'll talk with Sean about checking it in > > > and > > > what > > > wiki locations need to be updated. > > > > > > To get your key you'll need to log into UMLS, If you've not > > > been > > > there > > > recently you'll need to go through their profile upgrade process > > > where user > > > details will be rerouted through one of the public authentication > > > mechanisms. > > > Once in, go to your profile section and you'll find the API_KEY. > > > > > > All of you will need to do this eventually. > > > > > > Regards > > > Peter > > > > > > Regards, Peter > > > > > > On Wed, Nov 11, 2020 at 10:13 PM Greg Silverman < > > > g...@umn.edu.invalid> > > > wrote: > > > > > > > Hi Peter, > > > > Thanks, that would be great. I like the backwards compatible > > > > method. Our > > > > issue is that we have custom configurations for use in Docker and > > > > Kubernetes with UIMA-AS, so this would be ideal. > > > > > > > > Greg-- > > > > > > > > > > > > On Wed, Nov 11, 2020 at 3:
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS]
That came through for me. Thanks From: Peter Abramowitsch Sent: Tuesday, November 24, 2020 1:25 PM To: dev@ctakes.apache.org Subject: Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] * External Email - Caution * I can attach it here if attachments are allowed. On Tue, Nov 24, 2020 at 7:23 PM Finan, Sean mailto:sean.fi...@childrens.harvard.edu>> wrote: Hi Gandhi, That would be great! I think that an additional test would be useful and putting Peter's documentation on the wiki is important. Can you take one of those tasks? Or would you like to handle something else like point release prep, web site disclaimer, web site link update (to 4.1), etc.? Peter, is your documentation available only on your private (web) directory or do you have it someplace publicly available? Many thanks, Sean From: gandhi rajan mailto:gandhiraja...@gmail.com>> Sent: Tuesday, November 24, 2020 1:06 PM To: dev@ctakes.apache.org<mailto:dev@ctakes.apache.org> Subject: Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] * External Email - Caution * Hi Sean, I can take up a few things if you can guide me on the same. On Tue, Nov 24, 2020 at 9:59 PM Finan, Sean < sean.fi...@childrens.harvard.edu<mailto:sean.fi...@childrens.harvard.edu>> wrote: > Hi Tim and all, > > Peter kindly checked this into trunk last week. > I tested that version and it seemed to work. > > Another question might be "how do we get this into the/a release? > > I haven't looked into whether or not Apache svn servers have a locking > mechanism on release branches, but if not I think that a patch of 4.0 using > the version that you and Greg tested should be a simple checkin. > > I am sure that everybody is tired of hearing me say this, but I would like > to get out a version 5 asap and disclaim that it is required for the new > umls authentication. That would make patching v4 a non-issue. > > Regardless of repository inclusion, the documentation (also written by > Peter) needs to get to the ctakes wiki - and probably the main ctakes web > site. On that note, the web site needs to be redone asap. > > Anyway, cheers to Peter for taking upon himself this update! > We do still have a few things left to do. > Volunteers? > > Sean > > > From: Miller, Timothy > mailto:timothy.mil...@childrens.harvard.edu>> > Sent: Tuesday, November 24, 2020 11:07 AM > To: dev@ctakes.apache.org<mailto:dev@ctakes.apache.org> > Subject: Re: Changes to UTS Authentication for Authorized Content > Distributors [EXTERNAL] [SUSPICIOUS] > > * External Email - Caution * > > > Peter, > I was able to try your changes and get this new authentication > mechanism to work in the default pipeline. Peter, Sean, et al, what are > the next steps for getting this in to trunk? If you're not comfortable > checking in directly maybe you can share the patch for review. > Tim > > On Sun, 2020-11-15 at 20:54 +0100, Peter Abramowitsch wrote: > > * External Email - Caution * > > > > > > Hi Greg > > > > I've got the modifications finished for the new UMLS authentication > > method > > using API keys. If you're game, I'd like you to be next to test it. > > Contact me at pabramowit...@gmail.com<mailto:pabramowit...@gmail.com> and > > I'll get you a new > > ctakes-dictionary-lookup-fast.4.0,1,x,jar and Readme. > > > > If it's smooth for you, I'll talk with Sean about checking it in and > > what > > wiki locations need to be updated. > > > > To get your key you'll need to log into UMLS, If you've not been > > there > > recently you'll need to go through their profile upgrade process > > where user > > details will be rerouted through one of the public authentication > > mechanisms. > > Once in, go to your profile section and you'll find the API_KEY. > > > > All of you will need to do this eventually. > > > > Regards > > Peter > > > > Regards, Peter > > > > On Wed, Nov 11, 2020 at 10:13 PM Greg Silverman > > wrote: > > > > > Hi Peter, > > > Thanks, that would be great. I like the backwards compatible > > > method. Our > > > issue is that we have custom configurations for use in Docker and > > > Kubernetes with UIMA-AS, so this would be ideal. > > > > > > Greg-- > > > > > > > > > On Wed, Nov 11, 2020 at 3:07 PM Peter Abramowitsch < > > > pabramowit...@gmail.com<mailto:pabramowit...@g
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS]
I can attach it here if attachments are allowed. On Tue, Nov 24, 2020 at 7:23 PM Finan, Sean < sean.fi...@childrens.harvard.edu> wrote: > Hi Gandhi, > > That would be great! > > I think that an additional test would be useful and putting Peter's > documentation on the wiki is important. > Can you take one of those tasks? > Or would you like to handle something else like point release prep, web > site disclaimer, web site link update (to 4.1), etc.? > > Peter, is your documentation available only on your private (web) > directory or do you have it someplace publicly available? > > Many thanks, > Sean > > > > From: gandhi rajan > Sent: Tuesday, November 24, 2020 1:06 PM > To: dev@ctakes.apache.org > Subject: Re: Changes to UTS Authentication for Authorized Content > Distributors [EXTERNAL] [SUSPICIOUS] > > * External Email - Caution * > > > Hi Sean, > > I can take up a few things if you can guide me on the same. > > On Tue, Nov 24, 2020 at 9:59 PM Finan, Sean < > sean.fi...@childrens.harvard.edu> wrote: > > > Hi Tim and all, > > > > Peter kindly checked this into trunk last week. > > I tested that version and it seemed to work. > > > > Another question might be "how do we get this into the/a release? > > > > I haven't looked into whether or not Apache svn servers have a locking > > mechanism on release branches, but if not I think that a patch of 4.0 > using > > the version that you and Greg tested should be a simple checkin. > > > > I am sure that everybody is tired of hearing me say this, but I would > like > > to get out a version 5 asap and disclaim that it is required for the new > > umls authentication. That would make patching v4 a non-issue. > > > > Regardless of repository inclusion, the documentation (also written by > > Peter) needs to get to the ctakes wiki - and probably the main ctakes > web > > site. On that note, the web site needs to be redone asap. > > > > Anyway, cheers to Peter for taking upon himself this update! > > We do still have a few things left to do. > > Volunteers? > > > > Sean > > > > > > From: Miller, Timothy > > Sent: Tuesday, November 24, 2020 11:07 AM > > To: dev@ctakes.apache.org > > Subject: Re: Changes to UTS Authentication for Authorized Content > > Distributors [EXTERNAL] [SUSPICIOUS] > > > > * External Email - Caution * > > > > > > Peter, > > I was able to try your changes and get this new authentication > > mechanism to work in the default pipeline. Peter, Sean, et al, what are > > the next steps for getting this in to trunk? If you're not comfortable > > checking in directly maybe you can share the patch for review. > > Tim > > > > On Sun, 2020-11-15 at 20:54 +0100, Peter Abramowitsch wrote: > > > * External Email - Caution * > > > > > > > > > Hi Greg > > > > > > I've got the modifications finished for the new UMLS authentication > > > method > > > using API keys. If you're game, I'd like you to be next to test it. > > > Contact me at pabramowit...@gmail.com and I'll get you a new > > > ctakes-dictionary-lookup-fast.4.0,1,x,jar and Readme. > > > > > > If it's smooth for you, I'll talk with Sean about checking it in and > > > what > > > wiki locations need to be updated. > > > > > > To get your key you'll need to log into UMLS, If you've not been > > > there > > > recently you'll need to go through their profile upgrade process > > > where user > > > details will be rerouted through one of the public authentication > > > mechanisms. > > > Once in, go to your profile section and you'll find the API_KEY. > > > > > > All of you will need to do this eventually. > > > > > > Regards > > > Peter > > > > > > Regards, Peter > > > > > > On Wed, Nov 11, 2020 at 10:13 PM Greg Silverman > > > wrote: > > > > > > > Hi Peter, > > > > Thanks, that would be great. I like the backwards compatible > > > > method. Our > > > > issue is that we have custom configurations for use in Docker and > > > > Kubernetes with UIMA-AS, so this would be ideal. > > > > > > > > Greg-- > > > > > > > > > > > > On Wed, Nov 11, 2020 at 3:07 PM Peter Abramowitsch < > > &
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS]
Sean In the meantime, I think I have the 4.0.0 source somewhere. I can take my copy which is early 4.0.1 and make whatever small changes are needed (if any) to get it to build in 4.0.0. Would that be useful? Peter On Tue, Nov 24, 2020 at 6:46 PM Miller, Timothy < timothy.mil...@childrens.harvard.edu> wrote: > On Tue, 2020-11-24 at 16:29 +, Finan, Sean wrote: > > * External Email - Caution * > > > > > > Hi Tim and all, > > > > Peter kindly checked this into trunk last week. > > I tested that version and it seemed to work. > > > > Another question might be "how do we get this into the/a release? > > > > I haven't looked into whether or not Apache svn servers have a > > locking mechanism on release branches, but if not I think that a > > patch of 4.0 using the version that you and Greg tested should be a > > simple checkin. > > I think it's worth checking -- if we're allowed to just branch off the > 4.0.0 tag we can get a 4.0.1 distribution that just has this one > change, and we could have it built and uploaded quickly so we're ready > for the UMLS change. How would we find out? > > Tim > > > > > I am sure that everybody is tired of hearing me say this, but I would > > like to get out a version 5 asap and disclaim that it is required for > > the new umls authentication. That would make patching v4 a non- > > issue. > > > > Regardless of repository inclusion, the documentation (also written > > by Peter) needs to get to the ctakes wiki - and probably the main > > ctakes web site. On that note, the web site needs to be redone > > asap. > > > > Anyway, cheers to Peter for taking upon himself this update! > > We do still have a few things left to do. > > Volunteers? > > > > Sean > > > > ____ > > From: Miller, Timothy > > Sent: Tuesday, November 24, 2020 11:07 AM > > To: dev@ctakes.apache.org > > Subject: Re: Changes to UTS Authentication for Authorized Content > > Distributors [EXTERNAL] [SUSPICIOUS] > > > > * External Email - Caution * > > > > > > Peter, > > I was able to try your changes and get this new authentication > > mechanism to work in the default pipeline. Peter, Sean, et al, what > > are > > the next steps for getting this in to trunk? If you're not > > comfortable > > checking in directly maybe you can share the patch for review. > > Tim > > > > On Sun, 2020-11-15 at 20:54 +0100, Peter Abramowitsch wrote: > > > * External Email - Caution * > > > > > > > > > Hi Greg > > > > > > I've got the modifications finished for the new UMLS authentication > > > method > > > using API keys. If you're game, I'd like you to be next to test > > > it. > > > Contact me at pabramowit...@gmail.com and I'll get you a new > > > ctakes-dictionary-lookup-fast.4.0,1,x,jar and Readme. > > > > > > If it's smooth for you, I'll talk with Sean about checking it in > > > and > > > what > > > wiki locations need to be updated. > > > > > > To get your key you'll need to log into UMLS, If you've not > > > been > > > there > > > recently you'll need to go through their profile upgrade process > > > where user > > > details will be rerouted through one of the public authentication > > > mechanisms. > > > Once in, go to your profile section and you'll find the API_KEY. > > > > > > All of you will need to do this eventually. > > > > > > Regards > > > Peter > > > > > > Regards, Peter > > > > > > On Wed, Nov 11, 2020 at 10:13 PM Greg Silverman < > > > g...@umn.edu.invalid> > > > wrote: > > > > > > > Hi Peter, > > > > Thanks, that would be great. I like the backwards compatible > > > > method. Our > > > > issue is that we have custom configurations for use in Docker and > > > > Kubernetes with UIMA-AS, so this would be ideal. > > > > > > > > Greg-- > > > > > > > > > > > > On Wed, Nov 11, 2020 at 3:07 PM Peter Abramowitsch < > > > > pabramowit...@gmail.com> > > > > wrote: > > > > > > > > > Hi Greg > > > > > It's actually extremely simple for current UMLS licensees. > > > > > The new API uses an API_KEY instead of user/password.Just > > > > > login to > > > > the > > >
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS]
>> I haven't looked into whether or not Apache svn servers have a locking >> mechanism ... >I think it's worth checking -- if we're allowed to just branch off the >4.0.0 tag we can get a 4.0.1 distribution that just has this one >change, and we could have it built and uploaded quickly so we're ready >for the UMLS change. How would we find out? A 4.0.1 made directly from 4.0 with only the authentication update is probably the way to go. I suppose that for people with dependencies, downloads etc. fixed at 4.0 would have to get their new umls key and change their ctakes config anyway, so telling them to update any coded version numbers doesn't involve too much extra effort. The main apache org how to release documentation is at https://infra.apache.org/release-publishing.html I am not sure of anything specifically regarding patches. I don't know if we need to go through the full process for a point release ... From: Miller, Timothy Sent: Tuesday, November 24, 2020 12:45 PM To: dev@ctakes.apache.org Subject: Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS] [SUSPICIOUS] * External Email - Caution * On Tue, 2020-11-24 at 16:29 +, Finan, Sean wrote: > * External Email - Caution * > > > Hi Tim and all, > > Peter kindly checked this into trunk last week. > I tested that version and it seemed to work. > > Another question might be "how do we get this into the/a release? > > I haven't looked into whether or not Apache svn servers have a > locking mechanism on release branches, but if not I think that a > patch of 4.0 using the version that you and Greg tested should be a > simple checkin. I think it's worth checking -- if we're allowed to just branch off the 4.0.0 tag we can get a 4.0.1 distribution that just has this one change, and we could have it built and uploaded quickly so we're ready for the UMLS change. How would we find out? Tim > > I am sure that everybody is tired of hearing me say this, but I would > like to get out a version 5 asap and disclaim that it is required for > the new umls authentication. That would make patching v4 a non- > issue. > > Regardless of repository inclusion, the documentation (also written > by Peter) needs to get to the ctakes wiki - and probably the main > ctakes web site. On that note, the web site needs to be redone > asap. > > Anyway, cheers to Peter for taking upon himself this update! > We do still have a few things left to do. > Volunteers? > > Sean > > ____ > From: Miller, Timothy > Sent: Tuesday, November 24, 2020 11:07 AM > To: dev@ctakes.apache.org > Subject: Re: Changes to UTS Authentication for Authorized Content > Distributors [EXTERNAL] [SUSPICIOUS] > > * External Email - Caution * > > > Peter, > I was able to try your changes and get this new authentication > mechanism to work in the default pipeline. Peter, Sean, et al, what > are > the next steps for getting this in to trunk? If you're not > comfortable > checking in directly maybe you can share the patch for review. > Tim > > On Sun, 2020-11-15 at 20:54 +0100, Peter Abramowitsch wrote: > > * External Email - Caution * > > > > > > Hi Greg > > > > I've got the modifications finished for the new UMLS authentication > > method > > using API keys. If you're game, I'd like you to be next to test > > it. > > Contact me at pabramowit...@gmail.com and I'll get you a new > > ctakes-dictionary-lookup-fast.4.0,1,x,jar and Readme. > > > > If it's smooth for you, I'll talk with Sean about checking it in > > and > > what > > wiki locations need to be updated. > > > > To get your key you'll need to log into UMLS, If you've not > > been > > there > > recently you'll need to go through their profile upgrade process > > where user > > details will be rerouted through one of the public authentication > > mechanisms. > > Once in, go to your profile section and you'll find the API_KEY. > > > > All of you will need to do this eventually. > > > > Regards > > Peter > > > > Regards, Peter > > > > On Wed, Nov 11, 2020 at 10:13 PM Greg Silverman < > > g...@umn.edu.invalid> > > wrote: > > > > > Hi Peter, > > > Thanks, that would be great. I like the backwards compatible > > > method. Our > > > issue is that we have custom configurations for use in Docker and > > > Kubernetes with UIMA-AS, so this would be ideal. > > > > > > Greg-- > > > > > > > > > On Wed, Nov 11, 2020 at 3:07 PM Pet
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] [SUSPICIOUS]
On Tue, 2020-11-24 at 16:29 +, Finan, Sean wrote: > * External Email - Caution * > > > Hi Tim and all, > > Peter kindly checked this into trunk last week. > I tested that version and it seemed to work. > > Another question might be "how do we get this into the/a release? > > I haven't looked into whether or not Apache svn servers have a > locking mechanism on release branches, but if not I think that a > patch of 4.0 using the version that you and Greg tested should be a > simple checkin. I think it's worth checking -- if we're allowed to just branch off the 4.0.0 tag we can get a 4.0.1 distribution that just has this one change, and we could have it built and uploaded quickly so we're ready for the UMLS change. How would we find out? Tim > > I am sure that everybody is tired of hearing me say this, but I would > like to get out a version 5 asap and disclaim that it is required for > the new umls authentication. That would make patching v4 a non- > issue. > > Regardless of repository inclusion, the documentation (also written > by Peter) needs to get to the ctakes wiki - and probably the main > ctakes web site. On that note, the web site needs to be redone > asap. > > Anyway, cheers to Peter for taking upon himself this update! > We do still have a few things left to do. > Volunteers? > > Sean > > > From: Miller, Timothy > Sent: Tuesday, November 24, 2020 11:07 AM > To: dev@ctakes.apache.org > Subject: Re: Changes to UTS Authentication for Authorized Content > Distributors [EXTERNAL] [SUSPICIOUS] > > * External Email - Caution * > > > Peter, > I was able to try your changes and get this new authentication > mechanism to work in the default pipeline. Peter, Sean, et al, what > are > the next steps for getting this in to trunk? If you're not > comfortable > checking in directly maybe you can share the patch for review. > Tim > > On Sun, 2020-11-15 at 20:54 +0100, Peter Abramowitsch wrote: > > * External Email - Caution * > > > > > > Hi Greg > > > > I've got the modifications finished for the new UMLS authentication > > method > > using API keys. If you're game, I'd like you to be next to test > > it. > > Contact me at pabramowit...@gmail.com and I'll get you a new > > ctakes-dictionary-lookup-fast.4.0,1,x,jar and Readme. > > > > If it's smooth for you, I'll talk with Sean about checking it in > > and > > what > > wiki locations need to be updated. > > > > To get your key you'll need to log into UMLS, If you've not > > been > > there > > recently you'll need to go through their profile upgrade process > > where user > > details will be rerouted through one of the public authentication > > mechanisms. > > Once in, go to your profile section and you'll find the API_KEY. > > > > All of you will need to do this eventually. > > > > Regards > > Peter > > > > Regards, Peter > > > > On Wed, Nov 11, 2020 at 10:13 PM Greg Silverman < > > g...@umn.edu.invalid> > > wrote: > > > > > Hi Peter, > > > Thanks, that would be great. I like the backwards compatible > > > method. Our > > > issue is that we have custom configurations for use in Docker and > > > Kubernetes with UIMA-AS, so this would be ideal. > > > > > > Greg-- > > > > > > > > > On Wed, Nov 11, 2020 at 3:07 PM Peter Abramowitsch < > > > pabramowit...@gmail.com> > > > wrote: > > > > > > > Hi Greg > > > > It's actually extremely simple for current UMLS licensees. > > > > The new API uses an API_KEY instead of user/password.Just > > > > login to > > > the > > > > UTS site, go to your profile area and check on your key > > > > I or someone else will make changes to the cTAKES validator to > > > > accept > > > this > > > > key in lieu of name and password > > > > > > > > For new UMLS users, they will need a couple of extra > > > > steps. They will > > > get > > > > an identity from one of the authentication providers like > > > > Login.gov as a > > > > part of the UTS registration process. But having completed > > > > that, they > > > > will have a profile page with the API_KEY as above > > > > > > > > > > > > > > > > On Wed, Nov 11, 2020 at 7:27 PM Greg Silverman < > > > > g...@um
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS]
Hi Tim and all, Peter kindly checked this into trunk last week. I tested that version and it seemed to work. Another question might be "how do we get this into the/a release? I haven't looked into whether or not Apache svn servers have a locking mechanism on release branches, but if not I think that a patch of 4.0 using the version that you and Greg tested should be a simple checkin. I am sure that everybody is tired of hearing me say this, but I would like to get out a version 5 asap and disclaim that it is required for the new umls authentication. That would make patching v4 a non-issue. Regardless of repository inclusion, the documentation (also written by Peter) needs to get to the ctakes wiki - and probably the main ctakes web site. On that note, the web site needs to be redone asap. Anyway, cheers to Peter for taking upon himself this update! We do still have a few things left to do. Volunteers? Sean From: Miller, Timothy Sent: Tuesday, November 24, 2020 11:07 AM To: dev@ctakes.apache.org Subject: Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] [SUSPICIOUS] * External Email - Caution * Peter, I was able to try your changes and get this new authentication mechanism to work in the default pipeline. Peter, Sean, et al, what are the next steps for getting this in to trunk? If you're not comfortable checking in directly maybe you can share the patch for review. Tim On Sun, 2020-11-15 at 20:54 +0100, Peter Abramowitsch wrote: > * External Email - Caution * > > > Hi Greg > > I've got the modifications finished for the new UMLS authentication > method > using API keys. If you're game, I'd like you to be next to test it. > Contact me at pabramowit...@gmail.com and I'll get you a new > ctakes-dictionary-lookup-fast.4.0,1,x,jar and Readme. > > If it's smooth for you, I'll talk with Sean about checking it in and > what > wiki locations need to be updated. > > To get your key you'll need to log into UMLS, If you've not been > there > recently you'll need to go through their profile upgrade process > where user > details will be rerouted through one of the public authentication > mechanisms. > Once in, go to your profile section and you'll find the API_KEY. > > All of you will need to do this eventually. > > Regards > Peter > > Regards, Peter > > On Wed, Nov 11, 2020 at 10:13 PM Greg Silverman > wrote: > > > Hi Peter, > > Thanks, that would be great. I like the backwards compatible > > method. Our > > issue is that we have custom configurations for use in Docker and > > Kubernetes with UIMA-AS, so this would be ideal. > > > > Greg-- > > > > > > On Wed, Nov 11, 2020 at 3:07 PM Peter Abramowitsch < > > pabramowit...@gmail.com> > > wrote: > > > > > Hi Greg > > > It's actually extremely simple for current UMLS licensees. > > > The new API uses an API_KEY instead of user/password.Just > > > login to > > the > > > UTS site, go to your profile area and check on your key > > > I or someone else will make changes to the cTAKES validator to > > > accept > > this > > > key in lieu of name and password > > > > > > For new UMLS users, they will need a couple of extra > > > steps. They will > > get > > > an identity from one of the authentication providers like > > > Login.gov as a > > > part of the UTS registration process. But having completed > > > that, they > > > will have a profile page with the API_KEY as above > > > > > > > > > > > > On Wed, Nov 11, 2020 at 7:27 PM Greg Silverman < > > > g...@umn.edu.invalid> > > > wrote: > > > > > > > For example, the user installation guide has not been updated > > > > to > > reflect > > > > the changes NLM is implementing. The impact for our workflow is > > > > pretty > > > > significant, so without a clear picture about what we need to > > > > do in > > order > > > > to not have any down time is - to put it mildly - leaving us > > > > in the > > > dark. > > > > Greg-- > > > > > > > > On Tue, Nov 10, 2020 at 9:18 AM Greg Silverman > > > > wrote: > > > > > > > > > It's still unclear what this means for me as a user of a > > > > > piece of > > > > software > > > > > that uses UTS for authentication purposes. Could someone > > > > > please, in > > > plain > > > > > language, desc
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL]
Peter, I was able to try your changes and get this new authentication mechanism to work in the default pipeline. Peter, Sean, et al, what are the next steps for getting this in to trunk? If you're not comfortable checking in directly maybe you can share the patch for review. Tim On Sun, 2020-11-15 at 20:54 +0100, Peter Abramowitsch wrote: > * External Email - Caution * > > > Hi Greg > > I've got the modifications finished for the new UMLS authentication > method > using API keys. If you're game, I'd like you to be next to test it. > Contact me at pabramowit...@gmail.com and I'll get you a new > ctakes-dictionary-lookup-fast.4.0,1,x,jar and Readme. > > If it's smooth for you, I'll talk with Sean about checking it in and > what > wiki locations need to be updated. > > To get your key you'll need to log into UMLS, If you've not been > there > recently you'll need to go through their profile upgrade process > where user > details will be rerouted through one of the public authentication > mechanisms. > Once in, go to your profile section and you'll find the API_KEY. > > All of you will need to do this eventually. > > Regards > Peter > > Regards, Peter > > On Wed, Nov 11, 2020 at 10:13 PM Greg Silverman > wrote: > > > Hi Peter, > > Thanks, that would be great. I like the backwards compatible > > method. Our > > issue is that we have custom configurations for use in Docker and > > Kubernetes with UIMA-AS, so this would be ideal. > > > > Greg-- > > > > > > On Wed, Nov 11, 2020 at 3:07 PM Peter Abramowitsch < > > pabramowit...@gmail.com> > > wrote: > > > > > Hi Greg > > > It's actually extremely simple for current UMLS licensees. > > > The new API uses an API_KEY instead of user/password.Just > > > login to > > the > > > UTS site, go to your profile area and check on your key > > > I or someone else will make changes to the cTAKES validator to > > > accept > > this > > > key in lieu of name and password > > > > > > For new UMLS users, they will need a couple of extra > > > steps. They will > > get > > > an identity from one of the authentication providers like > > > Login.gov as a > > > part of the UTS registration process. But having completed > > > that, they > > > will have a profile page with the API_KEY as above > > > > > > > > > > > > On Wed, Nov 11, 2020 at 7:27 PM Greg Silverman < > > > g...@umn.edu.invalid> > > > wrote: > > > > > > > For example, the user installation guide has not been updated > > > > to > > reflect > > > > the changes NLM is implementing. The impact for our workflow is > > > > pretty > > > > significant, so without a clear picture about what we need to > > > > do in > > order > > > > to not have any down time is - to put it mildly - leaving us > > > > in the > > > dark. > > > > Greg-- > > > > > > > > On Tue, Nov 10, 2020 at 9:18 AM Greg Silverman > > > > wrote: > > > > > > > > > It's still unclear what this means for me as a user of a > > > > > piece of > > > > software > > > > > that uses UTS for authentication purposes. Could someone > > > > > please, in > > > plain > > > > > language, describe what we as normal users who use software > > > > > reliant > > on > > > > this > > > > > authentication mechanism will have to do in order to not > > > > > disrupt any > > > > > running workflows? > > > > > > > > > > Thanks! > > > > > > > > > > Greg-- > > > > > > > > > > > > > > > On Mon, Nov 9, 2020 at 7:13 AM McLaughlin, Patrick (NIH/NLM) > > > > > [E] > > > > > wrote: > > > > > > > > > > > Hello, > > > > > > > > > > > > > > > > > > > > > > > > The UMLS Terminology Services (UTS) is moving from a > > username/password > > > > > > login to an NIH-federal identity provider system on Monday, > > > > > > November > > > 9. > > > > > > UMLS users will begin migrating their accounts to the new > > > > > > system on > > > this > > > > > > date with a migration deadline of January 15, 2021. > > > > > > > > > > > > > > > > > > > > > > > > You will need to update any systems that use the UMLS user > > validation > > > > API > > > > > > < > > > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__uts.nlm.nih.gov_help_license_validateumlsuserhelp.html=DwIFaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=Heup-IbsIg9Q1TPOylpP9FE4GTK-OqdTDRRNQXipowRLRjx0ibQrHEo8uYx6674h=mRLdzmP8PH1wOUx_Eh0yspc_HfbCKRpLtcwojZLiy1U=vl8aEPfbmDAK-rTVWtqAu41tQQw1y1GI6MV0Gu6YDNI= > > > > > > >, > > as > > > > > > described in my previous emails. We recommend you implement > > > > > > the new > > > > > > workflow as soon as possible after November 9. > > > > > > > > > > > > > > > > > > > > > > > > Attached are instructions for implementing UMLS user > > > > > > validation with > > > the > > > > > > new system. You MUST supply NLM with the domains (e.g., > > > > > >
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL]
I was planning to make the change for our implementation at UCSF in the next couple of weeks. After discussions with Patrick McLauchlin and some testing with the new system, I thought of offering two cTAKES configuration options. One will mimic the current attributes, and the other would be self-evident, Option 1 (for backward compatibility) Wherever it is set, if UmlsUserValidator is called with "apikey" as the umls_user, it assume user umls_password is the UMLS_API_KEY Option 2. If there is a SystemProperty ctakes.umls_apikeyit will use its value with the validator Ditto if there is an EnvironmentVariable UMLS_APIKEY If you're interested I will post the changes. Peter On Wed, Nov 11, 2020 at 7:49 PM Finan, Sean < sean.fi...@childrens.harvard.edu> wrote: > Hi Greg, > > The simple answer is that we have no answer. yet. > > This change in authentication will require some work from ctakes > developers and we haven't yet mapped out the effort. > > We will endeavor to have both an implementation and documentation > available before the current authentication is no longer supported by the > NLM. > > Sean > > From: Greg Silverman > Sent: Wednesday, November 11, 2020 1:26 PM > To: dev@ctakes.apache.org; Reed McEwan; Raymond Finzel; Ben Knoll > Cc: Pei Chen > Subject: Re: Changes to UTS Authentication for Authorized Content > Distributors [EXTERNAL] > > * External Email - Caution * > > > For example, the user installation guide has not been updated to reflect > the changes NLM is implementing. The impact for our workflow is pretty > significant, so without a clear picture about what we need to do in order > to not have any down time is - to put it mildly - leaving us in the dark. > > Greg-- > > On Tue, Nov 10, 2020 at 9:18 AM Greg Silverman wrote: > > > It's still unclear what this means for me as a user of a piece of > software > > that uses UTS for authentication purposes. Could someone please, in plain > > language, describe what we as normal users who use software reliant on > this > > authentication mechanism will have to do in order to not disrupt any > > running workflows? > > > > Thanks! > > > > Greg-- > > > > > > On Mon, Nov 9, 2020 at 7:13 AM McLaughlin, Patrick (NIH/NLM) [E] > > wrote: > > > >> Hello, > >> > >> > >> > >> The UMLS Terminology Services (UTS) is moving from a username/password > >> login to an NIH-federal identity provider system on Monday, November 9. > >> UMLS users will begin migrating their accounts to the new system on this > >> date with a migration deadline of January 15, 2021. > >> > >> > >> > >> You will need to update any systems that use the UMLS user validation > API > >> < > https://urldefense.proofpoint.com/v2/url?u=https-3A__uts.nlm.nih.gov_help_license_validateumlsuserhelp.html=DwIFaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=mIcyXu5lIFGpKDoh1Gy8Cpi8zJMuo64EtaNNv3RRB_8=kuqvrMCb5p9FcXZjvAf2xzaeqn__Pi9PDsjbonEERNE= > >, as > >> described in my previous emails. We recommend you implement the new > >> workflow as soon as possible after November 9. > >> > >> > >> > >> Attached are instructions for implementing UMLS user validation with the > >> new system. You MUST supply NLM with the domains (e.g., > >> > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.example.com=DwIFaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=mIcyXu5lIFGpKDoh1Gy8Cpi8zJMuo64EtaNNv3RRB_8=AiVteA8b5xOfTwc2GWNl3Zk5bQ0aVjL-jVdSrvJrfuk= > in the instructions), so that we can whitelist > >> the domains first. > >> > >> > >> > >> The UMLS user validation API > >> < > https://urldefense.proofpoint.com/v2/url?u=https-3A__uts.nlm.nih.gov_help_license_validateumlsuserhelp.html=DwIFaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=mIcyXu5lIFGpKDoh1Gy8Cpi8zJMuo64EtaNNv3RRB_8=kuqvrMCb5p9FcXZjvAf2xzaeqn__Pi9PDsjbonEERNE= > > will > >> remain functional through January 15, 2021; however, UMLS users that > create > >> their UTS accounts after November 9 will not have a password, and you > will > >> be unable to validate their accounts. > >> > >> > >> > >> Please let us know if you run into any issues or have any questions. > >> Thank you! > >> > >> > >> > >> -Patrick > >> > >> > >> > >> *From:* McLau
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL]
Thanks Sean! I appreciate your candid answer. Greg-- On Wed, Nov 11, 2020 at 12:49 PM Finan, Sean < sean.fi...@childrens.harvard.edu> wrote: > Hi Greg, > > The simple answer is that we have no answer. yet. > > This change in authentication will require some work from ctakes > developers and we haven't yet mapped out the effort. > > We will endeavor to have both an implementation and documentation > available before the current authentication is no longer supported by the > NLM. > > Sean > > From: Greg Silverman > Sent: Wednesday, November 11, 2020 1:26 PM > To: dev@ctakes.apache.org; Reed McEwan; Raymond Finzel; Ben Knoll > Cc: Pei Chen > Subject: Re: Changes to UTS Authentication for Authorized Content > Distributors [EXTERNAL] > > * External Email - Caution * > > > For example, the user installation guide has not been updated to reflect > the changes NLM is implementing. The impact for our workflow is pretty > significant, so without a clear picture about what we need to do in order > to not have any down time is - to put it mildly - leaving us in the dark. > > Greg-- > > On Tue, Nov 10, 2020 at 9:18 AM Greg Silverman wrote: > > > It's still unclear what this means for me as a user of a piece of > software > > that uses UTS for authentication purposes. Could someone please, in plain > > language, describe what we as normal users who use software reliant on > this > > authentication mechanism will have to do in order to not disrupt any > > running workflows? > > > > Thanks! > > > > Greg-- > > > > > > On Mon, Nov 9, 2020 at 7:13 AM McLaughlin, Patrick (NIH/NLM) [E] > > wrote: > > > >> Hello, > >> > >> > >> > >> The UMLS Terminology Services (UTS) is moving from a username/password > >> login to an NIH-federal identity provider system on Monday, November 9. > >> UMLS users will begin migrating their accounts to the new system on this > >> date with a migration deadline of January 15, 2021. > >> > >> > >> > >> You will need to update any systems that use the UMLS user validation > API > >> < > https://urldefense.proofpoint.com/v2/url?u=https-3A__uts.nlm.nih.gov_help_license_validateumlsuserhelp.html=DwIFaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=mIcyXu5lIFGpKDoh1Gy8Cpi8zJMuo64EtaNNv3RRB_8=kuqvrMCb5p9FcXZjvAf2xzaeqn__Pi9PDsjbonEERNE= > >, as > >> described in my previous emails. We recommend you implement the new > >> workflow as soon as possible after November 9. > >> > >> > >> > >> Attached are instructions for implementing UMLS user validation with the > >> new system. You MUST supply NLM with the domains (e.g., > >> > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.example.com=DwIFaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=mIcyXu5lIFGpKDoh1Gy8Cpi8zJMuo64EtaNNv3RRB_8=AiVteA8b5xOfTwc2GWNl3Zk5bQ0aVjL-jVdSrvJrfuk= > in the instructions), so that we can whitelist > >> the domains first. > >> > >> > >> > >> The UMLS user validation API > >> < > https://urldefense.proofpoint.com/v2/url?u=https-3A__uts.nlm.nih.gov_help_license_validateumlsuserhelp.html=DwIFaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=mIcyXu5lIFGpKDoh1Gy8Cpi8zJMuo64EtaNNv3RRB_8=kuqvrMCb5p9FcXZjvAf2xzaeqn__Pi9PDsjbonEERNE= > > will > >> remain functional through January 15, 2021; however, UMLS users that > create > >> their UTS accounts after November 9 will not have a password, and you > will > >> be unable to validate their accounts. > >> > >> > >> > >> Please let us know if you run into any issues or have any questions. > >> Thank you! > >> > >> > >> > >> -Patrick > >> > >> > >> > >> *From:* McLaughlin, Patrick (NIH/NLM) [E] > >> *Sent:* Wednesday, September 16, 2020 5:35 PM > >> *To:* dev@ctakes.apache.org > >> *Cc:* Pei Chen > >> *Subject:* RE: Changes to UTS Authentication for Authorized Content > >> Distributors > >> > >> > >> > >> Hello, > >> > >> > >> > >> I’m following up on my previous message about changes to the NLM UMLS > >> Terminology Services (UTS) authentication. As an Authorized Content > >> Distributor of UTS content, you will need to modify your implementation &g
Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL]
Hi Greg, The simple answer is that we have no answer. yet. This change in authentication will require some work from ctakes developers and we haven't yet mapped out the effort. We will endeavor to have both an implementation and documentation available before the current authentication is no longer supported by the NLM. Sean From: Greg Silverman Sent: Wednesday, November 11, 2020 1:26 PM To: dev@ctakes.apache.org; Reed McEwan; Raymond Finzel; Ben Knoll Cc: Pei Chen Subject: Re: Changes to UTS Authentication for Authorized Content Distributors [EXTERNAL] * External Email - Caution * For example, the user installation guide has not been updated to reflect the changes NLM is implementing. The impact for our workflow is pretty significant, so without a clear picture about what we need to do in order to not have any down time is - to put it mildly - leaving us in the dark. Greg-- On Tue, Nov 10, 2020 at 9:18 AM Greg Silverman wrote: > It's still unclear what this means for me as a user of a piece of software > that uses UTS for authentication purposes. Could someone please, in plain > language, describe what we as normal users who use software reliant on this > authentication mechanism will have to do in order to not disrupt any > running workflows? > > Thanks! > > Greg-- > > > On Mon, Nov 9, 2020 at 7:13 AM McLaughlin, Patrick (NIH/NLM) [E] > wrote: > >> Hello, >> >> >> >> The UMLS Terminology Services (UTS) is moving from a username/password >> login to an NIH-federal identity provider system on Monday, November 9. >> UMLS users will begin migrating their accounts to the new system on this >> date with a migration deadline of January 15, 2021. >> >> >> >> You will need to update any systems that use the UMLS user validation API >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__uts.nlm.nih.gov_help_license_validateumlsuserhelp.html=DwIFaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=mIcyXu5lIFGpKDoh1Gy8Cpi8zJMuo64EtaNNv3RRB_8=kuqvrMCb5p9FcXZjvAf2xzaeqn__Pi9PDsjbonEERNE= >> >, as >> described in my previous emails. We recommend you implement the new >> workflow as soon as possible after November 9. >> >> >> >> Attached are instructions for implementing UMLS user validation with the >> new system. You MUST supply NLM with the domains (e.g., >> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.example.com=DwIFaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=mIcyXu5lIFGpKDoh1Gy8Cpi8zJMuo64EtaNNv3RRB_8=AiVteA8b5xOfTwc2GWNl3Zk5bQ0aVjL-jVdSrvJrfuk= >> in the instructions), so that we can whitelist >> the domains first. >> >> >> >> The UMLS user validation API >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__uts.nlm.nih.gov_help_license_validateumlsuserhelp.html=DwIFaQ=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao=mIcyXu5lIFGpKDoh1Gy8Cpi8zJMuo64EtaNNv3RRB_8=kuqvrMCb5p9FcXZjvAf2xzaeqn__Pi9PDsjbonEERNE= >> > will >> remain functional through January 15, 2021; however, UMLS users that create >> their UTS accounts after November 9 will not have a password, and you will >> be unable to validate their accounts. >> >> >> >> Please let us know if you run into any issues or have any questions. >> Thank you! >> >> >> >> -Patrick >> >> >> >> *From:* McLaughlin, Patrick (NIH/NLM) [E] >> *Sent:* Wednesday, September 16, 2020 5:35 PM >> *To:* dev@ctakes.apache.org >> *Cc:* Pei Chen >> *Subject:* RE: Changes to UTS Authentication for Authorized Content >> Distributors >> >> >> >> Hello, >> >> >> >> I’m following up on my previous message about changes to the NLM UMLS >> Terminology Services (UTS) authentication. As an Authorized Content >> Distributor of UTS content, you will need to modify your implementation to >> accommodate these changes. Our testing environment is now available for you >> to test. >> >> >> >> *We need some information from you.* >> >> >> >> In order for you to test your implementation, we need two things: >> >> >> >>1. A domain name from which you will link your users to our >>authentication service - We will need to whitelist your domain name for >> use >>in our test system. Example: www.yourwebsite.org. >>2. A Google email address - We will need to configure a test account >>for you so that you can test user authentication. >> >>
