What tags are for

Buyers, exporters and auditors seldom want all of your records. They want the blocks that grow for one market, the applications done for one buyer, or your crop protection without the foliar feeds. Intecrop cannot tell those apart on its own: a block does not know which market its fruit goes to, and a chemical does not know which programme you bought it for.

A tag is how you tell it. You put your own label on the block, the application or the chemical, and then, when you download a report, you say which labels it is for.

A key and a value

A tag has two parts. The key says what you are describing, and the value says which one: in Use: Raisins, the key is Use and the value is Raisins.

The key is what makes one tag the opposite of another. Use: Raisins and Use: Table grapes are two answers to the same question, so a block can carry only one of them. Give a block a new value for a key it already has and the new value takes the place of the old one. A block can still carry many tags, as long as each has a different key: Use: Raisins and Irrigation: Drip can sit side by side.

Capitals do not make a different tag. Use: Raisins and use: raisins are one tag, and extra spaces are taken out. A key or a value can be up to 40 characters long, and a key may not contain a colon (:), because that is what goes between the two.

Only a farm admin or a manager can add, rename, merge or delete tags, or put them on and take them off. Everyone else on the farm can see them.

Three kinds of tag

Each tag is for one kind of thing: blocks, applications or chemicals. A block tag cannot go on an application, even if the words are the same, because the reason you tag each one is different.

Blocks: what the block is for

A block's tag says something about the block that holds from one season to the next. The usual one is where its fruit goes: Use: Raisins on the blocks that are dried, Use: Table grapes on the ones that are packed. When an exporter asks for the records of the raisin blocks only, the tag is how you give them that and nothing else.

Because the tag is on the block, not on a season, it stays on the block until you take it off. You do not tag it again each year. The one time you do is when you re-establish a block: the new block starts with no tags, so tag it again.

Applications: who the application was for

An application's tag says who or what it was done for: Buyer: Woolworths on the applications that a buyer's programme called for. When the buyer asks what you did for them, you can give them a summary of those applications only.

You can tag an application at any step, also after it is confirmed, and tagging does not change the application. When you start a new application from an earlier one, it gets the earlier one's tags, so a programme you repeat stays tagged.

Chemicals: which group a product belongs to

A chemical's tag puts products into groups of your own: Programme: Foliar feed on your foliar feeds, so you can leave them out of a summary that should show only crop protection.

A chemical's tags are the same in all your stores. The tag is on the product, not on one store's stock of it, so tag it once and every store that holds it shows the tag.

Where tags count

A tag on its own changes nothing. It counts when you download a report: there you can say Only these, to keep what carries a tag, or Leave these out, to drop it. Not every report can use every kind of tag:

If your role sees costs, the application summary is called Application & cost summary. The summary for all your farms together cannot use tags: each farm has its own.

The reports that cannot use a kind of tag leave it out for a reason:

• One block's records were asked for by the block, so a block tag would either keep all of it or none of it.
• An application's instruction and confirmation are for one application, with totals over all its blocks, so only its products can be left out. The application itself stays on the document even if every product is left out. An instruction goes to the person mixing the tank, and a product left off it is a product that does not get applied, so leave a product off only when someone else's instruction carries it.

On the block records, a chemical condition takes product lines off each record, and a record left with no products at all goes too, so the report reads as if that application never happened.

A filter only takes things off the report. What Intecrop works out — the PHI, the expected harvest date, the protective wear on an instruction or a confirmation, the cost of a product — is still worked out from everything, as if there were no filter. A foliar feed left off a confirmation can still call for protective wear, and it still shows.

A condition is one key and any of its values. Only these with Use: Raisins and Use: Table grapes keeps the blocks that carry either, and leaves out every other block, also one with no tag at all. Leave these out with the same two values leaves out the blocks that carry either, and keeps the rest. Add a second condition and both must hold: only Use: Raisins blocks, and leaving out Programme: Foliar feed.

For how to do this on the application summary, see Create an application summary.

Tags never print

The tags themselves never appear on a report. The download screen tells you, in words, what each condition will include or leave out, but the PDF or spreadsheet you send does not. The person you send it to sees only what is left, with nothing to say that anything was taken off.

That is deliberate. Your tags are your own words for your own farm, and the buyer does not need to see Buyer: Woolworths on Woolworths' own report, or learn which other buyers you have. It does mean the report cannot explain itself: if a buyer asks why a block is missing, the answer is in your tags, not on the page they have.