.. TheSince the Wayback Machine API is highly . To work around the challenge of providing performant for simple queries, with a typical response . The delay in milliseconds, we are able to query the API before rendering the page using a Nuxt route middleware module. API error handling and a request timeout were adde to ensure that edge cases such as API failures or network timeouts do not block rendering of the 404 response page.
The only Internet Archive API feature missing for our initial list of requirements was access to snapshot page thumbnails in the JSON data payload . The received from the API. Access to these images would allow us to enhance our 404 page with a visual cue of archived page content.
Results and Next Steps
Our ability to include a link to an fresh mobile database archived version of a delete web page on our 404 response page helped ease the tough decisions content stakeholders were oblige to make about what content to archive and then delete from the website. We could guarantee availability of content in perpetuity without incurring the long term cost of maintaining the information ourselves.
The API brings back the most recent
Wayback Machine capture by default
which is sometimes not created by us and hasn’t necessarily
passed through our archive quality the actual residual income is assurance process. We intend to develop our application further
so that we privilege the display of Getty’s own page captures. This will ensure we’re delivering the highest quality capture to users.
Google Analytics has been configured
to report on traffic to our 404 pages and will track clicks on. The links pointing to Internet Archive pages, providing useful feedback on what portion of archived page traffic is referred from our 404 error page.
navigational affordances to legacy content and . To work around the challenge of providing ensure web page titles of old content remains . The accessible consumer data to search engines, we intend to provide an up-to-date index of all archived getty.edu pages.