Relational member data

[codygustafson]

I would like to start a conversation around the data dictionary Member information. In our database we store emails (as well as other information) as a "has many" relationship. I thought it would be good to start with one example, "emails" has the following fields.

• pkey
• member_key
• name
• type
• address
• is_primary
• is_display
• is_verified

Using the data dictionary, we can only export this as MemberEmail, which has mostly worked for exporting this data to third parties. But note that I can only export a single email's address, so some data is missing. The next problem comes up when we talk about writing data back into the MLS. We obviously cannot support writes using this field as an interface. We need either a complex type with all my fields or a separate entity type.

Should we be talking with data dictionary to make a new type or is there a way we can handle this within transport? I would like some discussion on how I can proceed with presenting all available information. This same problem exists for addresses, phone numbers, websites, and likely more.

[codygustafson]

See discussion https://github.com/RESOStandards/transport/discussions/53

[darnjo]

Closing for now. We can reopen depending on the outcome of the related discussion.