ALTER9: Events

3 min

the alter9 events option allows you to manage your dairycomp events configuration the changes you make here will impact the events that you can enter for your animals to manage your events configuration, simply enter alter\9 in the command line, or enter alter in the command line and then choose option 9 for user‑defined events either of these actions opens the alter9 events configuration window you can add new events or edit user‑defined events in this list, but you cannot change any of the system events that come with the original program (events 1–18), except for their event name beyond the 18 system events, you can create up to 63 additional events see the topics below when configuring your events in dairycomp create new event or edit settings for an existing one follow the guidelines below when creating or editing an event enter alter \9 in the command line to open the events configuration window to create a new event, select the add option, or press the insert key to edit an event, click on an event in the list and select the change option, or press the f2 key enter an event name up to 7 characters use the checkboxes below the event name to select which options the event should prompt for when it is entered (event day, remark, etc ) note that the command content field is updated as you select different options if you want to make this a combination event , you can check that box now and click ok see create a combo event docid 8 yopecfyeksw0dkfyism for additional instructions to define a gap for this event, enter the number of gap days in the duplicate event gap field see define a gap for an event docid 8 yopecfyeksw0dkfyism for details on what a gap is and how it works to associate a team with this event, select it from the team drop‑down list at the bottom of the window, you can use the text and background buttons to adjust the event's appearance these options adjust the text color and background color so that events of this type stand out differently from other events on the events tab docid\ dffsrgo 1rwzrvbymonew in your cowcard you can see a preview of your event format in the field to the left of those buttons when you finish defining your event settings, click the ok button at the top right of the window to save the new/updated event and add it to the system if you chose the option to make this a combination event, the system displays another pop up where you can select the events to add to the combo see create a combo event docid 8 yopecfyeksw0dkfyism for additional instructions delete/remove an event from alter9 events enter alter \9 in the command line to open the events configuration window, and then click on the last event in the table select the delete option or press the delete key \important \ you can only delete the last event that was added to the list you cannot remove any of the other events from the event table; you can only rename them there are options in the events command to remove an event from the animal records, if desired, as well as to map one event name to another see create new event or edit settings for an existing one docid 8 yopecfyeksw0dkfyism for help renaming events create a combo event a combination (or "combo") event exists in dairycomp solely to allow you to create event items that reference a set of events (as opposed to a single event) you cannot actually enter a combo event, and a combo event would never appear on a cowcard instead, it exists as an event for which you can make items why use a combo event? the goal is to make event items that reference a set of events (as opposed to a single event) for example, lets say you have interest in three specific repro events preg, open, and ok — we'll call them "vet events" — and as an item for reporting, you want to see the date of either the latest preg, open, or ok you could create 3 unique items to represent the "latest date" for each of these events, something like lok, lpreg, and lopen, and make these dates specific to those events however, that's not really what you want; you want a single date item that represents the latest of an open, preg, or ok this is where combo events come in a combo event is sort of a "virtual" event as mentioned above you cannot actually enter a combo event, and a combo event would never appear on a cowcard instead, it exists as an event for which you can make items continuing with our "vet events" example, if you create a combo event that contains all three of the open, preg, and ok events, you can then create a single item for that date — we'll call it lvet — and use it on reports to create the new event item, you'll need to use alter\2 proceed with the instructions below to create a combo event follow the steps below to create a combination event follow the steps in create new event or edit settings for an existing one docid 8 yopecfyeksw0dkfyism and be sure to check the combination event set box when you check that box, the system displays a window to confirm that you want to create a combo event click yes in that window the system assigns an event name with the next available number in the system, such as combo52 this name cannot be edited when you are done selecting the settings for the event, click ok this closes the "new event" window and opens another window where you can choose the events to include in the combo check the events you want to add, and click ok to save the combo event and add it to the system define a gap for an event in dairycomp, you can use the "gap" option to set the number of days that multiple treatment events will be considered part of the same occurrence setting a gap value is helpful when conducting analysis on the farm because the number of events can be greatly inflated if a gap value is not set and employees re enter the event multiple times to track daily treatments click here to see a detailed explanation of the gap value! to understand the gap value better, let's review an animal that has been treated for ketosis when checking the animal's cowcard, consider how many times she has had ketosis you might at first say 5 times but that is just the number of ketosis events, or treatments ; it's not necessarily the number of times the animal has had ketosis she was treated three times in early march, and again in early may if the question is how many times was this animal treated for ketosis? , then 5 times would be correct if the question is how many times did this animal have ketosis? , then it's more accurate to say she had ketosis 2 times the outcome of using a gap in events is that the type 74 item definition (“count of events”) will be reflected in the gap affected values in the example provided above, you could set a gap value of 5 on your ketosis event to ensure that all ketosis treatments that are entered within a 5‑day timeframe will all be included under one ketosis occurence in the “count of ketosis events” item you could then create 2 type 74 items for the number of ketosis treatments and the number of ketosis occurrences \item\ \type\ \alter2 asks use gap?\ \result\ xketo 74 no 5 nketo 74 yes 2 then the ketosis count in this instance would be 2, not 5 (the first occurrence being in early march and the second being in early may) the gap value is helpful in a situation like this because the dairy owner or veterinarian might want to look at trends in ketosis across the herd in this case, whether the cows were treated 3 times or 1 time per occurrence is less important it's more important to know if ketosis has become more of a problem recently, so maybe the time of year or stage of lactation is more relevant than number of treatments click here to see the gap value explained with the mast event! for this example, we will focus on the mastitis event (mast) with a gap of 14 days, assuming that an animal will receive multiple mast treatments for one occurrence of mastitis within those 14 days if the first mast event is entered into dairycomp today and again in 5 days, the system will still track both treatment events, but it will consider them as part of a singular occurrence in this case, here's what you can expect to see on the cowcard the events tab on the cowcard will show each individual mast event entry, along with its treatment details (date, protocol, and treatment area) the items tab on the cowcard will only show a value of 1 for the item, even though the mast event has been entered twice even if a mast event is entered within the gap period yet is treated in a different area (different hoof or teat), xmast will still consider this as part of the initial event continuing forward during the 14 days of this gap period, if the mast event is entered several more times, the gap value will calculate off of the last entry, and the system will still count it as one xmast event as long as it is entered within 14 days from that first mast entry if the same animal is given a second mast event entry 15 days from the initial entry, the system will consider this a new event because the initial gap value was set to 14 days if this occurs, the xmast item will now be updated to 2, indicating that the animal has been treated for mastitis twice during this lactation cycle to set a gap value enter alter\9 in the command line open the event that requires the gap enter a value (number of days) for duplicate event gap click the ok button at the top right of the window to save your changes related topics note that the instructions in this topic are for configuring the events that are available in dairycomp for information on events that have been added to an animal, see events tab docid\ dffsrgo 1rwzrvbymonew