CDR Tickets

BZDATETIME::2012-05-09 14:19:23
BZCOMMENTOR::Cynthia Boggess
BZCOMMENT::1

Yes I have created Deborah a CiteMS account.
We will be publishing the May citations by the 25th. So this will be here first batch of citations to review.

BZDATETIME::2012-05-22 09:53:01
BZCOMMENTOR::Alan Meyer
BZCOMMENT::2

Cynthia did everything that was needed for this task.

I'm marking the issue as resolved-fixed.

BZDATETIME::2012-05-22 11:08:02
BZCOMMENTOR::Cynthia Boggess
BZCOMMENT::3

Yes, but did you assign the topics listed above to her account? That I can not do.

BZDATETIME::2012-05-22 11:18:15
BZCOMMENTOR::Alan Meyer
BZCOMMENT::4

I didn't realize that you couldn't do that.

I'll do it by hand today.

BZDATETIME::2012-05-22 11:27:21
BZCOMMENTOR::Cynthia Boggess
BZCOMMENT::5

It would be nice if I could or if Victoria could 🙂
All the other boards have only one reviewer...aka the board manager. Because Victoria has too many citations to review by herself, the adult treatment citations were always divided up among several reviewers. Over the years we have only had to assign and reassign topics a few times so our programmer would just handle it.
So maybe an idea for a phase two addition?

BZDATETIME::2012-05-22 11:47:27
BZCOMMENTOR::Alan Meyer
BZCOMMENT::6

I updated the lu_summaries table in the test/dev database. I think that's all
I need to do but, in case it's not or in case I did something wrong, I think
it's desirable for someone who knows what they're doing (Cynthia? Robin?) to
test this and confirm that it worked before I do it in the production database.

If someone tells me that what I did worked, I'll implement it in production.

Incidentally, I ran the query to do this using the summary topic names given in
the issue description text. It turned up one short. I tracked that down and
found that the name:

Myelodysplastic/Myeloproliferative Neoplasms

Is off slightly with an extra space before Neoplasms in the database, i.e.,

Myelodysplastic/Myeloproliferative Neoplasms

I suspect that it's safe to fix that but I haven't done so. I don't know if
anything is keyed to the names and will break if I do fix it.

BZDATETIME::2012-05-22 13:55:54
BZCOMMENTOR::Cynthia Boggess
BZCOMMENT::7

(In reply to comment #6)
I think
> it's desirable for someone who knows what they're doing (Cynthia? Robin?) to
> test this and confirm that it worked before I do it in the production database.

Minaxi will import citations in the test db for these new reassigned topics and then I'll check to see that they end up in Deb's new que.

> I suspect that it's safe to fix that but I haven't done so. I don't know if
> anything is keyed to the names and will break if I do fix it.

We have changed topics in the past using the Edit/Delete Existing Summary Topic feature in the Admin Tool without anything breaking. So I went ahead and fixed this topic. The space was not all that noticable in the web interface which is why I guess no one noticed it before now.

BZDATETIME::2012-05-22 18:31:37
BZCOMMENTOR::Cynthia Boggess
BZCOMMENT::8

Ok this seems to be working fine in the test database. All of Deb's new topics are displaying in her que. After you move this to production, I will be ready to publish the May 2012 citations in a few days and will let you know if I notice any problems.

BZDATETIME::2012-05-22 18:34:00
BZCOMMENTOR::Alan Meyer
BZCOMMENT::9

(In reply to comment #8)
> Ok this seems to be working fine in the test database. All of Deb's new topics
> are displaying in her que. After you move this to production, I will be ready
> to publish the May 2012 citations in a few days and will let you know if I
> notice any problems.

Good.

I'll do it right now.

BZDATETIME::2012-05-22 18:37:31
BZCOMMENTOR::Alan Meyer
BZCOMMENT::10

(In reply to comment #9)

> I'll do it right now.

Done. Marking the issue as resolved-fixed.

We'll reopen it if there's a problem.

BZDATETIME::2012-05-29 10:02:50
BZCOMMENTOR::Alan Meyer
BZCOMMENT::11

For the record, and in case someone ever needs to do this again, here's the SQL statement used to re-assign summaries. First create the new user using the Admin interface. Then get the user's cips_reviewer_id number (or join to get it) and run a query like the following one.

• • use nci_cms_dev
    use nci_cms

UPDATE lu_summaries SET cips_reviewer_id = 21
WHERE summary_name IN
(
'Adult Acute Lymphoblastic Leukemia',
'Adult Acute Myeloid Leukemia',
'Adult Hodgkin Lymphoma',
'Adult Leukemia*',
'Adult Lymphoma*',
'Adult Non-Hodgkin Lymphoma',
'AIDS-related Lymphoma',
'Chronic Lymphocytic Leukemia',
'Chronic Myelogenous Leukemia',
'Chronic Myeloproliferative Disorders',
'Hairy Cell Leukemia',
'Myelodysplastic Syndromes',
'Myelodysplastic/Myeloproliferative Neoplasms',
'Plasma Cell Neoplasms (including Multiple Myeloma)',
'Hodgkin Lymphoma During Pregnancy',
'Non-Hodgkin Lymphoma During Pregnancy',
'Primary Central Nervous System Lymphoma'
)

After running the above, check to be sure that the correct number of summaries were re-assigned, e.g.,

SELECT COUNT⭐ FROM lu_summaries WHERE cips_reviewer_id = 21

If the number is short, compare the actual summary names with the ones in the IN list. If any strings in the IN list don't match, fix either the string in the database or in the query and re-run.

BZDATETIME::2012-05-30 13:59:42
BZCOMMENTOR::Robin Juthe
BZCOMMENT::12

Victoria and Deb met to go over the CiteMS review in Deb's queue, and it sounds like everything is working as it should. So, I am closing this issue.

Thanks!