Ask Your Question

Is there a way to download ALL

asked 2016-11-16 12:48:02 -0600

I'm just starting converting from the prior RETS/Innovia to the new Paragon system. I have an xls with a data map. I'd like to do something like a SELECT * to select all fields and field values, so I can see what I have to work with now (I will be inserting into our local db).

Is there a way to download ALL columns for Residential in my list of towns? And I'd like field/column names (either Standard or System is fine)

something like $search = $rets->SearchQuery("Property","RE_1","(City=Conway),(ListingStatus=1,3)", array( "Limit" => "2000", "Select" => "", "RestrictedIndicator" => "*", "StandardNames" => 1 ) );

Can do?

edit retag flag offensive close merge delete

5 Answers

Sort by ยป oldest newest most voted

answered 2016-11-16 13:25:24 -0600

You can set your Select = "*" or not pass it at all.

You probably also want to set StandardNames=0 and set Format=COMPACT or COMPACT-DECODED to get more data fields. Paragon RETS Standard names are pretty limited at the moment.

edit flag offensive delete link more


Paragon's list of Standard Names are worse than limited. They are the antithesis of the RETS/ mission: "publish data portability...and obtain maximum efficiencies" manifestly by implementing good Standard Names that everybody can understand what data fields represent.

dcgllc gravatar imagedcgllc ( 2017-07-09 15:21:31 -0600 )edit

answered 2017-07-08 15:07:36 -0600

As a database person, I understand Paragon system field names because they are standard database names (char, int, etc). When you create a standard database setup that then has to be customized for hundreds of customers, all with their specific names for different things, it is almost the only way to do it.

That being said, I don't envy the providers that have to deal with the changes. I have spent enough time trying to explain some of the field names to our vendors (as an MLS Admin person) to understand the confusion. I can say Paragon is working on coming up with a better way but it takes time to get 400+ systems to try to converge with some standard names.

edit flag offensive delete link more

answered 2017-07-07 10:44:58 -0600

i also use neren and since they change mls providers every 2 years or so i am used to the change over blues.

i started before there was rets, and i have had my own field names since the days when nneren had its own database.

the way i have handled it is i have a conversion table to rename all the fields to my names and i use tables that are setup for efficiency when searching, and table for property details, and now a table with all the photo urls linked.

I like not having to store all the images on my server but as they do not provide HTTPS access i have not been able to secure my sites, and Google will be complaining about that in October.

my query is ( 'NEREN/search?SearchType=Property&Class=%s' '&QueryType=DMQL2&Format=COMPACT-DECODED&rets-version=rets/1.8')&Query=((L_Status=|1_0,3_1),(L_UpdateDate=%s%%2b)

i use python and the variables are stored in a include for the table i am looking for.

edit flag offensive delete link more

answered 2017-07-05 23:49:49 -0600

I really don't understand with today's web technologies why having cryptic names was still a choice. The RESO data dictionary is a good starting point, but even then, the fields don't even come close to matching what the data dictionary provides. Is there a way we could come together to contribute to be Reso data dictionary standards?

How did you guys go about mapping this?

I am using MongoDB and mongoose, made my schema from the metadata. I was using the longname and converting it to camelCase. Then had to go through and set the data types. Used alias to the actual system name to get my data to save, but I was unaware of the data dictionary so going to redo my schemas and try to map this out. Retsly has a data dictionary schema tool on github but I haven't got it work just yet.

edit flag offensive delete link more

answered 2016-11-17 11:45:34 -0600

Paragon uses cryptic arbitrary names to identify its fields and has made no reasonable effort to create a list of standard names which identify by English-like name what such fields represent. The goal of RETS was to simplify the process for small real estate firms by making a good faith effort to populate "Standard Names" with a wide array of generally used fields with more intuitive names. Instead, Paragon has required every customer to match Paragon's cryptic names to whatever their own "standard names". To fill this gap, my company needed to create its own a list of translations, in effect a new list of 250+ "Standard Names", to generate the typical detailed HTML pages that nearly every RE firm uses in this regard. This took my company in total about 40 hours work to prepare, test, file trouble tickets, etc. to resolve. Clearly, such circumstance was a colossal waste of time across the broad spectrum of Paragon customers - - in New England there were over 2,000 agents who had a robust list of "Standard Names" from its previous vendor to use and were left with the task of reinventing a list of "Standard Names" one-by-one to fill the void. What a total lack of commitment to customer service by Paragon!

edit flag offensive delete link more


^ same boat! I just spent 40+ hours recreating all or our scripts, and creating a custom data map... ugh. But, done!

DriveBrandStudio gravatar imageDriveBrandStudio ( 2016-11-29 11:22:24 -0600 )edit
Login/Signup to Answer

Question Tools

1 follower


Asked: 2016-11-16 12:48:02 -0600

Seen: 3,373 times

Last updated: Jul 08 '17