Details
Reporter
Emma BoettcherEmma BoettcherPO Rank
0Rank: 5Colleges (Full Jul 2021)
R3Rank: Cornell (Full Sum 2021)
R4Rank: Chalmers (Impl Aut 2019)
R4Rank: GBV (MVP Sum 2020)
R2Rank: Grand Valley (Full Sum 2021)
R2Rank: Mainz (Full TBD)
R2Rank: Chicago (MVP Sum 2020)
R5Rank: MO State (MVP June 2020)
R1Rank: U of AL (MVP Oct 2020)
R5TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Reporter
Emma Boettcher
Emma BoettcherPO Rank
0
Rank: 5Colleges (Full Jul 2021)
R3
Rank: Cornell (Full Sum 2021)
R4
Rank: Chalmers (Impl Aut 2019)
R4
Rank: GBV (MVP Sum 2020)
R2
Rank: Grand Valley (Full Sum 2021)
R2
Rank: Mainz (Full TBD)
R2
Rank: Chicago (MVP Sum 2020)
R5
Rank: MO State (MVP June 2020)
R1
Rank: U of AL (MVP Oct 2020)
R5
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created June 12, 2020 at 6:30 PM
Updated January 23, 2025 at 5:39 PM
Purpose: Currently, the staff user's name is stored in the system in activity dates and other admin data. The feature would allow tenants to configure whether they store which staff members performed which transactions in FOLIO or anonymize the user data.
Information about which staff performed which actions displays across FOLIO. Future features may also require the storing and display of this data for some libraries. Examples:
Action tables on loan details and fee/fine details
Administrative data accordion
This feature would allow users to configure whether this information is stored, and specify UI behavior when this information is not available.