These items define the MLS data delivered in this version of the RESO Data Dictionary.
Added in Version
|The Data Dictionary version (i.e., 1.6, 1.7, 1.8) where the field or lookup was added.|
|Building Energy Data Exchange Specification (BEDES) is a dictionary sponsored by the U.S. Department of Energy to standardize information about high-performing / efficient homes. It is intended to be used in tools and activities that help stakeholders make energy investment decisions, track building performance and implement energy efficiency policies and programs. Also referred to as BEDES Mapping.|
|A Data Dictionary certificate can be awarded to applicants achieving predefined compliance levels. If a field/enumeration is part of the certification process, then the certification level for which that field applies is noted. As of Data Dictionary 1.7, the metallic levels – Bronze, Silver, Gold, Platinum – have been retired in favor of a newly established Core level.|
|A complex data type that references a collection or container of data items that have a shared relevance. Collections can be lists, sets, queues, dictionaries, etc. The common use in the RESO Data Dictionary is to show the relationship from a parent table (the location of the collection field) to a sub-table (child resource).|
Field Name (Standard Name)
|The only compliant name that represents the data point.|
|Field Definition||The written definition for the field. May contain special rules that must be observed.|
Used for both fields and lookup values (e.g., enumerations) that describe the state within the RESO Data Dictionary. The different values are listed directly below.
|A single designation identifying what category of fields to which the given field belongs. For example, "ListingKey Field" will have the value Property Resource, Listing Group.|
|The name of the collection of lookup values (enumerations) applied to the given field. An empty value implies no lookup items have been defined for this field.|
|Lookup Field (Enumeration) Identifier. An integer used as a unique identifier for a given set of lookup values.|
|Lookup Identifier. An integer used as a unique identifier for a lookup value in the RESO Data Dictionary.|
Pertains to a list of acceptable values (enumerations). Lookups (enumerations) may not exceed 128 characters in length.
|A single unique lookup item (value can be any alpha-numeric character set) within a set of lookup values within a lookup field.|
|Lookup Field or Values||A list of lookup values (also known as enumerated values) that apply to a given lookup field. For example, State is a lookup field that has lookup value entries for each state.|
|Original Entry Date||The date the field or lookup was added to the Data Dictionary (not yet implemented).|
|Modification Timestamp||The modification timestamp is displayed on the footer of each page with a field header of "Page Revision Date" and applies to any change to any column in the Data Dictionary. The change will receive a date/time entry representing when the change was made. This is not when the decision was made by the RESO Board of Directors or Data Dictionary Workgroup, but rather the action of applying that decision into the dictionary.|
|Any number of fields representing the payloads found in RESO transports. The listed payloads, if used, must be adhered to, but the list of payloads is extensible. When a payload is called by the client, the client may also select additional fields to be included.|
This field will only apply to items within the Property Resource. Possible values are listed below.
|Record Identifier. An integer used as a unique identifier for the fields in the RESO Data Dictionary.|
|A reference to another resource/field related to the current page where the field or lookup value is utilized.|
|A "Yes" value means the corresponding Field Name includes "[type]" indicating this may be repeated and will include a defining string that indicates the instance of the repeated element such that Room[type]Features becomes RoomKitchenFeatures and refers to the features of the kitchen.|
|The date a substantive change was made to the field or enumeration. This is the date the change was decided upon by the RESO Board of Directors or Data Dictionary Workgroup and not the modification timestamp representing when the change was applied to the dictionary.|
Simple Data Type
A particular kind of data item, as defined by the values it can take.
Spanish Lookup Fields and Values
|The Spanish equivalent of Lookup Field or Values. See above.|
Spanish (Standard Name)
|The Spanish equivalent to the column Field Name (Standard Name). See above.|
Sug. Max Length
|The suggested maximum length of a given field. Optional at this time but strongly recommended when a source MLS system is considering a metadata change. This field also determines integer from decimal. For example, "2" is an integer with a length of two places; 6.2 is a decimal with two places to the right of the decimal and 4 places to the left of the decimal. Integers are allowed one extra character to allow for a plus or minus "+/-" character.|
Status Change Date
|The date as dictated by the rules of the Element Status field (Field Status or Lookup Status). See those definitions for specific instruction on the population of this field. This is the date of the RESO Board of Directors or Data Dictionary Workgroup decision and not the modification timestamp in the dictionary. Also known as Element Status Change Date.|
|Another name for the given field having the same meaning. Synonyms are for reference only as an aid to data mapping and general understanding.|
Page Revision Date: November 19, 2020.