LHS Membership Integration

Resources:

• LHS website source code

Changes to member state:

• A new member joins
• A member leaves by actively cancelling their membership
• A member leaves by letting their subscription lapse
• A member rejoins (after having previously left)
• A member changes their email address or other personal details (name)

Actions to be supported:

• A member logs in to OCO
• A member receives a notification email from OCO

Considerations:

• We may need to send a notification email (e.g. new proposal) to a recently-joined member before they have logged into OCO for the first time. So we have to sync the member lists automatically, without relying on them logging in to OCO.
• Membership should still be checked at point of login as well. For example, if we sync the member list each midnight, and a member leaves LHS during the day, they would still be able to log into OCO for the rest of that day -- unless we also checked their membership at the point of login.
• The canonical list of members should remain with the LHS app.

Implementation ideas:

• Automatic syncing
  • Does OCO request data from LHS, or does LHS send data to OCO?
  • Transfer the complete member list each time, or transmit changes only?
  • Is there a standard format for information about people we should use?
  • Is there a standard protocol for changes (as opposed to sending full list) we should use?
• Login checking
  • Members log in to OCO via OAuth provided by the LHS app?