Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Verity stores information for processed request URLs in the Verity database. Data stored includes:

  • Page and Video classifications

  • Page metadata

  • Image metadata

  • Video metadata

If a request for a processed page URL is received, Verity recreates a JSON response based on the stored data (unless the ignoreCache flag is explicitly set for a page analysis request).

Time to Live (TTL) for Verity Data

JSON response data is maintained by Verity for a time-to-live (TTL) period. The default TTL varies depending on the type of content analyzed.

There are different TTL periods for Video, Image, and Text data. Page data is further analysed to differentiate between website home pages and all other pages on the site (as website home pages are likely to update frequently).

For example https://www.latimes.com/, the home page of the Los Angeles Times, will be updated frequently and will therefore have a TTL of 30 minutes. The page https://www.latimes.com/travel/list/la-best-dog-friendly-hikes-trails-beaches-parks is unlikely to be updated frequently and will have a TTL of 30 days.

Verity considers a home page to be a web page accessed at either:

  • <website URL>/

  • <website URL>/index.html

Content Type

Default TTL

Page

Website home page

30 minutes

All other pages

30 days

Video

360 days

Image

4 days

Text

30 days

Every Verity response includes processedAt and expiresAt fields, indicating the date and time that classification data was generated and will expire from Verity storage:

"processedAt": "2021-05-25T17:57:03.690Z"
"expiresAt": "2021-06-24T17:57:03.690Z"

GumGum backs up Verity page and video analysis classification data for 11 months. The page, image, and video metadata is backed up for 180 days.

Client Cache TTL Configuration

GumGum expects clients to store Verity classification result data in their own environment. GumGum recommends that clients configure a TTL of at most 30 days for their cached classification data. Beyond the configured TTL period, updated classifications can be requested from the Verity API.

Note: Although GumGum recommends a TTL of at most 30 days, the configuration of caching parameters is at the discretion of the client.


  • No labels