| Issue Number | 4239 |
|---|---|
| Summary | Release independent schema changes |
| Created | 2017-03-13 15:01:32 |
| Issue Type | Improvement |
| Submitted By | Osei-Poku, William (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2017-09-08 07:48:06 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.204578 |
Please explore the possibility of implementing schema changes outside
regular CDR releases.
There are some important schema changes [OCECDR-4236] we don't control,
and therefore cannot coordinate to be implemented with scheduled CDR
releases. And not implementing the changes sooner means that we cannot
publish important changes to summaries.
This is ready to be tested on DEV. I've done some testing, and I'd
like you to do some as well, ~volker. You'll find a new
Post Schema link on the Developer/SA admin menu.
Thanks.
https://github.com/NCIOCPL/cdr-admin/commit/a04b10d28cce56b325e4f220e714ce4fd753088d
https://github.com/NCIOCPL/cdr-admin/commit/7d65637ef087db71360acc8ec12f0d4d79db61d1
So, with this new tool we're loading a file that updates an existing (or creates a new) schema file? Will this work for any schema or is it limited to the Citations?
So, with this new tool we're loading a file that updates an existing (or creates a new) schema file?
Correct.
Will this work for any schema or is it limited to the Citations?
Any schema. Now you've got me scratching my head wondering what I put in the interface that made you think it just works with the Citation schema. :-)
Let me help you here:
The description links to OCECDR-4236 which is discussing the problem of
not being able to validate citations due to an NLM schema change. There
are many clues that point against that assumption, i.e. the option to
"Post New Schema" and the fact that you like to implement general
solutions but I wanted to be sure.
I've updated the CdrCommonBase.xml schema and adding a new
attribute to the element Email. This worked as expected.
I;ve also successfully added a new schema to the database.
Everything looks good.
As discussed in the CDR meeting on Thursday, here is one schema change for testing purposes. These is a real change we intend to make on PROD as well so I will open a new ticket after testing.
Please add these two new values: “Spanish Caption and content revised” and “Translation reviewed” to the list of values of the Media Doc.'s ProcessingStatusValue.
The following file has been updated
Please verify on DEV.
Verified on DEV.
Please add these two new values on QA: “Spanish Caption and content revised” and “Translation reviewed” to the list of values of the Media Doc.'s ProcessingStatusValue.
The schema file Media.xml has been updated on QA.
The schema file is part of my local branch [3082c0f cdr4239].
~oseipokuw, please let me know if you had already tested this.
Bob found a problem with the schema build code and had to refresh the schemas on QA again. This wiped out the updated Media schema from yesterday. It would be ideal to keep the version on QA as is to properly test Fermi only. If you do need the schema change I will go ahead and upload the schema but you will need to realize that it's not part of Fermi and won't be on STAGE or PROD after the release.
Osei-Poku, William (NIH/NCI) [C], please let me know if you had already tested this.
I have not tested it yet.
but you will need to realize that it's not part of Fermi and won't be on STAGE or PROD after the release.
So, you're removing this ticket from Fermi?
No, we're not moving this ticket from Fermi but you had requested to have the schema changes from ticket OCECDR-4324, which is not part of Fermi, loaded.
Oh okay. Got it. Thanks!
Elapsed: 0:00:00.001316