Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Information in italics is intended to provide guidance while writing documentation and in general should be removed when a doc is at a v.1 stage.
The italics are suggestions to help guide what might go in a particular section. If you feel a section does not apply to the app or feature, please keep the section but just add that it does not apply.
If you feel it makes more sense for your documentation, you can move sections up and down.

Purpose

This area of Settings lists calendars for FOLIO service points hat allow libraries to set open and closed hours for those service points.

There is one calendar for every service point, available under Library hours.

You do not create calendars directly. You create a Service Point, and then FOLIO creates an associated calendar for you to manage.

Library opening and closing hours must be set / configured for any service point that serves as a primary service point for one or more locations where items are held.

Permissions

Describe permissions that apply to the app or section you are outlining. Include default permissions and permission sets; dependencies that exist with permissions in other apps/parts of FOLIO. 
Describe action-based permissions (if any) that apply to the app or section you are outlining, including permission dependencies and associated functional workflows.
Describe what each permission does, in language accessible to non-IT library staff.

The Calendar section of Settings has basic CRUD permissions:

  • Settings (Calendar): Can view calendar events
  • Settings (Calendar): Can create, view, edit, and remove calendar events.
  • Settings (Calendar): Can create, view, and edit calendar events

No action-based permissions are currently known to exist in this area of FOLIO. If any are developed, please add them to this documentation.

UX/UI

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.

All Service point calendars are listed under Library Hours. 

  • Each Service Point has a corresponding calendar with the same name.
  • When you select that calendar, you will also see the service point code and discovery display name.

Then you have two options for creating / modifying hours for that service point.

  • Regular library hours
  • Actual library hours

The idea is that a library would create "Regular library hours" for specified time periods, and that would be the hours the library expects to be open. When a time period is created, it will be listed on the screen as Start Date - End Date.

Then, libraries would use the "Actual library hours" option to add exceptions to the regular library hours, such as weather closings, or expanded hours for exams.

Searching

There is no search functionality in this part of FOLIO.

Functional workflows

  • Add library regular hours
  • Modify / delete library regular hours
  • Add exceptions to a service point's calendar.

No action-based permissions are currently known to exist in this area of FOLIO. If any are developed, please add them to this documentation.

Reporting

There are no in-app reports in this section of FOLIO.

Integrations

Libraries may wish to develop integrations for this area that could support

  • use of hours from an institutional / broader calendar, if their institution has one that also offers an API;
  • connections between service point hours and room scheduling software such as LibCal;
  • external display of service point calendars, such as through Outlook or on a library's public website.

No existing integrations between this area of FOLIO and outside tools are currently known to have been developed. If any are developed, please add information on them to this documentation.



  • No labels