CRUD for Teams and addition of teams assignment to objects in various FOLIO apps (UXPROD-1147)

[UXPROD-1687] Manage users ability to view and work with Acquisitions records based on assigned "Acquisition Unit(s)" Created: 15/May/19  Updated: 08/Jul/21  Resolved: 23/Sep/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q3 2019
Parent: CRUD for Teams and addition of teams assignment to objects in various FOLIO apps

Type: New Feature Priority: P3
Reporter: Dennis Bridges Assignee: Dennis Bridges
Resolution: Done Votes: 0
Labels: acquisitions, cap-mvp, finances, invoices, orders, organizations
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks UIOR-317 Create Acq Unit filter for Orders Closed
Cloners
is cloned by UXPROD-2055 Ability to use Acquisition units with... Closed
Defines
defines UXPROD-1147 CRUD for Teams and addition of teams ... In Progress
Relates
relates to MODINVOICE-70 Restrict updates of invoice, invoiceL... Closed
relates to MODINVOICE-72 Restrict search/view of invoice, invo... Closed
relates to MODINVOICE-89 Disallow "deleted" acq units from bei... Closed
relates to MODORDERS-251 Restrict creation of PO, POL, Piece r... Closed
relates to MODORDERS-254 Restrict updates of PO, POL, Piece re... Closed
relates to MODORDERS-255 Restrict deletion of PO, POL, Piece r... Closed
relates to MODORDERS-256 Restrict search/view of PO, POL, Piec... Closed
relates to MODORDERS-294 Disallow "isDeleted" acq units to be ... Closed
relates to UIAC-4 Change acquisition unit(s) assignment... Closed
relates to UINV-23 Ability to assign acquisition unit(s)... Closed
relates to UIOR-300 Ability to assign acquisition unit(s)... Closed
relates to MODINVOICE-58 Add "acquisitionsUnit" field to vouch... Closed
relates to MODINVOICE-69 Restrict creation of invoice, invoice... Closed
relates to MODINVOICE-71 Restrict deletion of invoice, invoice... Closed
relates to MODINVOSTO-27 Create view joining invoice and acqui... Closed
relates to MODINVOSTO-28 Create view joining invoiceLine and i... Closed
relates to MODINVOSTO-30 Create view joining voucher and acqui... Closed
relates to MODINVOSTO-31 Create view joining voucherLine and v... Closed
relates to MODORDSTOR-81 Remove purchase-order.owner / purchas... Closed
relates to MODORDSTOR-94 Add acquisitions-unit-assignments.rec... Closed
relates to MODORDSTOR-95 Add acquisitions-unit-assignments.rec... Closed
relates to MODORDSTOR-96 Add acquisitions-unit-assignments.rec... Closed
relates to UXPROD-979 Ability to create Teams (acquisitions... Closed
Epic Link: CRUD for Teams and addition of teams assignment to objects in various FOLIO apps
Analysis Estimate: Medium < 5 days
Front End Estimate: XL < 15 days
Back End Estimate: XL < 15 days
Estimation Notes and Assumptions: Will need to updated estimates once a clearer approach is defined for implementation. Will this be limited to Create? When will permissions need to be enforced.
Development Team: Thunderjet
PO Rank: 96.4
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R5
Rank: Duke (Full Sum 2021): R5
Rank: 5Colleges (Full Jul 2021): R1
Rank: 5Colleges (ERM Jun 2020): R1
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R1
Rank: Lehigh (MVP Summer 2020): R4
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

Purpose: Use teams as a way of managing work with related records within a given tenant.

Acceptance criteria:
Governs ability to work with Orders
Governs ability to work with Invoices
Governs ability to work with Funds
Governs ability to work with Organization split (May need multiple teams)



 Comments   
Comment by Marie Widigson [ 28/May/19 ]

Hi Dennis Bridges Not exactly sure how this is intended to work. Please get back to us if you have any questions. In fact, I believe that Ann-Marie Breaux understands our needs for "teams" maybe even better than we do .

Comment by Ann-Marie Breaux (Inactive) [ 29/May/19 ]

Marie Widigson Dennis Bridges Key thing for Chalmers will be able to separate out the work for Main, Architecture and Math acquisitions units. It will only relate to orders, since they're not using funds or invoices in FOLIO.

Comment by Michael Arthur [ 30/May/19 ]

we discussed this recently in the Acq small group. I am still not clear on the purpose of assigned teams vs. just giving users permission to various functions. Often times the permissions given to individuals goes across teams that are designed to address functionality. So, there may be some staff in cataloging that have acq permissions but they do not need what the acq team has.
I just need more info.

Comment by Ann-Marie Breaux (Inactive) [ 30/May/19 ]

Michael Arthur The biggest use for teams is when certain people need a subset of permissions within a standard permission - e.g. they can create orders, but only for Main, not for Law or Med or Campus B. They can spend funds, but only for Main, not for Law or Med or Campus B. If all of Alabama's acq staff can create orders and spend money for all locations, then you may not need teams.

Comment by Michael Arthur [ 30/May/19 ]

thank you for the clear explanation. This seems doable for us with some planning. I don't think we would need teams as a go live.

We may need to talk this through a little at the f2f in June. You are correct that current permissions within acquisitions are not impacted by branch libraries because all acquisitions/fund management functions are managed within this department. However, there are levels of permission with acquisitions. Acquisitions/serials managers and I can approve invoices, and allocate and transfer funds while other staff can only create orders, receive and generate an invoice. Would this distinction be made by individual permissions to by having two teams?

Also, right now our Health Sciences Library on campus does use Voyager for cataloging. However, they do not use it for acquisitions/fund management. I am not sure how they will be handled in FOLIO but it appears that we would simply not give them any permissions.

Also, right now in Voyager we are not able to give users the ability to see the Materials Ledger (state money) without also giving them view access to the Gift and Endowment Ledger. Since we have to be guarded about the G&E ledger we are not able to give liaisons access to the Materials Ledger. I am hopeful that in FOLIO we can give view only access at the ledger level so that this is no longer a problem.

Generated at Fri Feb 09 00:17:38 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.