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.

versioncreated

This is the time this version of the object in question was created.

For photos this is the time of the photo.
For news articles it is the time of release.
For planning and event items it is the time of the release of the current version.

(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.)

versionstored

The time we added the object to our database.

For photos where TT act as a slave database, this is the time of archival in SDL.
For news articles it is when the item was added it to the TT delivery-database.
For planning or events when it was added to the TT delivery-database.

(TTNewsML does not show versionstored.)

embargoed

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

Date part only no time (see datetime).

The date of an object. This is most often the same as versioncreated, with notable exceptions:

For photos this is the date the photo was taken.
For news articles it is is the date the news story was released.
For event items it is the date of the event.
For planning it is the date of the planned activity. It can be the same date as the event the planning is about, but it can also be another date. All plannings are not connected to an actual event.

(In TTNewsML the date is shown in the contentMetaExtProperty of type date.)

datetime

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.)

enddate

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.)

enddatetime

Date and time

Same as datetime but for ending.

(In TTNewsML the date is shown in the contentMetaExtProperty of type enddatetime.)

week

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.)

_tstamp

Internal field used for search result sorting. It is mapped differently depending on type of data.

news
- this field is set to versioncreated (time of news story).
planning
- this field is set to datetime (time of planned event).
photos:
1. if versioncreated is 19700101 we assume it's unix time (epoch) 0 and not a correct date.
2. if versioncreated is not okay:
  1. use versionstored if it is before last midnight. The midnight rule is to avoid old photos appear on first page.
  2. else null (we have no okay date)
3. if versioncreated is okay:
  1. use versioncreated if it is before last midnight.
  2. else use now. This is so that photography for today that are indexed/recevied out-of-order, still will appear in the order we receive them.