In the Meeco Vault, Items, Item Templates and Slots can be tagged with Classification Nodes. If an Item has been tagged with a Classification Node, you can find it again by searching for that Classification Node.
Classification Nodes are a lot like tags, but are grouped into Schemes. Schemes might represent similar topics, or classifications from an existing app.
A Classification Node is structured like
Property
Type
Description
name
string
Machine-readable name
label
string
Human-readable name
description
string
Explains what the classification represents
scheme
string
Browsing Classification Nodes
The $VAULT_ACCESS_TOKEN can be grabbed from the user file you created in the guide.
All classification nodes can be queried by GET /vault/classification_nodes:
You can modify the request with the following query parameters:
scheme_name, see below
by_name - a "LIKE" search which will return results for partial matches - i.e. 'fin' will return 'financial'
Schemes
Classification Nodes are grouped by Schemes. Available Schemes are set by the Vault and cannot be changed.
These are the existing schemes:
tag
country
meeco_wallet
region
You must use tag as the default scheme.
Creating a Classification Node
You can create a Classification node as follows
curl --request POST 'https://sandbox.meeco.me/vault/classification_nodes' \
-H "authorization: Bearer $VAULT_ACCESS_TOKEN" \
-H 'content-type: application/json' \
-H 'Meeco-Subscription-Key: $API_SUBSCRIPTION_KEY' \
--data \
'{
"classification_node": {
"classification_scheme_name": "tag",
"name": "my-new-tag",
"label": "My Tag",
"description": "Hi There this is my Tag!"
}
}'
{
"classification_node": {
"id": "b4ff857f-6f50-4608-bd93-b61a7dd012d5",
"background_color": null,
"description": "Hi There this is my Tag!",
"image": null,
"label": "My Tag",
"name": "my-new-tag",
"ordinal": 0,
"scheme": "tag"
}
}
Properties classification_scheme_name and either name or label are mandatory. As mentioned above, classification_scheme_name should usually be 'tag'. As for other Vault objects, if only label is given, then the name is created by translating the label text.
Since name is used to link a Classification Node to a Vault object, it must be unique.
Note that currently, as for Item Templates, the API does not allow:
updating Classification Nodes,
deleting Classification Nodes,
sharing new Classification Nodes
Applying Classifications
Classification Nodes can be applied to Item Templates, Items and Slots. Most provide a way of creating new Classification Nodes in the same request.
Templates
Single Classification Nodes may be applied to Item Templates:
This has two effects. First, the Item Template can be found via its Classification Node or Scheme name, e.g. queries GET /vault/item_templates?by_classification=tag, or GET /vault/item_templates?by_classification=new_tag should include the template. Second, new Items created with the Item Template will be classified with the Classification Node.
Classification nodes are added to Items by passing classification_nodes_attributes, just like adding Slots. If the name and scheme match an existing Classification Node, it is used, otherwise a new one is created.
Classification Node can be applied to both the Item and the Slots it contains. Unlike Item Templates, Items may have multiple classifications.
Note that even if the Classification Node name property matches an existing Node, but other fields don't, then a new Classification Node will be created. The scheme property must match an existing Scheme.
Slots are usually given Classification Nodes via POST /vault/items, but you can add a classification to an existing Slot using PUT /vault/slots/{id}.
Slots cannot be searched by Classification Node or Scheme.
Some Slots have the type classification_node. The intent is that the owning Item will be classified with that node. Usually this is done within an app.
