jeffersonlab / bam Goto Github PK

Some Group Leaders think in terms of regions, not beam destinations. We might be able to help provide a mapping between the two.

Currently BAM uses oability group. A dedicated bam-admin group is requested.

It would be optimal if permissions can be stored/updated separately for each machine. When changes are made users must carefully study the new permissions to see what has changed and some users are only interested in a particular machine, which may not have been updated at all. Initially the beam authorization app was designed for just the CEBAF machine, but over the years we've bolted on LERF and UTIF as well. We may want to separate credited controls and beam destinations as well.

This would save Operations from having to manually copy this information into another tool (MaxJuice).

At the time when the Director saves an authorization a check could be run to see if any credited controls will expire during the authorized period. If so the Director should be warned / or perhaps not allowed to save.

On the flip side of this we could warn workgroup leaders who update a credited control to expire before the director's authorization, if one exists.

If Credited Control Participation changes perhaps the application needs to take action such as (1) downgrade director's authorization? (2) Email responsible groups?

The expiration date should be hidden/cleared when a Credited Control is manually downgraded as it is not useful anymore once already Not Ready / Expired. See screenshot:

Also, the automatic permission revoked doesn't appear to add an entry to the permission history. Prob nice if it did.

It would be helpful to include the director's notes field in the email to ops generated when the director changes authorization.

We need to document how users (operators in particular) are expected to use this application.

For example: perhaps add a Key/Legend that defines what "Provisional" means or add a FAQ, or a manual.