MyLIGO3 JIRA

  • Enrollments
    • Org Identities will be pooled, so enrollments must match to existing or pooled identities (CO-654)
    • LSC
      • During an enrollment flow and later as a detail about the COPerson record, need to be able to specify whether an actor is an administrative assistant (or undergraduate, or faculty, or staff) or not, which could be done via affiliation extended type (CO-526)
        • Initial use case could be satisfied with use of employeeType in LDAP provisioning
      • Collect country in a more reasonable/standardized way (CO-536)
      • Add postalAddress support to LDAP provisioner (CO-909)
      • Notification on petition status change, including minimally a link to the petition (and possibly customized text CO-784) (CO-659)
      • Need for COU admins to only be able to see petitions in that COU (CO-834)
      • Optional: fix up some data fields: address (CO-529) and phone (CO-678)
    • Virgo
    • LIGO Lab
      • Some subtleties around enrollment process that need to be discussed with Stuart and Melody
      • After approval, enrollee receives notification that they can login and update their attributes (eg: add middle name)
      • Use group (provisioned to Grouper) to track people who are also LSC members (or maybe use select extended attribute (CO-836))
    • "Transfer" Enrollments (This may really be a 3.1 requirement)
      • May not actually be a transfer so much as an expiration and an enrollment
      • See also enrollment flow matching enhancements (CO-298, CO-310)
  • COU Admins by default see their own COU's population (CO-567) but can't edit other COU's data (CO-505)
  • FTE as extended attributes
    • Right now registry supports this with extended attributes, but if we want sophisticated validation of the three values perhaps this would be better with a plugin and have the plugin use its own data model rather than extended attributes. If they are extended attributes then they will show up in COPersonRole record and will bypass the validation.
  • Council Delegates as a COmanage plugin (LIGO work)
  • Kerberos password management plugin (LIGO work)
  • Figure out expirations and grace periods (CO-56) (optional)
  • Multiple email identifier management (eg: alternate addresses for mailing list postings)
    • Self service via existing Registry interface, using extended types for email addresses (CO-370) (or maybe just add a predefined email address of type 'Alternate')
      • Current thinking is to add a predefined email address of type 'Alternate'
    • Provision alternate email address(es) from Registry into mailAlternateAddress and mailForwardingAddress -- may need to support qmail schema or equivalent (CO-835)
  • Author name self service updates (Depends on CO-333)
    • Via a plugin that looks simpler and forces format of A.B.C Last, Jr (LIGO work) and records to type=author
  • "I am also a member of another Gravitational Wave Experiment"
    • Boolean extended attribute type? (CO-576) Select extended attribute type? (CO-836)
  • Reporting of various types (CO-77, related tickets, etc) (compare to existing MyLIGO 2.x functionality around census and demographics)
    • Need a census report that shows active COPerson per COU and CO in some type of table format (CO-338)
    • Need a demographics report that shows a summary of the demographics information, including per-CO (CO-313)
  • Roster (Directory 0.2)
  • Percent FTE Plugin (LIGO work)
  • NSF Demographics Plugin (LIGO work)
    • No enable demographics tracking on a per-COU basis rather than the default per-CO basis
    • Depends on CO-917
  • LIGO IdMS?
    • Optional: CO Person without Org Identity (CO-870)
      • No, the IdMS will maintain an Org Identity record reflective of the email address used for self service reset of the LIGO password credential
  • No labels