2025-02-19 Cross App SIG Meeting notes
Date
Feb 19, 2025
Homework
Review
Housekeeping
Convener and notes: Tara
Topics: 2025 Meeting and Topic Calendar
Discussion topics
Time | Item | Presenter | Notes |
|---|---|---|---|
5 min | Announcements | Tara |
|
| Hidden Fields | Laura |
|
Notes
Today we focused on continuing our discussion of hidden fields functionality in FOLIO. We looked at Laura's updated document outlining the technical specifications.
We talked more about how hidden fields should work. When fields are hidden, they won't display anything in both view and edit modes, whether populated or not. We think it wise to include highlighting functionality when showing hidden fields, so users can easily identify which fields were previously hidden - similar to how FOLIO already highlights search results and version history changes.
We talked a lot about permissions and security. Owen clarified that hiding fields is purely a UI display feature - the data would still be accessible through browser dev tools, so this shouldn't be used for confidential information.
We debated whether required fields should be hideable. After considering use cases like Chicago's material type scenario, we agreed that any field should be able to be hidden.
For configuration, we determined that hidden field settings should be integrated into individual app settings rather than having a separate tenant-level section, since different people often manage different apps at institutions.
We also discussed adding an option for "hide only if populated" versus always hiding fields, which would provide more flexibility for different use cases.
Owen raised questions about screen layout behavior when fields are hidden - whether elements would move up to fill space and how accordions would behave if all their fields are hidden.
We acknowledged that we still primarily have inventory use cases and need examples from other apps. Other use cases will be gathered by the relevant SIGs.