CDR Tickets
| Issue Number | 4597 |
|---|---|
| Summary | [Drupal CMS] Create interface for administering glossifier sites |
| Created | 2019-03-15 06:56:21 |
| Issue Type | Task |
| Submitted By | Kline, Bob (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2019-03-27 12:59:31 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.241560 |
Implement a web-based page for controlling which Drupal CMS sites
should receive nightly refreshes of PDQ Glossary data for the CDR tier.
Possibilities for storage of the information include a separate table in
the CDR database or a row in the ctl table. The URL for the
PDQ Glossifier Refresh API will be stored for each site which
should receive the scheduled updates.
Implemented on DEV. ~volker is testing.
We haven't always been consistent with this but it would be nice to repeat the menu title in the sub-title for the page:
Change "Glossary Servers" to "Manage Glossary Servers".
Why do you include the Reports menu button?
Because that's the default set of buttons for the
cdrcgi.Control class. I have overridden the default to
remove the Reports Menu button as you suggest.
Would you still want that change if it means losing the confirmation display?
Or should I keep the confirmation message for the display after a
Submit, but start off with Manage Glossary
Servers?
Or (third option) change the confirmation message to Manage Glossary Servers (24 servers saved)?
You didn't say I'm not allowed to do this 🙂 :
'ascii' codec can't decode byte 0xc3 in position 6: ordinal not in range(128)
Entering "hann.münden" as an alias.
I would prefer option (2) over (3) but I like both of them. Whichever is simpler to implement would work.
Option 2 is ready for testing.
Good catch. Please give it another try.
We'll have to remember to apply this to the other three tiers.
ALTER TABLE ctl ALTER COLUMN name NVARCHAR(255)Done on QA. Please have CBIIT apply the changes on STAGE and PROD. I'll take care of making sure the script to manage the control table handles non-ASCII names correctly.
Just wondering: What kind of sorting is applied to the group of entries?
They're sorted by Alias (case sensitive).
CBIIT ticket NCI-RITM0168723 submitted for altering the ctl table.
The table has been updated on PROD and STAGE.
I noticed that in the tables.sql script in our repository the name element is listed as a NOT NULL column but the current definition (PROD, STAGE) allows NULL values. Hoping that's correct.
Nah, that's a bug in the SQL I gave you above. We'll fix that eventually, but for now the API enforces the requirement that a non-empty string be supplied, and we can't put anything in the table on STAGE or PROD except through the API (and we can fix the table definition on DEV and QA).
| File Name | Posted | User |
|---|---|---|
| glossary-server-confirmation.png | 2019-03-27 14:41:30 | Kline, Bob (NIH/NCI) [C] |
| Screen Shot 2019-03-27 at 14.21.20.png | 2019-03-27 14:23:09 | Englisch, Volker (NIH/NCI) [C] |
| Screen Shot 2019-03-27 at 14.26.31.png | 2019-03-27 14:27:12 | Englisch, Volker (NIH/NCI) [C] |
Elapsed: 0:00:00.001899