We built Financial Approval version 1.0 through Spring 2013. I completed it with help from Fruition, worked out bugs, and finally put it in test in summer 2013. Shortly after, it was demo-ed with focus groups, and various people pointed out oversights and flaws.
In late August 2013, we completed a spec for version 2.0. Backeberg is converting the paper-based specs to a technical spec for Fruition to work on.
Data needed to make decisions
We need a data mapping such that we can readily determine appropriate approvers for each active Organization at Yale. Organizations have six-digit codes, a name, as well as:
- Operations Manager (sometimes)
- Lead Admin (almost always)
- BOLT Team Member (even more often)
- BOLT Team Leader (always)
History
On Financial Approval version 1.0, we needed to reorganize our data loaders, and we added data dips that get us Operations Manager (where avaiable) and Lead Admin data for the Organizations. This works great and is well tested since Spring 2013
New feed
We need a new data feed for BOLT Team Member. Met with Nancy Scanlon and Igor B. in early Sept. Confirmed that this data only lives in the data warehouse. I need a feed on "yugl organization dm cur v" and the fields inside there are:
- CD six-digit ORG number
- Senior Director (bolt member)
New feed requirement
R1026 is the number in HPQC.
Request for access to Hyperion / Brio / DWH
Backeberg confirmed we can leverage the existing level of access already used for pulling similar information from DWH. However, a problem is that Senior Director is represented as a Real Name, and there are no other identifying characteristics for that user. This is a problem because Real Name is terribly ambiguous in most cases, and especially at Yale with a user table with 200k members. Need to bug Nancy Scanlon or somebody at DBAs to discern about how we possibly handle revising the DWH to have a UPI for the Senior Director in the DWH pull.