search

Battler45 / SierraMigrationToGitHub

Migration from unfuddle to GitHub
0 stars 0 forks source link

Implement Updater for New Region / COAR / Central Oregon #104

Open Battler45 opened 4 years ago

Battler45 commented 4 years ago

George,

We have the data feed for a new region that needs to be integrated -- central Oregon. Please add this region to the sierrainteractive-4 database.

This region is powered by Rappatoni, the same as SIRA and NKAR, and so integration for this region should be similar to those other regions. Here is the information to access the feed:

http://rets172lax.raprets.com:6103/CentralOregon/COAR/Login.aspx

Agent ID = Sierra

Password = B3nd0r

User/Header = Sierra/1.72

I've attached a document they provided which contains some information about the available fields.

This region is more of a priority than converting the MLBOR region, and so if you could put the MLBOR region on hold while you complete this, that would be good.

Please let me know if you have any questions.

Thanks.

Posted by Molchanov George(unfuddle username: george)

Battler45 commented 4 years ago

Ben,

I started the implementation of this importer and I found one significant difference between its RETS datasource and RETS datasources for NKAR and SIRA regions. For NKAR and SIRA regions we have access to the HISTORY resource which we are using to select sub-sets of data with condition by date of records' change. We need to use HISTORY resource because of the Rappatoni doesn't give an opportunity to use date in query. With COAR region we have not an access to the HISTORY resource. If it is unsoluble limitation we will need to use other method of data's requesting - get appropriate dates for all active records (there is about 4500 active listings for all classes) and then select records with using of this date. I think it will be some slower.

Could you please let me know should I implement this new method or we can have an access to HISTORY resource?

We have access to the next property classes. Please review these if my mapping to the property types is correct:

  1. Contains data for Business Opportunity searches. [BUSI] -> BusinessOpportunities

  2. Contains data for Income/Investment searches. [COMM] -> Commercial

  3. ResidentialProperty [FARM] -> Farm

  4. LotsAndLand [LAND] -> Land

  5. ResidentialProperty [MULT] -> MultiFamily

  6. ResidentialProperty [RESI] -> Residential.

Attached are RETS metadata and sample datesheets for all available types.

Thanks

Posted by Molchanov George(unfuddle username: george)

Battler45 commented 4 years ago

Ben,

Could you please give me some instructions for MLSRegions database's entry for this region (i.e. RegionName, CommonName, Abbreviation etc)?

Thanks

Posted by Molchanov George(unfuddle username: george)

Battler45 commented 4 years ago

Ben,

All additions are implemented. Updater is ready.

Thanks Posted by Molchanov George(unfuddle username: george)

Battler45 commented 4 years ago

Ben,

We also have not access to the agent and office phones. In data for listing we are getting agent's name and office's name but neither AgentId (as link to the AGENT resource) not phone. Office phone is missed both in listing's data and in available fields of OFFICE recourse.

Thanks Posted by Molchanov George(unfuddle username: george)

Battler45 commented 4 years ago

Ben,

Could you please give me some instructions for MLSRegions database's entry for this region (i.e. RegionName, CommonName, Abbreviation etc)?

Thanks

Posted by Molchanov George(unfuddle username: george)

Battler45 commented 4 years ago

George,

Here are my comments on COAR RESID data:

FeaturesBasement

FeaturesConstruction

FeaturesEnergy

FeaturesHOA

FeaturesInterior

FeaturesLot

FeaturesUtilities

Please try to apply these same ideas to other list types and let me know if you have any questions.

Thanks. Posted by Peskoe Ben(unfuddle username: bpeskoe)

Battler45 commented 4 years ago

George,

RE: #8

Yes, I believe ImportCommercialOperations is corect updater step -- list type 11 would be the correct ListType for this class.

Thanks. Posted by Peskoe Ben(unfuddle username: bpeskoe)

Battler45 commented 4 years ago

George,

I will check with our contact at COAR tomorrow (Monday) and will let you know if they will give us access to the History resource.

Thanks. Posted by Peskoe Ben(unfuddle username: bpeskoe)

Battler45 commented 4 years ago

Ben,

I noticed that ListType 11 has name "BusinessOpportunities" (BusOp) in code but appropriate step is named "ImportCommercialOperations". Is it correct type/step for COAR class 1 (1.Contains data for Business Opportunity searches. [BUSI])?

Thanks Posted by Molchanov George(unfuddle username: george)

Battler45 commented 4 years ago

Ben,

Below is the list of my questions regarding this new importer

  1. Should we use somehow field "CrossStreetAddress" (values are for example: White Buck, Combs Flat Road, CLA, hwy 26)?

  2. Listings of types Farm, Mult and Resi have not any date field which can be used as Listing Date (other types have EntryDate and ListingDate fields). Is it ok?

  3. I'm in doubts which field can be used for ListTypeDescrip. Most of classes contain field PropertySubtype1 but in some classes it looks like expansion of PropertyType field (for example for Lots and Land class PropertyType is "Land" and PropertySubtype1 is "Lots/Land to 1 acre" or "Commercial Land" or "Lots 1 acre or more") but for other types (like COMM) it just repeats value from PropertyType field ("Income/Investment")

  4. Should we use somehow field "Style" with possible values SW, NW, SE, NE, Other?

  5. Many fields have possible value "See Remarks" (FeaturesConstruction, FeaturesUtilities:Water etc). Should we include or exclude this value?

(to be continued...)

Thanks Posted by Molchanov George(unfuddle username: george)

Battler45 commented 4 years ago

Ben,

Below is list of fields which I'm using for features:

  1. FeaturesCommunity

    • RETS field: LANDCOMM/MULTCOMM/RESICOMM. Header: Community Features.

  2. FeaturesConstruction

    • RETS field: BUSICONS/COMMCONS/FARMCONS/MULTCONS/RESICONS. Header: Construction Type.

  3. FeaturesEnergy

    • RETS field: COMMHTCO/FARMHTCO/MULTHTCO/RESIHTCO. Header: Heat / Cool.

  4. FeaturesExterior

    • RETS field: FARMEXTE/MULTEXTE/RESIEXTE. Header: Exterior Features.

  5. FeaturesFoundation

    • RETS field: BUSIFOUN/COMMFOUN/FARMFOUN/MULTFOUN/RESIFOUN. Header: Foundation.

  6. FeaturesInterior

    • RETS field: FARMINTE/MULTINTE. Header: Interior Features.
    • RETS field: FARMFIRE/MULTFIRE/RESIFIRE. Header: Fireplace(s).
    • RETS field: COMMFLOR/FARMFLOR/MULTFLOR/RESIFLOR. Header: Floors.

  7. FeaturesGarage

    • RETS field: FARMGARA/RESIGARA. Header: Garage. Also NumParkingSpaces can be filled from own field COMMNOPS (for COMM class) or being based on Garage value.

  8. FeaturesHOA

    • RETS field: LANDHOA/RESIHOA. If its value is "yes" then FeaturesHoa can be filled from RETS field LANDHOAD/RESIHOAD with header HOA Amount. Question: for RESI class we also have access to the RETS field HOA Per [RESIPER]. It is free text field with some kind of period description (values from sample listings: "month", "year", "yearly", "Month for Road Maintainance"). Do we need to use this field?

  9. FeaturesLot

    • RETS field: FARMTOPO. Header: Topography.

  10. FeaturesLotAccess

    • RETS field: LANDROAD. Header: Road.

  11. FeaturesRoof

    • RETS field: COMMROOF/FARMROOF/MULTROOF/RESIROOF. Header: Roof

  12. FeaturesUtilities

    • RETS field: BUSIEXIS/COMMEXIS/FARMEXIS/LANDEXIS/MULTEXIS/RESIEXIS. Header: Water.
    • RETS field: BUSISEWR/COMMSEWR/LANDSEWR/MULTSEWR/RESISEWR. Header: Sewer.

For Rooms field we can use RETS field FARMROOM/RESIROOM (only FARM and RESI classes) which contains data as plain list of available rooms ("Living Room,Kitchen,Utility,Dining Area", "Living Room,Kitchen,Utility"). Do we need to transform this somehow?

Thanks Posted by Molchanov George(unfuddle username: george)