We are happy to announce the release of Data Dictionary 2.0. With this release Trestle systems will be RESO 2.0 certified, which means that you will have a dramatic improvement in standardization coverage. Trestle offers a single schema, delivering consistency to our users across every MLS. As such, you will see as this change rolled out to all customers at the same time. There are a few new features that you can take advantage of with this update, but in general, your biggest concern should be making sure that your fully replicated datasets are up to date.

When: Monday, Sept 30th 6AM EST - 12PM EST

What to expect

• On Release, you will see the new enumeration values in the metadata.
• A data refresh will occur in reverse order, correcting newer records first.
• We will only touch ModificationTimestamp for On-Market Listings.
• All rows going forward include the new values.
• The entire dataset will be updated over the next two weeks.

Reference “What to Do” below for details.             

 

What to Do

Review Changes:

• If you consume these fields as is, you may not need to make a change.
• If you are using enumeration values in your code or have complex mapping, you will need to review.
• Most users do not search on these fields.

Be prepared to update a lot of rows:

• We expect over 200m row updates across all resources.
• Most of our users are conditioned to the fast pace of our updates and will have no issues consuming data at the rate that we provide it.
• If you need additional quota, please reach out or upgrade to our Premium Quotas for a permanent boost.
• We will only touch ModificationTimestamp for On-Market Listings.
• You should repull off market data in a few weeks. We will send a reminder when all accounts have been refreshed.

Metadata changes:

• Check for changes in namespace.
• Check for changes in your internal references (are you mapping an enum to another enum?).
• Consider moving to Lookup/Field resource.

Major Changes

Cotality’s CLIP is now available:

• CLIP (Cotality Integrated Property) is a Machine Learning driven record identifier based on Cotality assets. Use it to uniquely identify a property across vast datasets.
• Interested in additional datasets that you can use with CLIP? Ask us about our collection.

UPI is now available:

• UPI is a Universal Parcel Identifier for each listing based on the concatenation for other values. Lean more about UPI at

City / County lookups:

• Data type is being changed from a String to a Lookup
• You will see case changes but should not see any value changes at this time.
• You can find references to the available Lookup values in the lookup resource.
• Over time, we will continue to standardize these values.

CustomFields json blob:

• This field is being converted into a stringified JSON.
• If you rely on this field (the blob), please let us know as we are considering deprecation in favor of a more standard approach.

Data Type Changes:

• Some strings were made enumerations and vice versa.
• See our field change documentation.

New Field & Lookup Resources:

• You can use these resources for determining available lookup values.
• You can filter this for a specific MLS.

Metadata is much larger:

• RESO certification requires that Enumerated fields must have all values in the metadata.
• If large Metadata files are a concern, use the Lookup Resource.

New field type of Lookup:

• Fields like PostalCity, CountyOrParish will be exposed as a string, with a reference to the Lookup Resource.
• You can use the Lookup resource to find available values for Lookup fields and enumerations.

Massive enumeration value changes

• RESO 2.0 testing enforces parity between a payload and the enumeration/lookup.
• The most common fields:

1. ListAOR
2. ListAgentAOR
3. ListOfficeAOR
4. BuyerAgentAOR
5. BuyerOfficeAOR
6. BuyerFinancing
7. Possession
8. LeaseTerm
9. MediaType

• See our field change documentation.

Review Field & Lookup Change Document

https://docs.google.com/spreadsheets/d/1mJ6UoqHemXhSgCJqAQKQZSrbVtCT6nx2/edit?usp=sharing&ouid=102124821205257899726&rtpof=true&sd=true