Determine if it is possible to set up the ability to do a full refresh of the aggregator feed if necessary to remove unwanted content, and if it is possible, estimate how much effort that would take.

[OpenGlobe]

User story

Does or can the page update based on what is happening on the original Tumblr feed? So, if a post disappears, can we make sure that it's not showing up on the aggregator? And what does this process look like in terms of a workflow?

(The workload here shouldn't be too much, but would need to be documented).

Acceptance criteria

• [ ]
• [ ]
• [ ]

Definition of done

• [ ]
• [ ]
• [ ]

[fureigh]

There doesn't seem to be a Drush or Drupal console command for this. (The Feeds module is a separate matter; we're using the core module Aggregator.)

I'd suggest writing a simple custom Drush command that deletes and re-updates a specific feed, taking the feed ID as an argument. Then you could run it with something like bin/drush reimport-feed 2, where 2 is the ID of the relevant feed source.

The relevant routes to hit are:

• /admin/config/services/aggregator/delete/{aggregator_feed}
• /admin/config/services/aggregator/update/{aggregator_feed}

(The way to do this manually, through the UI, is to go to /admin/config/services/aggregator, click Delete items (under the Operations heading for the relevant feed), then click Update items. "Update" here really means "look for new items," not "update items that have already been imported". But I recommend the scripting approach.)

[trinehar]

Feeds based on NSF social media properties will be a part of the site whether in this exact version or not, and the ability to force a refresh would always be a requirement.