...
| 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 |
Setting Metadata Values
When structured data is extracted from a source (via the File, Database, or other harvester), each field extracted is captured in the Feed.metadata object. Within the Structured Analysis Harvester data stored in the Metadata object can be access using the $ operator to signify that we are attempting to retrieve data from a field in our document.
...
| 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"
}, |
displayUrl
IN PROGRESS
Legacy documentation:
TODO