COmanage Developers List

[Scott Koranda <>]

Hi,

On a future dev call I would like to go over these and
translate them from "LIGO speak" to COmanage vocabulary and
see how many we need to capture as new requests/enhancements.

Thanks,

Scott

> 1 myLIGO 
>    * new requests
>       * Develop a way for PI's to declare proposed future FTE per MOU
>         Attachment. We talked to Phil and he suggested that a new table 
> should
>         be created in my.ligo with editable entries during the MOU review
>         period and frozen when the MOU is PI-ready.
>       * 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 betetr
>         track student activity in the collaboration.
>    * old requested enhancements
>       * High priority:
>          * FTE, status info available for LSC members' request in
>            roster.ligo.org. (Does this request comply with privacy laws?)
>          * Expiration dates for membership
>          * Create a new category for short-term undergraduate students.
>            (Compliance with Bylaws)
>          * Make sure that Virgo is listed correctly (not a federation). Also
>            for LCGT
>          * Inclusion of an index in group roster queries (numerical count 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?
>          * On-demand generation of eligible authors for the PIs and proxies 
> of
>            LSC groups. Membership history of each group.
>          * [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.
>       * Medium priority
>          * Ability to assign proxies of council members for votes.
>          * 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.
>          * [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.
>            Allow the PI to have an option for adding other emails being 
> copied
>            in all emails to PIs.
>          * [This must also have already been implemented] Ability to
>            add/remove LSC groups by spokesperson or designate, including
>            automatic notification to group PIs.
>       * 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.