CDR Tickets
| Issue Number | 5269 |
|---|---|
| Summary | Modify Create World Server Translated Summary tool |
| Created | 2023-08-03 12:20:06 |
| Issue Type | Improvement |
| Submitted By | Osei-Poku, William (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2023-10-17 09:35:55 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.354364 |
We would like to know if it is possible to modify "Create World Server Translated Summary" with the following changes:
1. Please replace the English Summary URL with
"https://www.cancer.gov/espanol/tipos/" for all Spanish summaries
created. This will avoid conflicts/validation errors with the existing
English summaries.
2. Please change SummaryLanguage from "English" to "Spanish" for all
summaries created
3. Please add TranslationOf element to all the summaries created and
popoulate the field with the title of the English summary. If a link to
the corresponding English summary can be created that would even be
better.
4. Please add PatientVersionOf element for Patient summaries and
populate the field with the title of the corresponding Spanish HP
summary If a link can be created that would even be better.
That script doesn't have the information it would need. We would need to completely rewrite the script to ask the user to supply the required values, or (preferably) make these modifications when the Fetch English Summary For Translation script is run.
~oseipokuw Unless I hear otherwise, I'm going to proceed with implementing these changes for the Fetch English Summary For Translation script (as part of Quinn).
Making modifications when the Fetch English Summary for Translation script is run would be great, but I think it will have an impact on how the summaries are set up in World Server. So, please hold off until I am able to discuss with Linda.
Checked my proposed approach with Linda, who gave the green light. Installed the enhancements on DEV and let her know they're ready for testing.
Linda has confirmed that the modified XML presents no problems when imported into Trados.
Verified on DEV. Thanks!
Verified on QA. Thanks!
Promoted by accident
It looks like the correct elements are showing. However, the text of the summary itself appears to be from the English summary instead of the Spanish translated summary.
Example on QA. CDR0000812136
Example on DEV. 0000812726
Looks like JIRA replies are broken again. Entering this a third time, this time as an independent comment instead of a reply.
Please go back and re-read all the comments for this ticket.
I think the problem was that we were not generating the XML from QA.
Verified on QA. Thanks!
I think the problem was that we were not generating the XML from QA.
Actually, I think the problem was that you forgot that for this ticket we decided to modify the script which exports a copy of the original English summary to be imported into Trados (where we have the information we need for these enhancements) instead of the script which imports the translated Spanish summary into the CDR (where we don't have all the information we need). Linda and her team do the work of translating the summary from English to Spanish, not the export script.
The document labeled "Modified English Summary" hasn't been translated yet. That's why it's in English instead of Spanish. Translation from English to Spanish happens in the next step.
Thanks, Bob! This is very helpful!!! Oh, how I wish every part of the CDR was explained with a diagram like that?😃
I did remember we decided not to go with my initial approach but what was happening on QA was that the Spanish team was using documents that had been generated on PROD, did a quick pass-through World sever (since we were just testing the affected elements and not the translation) and asked me to import/create them on QA. So, the XML's they provided from WS had translation issues and because the documents were not generated on QA, they missed the Export script step. So, we were bound to run into problems. 🙁
Oh, how I wish every part of the CDR was explained with a diagram like that?
That would be a LOT of diagrams! 😛
You mean, like this?
Yes, I love it. It is concise and straight to the point. Thank you!!
Verified on PROD. Thanks!
| File Name | Posted | User |
|---|---|---|
| image-2023-10-18-08-17-10-171.png | 2023-10-18 08:17:10 | Kline, Bob (NIH/NCI) [C] |
| image-2023-10-19-12-01-45-680.png | 2023-10-19 12:01:46 | Kline, Bob (NIH/NCI) [C] |
Elapsed: 0:00:00.001319