Dancer2 is a "micro" web framework which is modeled after a Ruby framework called Sinatra that constructs web applications by building a list of HTTP verbs, URLs (called routes) and methods to handle
snigdha SnigdhaD
SnigdhaD
/ tutorial.pod
Last active
February 9, 2025 17:19
In case you want to avoid a 404 error, or handle multiple routes in the same way and you don't feel like configuring all of them, you can set up a default route handler.
The default route handler will handle any request that doesn't get served by any other route.
All you need to do is set up the following route as the last route:
The list of projects that the Humanitarian OSM Team is currently working on, can be found here. You can get project details and ways to contribute by visiting the project's webpage.
Evergreen allows you to set up automated notifications and actions to respond to events in your system. An example of an event might be an item becoming overdue. An example of an action might be sending an email notification to users.
The Action Triggers and Notification module can be found in the staff client by navigating to Admin > Local Administration > Notifications / Action Triggers.
Normally, a penalty represents a kind of punishment. In Evergreen, however, a penalty is an action or alert related to a problem with a patron account. Some classes of Evergreen penalties are related to financial liabilities (Excessive fines, excessive money owed for other reasons like lost or damaged materials), while other Evergreen penalties are simply alerts to librarians about problems with a patron account such as an incorrect daytime telephonic number or invalid email address.
Library staff with the appropriate permissions can assign penalties to a patron account relating to patron misbehavior in the system. Penalties can range from a simple alert when a patron tries to check out materials to completely blocking a patron’s ability to check out materials until that patron pays the fines that she owed to the library.
This document covers some changes that users will need to be aware of while upgrading from Dancer1 to Dancer2.
1. In Dancer2, each module is a separate application with its own namespace and variables. You can set the application name in each of your Dancer2 application modules. Different modules can be tied into the same app by setting the application name to the same value.
NewerOlder