...
| Parameter | Description | Note |
|---|---|---|
title | The string expression or $SCRIPT(...) | |
description | Ibid. | |
publishedDate | Ibid. | |
fullText | Ibid. | |
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:
| |
appendTagsToDocs | ||
geoTag | using geo tag the following is possible
See example below. |
Setting Metadata Values
...
| Code Block |
|---|
{ "_id": "5048efb0e4b01fd6455420ee",
"title": "RE: Testing Preschedule workspace",
"url": "smb://modus:139/enron/testing/semperger-c/deleted_items/37QTKE~3",
"created": "Sep 6, 2012 06:42:01 PM UTC",
"modified": "Jul 24, 2012 01:13:02 AM UTC",
"publishedDate": "Jul 9, 2001 06:33:32 PM UTC",
"source": [
"Enron Emails (TextRank)"
],
"sourceKey": [
"modus.139.enron.testing.."
],
"mediaType": [
"Email"
],
"description": "I
am trying to pull it up now, it's taking a long time\r\n\r\n \r\nFrom:
\tSmith, Will \r\nSent:\tMonday, July 09, 2001 11:28
AM\r\nTo:\tSemperger, Cara\r\nSubject:\tRE: Testing Preschedule
workspace\r\n\r\nYes, but Vish made the changes in Table Edit. : -
)\r\n\r\nWill\r\n\r\n \r\nFrom: \tSemperger, Cara \r\nSent:\tMonday,
July 09, 2001 1:20 PM\r\nTo:\tSmith, Will\r\nSubject:\tRE: Testing
Preschedule workspace\r\n\r\nSo, this table edit that Brett is asking me
to test is really from ",
"entities": [
{
"disambiguated_name": "on- june 18-paloverde-day",
"index": "on- june 18-paloverde-day/keyword",
"actual_name": "on- june 18-paloverde-day",
"type": "Keyword",
"relevance": 0.10585404743253149,
"frequency": 1,
"totalfrequency": 12,
"doccount": 12,
"dimension": "What"
},
{
"disambiguated_name": "mulitple times additional data",
"index": "mulitple times additional data/keyword",
"actual_name": "mulitple times additional data",
"type": "Keyword",
"relevance": 0.18088061045762382,
"frequency": 1,
"totalfrequency": 12,
"doccount": 12,
"dimension": "What"
}, |
| Anchor | ||||
|---|---|---|---|---|
|
You can use document metadata to set location values using geoTag. In the example source, the docMetadata block has been configured to use javascript to set the city, country and stateProvince. In this example, the javascript function and variables were already defined using the globals.
| Code Block |
|---|
}, {
"docMetadata": {
"title": "$metadata.subject",
"description": "$metadata.summary",
"publishedDate": "$metadata.incidentdate",
"geotag": {
"city": "$SCRIPT( return _doc.metadata.location[0].citystateprovince.city; )",
"country": "$SCRIPT( return _doc.metadata.location[0].country; )",
"stateProvince": "$SCRIPT( return _doc.metadata.location[0].citystateprovince.stateprovince; )"
}
}
}, |
Output:
The output of the example source, returns the location information pertaining to the source data.
| Code Block |
|---|
"location": [{ "citystateprovince": {
"city": "Manugay",
"stateprovince": "Kunar"
},
"country": "Afghanistan",
"region": "South Asia" |
IN PROGRESS
| Panel |
|---|
Footnotes: Legacy documentation: Legacy documentation: |
...