| Issue Number | 4579 |
|---|---|
| Summary | [Drupal CMS] Tables to track published content |
| Created | 2019-02-25 14:04:00 |
| Issue Type | Task |
| Submitted By | Kline, Bob (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2019-03-15 09:04:45 |
| Resolution | Won't Fix |
| Path | /home/bkline/backups/jira/ocecdr/issue.240717 |
We will need separate tables to track the PDQ content in the Drupal CMS. Design and implement these tables. Part of https://github.com/NCIOCPL/cgov-digital-platform/issues/825 epic.
It has been decided that we will not worry about tracking shifts in which Drupal instance was populated by which CDR tier over time, or which of those systems was refreshed from a higher tier at which time. Instead we will deal with these shifts manually by
using the API which the Drupal CMS instances implement for returning a catalog of the PDQ content currently stored in the CMS
using the script created for OCECDR-4584 to re-populate the PDQ content on a given Drupal CMS instance
coordinating the refresh of a lower-tier Drupal CMS instance with a concurrent refresh of the CDR tier which publishes to it.
Elapsed: 0:00:00.001324