Considerations for Implementation
Describe decisions or implications that need to be considered when implementing this feature. Include topics such as order of operations during implementation or affects of implementing in a certain way.
- Institutions that need to support multiple timezones should monitor
. Currently there is one timezone setting per tenant so multiple timezones are not supported in a single-tenant implementation.
Jira server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key UXPROD-592
There is one permission control currently implemented for this area of Settings:
There are no action-based permissions currently implemented for this area of Settings. If that changes, please update this information.
Describe out of the box fields, including designed purpose, data requirements and validation, dependencies between fields.
Describe out of the box accordion menus, including purpose of the menus, customization options, and associated permission controls (if any)
Describe any workflows available through navigation menus, including purpose of the workflow, customization options, and associated permission controls.
Institutions are created through a settings table (that may look familiar as this is similar to other areas of Settings.)
In addition, you have
- Last Updated Byupdated by
- Displays date of last update and name of user who did update
- Refreshes when value is saved
- # of locations
- Automatically generated to show # of locations attached to Institution
- Two options - pencil icon (edit) and trash icon (delete)
- Trash icon gives error message and does not allow deletion if locations are attached to the institution
There is no default search function in the GUI for Institution records.
Describe available tasks that can be conducted in the app. To document those tasks, create a new page and link it to this page.
Describe action-based permissions that are connected to these functional workflows, if any.
- Creating, Editing, Deleting Institutions
Describe available There are no in-app reports , including parameters for the reports, and associated permissions.
If there are developed LDP reports/queries for this app / area of FOLIO, describe those reports as well.
List any fields that may not be available in the LDP (e.g., for privacy reasons.)available in this section of FOLIO.
Describe any APIs that interact with the app. Provide links to the API / module information in Github.
Describe integrations that individual libraries may wish to develop for this app / area of FOLIO, if relevant.
If existing integrations have been developed by adopting libraries, provide links to the integration in Github or wherever the information can be found.