CDR Tickets

BZDATETIME::2006-11-29 18:41:08
BZCOMMENTOR::Volker Englisch
BZCOMMENT::1

Ed, I went through the publishing process on TEST4 and it appears that TEST4 extracts the Updated date correctly (the correct DateLastModified is displayed in the DrugInfoSummary table) but this date does not appear to be picked up for the display since the date is still incorrect in the display.

BZDATETIME::2006-12-13 18:51:46
BZCOMMENTOR::Volker Englisch
BZCOMMENT::2

Still trouble shooting this problem but I am running into technical problems (error message when building web application with Visual Studio; DB permissions; etc.)
I should be getting a new system resolving some of these problems by tomorrow.

BZDATETIME::2006-12-14 19:03:35
BZCOMMENTOR::Volker Englisch
BZCOMMENT::3

Continue trouble-shooting. My new machine is coming on Friday or Monday.

BZDATETIME::2006-12-22 16:24:28
BZCOMMENTOR::Volker Englisch
BZCOMMENT::4

Visual Studio has been set up on my new system and I'm in the process of trouble-shooting.

BZDATETIME::2007-01-03 16:38:39
BZCOMMENTOR::Volker Englisch
BZCOMMENT::5

Olga and I found the problem. The table columns UpdateDate and ReleaseDate in the NCIView table have been populated incorrectly. The UpdateDate is the date when the record got updated, the ReleaseDate is the LastDateModified from the XML document.

I'm in the process of setting up the Cancer.gov website with Visual Studio on my workstation to test the code changes.

BZDATETIME::2007-01-11 10:58:25
BZCOMMENTOR::Volker Englisch
BZCOMMENT::6

With some help from Olga I was finally able to set up my system to properly run the data load in test mode.

I found the problem and made some additional modifications:
The real problem was that the ReleaseDate (the date coming from the DateLastModified element) was not updated in the table
CancerGovStaging..NCIView
This process is handled in the stored procedure
CancerGovStaging..dbo.PushDrugInfoSummaryToPreview

The procedure set the date to the DateFirstPublished (a.k.a. PostedDate) at the time the record is created during the first publishing and therefore the PostedDate and ReleaseDate are identical.

I changed the logic to only populate the ReleaseDate if a DateLastModified was available. This will result in the display of the ReleaseDate (the date displayed with the "Updated:" label) will only be displayed if the DateLastModified is available no matter if this is a new or an existing document.

Is there any reason to implement a different behavior?

I've tested the changes with existing documents but will still need to test a data load for new DrugInfoSummaries.

BZDATETIME::2007-01-19 13:07:31
BZCOMMENTOR::Volker Englisch
BZCOMMENT::7

For the record, these are the instructions on how to deploy updated Cancer.gov programs:
Building the Executable
=======================
Once the program is ready for production create a "Release" version of the program. Open the menu
Build --> Configuration Manager...
and select "Release" in the field
Active Solution Configuration
Close the Configuration Manager and rebuild the solution
Build --> Rebuild Solution

If your solution was located in the directory
Cancer.gov --> MyProgram
rebuilding the solution will create the release executable file in the directory
Cancer.gov -> MyProgram -> bin --> Release
During the development the programs are located in
Cancer.gov -> MyProgram -> bin --> Debug

Copy this program and any other program that has been changed during the development effort to a directory called
Cancer.gov/Release_YYYY-MM-DD

Migrating software to Test server
=================================
The production directory is
C:\WebResources...

• Log on to the Test server TEST4 using remote desktop.

• Map your system in order to copy the data.

• Make a backup of the directory that is being modified.

• Create a folder in the directory
  MyProgram/Backup/MyProgram_YYYY-MM-DD
  and copy all files from the MyProgram directory to this new directory except
  for the directory 'Backup' and 'Log'.

• Make sure no processes are currently running by making sure the process
  queue is empty:
  http://gatekeeper.cancer.gov/processcontrol/ViewReports.aspx?show=pm

Stop the ProcessManager:
Start -> Control Panel -> Scheduled Tasks
Right-Click on
runprocessmanager.exe
and select 'end task'.
Open Task Manager and end the process
ProcessManager.exe
if it exists.

Copy the file(s) to the production directory.

Start the ProcessManager:
Start -> Control Panel -> Scheduled Tasks
Right-Click on
runprocessmanager.exe
and select 'run'.
Log off from the TEST server.

If stored procedures need to be updated please notify Min (Zhuomin Gao) to perform this task.
Notify Testing/QA personnel that everything is in place.

Once the changes are approved notify the IT team to move the data to the production server. The IT team will have to follow the same instruction except that they will copy the updated programs from TEST4 instead of getting them from your local machine.

BZDATETIME::2007-01-19 14:46:08
BZCOMMENTOR::Volker Englisch
BZCOMMENT::8

The stored procedure
CancerGovStaging..dbo.PushDrugInfoSummaryToPreview
and the program
ProcessThread.exe
have been copied to TEST4 and to the production site (after QC completed)

There were 16 DrugInfoSummaries that needed to be reprocessed in order to show the correct update date on Cancer.gov.
This is complete and all documents are now displayed correctly.

Please verify on Cancer.gov and close this bug.

BZDATETIME::2007-01-25 12:51:09
BZCOMMENTOR::Margaret Beckwith
BZCOMMENT::9

It looks fine on Cancer.gov. Issue closed.