Versions Compared

Old Version 22

changes.mady.by.user AlexI

Saved on

compared with

New Version 23

changes.mady.by.user AlexI

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ParameterDescription
title

The string expression or $SCRIPT(...)

descriptionThe string expression or $SCRIPT(...)
publishedDateThe string expression or $SCRIPT(...) - must return one of the supported data formats below
mediaType
The string expression or $SCRIPT(...) specifying the document mediaType (otherwise taken from top-level source field)
tags
A ,-separated list of string expressions or $SCRIPT(...) - returning a ,-separated list, the result of each will be added to the tags
fullTextThe string expression or $SCRIPT(...)
displayUrl

"displayUrl" sets the corresponding document JSON field. It is guaranteed not to be used by the Infinit.e platform. It is therefore useful for linking documents to external content. For reference, the way that it is used in the Infinit.e GUI is as follows:

  • If it starts with "http://" then it is treated as a web link
  • If it starts with "$infinite" then it is treated as a relative web link to the cluster URL.
  • Otherwise, it is assumed to be a relative file path to the fileshare specified in the source url field. (eg you can use the "Document  - File - Get" call with the "sourceKey" concatenated to the "displayUrl" to retrieve the file directly from the fileshare).
appendTagsToDocs

If true, source tags are appended to the document.  Default value is false.

geoTag

using geo tag the following is possible

  • specify the fields to extract from your structured data source to use as your latitude and longitude values
  • specify city, state/province, and country.

 "lat": "string", "lon": "string, "city": "string", "stateProvince": "string, "country": "string", "countryCode": "string

See example below.

Supported date formats

Code Block
					"MMM d, yyyy hh:mm a",
					"MMM d, yyyy HH:mm",
					"MMM d, yyyy hh:mm:ss a",
					"MMM d, yyyy HH:mm:ss",
					"MMM d, yyyy hh:mm:ss.SS a",
					"MMM d, yyyy HH:mm:ss.SS",
					
					"EEE MMM dd HH:mm:ss zzz yyyy",
					"EEE MMM dd yyyy HH:mm:ss zzz",
					"EEE MMM dd yyyy HH:mm:ss 'GMT'Z (zzz)",					


					"yyyy-MM-dd'T'HH:mm:ss'Z'",


					"yyyyMMdd",
					"yyyyMMdd hh:mm a",
					"yyyyMMdd HH:mm",
					"yyyyMMdd hh:mm:ss a",
					"yyyyMMdd HH:mm:ss",
					"yyyyMMdd hh:mm:ss.SS a",
					"yyyyMMdd HH:mm:ss.SS",


					"yyyyDDD",
					"yyyyDDD hh:mm a",
					"yyyyDDD HH:mm",
					"yyyyDDD hh:mm:ss a",
					"yyyyDDD HH:mm:ss",
					"yyyyDDD hh:mm:ss.SS a",
					"yyyyDDD HH:mm:ss.SS",


					"dd MMM yy",
					"dd MMM yy hh:mm a",
					"dd MMM yy HH:mm",
					"dd MMM yy hh:mm:ss a",
					"dd MMM yy HH:mm:ss",
					"dd MMM yy hh:mm:ss.SS a",
					"dd MMM yy HH:mm:ss.SS",


					"MM dd yy",
					"MM dd yy hh:mm a",
					"MM dd yy HH:mm",
					"MM dd yy hh:mm:ss a",
					"MM dd yy HH:mm:ss",
					"MM dd yy hh:mm:ss.SS a",
					"MM dd yy HH:mm:ss.SS",
 
					"EEE, dd MMM yyyy HH:mm:ss Z" (SMTP)
					"yyyy-MM-dd" (ISO date)
					"yyyy-MM-ddZZ" (ISO date time-zone)
					"yyyy-MM-dd'T'HH:mm:ss" (ISO datetime)
					"yyyy-MM-dd'T'HH:mm:ssZZ" (ISO datetime time-zone)

If the date matches none of those, it is passed to the JChronic NLP package, however that has a low success rate.

Examples

Setting Metadata Values

...