Issue Number | 3898 |
---|---|
Summary | Modify PDQ Partner Documents |
Created | 2015-04-21 12:13:22 |
Issue Type | Improvement |
Submitted By | Englisch, Volker (NIH/NCI) [C] |
Assigned To | Englisch, Volker (NIH/NCI) [C] |
Status | Closed |
Resolved | 2016-01-22 20:01:54 |
Resolution | Fixed |
Path | /home/bkline/backups/jira/ocecdr/issue.159280 |
We have a couple of documents that are listing links to our website. With the release of NVCG these links will need to be updated to the current location
The initial information email text will need to be modified.
Lakshmi just asked to have this done. I'm increasing the priority on this ticket.
Email from Lakshmi:
===================================================
Volker
We need to look at all emails that are sent out from the Licensing
mailbox either manually or via scripts to make sure we don’t use the
term licensee. I can ask someone to in ODDC to help with the updates to
the letters if you send me the emails that we send out.
This was in the subject line of an email that we got questions from a
test partner.
The following files have been modified on the Linux server and will need to be tested in the DEV tier. The files are located at
~cdroperator/prod/bin
R13459: SendEmail.py
R13459: Jobmaster.py
Another program modified (in directory d:\cdr\Publishing:
LicenseeList.py
I modified the following program:
~/prod/bin/PDQAccessReport.py
The following documents have been updated:
R13668: ftp_memo.cdrxml
R13668: ftp_memo.test
Some of the programs are already in production.
Still requires PDQ XML document to be checked.
I versioned the following changes:
R13802: LicenseeList.py
~volker: I'm trying to put together the manual tasks, and I see mention of more commits than were hooked to this ticket. Can you modify the SVN comments so the commits are linked by JIRA? Thanks!
Can you modify the SVN comments
Modify SVN comments? I did not know this was possible.
I had the feeling this ticket might create problems because some of the changes are already in production. I wasn't able to identify exactly when the PDQAccessReport.py made it to PROD. The ticket is from April 2015.
I'm not exactly sure what you need me to change.
Elapsed: 0:00:00.001428