CDR Tickets

The software blows up when it tries to generate XML to be imported into the CDR because the editors of the content in the CMS have started using a new <button/> element inside paragraph elements, and instructions for how to handle this new element are not included in the specs for this conversion. I'm guessing that you're going to want me to modify the software so that it will just drop the element and its contents ("View Transcript" in this case).

However, I'm including ~duganal and ~juther on the watchers list for this ticket to remind them that we're still using a makeshift script for this conversion because the core JSON:API module still hasn't been enabled for the cancer.gov CMS. This means that every time we have to modify the conversion software we have to do it in multiple places: once in the temporary makeshift script we're using until that module is enabled, and once for the permanent script we'll use (without having to SSH into the production Drupal server to extract the node JSON by hand) once that module is enabled. Maintaining the same functionality in multiple places is never as safe as maintaining it in one place. Just want to make sure this doesn't fall through the cracks because everyone has forgotten about it. 😉

I could cut through the Gordian knot and just modify the scripts to simply ignore any new elements the editors decide to use in the future that we haven't seen before. But you'd want to be very confident you're never going to want the information which would be dropped using that approach.

We can discuss these issues in Thursday's status meeting.

Yes, please drop the <button/> element since don't need it in the CDR, and I agree that we should discuss these issues in the CDR meeting.

XML files have been generated and attached.

Verified. Thank you!