imported_from

[joshreisner]

context: the Meeting Guide app imports from a variety of AA website sources, and some of these sources are importing data from each other. there is no automated mechanism for Meeting Guide to use to distinguish which is the originating "canonical" source of the meeting data

real example: Quebec Région 89 would like to import data from 87, 88, and 90, yet only be the source to Meeting Guide for Region 89. the other regions are currently connected.

fake example: Area.org imports some of its meetings from District.org. Area was connected Meeting Guide first and so all of District's meetings in Meeting Guide are attributed to Area. Now District joins, and wishes these meetings to be imported from Area instead. Perhaps Area does not refresh its listings in a timely manner. Perhaps District wishes to be the point of contact in the app for these meetings.

solution: add imported_from key to JSON feed, which contains the domain of the data source of the imported meeting. in the example above, meetings that originated on Région 89's website would not have an imported_from, while regions that were imported would have, for example, "imported_from": "www.aa87.org"

problem: what if the originating feed is not on a unique domain, eg sheets.code4recovery.org or cloudfront.net? options:

• meeting guide importer doesn't care, and just uses the existence of imported_from to de-preference the meeting data
• include the whole data source URL eg https://sheets.code4recovery.org/storage/9d87LSfs88d27LHhmhsl.json which is unique (this might expose a secret depending on the outcome of TSML: Deprecate Feed Security)

problem: what if some meetings at an address are imported and some are not? since Meeting Guide uses addresses for registration, this could be unclear which entity to prefer