Users App
(UXPROD-784)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Users App |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Khalilah Gambrell | Assignee: | patty.wanninger |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | round_iv, usermanagement | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Users App | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimate: | Large < 10 days | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimator: | Khalilah Gambrell | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimate: | XL < 15 days | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimator: | Khalilah Gambrell | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Estimation Notes and Assumptions: | Backend Estimate includes Adding fields to the UI and Import. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Spitfire | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PO Rank: | 90 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PO Ranking Note: | This ranking is way higher than the organizational ranking because there isn't a good understanding of what functionality it would add. But with a few fields, custom fields, tags and this stat code, I think there would be a good package of functionality in Prod v. 1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R5 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
As of 12/9/2018, Inventory App is currently implementing Affiliation Group/Statistical Codes support. Users App has similar needs and may want to implement this feature in the same manner as Inventory given Custom Fields is not currently in development. |
| Comments |
| Comment by Khalilah Gambrell [ 09/Dec/18 ] |
|
Tania Fersenheim - maybe something to bring up to the UM SIG to see if they are okay with leveraging the work done by Inventory. |
| Comment by Erin Nettifee [ 06/Aug/19 ] |
|
So there will be two types of affiliation things people might want to have. One is department - Biology, Facilities, East Research Support, etc. For large institutions, this can be over a thousand entries. Then there is a more granular concept that Duke, at least, calls "Patron Type." So a patron group list might be short, and the type provides more granularity that is really helpful. Example 1: Type allows for granular understanding of visitors, helpful for fines, high touch situations, and relationships outside of a consortial setup.
Example 2: "Faculty" is a big umbrella - and type can help us distinguish a temporary person versus a tenured former department chair.
Can provide more examples if needed. |
| Comment by Khalilah Gambrell [ 23/Sep/19 ] |
|
Per 9/23 meeting - UM SIG has stated that this feature is of lower priority. Many of UM SIG's requirements can be handled with
|
| Comment by Holly Mistlebauer [ 17/Jun/20 ] |
|
Cornell comment from Round IV Outliers spreadsheet: This outlier is a showstopper for Cornell |
| Comment by Sharon Beltaine [ 20/Aug/20 ] |
|
Cornell
|
| Comment by Sharon Beltaine [ 01/Sep/20 ] |
|
Cornell: The patron data fields need to be able to be loaded through the Patron Feed |
| Comment by Sharon Beltaine [ 02/Sep/20 ] |
|
Cornell: a small group evaluated the options for Cornell with regard to Patron Codes. It appears that the combination of the Department field and Custom fields will provide the solution that Cornell needs. Testing of custom fields and reporting from them can begin with GoldenRod. Testing of Department fields and reporting from them can begin with Honeysuckle. The Cornell Patron Feed will be modified to accommodate the Patron Code reporting needs identified in
Pending testing, it appears that Cornell does not need to implement Statistical Codes in the Users application. |
| Comment by Erin Nettifee [ 02/Sep/20 ] |
|
Thanks for the update Sharon Beltaine - for what it's worth, that's the approach Duke has been planning on for our go-live for Users in 2022. |
| Comment by Sharon Beltaine [ 02/Sep/20 ] |
|
Good to know, Erin Nettifee - Thanks! |
| Comment by patty.wanninger [ 17/Sep/20 ] |
|
We are not pursuing this solution at this time. User Management added some fields to the User record and will use custom fields for statistics. |