...
In order to do something useful with enrollment flows, you have to click the box on "Enable Organization Attributes Via CO Enrollment Flow"; this would get clicked by the admin once per setup
- the early vision was that we would contact an LDAP or have a SAML assertion that would give us all the organizational info we would want. That didn't quite work out, so we need to accept attributes via an enrollment form.
- we need to have the documentation to be more accurate
- Hide "Enable LDAP Attribute Retrieval" and "Enable SAML Attribute Extraction" for now until we have a use case for their use. There is no code behind those items anyway. – See ticket CO-855
Calendaring
We don't know what the requirements or use cases are yet. CMP wants some "foodle" and some "event". LARPP wants to do mostly "foodle" - maybe this is just out of ignorance in terms of what is available?
Note that for bedework, the back end for consensus scheduling is done. UI is the next step, and there is a javascript implementation to start from.
Need to collect requirements, and need to figure out how to bring the bedework developer (Mike) on to a subcontract to get him involved.
Review myLIGO 3.0 Checklist
- Notifications via enrollment flows (requirements vs implementation)
- Concerned that we are not going to get 3.0 fully deployed before the end of the grant
- the list is still accurate for now; nothing to add