comanage-dev - [comanage-dev] items for dev call
Subject: COmanage Developers List
List archive
- From: Scott Koranda <>
- To: comanage-dev <>
- Subject: [comanage-dev] items for dev call
- Date: Fri, 10 Jul 2015 09:46:40 -0500
Hi,
I have 4 items for the dev call that came out of a "gap
analysis" meeting I had with Mike Manske and Warren Anderson
from LIGO.
The 4 items below are in my words and will probably be a bit
cryptic--I prefer to try and clarify on the call rather than
wordsmithing them now.
So here they are for the record...no need to really parse them
until the call:
- status of adding a second role to a CO Person record through
and enrollment, needs to be enrollment because addition of
that role usually means "joining" a COU and the admin for
that COU needs to approve, also maybe adding a role like
"student" or "staff"--any addition of extra "affiliation"
may need approval
- can an approver edit text of email to be sent if this is
done using an enrollment plugin? (#15 on Mike's page)
- in the new enrollments, how much control will there be to
present MOUs (COUs?) that a user may or may not join?
- better identity linking during anonymous enrollment because
about half of user support issues are duplicate
enrollments/registrations (people tend to register again
just because they have forgot a "password", or they just
change name and register again)
Thanks,
Scott
- [comanage-dev] items for dev call, Scott Koranda, 07/10/2015
- Re: [comanage-dev] items for dev call, Arlen Johnson, 07/10/2015
Archive powered by MHonArc 2.6.16.