Board Support
      Back to home
      1. Internal RG Wiki
      2. Internal Documents
      3. Board Support

      Combining MLS boards onto a site

      Right, now that you have reviewed how to create a new board, you can now read below.

      Combining example:    *** If a client has been on one board for a long time and are looking to combo with new boards, make sure the newly added board go in and fit well with the board they are already on.  If any fields are not compatible with the old board, let the client know why they did not work with the new boards.  If they are a fully new client you can do whatever makes sense. Try to keep the same names of the fields that both boards have. For example, if both boards have the field level and the name that was decided to identify it is "stories", you would name the new board field "stories".     NTREIS (45), Houston (161) and WFAR (241)

       

      1. Go to Mongo to check what databases each of the boards are on.  
      2. cid 45    connecting to: m10e-2.real-geeks.6626.mongodbdns.com:27017/properties (this is the database that the board is on)
      3. cid 161 connecting to: m10e-2.real-geeks.6626.mongodbdns.com:27017/properties (this is the database that the board is on, which is the same as Board 45)
      4. cid 241 connecting to: m10d-2.real-geeks.6626.mongodbdns.com:27017/properties (this one is in database d and should be moved over to database e)

      IMPORTANT:

      If you need to perform a database migration you need to make sure that all other boards that the board is combo'ed with are migrated to the new database as well.

      Consult with Paul if you are unsure.

       EXPORT   root@ip-172-30-4-197:~# mongoexport --collection properties --out board_264.json --query '{ board: 264 }' --uri mongodb+srv://igor:Aethi3maqu@m11b-oxdzz.mongodb.net/properties  IMPORT root@ip-172-30-4-197:~# mongoimport --collection properties --file board_264.json --uri mongodb+srv://igor:Aethi3maqu@m11a-oxdzz.mongodb.net/properties    http://rope.realgeeks.com/rope/dbserver/  You would then go to the new board you created in rope and CHANGE INFO IN ROPE          COMPARE THE YAML FILES
      • This is how to see what is mapped.  Go to the forms/fields YAMLs for the boards and compare them.
      • Ex: open the forms/fields YAMLs for ntreis_hart.yaml (the combo board) and 
        wichita_falls_tx.yaml (the YAML for 241)
      • Open Rope to see if we can map fields that are mapped on the old board for this board. Compare the formats of how the data is provided. Ex: for Stories on 241 it is provided in word format and it is in number format in the ntreis_hart.yaml  so it is not compatible.  Can also check in RET-S for other fields such as “style” which is similar to “Stories” - but in this case the data was still provided in a non-compatible format.  Start with basic data and add more if the client requests - they are aware that not all fields will be compatible and that duplicate listings may exist if they are in each board. 
      • Make sure to compare the field and the format that it is provided in (you would need to do distincts for each field if you are not sure to make sure that the values are similar)
      • Create a new YAML with the data that will combine for the combo board. Save this YAML file by separating all three names with underscores.

      NOTE: If the field is not mapped across all boards, do not use it in the forms or fields. While it will technically work, it will create a poor user experience. To use the field as a searchable field, it must be "All or none." With that being said, you can still use these fields in the prop_fields so that they display in the property display search options.

      • Open the combo forms yaml (here for board 45 and 161) and crosscheck the other fields in Rope to see which ones are not mapped from board 241
        • Ex: here short sale was not mapped for the board - looked in RETS-MD to search for it under the property path and see that it has a unique name.  Search for this name in the board data in Rope.  Map this field as “short_sale: Hit Save.
      • Save the new Forms YAML with the board combo name
      • Prop file: copy and paste the file for all three of the boards into one new Prop field and hit Save. 
      • Commit the new boards in GitHub: Commit Message: Initial Commit, New Combo Board 45, 161, 241
      • SYNC
       Go to iTerm (terminal) and do this:  root@ip-172-30-4-197:~/scripts# ./background.sh ./runner.py refresh_known_properties --skip-images 241 5bd19af495ea6a055434594764e592089c5d14f37897ed2c2590b937fe86c502  Go to MCP: Open the board specific MCP site for both the existing combo board (45 and 161) and also the other board (241) or if you are only combining two, then open the existing board.  - Go to the board settings tab and get the info in the first two lines to combine into a new board  - scan both the existing boards and see if anything is unusual, such as not set to Default     Copy over the IDX Service URL and the Property Cache Time to the new board   HIT SAVE.    Copy the Search Status Map and the Alert Status Maps from the old boards into the new boards and make sure all the things are covered.    Set the YAMLs   — Go to your dev site and reset the board and the YAMLs to test out the new site info.                 - test each property type, each search field and higher and lower numbers to make sure that things are changing, a few location sections, check out county and city and make sure they all load, check property detail page for each property type.                — If the neighborhood search freezes, make sure to remove the All option from County so that it will limit what appears. flags: [+no_all] — Check the command that you ran in Papertrail to see if the background refresh_known_properties is complete — search for the keys in all systems.   Click here for instructions for migrating a board from one idx server to another.  

       Click here to see the example email after combo-ing a site