2
Антон
no recommendations
no complaints
Closed
Project title: Parser perll
Type of cooperation: Periodic employment
Section: Software development
Prepayment: prepayment is possible
Payment methods: Electronic money
Acceptance of requests: closed
Type of cooperation: Periodic employment
Section: Software development
Prepayment: prepayment is possible
Payment methods: Electronic money
Acceptance of requests: closed
Project description:
It is necessary to perform the most efficient multithreaded proxies parsing on perl, collecting data, dynamic information (structures) in the bookmaker’s office betcity, and the data obtained are identified with the data from the dictionary and then write in the desired format to the mysql database.
Structure: name of BC -> Sports (line ) -> category -> event (date, time, team 1, team 2, url ) -> betting (type of bet -> values, url )
Next, the number of BCs will be parsed for comparing data, namely, rates (example www.livescore.in/en )
At each stage, the data has its own vocabulary, starting with the sport, i.e., the data has its own vocabulary. Different BC the same information can be in Russian, in English, on the translit, "I will ask in advance" and so on. The task of the dictionary at each stage, regardless of the form in which the information was provided, was run through it and recorded in the desired format in the database.
For example, the dictionary sport: football, volleyball, basketball, hockey, tennis, etc., in betcity it looks like this, and in another BC this information will be in English, i.e. The dictionary contains all possible options, but with its own keys for infofication by sport. In other words, the information is submitted in English, and we convert, using a block dictionary, always in Russian format (by the first value) into a database. And if there are no coincidences in the dictionary, then there is no key "0";
In the database, the information is only current.
It is necessary to perform the most efficient multithreaded proxies parsing on perl, collecting data, dynamic information (structures) in the bookmaker’s office betcity, and the data obtained are identified with the data from the dictionary and then write in the desired format to the mysql database.
Structure: name of BC -> Sports (line ) -> category -> event (date, time, team 1, team 2, url ) -> betting (type of bet -> values, url )
Next, the number of BCs will be parsed for comparing data, namely, rates (example www.livescore.in/en )
At each stage, the data has its own vocabulary, starting with the sport, i.e., the data has its own vocabulary. Different BC the same information can be in Russian, in English, on the translit, "I will ask in advance" and so on. The task of the dictionary at each stage, regardless of the form in which the information was provided, was run through it and recorded in the desired format in the database.
For example, the dictionary sport: football, volleyball, basketball, hockey, tennis, etc., in betcity it looks like this, and in another BC this information will be in English, i.e. The dictionary contains all possible options, but with its own keys for infofication by sport. In other words, the information is submitted in English, and we convert, using a block dictionary, always in Russian format (by the first value) into a database. And if there are no coincidences in the dictionary, then there is no key "0";
In the database, the information is only current.
