Prepare for transition to new News feed.

[camikazegreen]

Motivation

When the QS2 version of news.arizona.edu launches, it will only be using the new version of the News feed and the current version on news.arizona.edu will cease to exist. There is no intention for the QS1 news site to support the current version, or for the QS2 version to support the old version.

Quickstart currently provides a News feed importer to pull news in from the old version of the importer, and an unknown number of sites are using it. This will stop working when the new site launches.

Proposed Resolution

Can we update the News importer to use the old endpoints, but quietly fail over to the new endpoints if the old one is unavailable? This would allow us to roll out the changes to the importer before the API changes.

[trackleft]

Related: #2582

[camikazegreen]

We also want to make sure that the News articles on both versions of the API can be correctly identified as the same article, so that sites don't start pulling in duplicates.

[joeparsons]

Quickstart action items

• [x] Update QS2 REST news export API view with any fields present in legacy feed that don't yet exist (UUID, alt text for image, etc)
• [x] Ensure QS2 news importer doesn't delete any previously imported content if feed is unavailable

[joeparsons]

Quickstart action items

• [ ] Update QS2 REST news export API view with any fields present in legacy feed that don't yet exist (UUID, alt text for image, etc)
• [ ] Ensure QS2 news importer doesn't delete any previously imported content if feed is unavailable

Working on these items.

[trackleft]

See https://quickstart.arizona.edu/node/199 for more info

[trackleft]

I will evaluate any additional steps required to close this issue.