The web parser uses django's get_or_create to check if the exact object is already in the database. If the get fails, we save the object.
However, when modifying the object before saving, we only get a match if we tried to store e.g. a location, that already matches of the google places' data.
That never happens since we would need the geo information (latitude, longitude) for that, which is why we try to modify the object in the first place.
My suggestion is to move the geo information lookup to the data scraping. We should have two additional classes:
The web parser uses django's get_or_create to check if the exact object is already in the database. If the get fails, we save the object. However, when modifying the object before saving, we only get a match if we tried to store e.g. a location, that already matches of the google places' data. That never happens since we would need the geo information (latitude, longitude) for that, which is why we try to modify the object in the first place.
My suggestion is to move the geo information lookup to the data scraping. We should have two additional classes:
these two classes are called by any parser.