This is an attempt to document the interpretation of various date fields in the ttninjs spec. Some fields are internal to TT and not visible in metadata delivered to customers.
This is the time this version of the object in question was created.
(In TTNewsML the newsItem, planningItem or eventItem have an element for versionCreated. The packageItem uses the same date and time as the item it is handling. It is no separate versionCreated dateTime for the package item.)
The time we added the object to our database.
(TTNewsML does not show versionstored.)
The date and time an object is embargoed until. Including the time. The date and time says when the item can be published. For digital media it mean from when it can be showed to users at the site. For print media the item can be used for editing purposes as long as the newspaper or such is not printed and distributed before the embargo date and time. The embargo is also explained in description_usage property.
(In TTNewsML the embargo is shown in the embargoed element in the itemMeta-section. description_usage is shown in the edNote.)
Date part only no time (see datetime).
The date of an object. This is most often the same as
versioncreated, with notable exceptions:
(In TTNewsML the date is shown in the contentMetaExtProperty of type date.)
Date and time
The date and time of an object.
This field is exactly the same as date, but only exists when there is a relevant time to communicate. For items where we have no time, just a date (such as for old photography), this field is left blank.
We want to avoid confusion about communicating 00:00 as time, when we actually have no relevant time data. Many events and plannings do not have a fixed time.
(In TTNewsML the datetime is shown in the contentMetaExtProperty of type datetime.)
Date part only
Same as date but used mainly when the enddate of an event or planning is known.
(In TTNewsML the date is shown in the contentMetaExtProperty of type enddate.)
Date and time
Same as datetime but for ending.
(In TTNewsML the date is shown in the contentMetaExtProperty of type enddatetime.)
This property will be present in TTNinjs when it is a feature text item and the proposed usage is planned for this week. Planning and Event items will also have the week property and for those types the week hold the week number when the event/planning is happening.
(In TTNewsML the week is shown in the contentMetaExtProperty element of type week.)
Internal field used for search result sorting. It is mapped differently depending on type of data.
newsthis field is set to
versioncreated(time of news story).
planningthis field is set to
datetime(time of planned event).
19700101we believe it's unix time (epoch) 0 and not a correct date.
versioncreatedis not okay:
versionstoredif it is before last midnight. The midnight rule is to avoid old photos appear on first page.
null(we have no okay date)
versioncreatedif it is before last midnight.
now. This is so that photography for today that are indexed/recevied out-of-order, still will appear in the order we receive them.