CDR Tickets

Issue Number 3156
Summary [Genetics Directory] Validation Rule for GP and GPMailer attributes
Created 2010-05-19 15:19:40
Issue Type Improvement
Submitted By Osei-Poku, William (NIH/NCI) [C]
Assigned To Kline, Bob (NIH/NCI) [C]
Status Closed
Resolved 2010-05-28 10:17:59
Resolution Fixed
Path /home/bkline/backups/jira/ocecdr/issue.107484
Description

BZISSUE::4843
BZDATETIME::2010-05-19 15:19:40
BZCREATOR::William Osei-Poku
BZASSIGNEE::Bob Kline
BZQACONTACT::William Osei-Poku

**Please, do not start work on this issue yet. These are for discussion on
Thursday**

1. The ProfessionalType element in the GP Person document is found at the end of the document. We are proposing that, it should be moved up into the <GeneticsProfessionalDetails> block. Currently because it is found at the end of the document, and also because it is not included in the default template, users miss it when entering new application or when updating existing ones or they sometimes find it difficult to locate the element.

2.

i. We are proposing that a macro be created for selecting the GP and GPMailer attributes. These attributes are very importation for publishing and for sending out mailers however, if there are typos in entering them, they may go undetected for a long time.

ii. On the other hand, if we can create a validation rule for the GP and GPMailer attributes so that the attributes can be checked for the correct spelling or order, upon save, that will be helpful.

3. For new applications that are missing information, we need to contact the applicants for the missing information. Some of the information is required for their applications to be included in the directory. We propose a Missing Required Information block for the Gen Prof. Person document, modeled after the InScopeProtocol Missing Required Information block, which will also allow users flag records that are missing required information and easily generate standard language emails from XMetal and send them to applicants.

Comment entered 2010-05-20 11:14:48 by Osei-Poku, William (NIH/NCI) [C]

BZDATETIME::2010-05-20 11:14:48
BZCOMMENTOR::William Osei-Poku
BZCOMMENT::1

I am adding two more possible changes below:

4. The GeneticsTeamServices element has a list of values. After we have typed Ctrl + Enter and the list is displayed, we want to be able to select all of the values or some of the values (and click OK) so they will be automatically populated. Currently, we are only able to do this one at a time.

5. In the same way, we want to be able to select all 35 syndromes, or some of them, for the FamilialCancerSyndrome element by doing a Ctrl + Enter and selecting the appropriate syndromes and clicking OK to populate the terms in XMetal. All the syndromes have a SemanticType of ‘Genetic condition’. However, using ‘Genetic condition’ alone as the selection criteria will also include other terms that are not part of what we need for the Genetics Professional document. I am wondering if we can use a TermSet to create a list for the 35 syndromes and create a macro to insert the links in the Genetics Professional document, just like we do with the ‘Insert Diagnosis Links’ macro in the InScopeProtocol document? If we use a TermSet, the user can add all the terms to the Gen. Prof. document in just a few steps and then delete the unwanted terms.

Comment entered 2010-05-20 15:31:29 by Osei-Poku, William (NIH/NCI) [C]

BZDATETIME::2010-05-20 15:31:29
BZCOMMENTOR::William Osei-Poku
BZCOMMENT::2

Per this afternoon's discussions:
#1 was not approved
#2 ii was approved
#3 was not approved
#4 (Should be only included in the template) the template issue, OCECDR-3155 will take care of this.
#5 (Should be only included in the template) the template issue,. OCECDR-3155 will take care of this.

The only issue to be tracked by this bug is the validation rule for the GP and GP Mailer attributes. I have updated the title of this bug to reflect that.

Comment entered 2010-05-21 14:08:42 by Kline, Bob (NIH/NCI) [C]

BZDATETIME::2010-05-21 14:08:42
BZCOMMENTOR::Bob Kline
BZCOMMENT::3

Added constraint to values allowed for UsedFor attribute in the schema on Mahler.

Comment entered 2010-05-24 10:23:47 by Osei-Poku, William (NIH/NCI) [C]

BZDATETIME::2010-05-24 10:23:47
BZCOMMENTOR::William Osei-Poku
BZCOMMENT::4

(In reply to comment #3)
> Added constraint to values allowed for UsedFor attribute in the schema on
> Mahler.

Verified on Mahler. Please promote to Bach.

Comment entered 2010-05-26 10:54:59 by Kline, Bob (NIH/NCI) [C]

BZDATETIME::2010-05-26 10:54:59
BZCOMMENTOR::Bob Kline
BZCOMMENT::5

Promoted to Bach; please check (and close if OK).

Comment entered 2010-05-28 10:17:59 by Osei-Poku, William (NIH/NCI) [C]

BZDATETIME::2010-05-28 10:17:59
BZCOMMENTOR::William Osei-Poku
BZCOMMENT::6

(In reply to comment #5)
> Promoted to Bach; please check (and close if OK).

Verified on Bach. Issue closed.

Elapsed: 0:00:00.001636