-
-
Notifications
You must be signed in to change notification settings - Fork 403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Understanding JSON taxonomy fields #892
Comments
categories_hierarchy is a re-ordering of categories_tags, with the "level" of the entries as the sort key. The level is how deep the category is from one of the roots. categories is what the user entered last in the form, but what is shown on the form to the user when the page is edited is the content of categories_hierarchy, in the language of the interface. |
The difference between _hierarchy and _tags seems not very useful, especially when it is not possible to identify the tops of the trees. I like to know how off uses to interpret and extend what has been entered by the user. This can be used to give suggestions to the editors of taxonomies. |
I will have to incorporate the taxonomies and do my own processing. |
The new taxonomy exports may help: #1126 |
I will play wiith the json-versions. |
to \o old |
The API allows to inspect how OFF interprets taxonomy based fields. A taxonomy based field consist of one or more tags (one or more words tied together). This information could be used by the user to suggest improvements to taxonomies. I would like to support this in my app, but before that it must be clear what information the API offers.
Any taxonomy based field presents its data in the json in three variants. An example for categories:
These three fields are in this example very similar. I (want to) interpret them as:
In my app I support the viewing of these different fields. By double tapping you can cycle through them. It would be nice if these fields have actual meaning.
The text was updated successfully, but these errors were encountered: