Field admin

“Field admin” in the storage module is the same list of fields as in the field module, and it is shown to agricultural companies. In the storage module a field matters in two ways: the harvest is hauled from the field to a storage, and the field itself can be used as a storage (for example a silage store or clamps on the field).

Page layout

• Views “List”, “Agreements” and “Map view”, buttons “Add new agrifield” and “Add from file”.
• Crop year buttons: “Consolidated view (last active cropyear)” or a specific crop year.
• The table includes “Name”, “Field number”, “Reg no”, “Area (ha)”, “Crop” and “Variety”. Click a row to open the field.
• The buttons for actions on several selected fields at once (export, “Works and materials”, yields and more) are described on the page Field admin.

How to use a field as a storage

1. Click the field’s row.
2. On the “Main data” tab, tick “Used as storage”.
3. Press “Save”.

Such a field can then be selected in the “Storage” field on a work’s material row and when entering an inventory balance, and used as the origin or destination of a transport just like a storage. The field’s window then has an “Inventory” tab with the materials in it and their amounts.

Harvest from the field to a storage

When the origin of a transport is a field, the destination is a storage and the material hauled is of the silage type, the transport is saved as a harvest transport (see Transport of harvest). Terake sets the material hauled from the field’s crop year:

• if the crop year’s “Crop purpose” is “teraks või avamaal” (for grain or in open field) or “katmikalal” (under cover), the material is the harvest of that crop;
• otherwise the material is the destination’s silage of that year.

A missing harvest or silage material is created, and the destination of the transport is marked as a storage. The amount hauled is added to the destination’s inventory. That is why it pays to keep the crop and the “Crop purpose” correct in the field’s crop year; you change them on the field’s “Crop years” tab.

How to add or change a field

1. Press “Add new agrifield” or click an existing field.
2. On the “Main data” tab, fill in “Workobject name”, “Reg no”, “Field number” and other fields as needed. Press “Save”.
3. Add the crop year, the crop and the field boundary on the “Crop years” tab.

All the fields and tabs of a field are described on the field module page Field admin.

Who can see and change it

The menu item is in the storage module for employees of an agricultural company who have the role “Stock management”. The roles “Administrator”, “Stock management” and “Agronomist” can add and change fields.

Tips

• Work objects used as storages are managed on the page Workobjects.
• The inventory and movements of the harvest are shown in the harvest material’s window on the page Materials.

API calls on this page

For integrations and AI assistants: this page uses the following Terake API calls. The full description is in the API reference.

When the page opens:

• GET /api/agrifield_data/{crop_period_id} – Agrifield collection

Adding, changing and deleting (from the API description):

• DELETE /api/agrifield_data/{crop_period_id}/{id} – Delete Workobject

Other calls from this screen’s dialogs and actions (from the web client’s code):

• DELETE /api/agreements/{id} – Delete Agreement by ID or UUID
• DELETE /api/agreements/{agreement_id}/agreement_object/{agreement_object_uuid} – Removes an agreement object
• DELETE /api/agrifields/{id} – Delete Workobject
• DELETE /api/inspections/workobject/{id} – Delete InspectionCase by ID or UUID
• DELETE /api/workobjects/cadastres/{workobject_id}/{cadastre_id} – Removes a Workobject from a Cadastre
• DELETE /api/workobjects/{id} – Delete Workobject
• DELETE /api/workobjects/{id}/files/{uuid} – Delete file
• GET /api/agreements/agrifield – Agreements collection
• GET /api/agreements/{id} – Agreement by ID or UUID
• GET /api/agrifield_data/{crop_period_id}/{random} – Agrifield collection
• GET /api/agrifield_data – Agrifield collection
• GET /api/agrifield/pria/massive/{massiveid} – Returns Pria Massive
• GET /api/agrifields/{id} – Get Workobject
• GET /api/agrifields – Agrifield collection
• GET /api/agrifield-multiworks – Work of several Agrifields around a date
• GET /api/cadastres/{id} – Get Cadastre
• GET /api/faults/workobject/{faultitem_consumer_id} – Faultitem collection of one work object
• GET /api/faults/workobject – Faultitem collection of work objects
• GET /api/fieldbook – Fieldbook Agrifield collection
• GET /api/fieldsshapefile – Fields as a shapefile
• GET /api/geoinfo/cadaster/{num} – Cadastral register information for one cadastre number
• GET /api/geometry/agrifielddata/{id} – Geometry of one agrifield_data record.
• GET /api/inspections – InspectionCase collection
• GET /api/inspections/workobject/{consumer_id} – InspectionCase collection of one work object
• GET /api/inspections/workobject – InspectionCase collection
• GET /api/fieldbook/overlapping-check/{agrifield_id}/{crop_period_id} – Reports fieldbook entries whose geometry overlaps for one Agrifield and crop period
• GET /api/workobjects – All Workobjects list
• POST /api/agreements – Create new Agreement
• POST /api/agrifieldplannedyield/{crop_period_id} – Sets the planned yield on the listed Agrifields for the crop period
• POST /api/agrifield-multiworks – Creates work for several Agrifields at once
• POST /api/agrifields – Creates or modifies a Workobject
• POST /api/agrifieldyield/{crop_period_id} – Saves the harvested yield on the listed Agrifields for the crop period
• POST /api/pria-send-yields/{crop_period_id} – Sends the yields of the crop period to e-PRIA
• POST /api/workobjects/cadastres/{workobject_id}/{cadastre_id} – Add Cadastre to Workobject
• POST /api/workobjects – Creates or modifies a Workobject
• PUT /api/agreements/{id} – Modify Agreement
• PUT /api/agreements/{id}/togglearchive – Toggle Archive/Un-archive Agreement
• PUT /api/agrifields/{id} – Modifies a Workobject
• PUT /api/agrifields/{id}/setcropperiod – Sets the Agrifield data for a crop period
• PUT /api/agrifieldworks/{id}/agrifieldsoperation/{action} – Add, exclude or clear one field in a planned job's selection
• PUT /api/agrifieldworks/{id}/joinagrifield/{agrifieldid} – Add one field to a planned job
• PUT /api/agrifieldworks/set/{id}/agrifields – Add fields to, or exclude them from, a planned job
• PUT /api/crops/merge/{mergerId} – Merge crops
• PUT /api/geometry/agrifielddata/{id} – Stores the geometry of an Agrifield data record
• PUT /api/workobjects/{id} – Modifies a Workobject