Versions Compared

Old Version 21

changes.mady.by.user AlexI

Saved on

compared with

New Version 22

changes.mady.by.user AlexI

Saved on

Key

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

...

  • "JSON" - this is the full source including all fields
  • New source pipeline:
    • "JS" - The global script that all other elements can use - all of the logic can be written in here as separate functions, and then the scriptlets in other pipeline elements can be simple calls to these functions, to maximize the maintainability of the code in the source.
    • "LS" - If generated Logstash sources, you can write the configuration directly into here
    • "UI" (currently only supported in the enterprise build) - brings up the source builder GUI
  • Legacy sources:
    • "JS-U" - the Unstructured Analysis Module allows content to be transformed by "scriptlets" (xpath/regex/javascript) into document metadata. This view shows only the javascript maintained in "unstructuredAnalysis.script" - all of the logic can be written in here as separate functions, and then the scriptlets can be simple calls to these functions, to maximize the maintainability of the code in the source.
    • "JS-S" - the Structured Analysis Module allows content to be transformed by "scriptlets" (xpath/regex/javascript) into document metadata. This view shows only the javascript maintained in "structuredAnalysis.script" - all of the logic can be written in here as separate functions, and then the scriptlets can be simple calls to these functions, to maximize the maintainability of the code in the source.
    • "JS-RSS" - (only visible if the "searchConfig" field of "rss" is specified; use "Save Source" to reset visibility if it changes during editing) the Feed Harvester can use javascript (and xpath) to create multiple documents out of a single received feed. This view shows only the javascript maintained in "rss.searchConfig.globals" - all of the logic can be written in here as separate functions, and then the scriptlets can be simple calls to these functions, to maximize the maintainability of the code in the source.
Info

By default only you can see your temporary copies of sources (so for example you cannot share links to sources being edited). You can use the file uploader to share in either read or read-write:

  • Go to the file uploader , filter on JSON type "source", select your source
  • Share with a community in which your collaborator belongs (and is at least a "content publisher" if you want him to make changes)
  • If you want to provide him with the ability to make changes, set the read access
    • Warning - there is no automatic synchronization, so if you both make changes at the same time work can be lost

Validating the Source Format

...