| Issue Number | 5084 |
|---|---|
| Summary | [Glossary] Modify XMetal CSS to display new external website descriptions |
| Created | 2022-01-06 10:37:07 |
| Issue Type | Improvement |
| Submitted By | Osei-Poku, William (NIH/NCI) [C] |
| Assigned To | Englisch, Volker (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2022-01-10 17:42:04 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.308288 |
As a CDR glossary term editor, I would want to be able to add the new SourceKey attribute and select one of the values so that I can see the text of the descriptions of the new attributes being added to the “Related External Ref” element in the glossary term concept documents in OCECDR-5037.
We are currently working on a global to add a new attribute (SourceKey) with values to the Related External Ref element in the glossary term concept schema. When these values are selected, the corresponding website description should be displayed in XMetal for users to see.
Acceptance criteria:
Scenario: XMetal has the ability add the new SourceKey attribute with the list of values
Given that I am CDR Glossary term editor
And I have permission to create or update Glossary Term documents
When I Create or update a new or existing Glossary Term Concept document
And I add the new SourceKey attribute to the Related External Ref element
And I select one of the SourceKey attributes from the list
Then XMetal should display the corresponding description for the value selected
Will the current attribute name be changed to SourceKey or did you mean SourceTitle in your ticket description?
Also, you are saying "... select one of the values ..." but the SourceTitle attribute does not have a drop-down LOV at this point. This fact is not important for this ticket but I thought I'd check to make sure I'm looking at the correct element.
The new attribute is yet to be added in OCECDR-5076. Sorry for the confusion. I have linked this ticket also.
The CSS has been updated to display the attribute for the RelatedExternalRef element.
Please take a look on DEV if this approach will work.
~oseipokuw - I think you may have missed ~volker's previous comment. Wasn't this the display which you were saying in yesterday's meeting had surprised you?
~bkline That is right. I think I looked at the different/wrong ticket that gave me the impression that Volker had not done any CSS changes. I will update this ticket in my next comment. Thanks!
~volker When a new attribute is selected, the value (GARD, for example) is automatically displayed in the Related External Ref element field. Could you please remove this feature? It does make the data in the element quite busy. In its place, the website descriptions should be displayed there.
Are you saying instead of the current display (using CDR635471 as an example):
Rel Ext Ref & + @: Office of Human Research Protections (Source='GARD')
you would prefer the following?
Rel Ext Ref & + @: Office of Human Research Protections Genetic and Rare Diseases Information Center
Yes, except that it has to be in parenthesis.
Rel Ext Ref & + @: Office of Human Research Protections (Genetic and Rare Diseases Information Center)
The following CSS file has been updated as requested:
GlossaryTermConcept.css
https://github.com/NCIOCPL/cdr-client/commit/420e966
This is ready for review on DEV.
for this GTC CDR0000801477, the display for CDR should be in Spanish and not in English.
I am attaching the spreadsheet that shows what needs to be displayed for which URL. More Information Links_DEC16_2021 (3).xlsx
I'm guessing you are aware that nowhere in the ticket had it been mentioned for the display of the SourceKey strings to also take into account the UseWith language attribute.
The changes have been added and are ready on DEV:
GlossaryTermConcept.css
https://github.com/NCIOCPL/cdr-client/commit/93bb022
I'm guessing you are aware that nowhere in the ticket had it been mentioned for the display of the SourceKey strings to also take into account the UseWith language attribute.
The URLs are unique so we thought you could use that (At least for the filter change ticket, that is the expectation) but I guess the UseWith attribute will beef things up.
I'm guessing you are aware that nowhere in the ticket had it been mentioned for the display of the SourceKey strings to also take into account the UseWith language attribute.
The URLs are unique so we thought you could use that (At least for the filter change ticket, that is the expectation) but I guess the UseWith attribute will beef things up.
Verified on DEV. Thanks!
Verified on QA. Thanks!
| File Name | Posted | User |
|---|---|---|
| More Information Links_DEC16_2021 (3).xlsx | 2022-01-20 16:00:29 | Osei-Poku, William (NIH/NCI) [C] |
Elapsed: 0:00:00.001947