Design Definition

- POPS must be made to be a compliant AMIE site.

  A full-fledged AMIE implementation is being put in place.

- POPS must be able to originate all Project and co-PI Account creates for all
  board types, for all request types (New, Renewal, Externsion, etc.)

  The POPS/AMIE implementatation is being written such that at the click of
  a button in POPS Admin, the notify_project creates for proposals, and all
  corresponding co-PI notify_account_creates can be generated (and sent to the
  TGCDB via AMIE, as usual).  This can be done either for a single proposal
  (most relevant to DACs, extensions, supplements, etc.) or for a whole meeting
  (most relevant to xRAC meetings).

- There should be an interface to "bless" and send, singly, or by meeting, any
  awarded proposals.

  The POPS Admin interface will provide a means to generate these AMIE packets.
  This option will only be available for awarded proposals, and will be
  available from within the Award/Reject Admin tool (probably).

  It will be expected that all vetting of the relevant proposals will have been 
  completed (including data correction, reassignment to different boards,
  proposal number correction, etc.) prior to generating the packets.  Also,
  the PI and co-PIs of the proposals must have been reconciled against the POPS
  person database prior to generating the packets - failure to do so will cause
  and error.

- The POPS login, as a means of authenticating to POPS, should be removed.

- POPS must support TGUP Login-based authentication (already in place).

  See Objective 1.2_1 for a dewscription of the integration of POPS and the
  TGUP.

- A web-based "person reconciliation" app must be provided for Allocations
  Admins to reconcile new POPS persons against the POPS person database.

  This app is nearly complete.  It assumes one or more sources of un-reconciled
  person information, and a target to which to reconcile.

  This app is written as a core implementation independent engine, and it is
  assumed that different implementations will be implemented for different
  purposes (e.g., POPS person reconciliation, unvetted TGUP login/person
  reconciliation, etc.).