Inventory (UXPROD-785)

[UXPROD-1371] Inventory Permissions (Basic CRUD) Created: 28/Nov/18  Updated: 16/Sep/20  Resolved: 05/Dec/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q4 2019
Parent: Inventory

Type: New Feature Priority: P3
Reporter: Charlotte Whitt Assignee: Charlotte Whitt
Resolution: Done Votes: 0
Labels: cap-mvp, po-mvp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
is cloned by UXPROD-2166 Inventory Permissions. View Instance ... Closed
Defines
is defined by UIIN-739 Permissions. Rename Inventory: <tempo... Closed
is defined by UIIN-401 Permissions - Inventory. View instanc... Closed
is defined by UIIN-698 Permissions - Inventory. Instance vie... Closed
is defined by UIIN-699 Permissions - Inventory. Holdings vie... Closed
is defined by UIIN-700 Permissions - Inventory. Item View, c... Closed
is defined by UIIN-701 Permissions - Inventory. Instance vie... Closed
is defined by UIIN-702 Permissions - Inventory. Holdings vie... Closed
is defined by UIIN-703 Permissions - Inventory. Item view, c... Closed
is defined by UIIN-707 Permissions - Inventory. Holdings delete Closed
is defined by UIIN-708 Permissions - Inventory. Item delete Closed
is defined by UIIN-709 Permissions - Inventory. Mark item as... Closed
is defined by UIIN-801 Create permission for view all Invent... Closed
is defined by UIIN-805 Inventory permissions. Rename existin... Closed
Relates
relates to UIIN-103 Create logical permissions for the In... Closed
relates to CHAL-124 Unable to assign granular Inventory p... Closed
Epic Link: Inventory
Analysis Estimate: Small < 3 days
Analysis Estimator: Charlotte Whitt
Front End Estimate: Medium < 5 days
Front End Estimator: Niels Erik Nielsen
Front-End Confidence factor: Medium
Development Team: Vega
PO Rank: 160
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R1
Rank: hbz (TBD): R1
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: Leipzig (Full TBD): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

Purpose: To get the basic Inventory permission functioning in FOLIO which would provide access to e,g, CRUD functionality, Mark for deletion, Settings app for Inventory etc.

Usecase: Cataloger managers/Library administrators want to be able to give some staff limited access to view Inventory records without creating or editing them.

The focus of this feature is to implement basic CRUD based permissions for Inventory:

C: Can view and create (and duplicate) records in Inventory (instance/holdings/item), but will not include the ability to edit, or delete.
R: Can view records in Inventory (instance/holdings/item), but will not include the ability to create (duplicate), edit, or delete.
U: Can view, create (duplicate), and edit records in Inventory (instance/holdings/item), but will not include the ability to delete
D: Can view, create (duplicate), edit and delete records in Inventory.

The permissions needs to be flexible enough to module for catalogers, and circulation, student-worker, and technical services staff.

Documentation:

Permissions needed for circulation staff:
Circulation or public services staff have many use cases for editing holdings and items. For example, staff often have a source bib record for, say, a type of equipment, and then they manage the equipment underneath the record without having to get tech services involved. They may edit holdings, add/withdraw items, and other features. Some public services staff also have stacks management responsibilities, esp. the case for special collections libraries. How are these permissions sets being conceived / defined?

These comments re. permissions needed for circulation staff originate from:
Gap Analysis 2019 Missing Features - https://docs.google.com/spreadsheets/d/1b3VY1EUOAyoySuEaT0lJfKUBYLMUPZM6PDSBnGiMxYk/edit#gid=739330010

Original order # 176



 Comments   
Comment by Cate Boerema (Inactive) [ 18/Mar/19 ]

Per discussion today with Chalmers, additional inventory permissions will only be needed as a workaround if the Source Record Storage integration isn't working such that instances with associated MARC records are uneditable. So, if we have the following features, we won't need this one for Chalmers:

  • UXPROD-1577 Closed - Make Inventory Instance rely on SRS MARC Bib (Part 1 of Connecting SRS, Inventory, and MARCCat for Bibs/Instances)
  • UXPROD-1447 Closed - Block edit of Instance elements maintained in MARC Bib (part 2 of Connecting MARCcat, SRS, and Inventory for MARC Bibs)

FYI Charlotte Whitt, Ann-Marie Breaux and Theodor Tolstoy (One-Group.se)

Comment by Cate Boerema (Inactive) [ 24/Apr/19 ]

Hi Charlotte Whitt, this feature is marked analysis complete but the only story attached doesn't seem done. I am putting this back in Draft for now.

Comment by Cate Boerema (Inactive) [ 26/Jun/19 ]

Charlotte Whitt this feature is targeted for Q3. Can you get some stories in? Thanks!

Comment by Cate Boerema (Inactive) [ 28/Jun/19 ]

Charlotte Whitt, we should probably just rename this Inventory Permissions (Basic CRUD) since there will be technical blockers for anything beyond that at this point (namely Action based permissions UXPROD-1828 Closed )

Comment by Charlotte Whitt [ 28/Jun/19 ]

Okay Cate Boerema - I have updated the title of this feature.

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