Sympa Integration

[profmikegreene]

• [x] outline goals of the integration

  Add app

  1. Instructor clicks add app and selects Sympa in the app store
• App store content for Sympa includes prominent link to https://oit.duke.edu/help/articles/sympa-mailing-lists-approval-guidelines so that instructors don't have to agree with TOS each time they want to add Sympa
  2. Kits checks for a sympa list with the kit id and if exists, links to that, otherwise
  3. Sympa list created with the name of the kit and users added. The following form is presented:

Fieldname	Type	Immutable	Meta
Kits Display name	textbox	❌	display name shown to kit members on card
Who can view	radio button	❌	toggle between Just me, Instructors + Assistants Only, Everyone in kit

4. Sympa list membership synced near real time

Edit app

1. Instructor goes into kit edit mode and selects Sympa. The following form is presented:

Fieldname	Type	Immutable	Meta
Email address	text	✅	address of sympa list attached to this kit {{adhoc-dukecit@duke.edu }}
Manage Sympa list	href	✅	dynamic link to the sympa management for list attached to this kit {{https://lists.duke.edu/sympa/info/adhoc-dukecit}}
Kits Display name	textbox	❌	display name shown to kit members on card
Who can view	radio button	❌	toggle between Just me, Instructors + Assistants Only, Everyone in kit

2. Instructor makes edits and selects save
3. Kits applies changes and routes the instructor back to My Kits

Remove app

1. Instructor goes into kit edit mode
2. Instructor selects the option to remove Sympa
3. Kits removes all users in the kit from the Sympa list, Kits does not delete the list

• [x] map roles

Kits UI Display	Kits Role	Sympa Role
Instructor	Instructor	Owner
Assistant	Assistant	Editor
Student	Student	Subscriber
Visitor	Visitor	Subscriber

• [ ] explore API's ability to accomplish goals
• [ ] build a proof of concept

[ewendland23]

I just want to point out that a Sympa list can only have one owner. We set it to whomever requested the Sympa app.