Welcome to the Genotrack doc centre.
This will be the primary source of information relating to the Genotrack Project, support materials and other news.
You can use the table of contents to the left, or search the Genotrack documentation using the box below:
A minor (but annoying) bug was introduced with the 1052 release over the Christmas break.
When marking animals as dead via multiedit (eg: culling or discarding) an error dialog was appearing during the update process, as shown below:
So what does this mean? Were my changes being saved?
EVENT_RECORD creates the history record that gets associated with the animal.…
What's new in Genotrack 1052
Genotrack 1052, in addition to a range of bug fixes and interface and general improvements, introduces a number of our most requested additions and improvements.
The "big ticket" items include:
Date based project allocation
Until 1052, an animals association with a project (and the subsequent reporting) was 1:1 and in real time.
In other words, an animal is listed as being in use for one project, and the reporting will use the value currently assigned to a project.…
From time to time, we're asked about how the data in Genotrack is protected, and what you as the client should be doing to make sure their data is safe.
In essence, the Disaster Recover plan for Genotrack should have a minimum of 4 stages:
Stage 1 - Backup
The running database is backed up, with the log file allowing us to recover to any point between backups in the event of a serious corruption of the datafile.…
|
|---|
Labels
Page: Genotrack 2 - the G2 project
Page: Technotes
Page: Genotrack Manual
Page: Training Materials
Page: Release Notes
Page: Backlog