Currently, the Taxonomies plugin works by scanning indexed pages for particular metadata fields. This works well for aggregating arbitrary pages throughout your site, regardless of plugin/collection structure, and for applying custom tagging, but it is mentally complex and by nature creates a 2-level hierarchy: Taxonomy > Term > Page.
In addition to that, the Taxonomies should be able to work with the model of page relationships already well-supported throughout the rest of the Orchid, by specifying collections and having it generate a single-level archive: Collection > Page. These will naturally be simpler and less flexible but should be much easier to set up and use. Configurable properties should be very similar to those on Term objects (sort order, permalinks, etc.)
Currently, the Taxonomies plugin works by scanning indexed pages for particular metadata fields. This works well for aggregating arbitrary pages throughout your site, regardless of plugin/collection structure, and for applying custom tagging, but it is mentally complex and by nature creates a 2-level hierarchy: Taxonomy > Term > Page.
In addition to that, the Taxonomies should be able to work with the model of page relationships already well-supported throughout the rest of the Orchid, by specifying collections and having it generate a single-level archive: Collection > Page. These will naturally be simpler and less flexible but should be much easier to set up and use. Configurable properties should be very similar to those on Term objects (sort order, permalinks, etc.)