CDR Tickets

BZDATETIME::2011-01-25 15:16:35
BZCOMMENTOR::William Osei-Poku
BZCOMMENT::1

> I have also attached a spreadsheet of the trials.

..and now the attachment (it failed to attach it in the original submission)

Attachment Problem Transfers.xlsx has been added with description: Problem transfers

BZDATETIME::2011-02-02 11:57:02
BZCOMMENTOR::Bob Kline
BZCOMMENT::2

If I understand this request correctly, the following steps need to happen:

1. find rows in ctgov_import corresponding to values in column B
2. set cdr_id column for those rows to integer for value in column A
3. set disposition for rows to 'import requested'
4. fill xml columns from documents received the night before from NLM
5. set changed and dt columns to current date/time
6. append to comment columns documenting what we've done
7. run import job by hand

It might seem attractive to perform all steps but the last and let the scheduled import job take care of step 7, but I believe we've tried that approach in the past and have been tripped up by the download job undoing some of the work we did in the previous steps. If it helps CIAT's processing, we can try to perform the manual invocation of the import job closer to the beginning or end of the work day.

Assuming my analysis is correct, only the first two columns in the spreadsheet attached to the issue are needed for the task. The NCT IDs in column D are identical to the values in column B, and there's nothing I need to do with the values in columns C or E, right? I propose calling this type of request "FORCE TRANSFER CONVERSION OF IN-SCOPE TO CTGOV PROTOCOL" so that we can easily identify future requests to perform this same sequence of steps, and using a spreadsheet with only two columns: CDR ID (integer only) in column A and NCT ID in column B. No header row would be needed. It won't be necessary to resubmit the spreadsheet for this request, but let's use that format for future jobs of this type.

Does all of this seem reasonable?

BZDATETIME::2011-02-02 13:42:14
BZCOMMENTOR::Bob Kline
BZCOMMENT::3

Turns out we needed a replacement version of the spreadsheet after all. Until there's a module available for reading the newer XML-based spreadsheets Excel creates we'll need to use Excel-97 style workbooks.

Attachment task4993.xls has been added with description: Excel-97 version of worksheet, modified to match specs in comment #2

BZDATETIME::2011-02-02 14:11:24
BZCOMMENTOR::William Osei-Poku
BZCOMMENT::4

(In reply to comment #2)
> If it helps CIAT's processing, we
> can try to perform the manual invocation of the import job closer to the
> beginning or end of the work day.
>
Closer to the end of the day should be fine. We are now aware that running the import job manually affects all documents that have been marked to be imported. That was one of the causes of our confusion but since we are aware of that now there shouldn't be any confusion.

> Assuming my analysis is correct, only the first two columns in the spreadsheet
> attached to the issue are needed for the task. The NCT IDs in column D are
> identical to the values in column B, and there's nothing I need to do with the
> values in columns C or E, right?
That is correct.

>I propose calling this type of request "FORCE
> TRANSFER CONVERSION OF IN-SCOPE TO CTGOV PROTOCOL" so that we can easily
> identify future requests to perform this same sequence of steps, and using a
> spreadsheet with only two columns: CDR ID (integer only) in column A and NCT ID
> in column B. No header row would be needed. It won't be necessary to resubmit
> the spreadsheet for this request, but let's use that format for future jobs of
> this type.
>
Agreed. However, there is another scenario where it would be necessary to include a third column in the spreadsheet. That is, when NCT IDs are different for the InScopeProtocol and CTGovProtocol documents and one of them is active. I guess we can title that differently at the appropriate time.e.
> Does all of this seem reasonable?

Yes.

>Turns out we needed a replacement version of the spreadsheet after all.
>Until there's a module available for reading the newer XML-based
>spreadsheets Excel creates we'll need to use Excel-97 style
>workbooks.
I have attached the new spreadsheet.

Attachment Problem Transfers.xls has been added with description: Problem transfers

BZDATETIME::2011-02-02 14:12:28
BZCOMMENTOR::William Osei-Poku
BZCOMMENT::5

updated title

BZDATETIME::2011-02-02 18:09:38
BZCOMMENTOR::Bob Kline
BZCOMMENT::6

Done.

BZDATETIME::2011-02-03 11:13:52
BZCOMMENTOR::William Osei-Poku
BZCOMMENT::7

(In reply to comment #6)
> Done.

Verified. Thanks!
Issue closed.