So. We have a bunch of layers.
For RETS, it starts at the RETS feed coming in - you can debug see whats in the feed, and see what happens with our mapping. so that's interacting with layer 1. Rope. Once it gets pulled through rope, it goes into our DB, Mongodb which is layer 2. Theeen from there property-search picks up what exists in mongodb. layer 3. and lastly it goes to their website, layer 4, which is where RG2 comes in and decides what to do with the data.
For WebAPI it's mostly the same as RETS except adding an additional layer for tycho, which stores the raw data from the WebAPI feed. feeds.realgeeks.com is used to configure the pulls for tycho raw similar to how rope is used to configure the pulls for pulley, but with a lot less mapping since we are storing the raw data set.
For RETS feeds:
layer 0 = the RETS feed
layer 1 = rope & pulley
layer 2 = mongodb
layer 3 = property-search
layer 4 = rg2
layer 5 = client's website
For WebAPI feeds:
layer 0 = WebAPI feed
layer 1 = feeds.realgeeks.com & tycho raw
layer 2 = rope & pulley
layer 3 = mongo
layer 4 = property-search
layer 5 = rg2 / their website