methnen

Registers taxonomies programtically from a config array and provides other helper functions.
We needed a way to add taxonomies that we rely on accross sites and managing those was becomeing cumbersome. This allows us to manage them via a config array.
The plugin also provides workarounds for limitations in WordPress handling of terms in feeds and post term sorting.
<h4>Sorted Terms</h4>
There’s also a <code>sorted_terms</code> helper function you can use in plugins and templates like this:
<pre><code>go_taxonomy()->sorted_terms( $post_id, $args ); </code></pre>
<h4>Parameters</h4>
$post_id
(int) (optional) The ID of the post you want to get sorted terms for
<h4>Argument Options</h4>
taxonomies
(array)
<ul>
<li>array( ‘post_tag’ ) – Default</li>
</ul>
number
(int)
<ul>
<li>99 – Default</li>
</ul>
format
(string)
<ul>
<li>list – Default</li>
<li>array</li>
<li>name</li>
</ul>
orderby
(string)
<ul>
<li>name – Default</li>
<li>count : terms ordered by their usage count</li>
</ul>
order
(string)
<ul>
<li>ASC – Default</li>
<li>DESC</li>
</ul>
<h4>Report Issues, Contribute Code, or Fix Stuff</h4>
https://github.com/GigaOM/go-taxonomy/

Gigaom Taxonomy

Registers taxonomies programtically from a config array and provides other helper functions.

parakeet

Many WordPress installs suffer from cramming hundreds or thousands of varied taxonomy terms in to a limited number of ill-suited, all-purpose taxonomies (eg. the default “categories” and “tags”).
These are better off split in to dedicated taxonomies. For example, storing “Bill Gates” and “Microsoft” terms in “tags” is not optimal, because one is a person whilst the other is a company.
There is no straightforward way to split up existing taxonomies more granularly in this way, except for labour-intensive and manual, technical effort. So, many WordPress installs continue to suffer from not having created granular taxonomies intentionally at the outset.
Term Tidier tidies up messy taxonomies like these automatically. It uses natural language processing and knowledge graph technology to determine the real <a href="https://gcloud.readthedocs.io/en/latest/_modules/google/cloud/language/entity.html#EntityType" rel="nofollow ugc">entity type</a> of existing terms, then re-assigns them each to a more appropriate, alternative taxonomy.
<h3>How it works</h3>
Term Tidier uses Google Cloud’s Natural Language Processing features via API calls.
Users set a “source taxonomy”, the taxonomy they want to be tidied up.
For each term within that taxonomy, Term Tidier calls Google Cloud to examine the term name, aiming to return a determination as to its true “entity”.
The plugin receives one of eight “entity” type determinations from Google Cloud – UNKNOWN, PERSON, LOCATION, ORGANIZATION, EVENT, WORK_OF_ART, CONSUMER_GOOD or OTHER.
For each entity type, users specify a target taxonomy to which a matching term will be moved. For example, you can map all terms found to be a “LOCATION” to your own “Places” taxonomy, if it exists.
For each term in the source taxonomy, if a particular entity was determined, Term Tidier moves the term to your corresponding taxonomy.
<h4>Usage</h4>
Use Term Tidier from the WordPress Tools menu (Tools > Context Term Tidier).
The plugin page confirms your settings as set in Settings, displaying the taxonomy and terms which will be examined.
Click the “Tidy Terms” button to execute the operation.
Term Tidier will cycle through each term, seeking an “entity” determination and re-assigning any terms possible.

Context Term Tidier

Tidies taxonomies that contain a mess of unrelated terms by using AI to move terms to more appropriate taxonomies.

Gigaom Taxonomy vs Context Term Tidier