QualityTimebasedSyntacticDate

AI Overview😉

The potential purpose of this module is to analyze and understand the date-related information of a webpage, such as the publication date, byline date, and time zone, to determine its relevance and freshness for search results.
This module could impact search results by influencing the ranking of webpages based on their date-related information. For example, a webpage with a more recent publication date or a high-confidence byline date may be considered more relevant and therefore ranked higher in search results.
To be more favorable for this function, a website could ensure that its date-related information is accurate, consistent, and easily machine-readable. This could include using standard date formats, providing explicit time zone specifications, and ensuring that byline dates are correctly attributed to authors. Additionally, websites could focus on publishing fresh and regularly updated content to increase their relevance and ranking in search results.

Interesting Module? Vote 👇

Voting helps other researchers find interesting modules.

Current Votes: 0

GoogleApi.ContentWarehouse.V1.Model.QualityTimebasedSyntacticDate (google_api_content_warehouse v0.4.0)

Next ID: 21

Attributes

bylineDate (type: String.t, default: nil) - The following field is set only when the byline date is different from the "date" field above. Currently this happens when the byline date is within the 24 hours of the crawl time, or close but not exactly the same as blog post date due to time zone. The syntactic date is never later than the crawl time. NOTE: If this field is set, use_as_byline_date will be meaningless, and better to be cleared.
date (type: String.t, default: nil) - The number of seconds since epoch (Jan 1, 1970). This can be negative to indicate a publication date that is before 1970. For example, the ones from NY Times archive: "http://select.nytimes.com/gst/abstract.html?res=F10B13FB3D5A10728FDDAF089" "4DD405B8588F1D3&scp=91&sq=world+war+II&st=p"
daterange (type: GoogleApi.ContentWarehouse.V1.Model.QualityTimebasedSyntacticDateDateRange.t, default: nil) -
debugInfo (type: String.t, default: nil) -
fromExplicitTimeZone (type: boolean(), default: nil) - If set to true, the source of the date has explicit time zone specification. Note: This is only used internally and should not be populated in docjoins.
info (type: integer(), default: nil) - Used to store extra information about the syntactic date. For now only two bits are set. Please refer to the encoding/decoding functions provided in: quality/timebased/syntacticdate/util.h Bit 1 = High confidence byline. This bit is set if the syntactic date has a byline date and this date is considered to be high confidence. Bit 2 = High confidence byline without content age. This bit is set if the syntactic date has a byline date and this date is considered to be high confidence without support from content age.
position (type: GoogleApi.ContentWarehouse.V1.Model.QualityTimebasedSyntacticDatePosition.t, default: nil) -
precisionMark (type: integer(), default: nil) - The precision mark should be of type PRECISION_MARK.
syntacticDateNotForRestrict (type: boolean(), default: nil) - If this is true, do not use syntactic date in date restricts.
timeZoneOffsetSeconds (type: String.t, default: nil) - Indicates the time zone offset in seconds applied to derive date' in UTC. Example: Annotation: "1pm PST" (UTC-8) => -8 * 3600 = -28800 Note: This is only used internally and should not be populated in docjoins. *trustSyntacticDateInRanking(*type:*boolean(), *default:*nil) - This bit is set if we believe that the syntactic date is really high confidence, but does not qualify as a byline date. *useAsBylineDate(*type:*boolean(), *default:*nil) - Whether this date is good for display as the snippet byline date. *useInTimeZoneGuessingMode(*type:*boolean(), *default:*nil) - This bit is set if the syntactic date is good to be used in site-level timezone guessing statistics calculation. (The date should be absolute date having a timestamp with hour and minute level information. It can come with or without time zone information, which is indicated in from_explicit_time_zone field defined below.) *useRangeInsteadOfDateForRestrict(*type:*boolean(), *default:*nil`) - If true, the DateRange is used as date restrict, if false, the date is used as date restrict. Has no effect if syntactic_date_not_for_restrict is true.

Summary

Types

t()

Functions

decode(value, options)

Unwrap a decoded JSON object into its complex fields.

Types

Link to this type

t()

@type t() :: %GoogleApi.ContentWarehouse.V1.Model.QualityTimebasedSyntacticDate{
  bylineDate: String.t() | nil,
  date: String.t() | nil,
  daterange:
    GoogleApi.ContentWarehouse.V1.Model.QualityTimebasedSyntacticDateDateRange.t()
    | nil,
  debugInfo: String.t() | nil,
  fromExplicitTimeZone: boolean() | nil,
  info: integer() | nil,
  position:
    GoogleApi.ContentWarehouse.V1.Model.QualityTimebasedSyntacticDatePosition.t()
    | nil,
  precisionMark: integer() | nil,
  syntacticDateNotForRestrict: boolean() | nil,
  timeZoneOffsetSeconds: String.t() | nil,
  trustSyntacticDateInRanking: boolean() | nil,
  useAsBylineDate: boolean() | nil,
  useInTimeZoneGuessingMode: boolean() | nil,
  useRangeInsteadOfDateForRestrict: boolean() | nil
}

Functions

Link to this function

decode(value, options)

@spec decode(struct(), keyword()) :: struct()

Unwrap a decoded JSON object into its complex fields.