Welcome Guest to Defaut site!

BMaster Application

Overview

This application is intended to both educate and provide a platform for beekeepers to manage their hives and apiaries. It allows beekeepers to log various details about their hives, and then use this data to generate a graph showing changes over the season.

Features

The BMaster application includes several features designed to assist beekeepers in managing their hives:

Data Collection: Beekeepers can input data about their hives, such as the number of frames of bees, brood, comb, honey, pollen, and empty in each box, the queen and her heritage, and the location of the hive.
Data Visualization: The application can generate a graph showing changes in the hive over the season.
API Integration: The application includes an API that allows other systems to retrieve the data.

API Integration

The BMaster application includes an API that allows other systems to retrieve data about the hives. The API provides endpoints to get data for a specific hive, get data for all hives for a specific beekeeper, and get data for a specific season.

Instructions for Developers

Developers contributing to the BMaster project should adhere to the following guidelines:

Naming Conventions: Follow the existing naming conventions for consistency. If you encounter any deviations, normalize them to maintain uniformity.
Code Quality: Ensure that all code is well-documented and adheres to the project's coding standards. Use meaningful variable and function names to enhance readability and maintainability.
Error Handling: Implement robust error handling in all subroutines to ensure the application behaves predictably under unexpected conditions.
To-Do List: If you identify any issues or potential improvements in the code, add them to the 'Todo' section of this documentation.
Code Reviews: Submit your code for review by peers to catch potential issues early and ensure adherence to best practices.

Future Improvements

Future improvements to the BMaster application may include enhancements to existing features or the addition of new ones. Developers are encouraged to contribute to these improvements by keeping this documentation up to date and following the guidelines provided.

Routes

The BMaster module includes the following routes:

/BMaster (Not defined yet)
/BMaster/bee_pasture
/BMaster/add_graft
/BMaster/frames (Error: Can't call method "get_frames_data" on an undefined value)
/BMaster/api/frames (Error: Can't call method "get_frames_data" on an undefined value)
/BMaster/products
/BMaster/yards (Error: Can't call method "get_yards" on an undefined value)
/BMaster/apiary
/BMaster/Queens
/BMaster/hive
/BMaster/honey
/BMaster/beehealth
/BMaster/environment
/BMaster/education

BMaster Controller Documentation

base

The 'base' function serves as the root of the chained actions in the BMaster controller. It captures '/BMaster' in the URL and performs common setup tasks that are shared by multiple actions in the controller. This function is crucial for avoiding code duplication and enhancing code maintainability and readability. Here are some tasks that the 'base' function can perform:

Loading Model Data: The 'base' function can load data from the BMaster model that is required by multiple actions in the BMaster controller. This data is stored in the stash for other actions to use.
Checking User Permissions: The 'base' function can verify if the user has the necessary permissions for multiple actions in the BMaster controller. If the user lacks the required permissions, they are redirected to an error page.
Setting Common Template Variables: The 'base' function can set template variables that are used by multiple actions in the BMaster controller.

index

The 'index' function sets the template to 'BMaster/BMaster.tt' and forwards to the TT view. This function is responsible for rendering the main page of the BMaster section.

frames

The 'frames' function retrieves the frames for a specified queen and sets the template to 'BMaster/frames.tt'. This function is used to display the frames associated with a particular queen bee.

api_frames

The 'api_frames' function fetches the data for the frames and sets the response body to the JSON representation of the data. This function is used to provide a JSON API for accessing frame data.

products

The 'products' function sets the template to 'BMaster/products.tt'. This function is used to render the page that displays the products of the BMaster.

yards

The 'yards' function retrieves the yards and sets the template to 'BMaster/yards.tt'. This function is used to display the yards associated with the BMaster.

apiary

The 'apiary' function sets the template to 'BMaster/apiary.tt'. This function is used to render the page that displays the apiary of the BMaster.

queens

The 'queens' function sets the template to 'BMaster/Queens.tt'. This function is used to render the page that displays the queens of the BMaster. It also calculates and displays the graft dates for each queen.

hive

The 'hive' function sets the template to 'BMaster/hive.tt'. This function is used to render the page that displays the hives of the BMaster.

honey

The 'honey' function sets the template to 'BMaster/honey.tt'. This function is used to render the page that displays the honey products of the BMaster.

beehealth

The 'beehealth' function sets the template to 'BMaster/beehealth.tt'. This function is used to render the page that displays the health status of the bees in the BMaster.

environment

The 'environment' function sets the template to 'BMaster/environment.tt'. This function is used to render the page that displays the environmental conditions of the BMaster.

education

The 'education' function sets the template to 'BMaster/education.tt'. This function is used to render the page that displays the educational resources of the BMaster.

Back to top

BMaster Model Documentation

get_frames_for_queen

This function fetches the frames for a given queen based on the queen's tag number. It returns a reference to an array of frames.

get_yards_for_site

This function fetches all yards for a given site based on the site's name. It returns a reference to an array of yards.

Back to top

Queen Management System

Our queen management system is designed to manage the lifecycle of the queen bees in our apiary. Here are the key activities and their timelines:

Date	Activity
Graft date	The date when the grafting process starts.
3 days after graft date	Move the brood back from the incubator and count the number of cells that have been started.
10 days after graft date	Move the cells to the mating nucs.
20 days after graft date	The queen will have been mated and start laying.
Queen pull	The number of days entered in the form egg laying day.
Second graft	Done 10 days before the queen pull.

We store the graft date and the number of days of egg laying in the database. This helps us to track and manage the lifecycle of each queen bee.