Current and future versions of Data Dictionary in spreadsheet format have been added to the home page of the Data Dictionary Workgroup on RESO’s workgroup collaboration system, Confluence, and to RESO’s website. The versions include:
- Data Dictionary 1.7 Ratified Spreadsheet
- Data Dictionary 2.0 DRAFT Spreadsheet
- Data Dictionary 2.1 (formerly 1.9) In Process Spreadsheet
RESO Web API Transition Guide
We are excited to share an initial draft of Transitioning Your Customers to RESO Web API: A Guide For MLS Leaders. This guide will help you get started and see the transition through to completion.
This is just version 1.0. We welcome suggestions/edits from the community before we unveil a printed version 2.0 at the upcoming RESO 2023 Spring Conference in San Antonio, TX, April 18–20.
Feel free to contact us at firstname.lastname@example.org with any suggestions. This is a team effort, and we are grateful for your contributions.
A new resource and accompanying fields were approved for Data Dictionary 2.1.
Data Dictionary JSON Payloads (RCP-025 ) has been renamed RESO Common Format.
Transitioning Your Customers to RESO Web API, A Guide for MLS Leaders has been produced with feedback from dozens of member organizations.
MLSs, technology vendors and brokerage companies contributed their experiences in preparation, communications, scheduling and distribution for a successful transition from RETS to Web API.
Version 1.0 of this guide will be distributed in Q1 to all MLSs via email. RESO is seeking your feedback to continue improving the guide.
A final version will be printed and shared with attendees at RESO’s Spring Conference in San Antonio, TX April 17-20.
A field to contain a listing’s participant-provided contact phone or email called AttributionContact was voted into Data Dictionary 2.1.
A field called CompensationComments was voted into Data Dictionary 2.1.
A field called GrossLivingAreaAnsi was voted into Data Dictionary 2.1.
A lookup called Affiliate under the MemberType field was voted into Data Dictionary 2.1.
A lookup called Steel Frame under the ConstructionMaterials field was voted into Data Dictionary 2.1.
The Owner Will Carry lookup of the ListingTerms field’s definition was corrected to read, “The seller will carry the mortgage note.”
A new Resource called InternetTrackingSummary, as well as new fields and lookups, were voted into Data Dictionary 2.1.
The Lookup Resource additions to the Data Dictionary 1.7 specification were approved.
Changes were made to the proposal for Metadata Localization, and the group approved moving forward with producing a specification.
Two implementations of the Data Dictionary JSON Payloads (RCP-025) proposal have been identified. The group will review the specification and testing rules next.
The draft Add/Edit (RCP-010) proposal has been updated to reflect the changes from the original proposal. One implementation has been validated.
The v1.3.0 release for the Certification System contains the following features:
Performance Metrics Improvement – Estimated Seconds per 1,000 Records
Estimated Seconds per 1,000 Records as a large number metric, including industry averages.
Addition of Sort by Time in Endorsements List
Users can now sort by time in the endorsements list.
This will show each endorsement individually rather than grouped because they could have been tested/approved at different times.
Archive Reports Feature
Added the ability to archive reports for providers and admins.
Providers should archive their reports when they have results they no longer want or if they have a customer that they no longer are doing business with. We want them to manage their own customers.
The public feed will be updated automatically if a provider archives their reports, and their “pair” will not be counted as certified for an MLS with only one of the two required endorsements in cases where they only archive one endorsement (e.g. Data Dictionary) and not the other (e.g. Web API).
Notifications will not be sent to the recipient of the endorsement when an item is archived. Just to the provider.
RESO Admins can also archive reports, which is a softer option than Revoke. The provider will be notified if RESO archives an endorsement.
High-level statistics will be saved when reports are archived, as RESO will be offering Provider Metrics in the future, which will allow providers to see whether they’ve improved against their historical averages, including standardization and performance stats.
RESO Public Feeds
A new organization service is available for those wanting the authoritative source for Unique Organization Identifiers (UOIs). It matches the schema of the OUID Resource in the Data Dictionary.
The data reflects current Organization and Endorsements Feeds also used by Certification, and provides a formatted view of high-level statistics as well.
1. Organization Feed
The orgs service shows the data from the production UOI service in JSON format, matching the OUID Resource
2. Orgs Plus Endorsements Feed
Parameters may be passed to show the endorsements for each org as well.
3. Formatted Stats Feed
There is also a service that shows formatted metrics in JSON format.
The response looks like the following:
Each bucket we certify is represented, as well as an “All” category, showing everything.
For MLSs to be counted as “Certified Current,” they MUST have approved Data Dictionary and Web API Core Endorsements. As of this afternoon, there are 233 Certified Current MLSs and 184 Passed Current. We should perhaps reach out to the Certified Legacy and Uncertified.
This information will be the same that drives the map and the other lists on the public RESO site, and a working demo of that can be found here: https://resostg.wpengine.com/certification/
Coming in Certification v1.4.0
Provider and Market Alignment Tools, including comparisons against Industry Aggregates.
Those interested in beta testing this product should reach out to email@example.com.