COmanage Developers List

[Benn Oshrin <>]

At the DC f2f, we reviewed various LIGO requirements that were presented 
to the dev list. Since not all of these requirements generated JIRA 
tickets, I'm posting my summary here so we can possibly find it again 
later if we need it. No follow up to this message is otherwise needed.

-Benn-

* For each graduate student entry in my.ligo, add a field where the PI
  can specify the student thesis title and possibly other information
  (estimated date for graduation). This also would require to add an
  editable table. The idea here is to help the folks of LAAC to better
  track student activity in the collaboration.

-> Add longer VARCHAR extended attribute
-> Configure "View CO Person" to show only configured attribute, 
probably on a per-affiliation type basis

* FTE, status info available for LSC members' request in
  roster.ligo.org. (Does this request comply with privacy laws?)

-> Reporting requirement on Person + FTE + Status (active, etc)

* Create a new category for short-term undergraduate students.
  (Compliance with Bylaws)

-> Figure out how to define / configure extended affiliation types
-> Enrollment flows should force default value for affiliation type

* Inclusion of an index in group roster queries (numerical count on
  the left)

-> Reporting requirement: have a row number on the left

* Creating a push-button information about the size of the LSC and
  Virgo (total number of people and total number of LIGO FTEs.) This
  seems to be done in https://my.ligo.org/census.php but not linked
  anywhere. Should be linked in the left menu of my.ligo.org where
  the demographics report is?

-> Reporting requirement: Scott TBD

* On-demand generation of eligible authors for the PIs and proxies of
  LSC groups. Membership history of each group.

-> Reporting: Complex reporting requirement to be further discussed
-> Be able to see CO/COU membership changes over time (eg: person X was 
added by person Y on date Z)

* [New item] A change in the database to comply with the new bylaws
  which now state that group PIs should not be automatically be
  granted authorship rights.  PIs with < 50% FTE should now file a
  one-time petition to become authors of LVC full-author appers.

-> More reporting

* Ability to assign proxies of council members for votes.

-> Delegation of an authorization

* Automated e-mails sent out 2-4 times a year requesting PIs to
  update their rosters with a report of roster, demographics, council
  members, and author list.

-> Reporting?

* [I guess this has been done] Notification to the LIGO Lab director
  and deputy directory when there is a pending administrative action
  for LIGO-CIT and cc'd on pending actions at LHO, LLO and MIT. This
  includes notification of excess/too few council delegates, etc.

-> Reporting (excess/too few)

  Allow the PI to have an option for adding other emails being copied
  in all emails to PIs.

-> Delegation for notification?... Scott TBD

* [This must also have already been implemented] Ability to
  add/remove LSC groups by spokesperson or designate, including
  automatic notification to group PIs.

-> CO Admin sets COU to Inactive, notification fires off to <someone 
within COU TBD>
-> Maybe make CO/COU admins see "expire or make inactive" whereas CMP 
admins also see "delete"

* Low priority
  * Google earth plot with coordinates for each institution (provided
    by them) and a .kml file that google earth uses to make plots with
    "pins" stuck in appropriately. Something similar to this:
    http://www.zeemaps.com/map?group=245330 Also, request a city and
    country from each group, and use it to count members per country in
    the census report.