Create automated sitemap.xml generation for policy/guidance pdfs #3598
Labels
Guidance Search
Work associated with Executive Order requiring Policy and Guidance search page
Technical debt
Work: CMS back-end
Milestone
@jason-upchurch commented on Fri Feb 28 2020
Summary
From #3554, we need to build automated sitemap generation based on existing/added/deleted content and create update policy/schedule, e.g., once per day to be consistent with search.gov
No longer blocked: This ticket is presently blocked by fecgov/openFEC#3580, which creates the strategy for dealing with policy/guidance documents in an unambiguous way to enable automatic sitemap generation (which will enable automatic index updating).
When working on this ticket, we need to consider: #3280
Completion criteria
proxy
url to "correct one")robots.txt
and indexing multiple sitemapsTechnical considerations
ATOAWS/cloud.gov v server@jason-upchurch commented on Tue Mar 03 2020
Related issue opened with cloud.gov to consider AWS Lambda or Scheduled Task: cloud-gov/s3-broker#38
@jason-upchurch commented on Tue Mar 03 2020
@lbeaufort advised in sprint planning to use caution with respect to this work as it pertains to ATO.
cc @wjiangFEC @PaulClark2
@jason-upchurch commented on Tue Mar 03 2020
requesting ATO for review. Issue open with cloud.gov to check feasibility of deploying cloud.gov only solution. Investigating contingency plans, i.e., server based, in the event cloud.gov is unable to support application.
The text was updated successfully, but these errors were encountered: