Analytics: Add Purchase Request Requester user information at the time of request
The Purchase Request Subject Area Purchase Request Requester user information is updated every day by ETL to the current user information.
In many cases, this is useful. But it is not useful for reporting when it is important to know the information of a user at the time of an action.
As one example: We would like to report on the number of patrons submitting purchase requests by user group such as undergrads vs postgrads vs staff. If a patron submits a purchase request as an undergrad and then becomes a postgraduate, the outcome of current analytics is that all their purchase requests are reported as submitted by a postgraduate. This is completely incorrect and cannot be reported upon.
As another example, we have Statistical Categories for School and Faculty. If a student is associated with one School by a course they are enrolled in for one semester and then is associated with another in the next semester, all purchase requests update to the latest information and the data is again useless.
It is proposed that Analytics cover this scenario by adding fields for user information at the time of action of submitting a purchase request.
This is the same concept as in the Fulfillment area to record user information at the time of loan.
In order to avoid disruption, the request is specifically to add fields, not replace them.
Note: This submission covers all relevant fields in the Purchase Request Requester dimension table, not just user group.
Stacey van Groll
shared this idea
-
Davin Pate
commented
Added this to the Use Cases submitted to Ex Libris regarding Rialto