-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Birth and movement quick form blog posts.
- Loading branch information
Showing
5 changed files
with
218 additions
and
0 deletions.
There are no files selected for viewing
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,118 @@ | ||
--- | ||
title: Birth Quick Form | ||
date: 2023-05-22 | ||
author: Michael Stenta | ||
slug: 2023/birth-quick-form | ||
--- | ||
|
||
# Birth Quick Form | ||
|
||
The farmOS [v2.1.0 release](https://github.com/farmOS/farmOS/releases/tag/2.1.0) | ||
includes a new and improved *Birth Quick Form* for quickly and easily recording | ||
animal births. This feature existed in farmOS v1, and has now been ported to v2. | ||
|
||
See the video below for a quick demonstration, and read on for more details. | ||
|
||
<video autoplay control loop style="width: 100%; height: auto;"> | ||
<source src="./birth.mp4" type="video/mp4"> | ||
</video> | ||
|
||
Recording the birth of animals in farmOS requires creating a few different | ||
records: | ||
|
||
1. A mother Animal asset to represent the animal that is pregnant. | ||
2. A Birth log that represents when/where/how she gave birth. | ||
3. One or more Animal assets that represent the newly born children. | ||
4. One or more Observation logs to record the child birth weights. | ||
|
||
Creating all of these records can be tedious, especially during a busy birthing | ||
season! | ||
|
||
The Birth Quick Form tries to make this process easier with a single form for | ||
creating the Birth log and all the children Animal assets in one step. The only | ||
requirement is that you have a mother Animal asset record to start. | ||
|
||
## Birthdate | ||
|
||
The form starts by asking for the date of birth. This defaults to the current | ||
date, so you can record births on the fly when they happen. You can also adjust | ||
this date to record births that happened in the past. This date will be used | ||
for the Birth log's timestamp, as well as in the "Birthdate" field of all the | ||
children assets. | ||
|
||
## Child information | ||
|
||
Next, the form asks how many children were born. Below this dropdown there will | ||
be sets of questions for each child. Changing the number of children in the | ||
dropdown will add/remove additional sets of child questions automatically. | ||
|
||
Within each set of child questions, you can fill in the following information: | ||
|
||
- Child name | ||
- Child ID tag information (tag type, tag ID, tag location) | ||
- Sex (male or female) | ||
- Birth weight | ||
- Notes about this child | ||
- Survived birth (yes or no) | ||
|
||
You must enter *either* a child name *or* child ID tag information. If a name is | ||
not provided, the tag ID will be used as the child asset's name. | ||
|
||
Birth weight can be specified in *lbs* (for US/imperial measurements) or *kg* | ||
(for metric measurements), depending on how your farmOS is configured. If a | ||
birth weight is entered, then an Observation log will be created that references | ||
the child asset with the recorded weight as a quantity on the log. | ||
|
||
Notes about the child will be saved to the Notes field of the child Animal | ||
asset itself. There is a separate Notes field for the overall birth of all | ||
children at the bottom of the quick form. | ||
|
||
The "Survived birth" checkbox will determine whether or not the child Animal | ||
asset status is set to "Active" or "Archived" when it is created. Assets will | ||
still be created for animals that did not survive birth, but will be immediately | ||
archived so their data is still saved. | ||
|
||
## Birth information | ||
|
||
Below the child-specific questions are three sections in vertical tabs: | ||
|
||
- Lineage | ||
- Group (if the Group module is enabled) | ||
- Notes | ||
|
||
Within the Lineage tab there are three fields: | ||
|
||
- Birth mother | ||
- Genetic mother | ||
- Genetic father | ||
|
||
A new feature of the farmOS v2 Bith Quick Form is the ability to differentiate | ||
the birth mother and genetic mother. The birth mother will be referenced in the | ||
Birth log that is created. The genetic mother will be referenced as a parent of | ||
the children assets that are created. | ||
|
||
You must specify *either* the birth mother *or* the genetic mother by | ||
referencing an existing Animal asset. If you haven't created this asset yet, you | ||
can open a new browser tab, create the mother asset, and then go back to the | ||
Birth Quick Form tab to reference it. Start typing the mother asset's name into | ||
the field and select the mother asset you want from the dropdown that appears. | ||
|
||
If only one mother is referenced in either field, it is assumed that they are | ||
both the birth mother and genetic mother. So at the very least you only need to | ||
specify one. | ||
|
||
If the Group module is enabled, a "Group" tab will be visible under "Lineage". | ||
This allows you to specify which Group asset the children will be made members | ||
of. If this is left blank, the children will become members of the birth | ||
mother's group, if available. Otherwise, no group membership will be assigned. | ||
|
||
Finally, a Notes field is provided for the overall birth. This can be used to | ||
record any notes, observations, complications, etc about the birthing process. | ||
These will be saved to the Notes field of the Birth log, as opposed to the Notes | ||
field of individual children assets described above. | ||
|
||
## Submit | ||
|
||
If everything you entered is valid, when you submit the form you will see a | ||
number of status messages with links to the records that were created, including | ||
the Birth log, child Animal assets, and weight Observation logs. |
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,100 @@ | ||
--- | ||
title: Movement Quick Form | ||
date: 2023-05-22 | ||
author: Michael Stenta | ||
slug: 2023/movement-quick-form | ||
--- | ||
|
||
# Movement Quick Form | ||
|
||
The farmOS [v2.1.0 release](https://github.com/farmOS/farmOS/releases/tag/2.1.0) | ||
includes a new and *Movement Quick Form* for quickly and easily recording the | ||
movement of assets to a new location. This feature existed as a more specific | ||
*Animal movement* quick form in farmOS v1, and has now been ported to v2 and | ||
generalized for use with any asset type (eg: Equipment, Plants, etc). | ||
|
||
See the video below for a quick demonstration, and read on for more details. | ||
|
||
<video autoplay control loop style="width: 100%; height: auto;"> | ||
<source src="./movement.mp4" type="video/mp4"> | ||
</video> | ||
|
||
Recording the movement of assets in farmOS requires creating a log with the | ||
following information: | ||
|
||
- The date of the movement | ||
- The assets that are moving | ||
- The locations that they are moving to | ||
- The geometry of the new location | ||
|
||
In order for this log to be counted towards the asset's current location, it | ||
must have a status of "Done", with a date in the past, and the "Is movement" box | ||
checked. | ||
|
||
For more information, see: | ||
[farmOS Location Logic](https://farmOS.org/model/logic/location) | ||
|
||
The Movement Quick Form streamlines this process by asking for only the | ||
essential information and filling in the rest automatically. | ||
|
||
The form starts by asking for the date when the movement took place. This | ||
defaults to the current date, so you can record movements on the fly when they | ||
happen. You can also adjust this date to record movements that happened in the | ||
past, or movements that you are planning in the future. If you plan future | ||
movements, be sure to uncheck the "Completed" box at the bottom of the form to | ||
indicate that it hasn't happened yet. | ||
|
||
Next, you must specify the assets that are moving. Start typing an asset's name | ||
into the Assets field and select the one you want from the dropdown that | ||
appears. Separate multiple assets with a comma. | ||
|
||
You can select the locations that the assets are moving to in the same way. If | ||
no locations are specified, this will clear the current location of the assets. | ||
|
||
If the assets and locations you selected have a geometry already, they will | ||
automatically show up on the map within the form. Current asset location | ||
geometry will be displayed in blue, and the location geometry will be displayed | ||
in orange. | ||
|
||
The location geometry is editable within the map, which allows you to customize | ||
the asset's new geometry. Use the map's edit controls to select the geometry | ||
you want to edit, and use the modify, move, or delete buttons to change them. | ||
You can also use the polygon, line, point, and circle buttons to draw new | ||
geometries. | ||
|
||
Customizing the geometry of the movement does *not* change the geometry of the | ||
location assets you selected. The new geometry is saved to the movement log | ||
itself, which is what gets referenced when you look at the location of your | ||
assets. Asset location geometry is determined by its movement logs. For more | ||
information, see [Movements and location](https://farmos.org/guide/location/) in | ||
the farmOS user guide. | ||
|
||
See the video below for a quick demonstration. | ||
|
||
<video autoplay control loop style="width: 100%; height: auto;"> | ||
<source src="./geometry.mp4" type="video/mp4"> | ||
</video> | ||
|
||
One example where this is useful is moving animals with temporary fencing for | ||
rotational grazing purposes. You may move a fence multiple times within the same | ||
paddock, and you want to be able to record exactly where the animals were grazed | ||
and for how long. The Movement Quick Form can accomplish this by referencing the | ||
same location multiple times, but drawing the fence geometry differently each | ||
time. | ||
|
||
Another example could be moving a piece of equipment to a field, but specifying | ||
the exact point where it was moved, so you (or someone else) can find it again | ||
easily. Using the Movement Quick Form, you can specify a location like "North | ||
Field" and also draw a point on the map exactly where the equipment is in "North | ||
Field". | ||
|
||
At the bottom of form there is an area to enter notes about the movement, which | ||
will be saved to the "Notes" field of the log that is created. | ||
|
||
The "Completed" checkbox at the bottom defaults to "Completed", but can be | ||
unchecked if you are planning a future movement. | ||
|
||
Upon submitting the form, you will see a message with a link to the new log that | ||
is created, and if you look at your asset records you will see that their | ||
current location and geometry has been updated. | ||
|
Binary file not shown.