Issue Number | 4960 |
---|---|
Summary | Include alternate names in glossifier |
Created | 2021-03-15 15:49:20 |
Issue Type | Improvement |
Submitted By | Osei-Poku, William (NIH/NCI) [C] |
Assigned To | Kline, Bob (NIH/NCI) [C] |
Status | Closed |
Resolved | 2021-05-11 19:44:21 |
Resolution | Fixed |
Path | /home/bkline/backups/jira/ocecdr/issue.286940 |
For the Spanish content, could you please modify the glossifier for it to be able to pick up alternate names for glossification? Currently, they are not picked up by the glossifier. We would also want to be able to assign the ExcludeFromGlossifier attribute to some of the alternate names when necessary.
Could I have some examples of alternate Spanish names which are NOT
marked ExcludeFromGlossifier="Yes"
AND are NOT picked up by
the glossifier, please?
By the way, if you find any, that WOULD qualify for a bug report. 😃
~oseipokuw have you been able to find any examples of the glossifier failing to pick up alternate Spanish names which are not explicitly excluded?
Just to make sure, you do remember https://tracker.nci.nih.gov/browse/OCECDR-4685, right?
This is one example from PROD. Glossary Term 476408 - alternate name = “afflicción del duelo”.
Summary - 256661
~oseipokuw have you been able to find any examples of the glossifier failing to pick up alternate Spanish names which are not explicitly excluded?
Just that this will be a deliberate effort to remove the attribute (not that there are several without the Exclude.. attribute) in order to have them included in glossifier.
Looks like this is indeed a bug. Will confirm tomorrow.
Bug confirmed. Fixed on CDR DEV.
Would you know why this alternate name "antecedentes familiares" (CDR0000302456 ) is not be picked up for glossification of this summary - CDR0000584383? The first word "antecedentes " - CDR0000642019 is picked up for glossification but not the two words "antecedentes familiares" together.
I also added a new alternate name "testing" to the term CDR0000302456 to test this ticket but it is not picked up in the same summary above. Do we need to publish the term for it to show up in the glossifiier ?
I assume you're trying the original glossifier without audience or dictionary filtering, right? Is it possible you're looking for names which were added to the term name document after your XMetaL session started?
Ah, no. You're hoping that a rejected term will show up. In this
context, the top-level TermNameStatus
is interpreted to
refer to the entire document, not just the English name. One of the
drawbacks of unusual placement of elements in the schema structure. I
see from the publishing selection queries that the publishing system
looks at that element the same way, skipping over the document for
publication jobs if the value is Rejected. So it makes sense
that the glossifier skips it, because it would be embarrassing to have
the summary link to glossary terms which weren't on the web site. 🙂
That makes sense. If the main term is rejected then the glossifier should ignore the alternate names as well. Thanks!
Verified on QA. Thanks!
We have not tested this yet but I am closing the ticket and will report any problems after this OCECDR-4993 global change is completed and tested.
Elapsed: 0:00:00.001351