Ordering functionality that FOLIO needs to stay competitive
(UXPROD-3440)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Ordering functionality that FOLIO needs to stay competitive |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Joseph Reimers | Assignee: | Dennis Bridges |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | IC_review, LC-priority2, loc, requires-discussion | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Release: | Not Scheduled | ||||||||
| Epic Link: | Ordering functionality that FOLIO needs to stay competitive | ||||||||
| Front End Estimate: | Large < 10 days | ||||||||
| Front End Estimator: | Khalilah Gambrell | ||||||||
| Front-End Confidence factor: | 20% | ||||||||
| Back End Estimate: | Large < 10 days | ||||||||
| Back End Estimator: | Khalilah Gambrell | ||||||||
| Back-End Confidence factor: | 20% | ||||||||
| Development Team: | Thunderjet | ||||||||
| PO Rank: | 0 | ||||||||
| Rank: Cornell (Full Sum 2021): | R3 | ||||||||
| Description |
|
Current situation or problem: When the Acquisition accordion was added to Inventory view and Instance, Holding and Items with order data were enabled, libraries with acquisitions units enabled lost the ability to view acquisitions information from within Inventory unless the staff member was assigned to the acquisitions unit in addition to having the appropriate permissions. Library staff outside the acquisitions unit, or within another tenant in a multitenant environment, want to be able to see whether order information is present, as well as seeing other relevant bibliographic information, without having access to sensitive information or information protected via nondisclosure agreements or contract (such as pricing information.)
In scope: Define and designate "protected" order information Allow view-only permissions for non-privileged fields for otherwise authorized staff who are not in the acquisitions unit. Modify ECS functionality to support limited order visibility in tenants outside the ordering tenant. Out of scope Use case(s) A typical use case is: a university library system has 2 accounting units (main and law.) Law wants to see if Main has ordered this material so they can determine whether there is a need to purchase it for themselves. An acquisitions librarian within a resource sharing consortium wants to know if a forthcoming title is already on order elsewhere in the consortium, and if so, how many copies have been ordered. Proposed solution/stories Links to additional info This feature was derived from https://folio-org.atlassian.net/browse/UIIN-2292 Specific fields to be exposed are identified under Acceptance criteria. Questions Are the fields exposed under "Acceptance criteria" in the linked Jira universal, or will libraries want additional control? Should there also be the option for "reduced visibility" beyond what is described above, consisting of a minimal "X copies on order for Location"? Should we allow libraries to designate certain order types as "suppressed" outside the acquisitions unit? (Example: a library subscribes to an e-content database and does not have document delivery permissions. At a single-campus university with a separate law school, the law school may have access to university-licensed databases, but not vice-versa, so the main library will want to expose everything, but the law library may want to restrict visibility because it cannot share that database.) |