farmerswife basic terminology

This article should give you a better understanding of the used terminology in farmerswife and how it might translate form your systems in use.

Objects

In farmerswife, an “Object” is a general term for the items you create and manage in the “Object Manager.”

Examples:

| “Users” | People with farmerswife access |

| “Resources” | People without a user license, e.g. freelancers |

| “Rooms / Machines / Equipment” | Bookable items on the timeline |

| “Services / Materials / Expenses” | Extra cost items added to projects |

| “Groups” | Collections of multiple objects |

| “Time Units” | Unit-based tracked items |

A simple way to think about it:

Object = anything you need to schedule or manage in farmerswife

Related terms:

| “Object” | The actual item/person/resource in farmerswife |

| “Object Type” | Broad category, like User, Resource, Equipment, Room, Service |

| “Object Class” | More specific grouping/category, like Editors, Cameras, VFX Artists |

Object Classes

An "Object Class" is the main way to "categorize Objects or Users" in farmerswife.

Related terms:

| "Object" | The actual item or person |

| "Object Class" | A group/category those items belong to |

Examples:

| "VFX Artists" | Emma Sullivan, other VFX artists |

| "HD Cams" | Individual camera objects |

| "Editors" | Individual editor resources/users |

What Object Classes are used for:

| "Grouping" | Puts similar objects/users into one category |

| "Booking" | Lets you book the "class" and have farmerswife allocate an available member |

| "Rates" | Lets members share pricing from the class |

| "Availability" | Helps view availability by class |

Key points:

- A class can be a "role" like “VFX artists”

- You can book the "class" instead of a specific member

- farmerswife can "automatically allocate" an available member from that class

- An Object/User can belong to "more than one Object Class"

Projects

A “Project” is the central record that groups related work in farmerswife. Projects are a central key in farmerswife that hold Bookings and all the Financial Data such as Budgets, Actuals and all the Extras. 

Projects can be grouped into Containers and/or broken up in Binders.

Examples:

| “Bookings” |  Scheduled people, rooms, machines, services |

| “Financial data” | Budgets, actuals, extras |

| “Project details” | Name, number, client/contact, notes, custom fields |

| “Structure options” |  Containers and Binders |

A good shorthand is:

> Project = the overall job

> Booking = scheduled work inside that project

Booking

A "Booking" is the scheduled record used to allocate "Objects" in farmerswife. Bookings are records created in the "Timelines" when Objects are added.

A Booking can define…

| "What / who is involved" | users, resources, rooms, equipment, services |

| "When" | date and time |

| "Status" | preliminary, confirmed, conflict-related statuses depending on setup |

| "Project connection" | linked to a Project and often its financial/budget context |

In practice:

> "Project = the overall job"  

> "Booking = the scheduled allocation inside that job"