Manage users ability to view and work with Acquisitions records based on assigned "Acquisition Unit(s)"

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)

Priority

Fix versions

Development Team

Thunderjet

Assignee

Solution Architect

Parent Field Value

None

Parent Status

None

relates to

Checklist

hide

TestRail: Results

Activity

Show:

Michael ArthurMay 30, 2019 at 4:00 PM

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.

Ann-Marie BreauxMay 30, 2019 at 3:32 PM
Edited

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.

Michael ArthurMay 30, 2019 at 3:17 PM

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.

Ann-Marie BreauxMay 29, 2019 at 5:41 AM

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.

Marie WidigsonMay 28, 2019 at 1:25 PM

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

Done

Details

Reporter

PO Rank

96.4

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.

Analysis Estimate

Medium < 5 days

Front End Estimate

XL < 15 days

Back End Estimate

XL < 15 days

Rank: FLO (MVP Sum 2020)

R4

Rank: 5Colleges (ERM Jun 2020)

R1

Rank: 5Colleges (Full Jul 2021)

R1

Rank: Cornell (Full Sum 2021)

R5

Rank: Chalmers (Impl Aut 2019)

R1

Rank: GBV (MVP Sum 2020)

R1

Rank: TAMU (MVP Jan 2021)

R1

Rank: Chicago (MVP Sum 2020)

R4

Rank: U of AL (MVP Oct 2020)

R1

Rank: Lehigh (MVP Summer 2020)

R4

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created May 15, 2019 at 7:48 PM
Updated July 8, 2021 at 4:45 PM
Resolved September 23, 2019 at 8:46 PM
TestRail: Cases
TestRail: Runs