Hi Peter, Kean and others, > Seems to me that if we don't do anything, - I plan to give this 100% of my time starting next week. Well, right after I clean the basement.
> we will have a flurry of support > emails in 4.0.0 as soon as the NLM completes its roll-over. - I would call that optimistic :^) > 1. offer a tar file containing the two needed jars with instructions on > setting up new credentials and blanking out fields in the various xml > resources. > 2. for 4.0.0 users that have done no customization whatsoever, - are good options for people that only ever install the binary. - This should be easy enough. I will try to host it from the ctakes website. >> 3. for 4.0.0 users that compile their own, provide a tar file containing > the sources plus instructions for modifying xml files and removing obsolete > Junit file. >+1 for Option 3! - This should also be easy enough. I will try to host it from the ctakes website. >> 4. Create a new 4.0.0.x tag and build new binary and source packs with > pre-blanked xml files - I plan to do at least this much, and I would hope that it covers everybody that uses the source directly. >> Is it worth a quick email poll of 4.0.0 users? -Go for it! Just to warn you, users may not be very responsive. Cheers, Sean ________________________________________ From: Kean Kaufmann <[email protected]> Sent: Wednesday, December 9, 2020 9:04 AM To: [email protected] Subject: Re: What to do about 4.0.0 and UMLS [EXTERNAL] * External Email - Caution * > > 3. for 4.0.0 users that compile their own, provide a tar file containing > the sources plus instructions for modifying xml files and removing obsolete > Junit file. Is it worth a quick email poll of 4.0.0 users? +1 for Option 3! Thanks Peter (and everybody)... On Wed, Dec 9, 2020 at 8:48 AM Peter Abramowitsch <[email protected]> wrote: > Hi Sean et al > > Seems to me that if we don't do anything, we will have a flurry of support > emails in 4.0.0 as soon as the NLM completes its roll-over. I can see > several options and wonder which of these would stem the most calls and > provide the least work for source maintainers. > > 1. offer a tar file containing the two needed jars with instructions on > setting up new credentials and blanking out fields in the various xml > resources. > > 2. for 4.0.0 users that have done no customization whatsoever, offer a tar > file containing the new jars plus pre-modified xml files in desc and in > resources that can just overlay a virgin release. This should just run as > soon as the user has added the umls key to the environment or command line > > 3. for 4.0.0 users that compile their own, provide a tar file containing > the sources plus instructions for modifying xml files and removing obsolete > Junit file. > > 4. Create a new 4.0.0.x tag and build new binary and source packs with > pre-blanked xml files (Obviously this is the most work but may not be > needed) > > Is it worth a quick email poll of 4.0.0 users? > > Peter >
