On 30/08/2012, at 4:18 PM, Malthe Borch wrote:
On 30 August 2012 03:22, Dylan Jay <[email protected]> wrote:
I think part of the issue with taxonomies is the same word gets
used to mean
different things in the CMS world. Drupal in particular has
"abused" it to
mean not just classifying something with a hierarchical tags, but
creating a
navigation structure based on those hierarchical tags. It's not
clear to me
if you are suggesting ways to tag content or ways to use tags in
content to
build navigation or something else? It's not clear to me your use
case, so I
think it might help to write this out more fully.
Just putting tags on content.
I really want to help get this sorted however so that we have one
solution
that is very flexible instead of all these partial implementations.
However
I think starting from small steps that integrate well with how we
currently
do things in plone is the best way to get there. Hence why
collective.facets
is very minimal and only deals with adding classification to existing
content.
==> collective.facets
This is not our typical use-case. We have a fixed model with fields
that pull values from a named vocabulary component.
yeah. c.facets is more for when you don't want to create your own
content types but do want more flexibility with classification of
existing types. I do want to extend it to use any fixed vocabularies
that might exist, including any taxonomy vocabularies such as what
you're suggesting creating.
What we want is to connect this component with a taxonomy hierarchy
implemented as Dexterity-content – which we'll try to keep as
light-weight as possible.
==> redomino.advancedkeyword
The basic motivation is the same, but we need a more general
implementation that really bridges the formal interface declarations
with an editable taxonomy.
Content items seems a clumsy way to create a taxonomy but I'm guessing
you want to make use of the permissions system such that colour/* can
be "owned" by one group and type/animal/bigcat/* could be some other
group?
Your other options are:
http://plone.org/products/atvocabularymanager/ which has tree like
vocabularies. This uses content types as terms.
http://pypi.python.org/pypi/collective.taxonomysupport which confuses
me but seems to reuse folders as terms via marker interfaces but then
also combines that with navigation. The problem I see with this
approach is that you can use the same taxonomy for navigation in two
different places in the site.
http://plone.org/products/collective.categorizing - seems to exactly
what you want, just with ATContentTypes.
http://plone.org/products/metanav - more on the navigation side of
things. You create heirachies which are menus (using folders again)
and users submit their content to be included in that menu (term).
There are probably more.
Wouldn't it be a nicer UI to create and edit taxonomies in the control
panel and then create a UI on top of that for assigning editing rights
to parts of a taxonomy? Perhaps using rules like I've outlined above?
Potentially a lot less clicking around and less confusing than having
your taxonomy and content items mixed together. How would you hide the
taxonomy content items from the public?
Have you thought of upgrading ATVocabularyManager to use dexterity
instead?
\malthe
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers
