Tips

4 авг 2013


  • This page is used for automatically generate tips in the parser.
    Tips available if you hover the mouse an item in the parser.


    AddTask(top)



    Config Preset(top)


    Choice of settings threads for the current task, click the pencil to edit.

    Task Preset(top)


    Selecting a previously saved task. When you create task, you can save all of its settings, in the future simply select it from the list.

    Save Preset(top)


    Saving a preset task with the current name given in the Task preset. Preset with the default name can not be changed - you need to save under a new name.

    Save Preset As New(top)


    Saving a preset task under a new name.

    Add Parser(top)


    Adding a new parser in the task. In one task can use multiple parsers, that allows to for a single query to get information from different sources (e.g. link Google and Yahoo or different domain parameters, such as date registration, PR, the number of pages in the index, etc.) and combining the results from all parsers using the Result format.

    Query Format(top)


    Template format used for each query, you can add the substitution
    Supports the following macros:

    {query} - the original query, for example:
    "{query}", site:{query}, info:{query}, http://{query}/

    {az:START:END} - substitution of numeric-symbol sequence, for example:
    {az:a:z} - substitution all symbols from a to z (a, b, c, ..., x, z)
    {az:aaa:zzz} - substitution all symbols from aaa to zzz(aaa, aab, aac, ..., zzx, zzz)
    {az:a:zz} - substitution all symbols from a to zz(a, b, c, ... aa, ab, ..., zx, zz)
    {az:00:99} - substitution all numbers from 00 to 99(00, 01, 02, ..., 98, 99)
    {az:а:яяя} - substitution all cyrillic symbols from а to яяя(а, б, ... аа, аб, ... яяю, яяя)

    {num:START:END} - substitution numbers in that interval, for example:
    {num:1:1000} - substitution all numbers from 1 to 1000(1, 2, 4 ..., 999, 1000)

    {each:WORD1,WORD2,...} - substitution specified words WORD1, WORD2 and etc., word length is not limited to, for example:
    {each:green,blue,red,black} - substitution of the words green, blue, red, black
    {each:,buy,sell} - substitution of the empty word, than buy and sell

    {subs:NAME} - substitution of additional words of the files in the folder queries/subs/, for example:
    {subs:zones} - substitution of all rows from the file queries/subs/zones.txt

    Result format(top)


    Allows you to to set format of the result as using one parser, and using multiple parsers, macros:

    parserN(RESULT) - specify which parser N display the result RESULT
    Number N indicates the number of parser that is displayed in front of each selected parser
    Instead of RESULT substituted macros indicating which result from the parser you want to display
    Every parser has its own set of results, such as a parser SE::Google as a result can produce lists of links, anchor text, code snippets, and also number of pages. The list of possible results you can view by hovering the cursor on the parser.

    {query} - displays the current query
    {origquery} - displays the current query before format through Query format
    {firstquery} - displays the original query when using options Parse to level and Parse all results
    {querynum} - displays the serial number of the query
    {lvl} - shows the number of multi-level nested query by parsing
    For example, choose one parser - SE::Google and preset 1000 Links use Proxy, in field Queries inscribe 2 queries test1 and test2, in Result Format we write:
    {query}: parser1({totalcount}\nserp[{link}\n])

    Result:
    Let us examine more:
    {query} - displays query
    parser1(...) - displays information for the parser 1(SE::Google):
    • {totalcount} - total count pages in Google for this query
    • serp[{link}\n] - displays a list of links.
    Additional features of arrays:
    • {num} - current position in the array, starting from zero
    • {query} - query, allows us to derive a query for each element of the array
    • array[...][N] и array[...][N-M] - displays results on the a specified position or on the range
    • array[].size - displays the number of elements in the array

    Queries from(top)


    Determines where to get queries for parsing.
    A large list of queries must be saved in a file that is must placed on a folder queries/, after which it will be possible to choose in the field Select File.
    A small number of requests (up to 8K) can be specified directly in the form, it is necessary to select Queries from: text
    Optional available with a choice as query files from the folder with the results - results/

    Unique queries(top)


    Determines whether to make queries unique, it is necessary to then 2 cases:
    • In queries can be an unwanted repeats - parser automatically screened out their
    • When using Parse to level possible substitution of previously passed queries, which can cause to infinite loops parsing. When using Parse to level necessary to choose Unique queries

    Make unique(top)


    Defines make the results unique or not. This is an easy method to make the result unique - after the formation of the final result it is broken down line by line and deletes the repeated lines
    In order to make the result unique in the domain, subdomains, mailboxes, etc. need to use the Add unique results, which can be selected by clicking the tool icon to the right of the parser. If you select Add unique results, then there is no need to include a unique result on the line.
    Quality setting Unique result and memory consumption are in Settings -> Configs Presets.

    File Name(top)


    The file name to save the results, the results are saved in a folder results/
    Supports templates from Results format, additionally supports the following macros:
    • {date} - The date in the format Jan-12 at the time of start tasks
    • {time} - The time in the format 16-22-49 at the time of start tasks
    • {queriesfile} - Substitute the name of the file with queries
    Possible to use subfolders in the path of unlimited nesting levels, they will be created, if necessary, for example:
    {date}/{time}/{queriesfile}

    Do log(top)


    Determines whether to record a log of completion for each request. Slows down work, there is usually no need to keep a log.

    Keep unique(top)


    Ability to save information about Unique.
    Suppose we need parse references in the task, but in the future parse more links to other requests, but retain only the new links:
    The first parse we create a new base Unique and give it a name. For the second and subsequent parsing we select a previously created database.