CDR Tickets

Issue Number 3840
Summary CDR Schema Changes
Created 2014-12-18 16:29:09
Issue Type Sub-task
Submitted By Englisch, Volker (NIH/NCI) [C]
Assigned To Kline, Bob (NIH/NCI) [C]
Status Closed
Resolved 2015-03-05 14:39:54
Resolution Fixed
Path /home/bkline/backups/jira/ocecdr/issue.143855
Description

Modifying schema to enforce maximum string length for Navlabel string.

Comment entered 2014-12-23 11:36:46 by Kline, Bob (NIH/NCI) [C]

From an email message sent by Victoria Sun 2014-12-03:

Would the maximum length for the short title in the schema be the same as it is in Percussion? In which case, we looked it up again, and it is 100 characters for the Short title field in percussion.

Comment entered 2014-12-23 11:58:41 by Kline, Bob (NIH/NCI) [C]

Implemented on DEV. Will be tricky to test until https://tracker.nci.nih.gov/browse/OCECDR-3799 gets taken out of Hold status.

R13047 /branches/Ampere/Schemas/CdrCommonBase.xml

Comment entered 2014-12-23 12:01:01 by Kline, Bob (NIH/NCI) [C]

Hmm. Has JIRA's behavior changed? I thought I was marking this ticket as "Resolved/Fixed" but it appears that the ticket got closed. ???

Comment entered 2014-12-29 14:07:13 by Englisch, Volker (NIH/NCI) [C]

Oh yes, there have been many changes - good and bad. However, I've haven't experienced a change in the workflow process yet.

Comment entered 2014-12-29 14:10:49 by Kline, Bob (NIH/NCI) [C]

Well, I'm reopening the ticket, because it shouldn't be closed until the change is in production.

Comment entered 2014-12-29 14:13:37 by Kline, Bob (NIH/NCI) [C]

Doesn't look like I can move the status of this ticket beyond "in progress" without closing it completely again, which isn't right. JIRA didn't used to behave like this. If you (Volker) can see a way to select a non-closed status indicating that the development work is done and it's ready for testing, be my guest.

Comment entered 2014-12-29 14:19:54 by Englisch, Volker (NIH/NCI) [C]

You're correct. Looking at the workflow there doesn't exist a QA/Verified status anymore.
I bet this has something to do with the fact that this is a sub-task instead of a regular task because the parent task would keep the overall status.

Comment entered 2014-12-29 14:31:57 by Kline, Bob (NIH/NCI) [C]

If that's the explanation, then perhaps we should avoid the use of sub-task tickets for work that gets tested (and possibly deployed) separately from other work, as we have no way to indicate "this is ready for testing" or "this has been tested successfully and is ready to be deployed."

Comment entered 2014-12-29 14:34:48 by Englisch, Volker (NIH/NCI) [C]

I agree. We could also ask Erika if the workflow for sub-tasks could be adjusted.

Comment entered 2015-01-02 16:49:25 by Englisch, Volker (NIH/NCI) [C]

Bob, the TitleType attribute is coming from a drop-down list for which we need to add the new Navlabel.
Could you add that change to the schema, please?

Comment entered 2015-01-02 16:56:45 by Kline, Bob (NIH/NCI) [C]

I can add the new value, but is this the right ticket? The description for this ticket just says:

Modifying schema to enforce maximum string length for Navlabel string.

Comment entered 2015-01-02 17:04:07 by Englisch, Volker (NIH/NCI) [C]

The title of the ticket is CDR Schema Changes and this is a subtask of the Navlebel task, so I do think this would be the appropriate ticket. If you want I can update the description and add ... and other tasks as needed. :-)

Comment entered 2015-01-05 09:19:53 by Kline, Bob (NIH/NCI) [C]

New AltTitleType value added on DEV.

Comment entered 2015-01-05 10:56:36 by Englisch, Volker (NIH/NCI) [C]

I've tested the changes in XMetal and everything appears to be working as expected.

Comment entered 2015-03-05 14:39:54 by Kline, Bob (NIH/NCI) [C]

On production.

Elapsed: 0:00:00.001508