CDR Tickets

Attachment lip_feb10.txt has been added with description: CMS file

BZDATETIME::2010-04-14 14:32:48
BZCOMMENTOR::William Osei-Poku
BZCOMMENT::1

Alan,
I heard back from Cynthia regarding the priority of the issues. I have marked this as a P4. You can start with this after the current globals are completed.

BZDATETIME::2010-04-21 00:15:47
BZCOMMENTOR::Alan Meyer
BZCOMMENT::2

So far I'm not having any luck duplicating this using the test
database.

I tried importing one of the records by itself and it imported
fine. I tried importing another record from which I had deleted
an IS element. Again, the import succeeded. I tried importing
the entire file from the attachment, but everything imported
there too except records that I had already imported, for which I
got the message: "PMID .... Result: Duplicate - Only Summary(s)
Imported"

The way I did the imports was:

Sign on as an ordinary user.

Click File /
Add New Batch (import)
Fill in the control fields:
Search Source: CMS2
Board: Adult Treatment
Summary Topic: Lip and Orac Cavity Cancer
Review Cycle ID: January 2010

The database in the test system is old and January was the latest
month in it.

I don't know whether to ask, "What am I doing wrong?" or "What am
I doing right?"

I looked through the source code to find the error message. I
didn't find an exact match, but did find

"File Error: No PMID Found!"

I assume that's what the users saw. I seem to recall that we got
the same error message before in the bug that Brent resolved,
which could mean that that error and this one had a similar
cause, namely the system getting lost when parsing the input
record and not finding something it was expecting. A missing IS
field is certainly a reasonable guess, but that may not be it.

Also, I notice that all of the records in the input file have at
least one IS field. The two that caused the error had only one,
an "Electronic" ISSN. All the others had two, including a
"Linking" ISSN and either an "Electronic" or "Print" ISSN. I
searched the source code for the word "Linking" in hopes of
finding something that depended on the presence of an ISSN of
that type, but didn't find anything - which doesn't prove
anything, but I was hoping for a break.

Does the error still occur when trying to import those records?
If so, then perhaps the next thing for me to try is to get a
backup of the production database, restore it in the test
database so that I'm testing with the same data, and see if I can
reproduce the problem in the test setup. If that still doesn't
reproduce the error, then I can try something radical, like
having all users out of the system, take a full backup in case I
break something, and then try debugging with the live system.

I hope it doesn't come to that.

BZDATETIME::2010-04-26 16:07:10
BZCOMMENTOR::William Osei-Poku
BZCOMMENT::3

(In reply to comment #2)
> So far I'm not having any luck duplicating this using the test
> database.
>
> I tried importing one of the records by itself and it imported
> fine. I tried importing another record from which I had deleted
> an IS element. Again, the import succeeded. I tried importing
> the entire file from the attachment, but everything imported
> there too except records that I had already imported, for which I
> got the message: "PMID .... Result: Duplicate - Only Summary(s)
> Imported"

I asked Cynthia and Minaxi to try and import the citations again and to everyone's surprise, the citations had been imported (and without any of the problems they saw earlier). They checked and found that the PMIDs were contained in another file they had imported after they reported the problem. No one knows exactly what happened. It is possible that the file they used was corrupted in some way. Besides, they have not seen this problem come up again since they reported it. If you agree, I will close this issue and re-open it if the problem happens again the in the future.

BZDATETIME::2010-04-26 16:18:21
BZCOMMENTOR::Alan Meyer
BZCOMMENT::4

(In reply to comment #3)
> ... If you agree, I will close this issue and re-open it if
> the problem happens again the in the future.

Sounds good to me.

BZDATETIME::2010-04-26 16:19:26
BZCOMMENTOR::William Osei-Poku
BZCOMMENT::5

(In reply to comment #4)
> (In reply to comment #3)
> > ... If you agree, I will close this issue and re-open it if
> > the problem happens again the in the future.
>
> Sounds good to me.

Issue closed. Thanks!

BZDATETIME::2010-04-26 16:21:13
BZCOMMENTOR::William Osei-Poku
BZCOMMENT::6

(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #3)
> > > ... If you agree, I will close this issue and re-open it if
> > > the problem happens again the in the future.
> >
> > Sounds good to me.
>
> Issue closed. Thanks!

Now closed.