LHS membership list syncing

[Chris Mear]

Hi all,

As part of the LHS project, we will need to sync the LHS's membership system with the list of members in OCO.

I have started a wiki page here:

https://github.com/oneclickorgs/one-click-orgs/wiki/LHS-Membership-Integration

with some initial thoughts and ideas. Please feel free to edit that page, or just post your thoughts here on the list.

Thanks,
Chris

[Martin Dittus]

I'd like to check out existing protocols before we start building our own. I lack the background though, so let me know what's worth checking out. E.g. how about FOAF?

m.

> --
> You received this message because you are subscribed to the Google Groups "One Click Orgs / Devspace" group.
> To post to this group, send email to oneclickor...@googlegroups.com.
> To unsubscribe from this group, send email to oneclickorgs-dev...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/oneclickorgs-devspace?hl=en.
>

[Chris Mear]

On 20 Oct 2011, at 21:19, Martin Dittus wrote:

> I'd like to check out existing protocols before we start building our own. I lack the background though, so let me know what's worth checking out. E.g. how about FOAF?

I think there's two aspects to this:

1. We need a data format for the information about a person (email, name, what else?).

E.g. vCard is a standard format for contacts, but is that over-the-top if we're just exchanging email and name? What about JSON with id/first_name/last_name/email?

2. Where and how do we do reconciliation of changes to the member list (additions, deletions, change of email/name)?

For instance, the LHS app could be responsible for sending the data when a change is made to the member list. Then you need a protocol that can express the idea of additions/deletions/edits. (CardDAV?)

Or, we exchange a full list of members (which makes the data format simple), and the OCO end is responsible for reconciling both additions/deletions and edits to an existing member (for which we'd need a unique ID for each member, given that they might change their email address).

Chris

[Martin Dittus]

We just discussed it with Jonty in person.

OAuth is very likely to be involved.

There are a few corner cases (e.g. notifying members who never signed in to OCO) where there's no clear technical solution and we may have to improvise.

Jonty also suggested it's time to bring a few people together and discuss the current state of things before we start building lots of stuff.

m.