Skip to main content

Glossary

Parser​

A parser is a script that collects data from specified web resources based on given queries, processes them, and outputs the result in a default or specified format.

Built-in parsers​

Built-in parsers are pre-installed parsers available by default, whose functionality is maintained on a permanent basis.

Custom JS parsers​

Custom JS parsers are open-source parsers written in JavaScript and available in the JS Parser Editor, which can be exported and imported along with a task. Examples of such parsers can be found in the Parser and Preset Catalog.

Preset​

A preset is both a saved task created in the Task Editor by selecting a combination of parsers, settings, and options to perform a task, and individual parser settings (settings preset).

Parser settings​

Parser settings are options that can be edited or changed (overridden) for a different parser algorithm to obtain a non-standard result.

Saved task​

A saved task is a preset that has been saved and can be reused.

Threads config​

A threads config is a set of thread settings that can be saved under a name and reused with different presets.

Threads​

Threads are multiple contexts launched simultaneously for parsing, in which the parser executes queries in parallel, rotates proxies according to a specific strategy defined in the Threads config, and logs the parsing process for each query.

Proxy checker​

A proxy checker is a controller responsible for loading and checking proxies using a set of proxy checker settings.

Proxy​

A proxy is a string/array of strings of a certain format (or a link to a string/array of strings) that allows hiding the real IP address by sending requests during parsing and transferring data packets from the server to the client via an intermediate proxy server.

Result template​

A result template is a template that defines the format and collected data of the result, specified directly or using the built-in Template Toolkit engine.