Issue Number | 3309 |
---|---|
Summary | Automate CDR to Visuals Online process |
Created | 2011-02-28 10:12:43 |
Issue Type | Improvement |
Submitted By | Beckwith, Margaret (NIH/NCI) [E] |
Assigned To | Kline, Bob (NIH/NCI) [C] |
Status | Closed |
Resolved | 2011-03-24 11:05:34 |
Resolution | Fixed |
Path | /home/bkline/backups/jira/ocecdr/issue.107637 |
BZISSUE::5001
BZDATETIME::2011-02-28 10:12:43
BZCREATOR::Margaret Beckwith
BZASSIGNEE::Bob Kline
BZQACONTACT::Robin Juthe
We would like to explore ways to make the process of adding new and revised CDR images to Visuals Online more automated. Right now, Kevin Broun gets an email letting him know what new and revised images have been published. He has a script that picks up the metadata from the media docs, but then he has to manually resize each image to 4 different sizes, and manually fill out the forms for getting the images into VOL.
BZDATETIME::2011-02-28 10:20:05
BZCOMMENTOR::Bob Kline
BZCOMMENT::1
Kevin:
Can I stop by your office some time tomorrow to chat about our options? If you'd prefer to talk today, let me know and I'll give you a call.
Bob
BZDATETIME::2011-03-01 09:47:08
BZCOMMENTOR::Bob Kline
BZCOMMENT::2
Kevin:
I've implemented this on Franck (the test server) while we're testing. I'll move it to Bach (the production server) when we're satisfied that it does what we want. The syntax is:
http://host/cgi-bin/cdr/GetCdrImage.py?id=I&res=R[&quality=Q]
... where:
I is the CDR ID (can be 999999 or CDR0000999999 or CDR999999)
R is one of 300 | 150 | 75 | thumb
Q is optional integer for compression/quality balance, defaulting to
85
For example:
http://franck.nci.nih.gov/cgi-bin/cdr/GetCdrImage.py?id=415505&res=75&quality=95
Please give it try.
BZDATETIME::2011-03-01 10:01:51
BZCOMMENTOR::Bob Kline
BZCOMMENT::3
[posted for Kevin]
That's looking really good. Just a couple of things:
The resolution option "75" should be "72" instead - it looks like it's actually doing the correct 72 DPI scale of 24%, it's just named incorrectly.
Is it possible to have a "sharpen" option? This would be very helpful with the thumbnails in particular, which tend to be pretty blurry regardless of the quality parameter.
Thanks,
Kevin
BZDATETIME::2011-03-01 11:03:18
BZCOMMENTOR::Bob Kline
BZCOMMENT::4
(In reply to comment #3)
> - The resolution option "75" should be "72" instead - it looks
like it's
> actually doing the correct 72 DPI scale of 24%, it's just named
incorrectly.
Fixed.
> - Is it possible to have a "sharpen" option? This would be very
helpful with
> the thumbnails in particular, which tend to be pretty blurry
regardless of the
> quality parameter.
Added. A value of 1 gives you the original image. Less than 1 blurs the image. Greater than 1 sharpens the image. A good value is probably around 2 for thumbnails, but you might want to experiment.
http://franck.nci.nih.gov/cgi-bin/cdr/GetCdrImage.py?id=415505&res=thumb&sharpen=2
BZDATETIME::2011-03-08 10:03:48
BZCOMMENTOR::Bob Kline
BZCOMMENT::5
Kevin:
Just checking in to see what the status is for this task. Just want to make sure we're talking to the production CDR before you start pulling in the images to the live VOL database.
BZDATETIME::2011-03-08 14:46:57
BZCOMMENTOR::Bob Kline
BZCOMMENT::6
From Kevin:
> Just got my end working (version 1 anyway) and it appears to be
working
> well - see http://visuals-dev.nci.nih.gov/details.cfm?imageid=8799
for
> an example on the VOL dev server. This can be promoted to
production
> on the CDR side as far as I'm concerned.
The script is now on Bach:
http://bach.nci.nih.gov/cgi-bin/cdr/GetCdrImage.py?id=415505&res=72&quality=95
(as an example invocation).
BZDATETIME::2011-03-24 11:04:04
BZCOMMENTOR::Margaret Beckwith
BZCOMMENT::7
This appears to be working now, so I am closing the issue.
BZDATETIME::2011-03-24 11:05:20
BZCOMMENTOR::Margaret Beckwith
BZCOMMENT::8
Changing to resolved.
BZDATETIME::2011-03-24 11:05:34
BZCOMMENTOR::Margaret Beckwith
BZCOMMENT::9
Now closing issue!
Elapsed: 0:00:00.001650