CDR Tickets

Moved out of Newton since we aren't ready to move forward with this yet.

An upcoming meeting (next Thursday) is scheduled to review the proposed elements, which will be added to the ticket.

Media Schema Changes to include Demographic Information.docx

I have attached the requirements document for the schema change.

You need to tell me which of the attributes are required and which are optional.

Where would the new Demographic Information block be positioned?

Between RelatedDocuments and TranslationOf (when ~oseipokuw  tells me which attributes are required).

Please position the new block between the between Media Source and Media Content blocks.

All the attributes are optional.

It would be preferable, if you care about specific details for how an enhancement should be implemented, if you would specify these requirements before the work for the enhancement is done, rather than after, please.

Thanks. 😉

Installed on DEV. I placed the new block between PermissionInformation and MediaContent (there wasn't any way to place it directly between MediaSource and MediaContent without moving PermissionInformation, which is already between MediaSource and MediaContent).

Sure. Sorry about that. It was not intentional. I will make sure to include it the next time.

I found these 3 issues on DEV while reviewing the changes. Could you please take a look and make the appropriate changes?

1. Age element: put the value pick-list items in chronological order (child, adolescent, adult, older adult) instead of alphabetical order. 

2. Skin tone element: Add the following Source to the Attribute Inspector: Fitzpatrick Scale 

3. Skin tone element: fix the value pick-list so that a dash is displayed instead of a pipe character

Age element: put the value pick-list items in chronological order (child, adolescent, adult, older adult) instead of alphabetical order.

The values are in the schema as you gave them to me. The interface always sorts them alphabetically. We've had this conversation about various valid values lists in Jira a few times in the past. 😛

Skin tone element: Add the following Source to the Attribute Inspector: Fitzpatrick Scale

The user can put the value there, but the software can't, as long as any of the valid values for the attribute have spaces in them (another familiar conversation).

Skin tone element: fix the value pick-list so that a dash is displayed instead of a pipe character

Dialog boxes in MFC can only display Unicode characters in code positions below 256 with its default font, so it can't render a dash properly. The dash displays correctly in the element once the value has been chosen, and is stored correctly when the document is saved. There may be a way to customize Microsoft's dialog box, but that would out of scope for this ticket (and release).

Skin tone element: Add the following Source to the Attribute Inspector: Fitzpatrick Scale

The user can put the value there, but the software can't, as long as any of the valid values for the attribute have spaces in them (another familiar conversation).

Please add the value as FitzpatrickScale

Changed value on DEV as requested.

Verified on DEV. Thanks!

Verified on QA. Thanks!