[TYPO3-ect] Global categories startup

steve ryan stever at syntithenai.com
Wed Sep 13 01:33:40 CEST 2006


An afterthought is that the biggest downside to using the pid field is 
that is single selection only. It's not like you can hack the meta data 
without consequence either.
Possible to create an additional multiselect to pages but that kills one 
of the big advantages - it's already there. Possibly hack metadata on 
one of the exclude fields across all the categorised tables if you need 
to......hmmm ughh
Retrofitting existing tables to a category source with MM including 
table name as a field or MM per categorised table is better design and 
performance that the old comma seperated list anyways.
Nice would be a kickstarter option alongside enable fields.

I think that implementing standards like RDF resource tags is a 
rendering function derived from many layers of your custom data model 
including categorisation, table and field meta data, ....... Certainly 
something could be built that works with the existing 'standard' tables 
page, content, news etc, recursing objects to combine custom and 
globally categorised(possibly page based) summary information for the 
RDF output.
Without looking deeply, it appears that OWL provides for the schema for 
any sane categorisation scheme to be included in the RDF if you are keen.

Other thoughts - ownership of categories. Implemented using pages, the 
backend users have a complete permissions setup for access to 
'categories'. Front end, cruser_id could be stretched through groups to 
limit access to groups.

DAM integration..... my impression is that DAM is about managing file 
resources?????  Categorisation of file resources according to customised 
or global categories is the same as for any other table.

Tags clouds are just a style of form rendering for categorisation.


Stever

Elmar Hinz wrote:
> steve ryan wrote:
> 
>>Hey Elmar,
>> I'm with Ernesto, pages are a pretty good category tree.
>>Advantages ->
>>* The backend page tree is a no work visual category editor. It also
>>very intuitive for record editing by being similar to a file manager.
>>* Every table has a foreign key reference available for this 'category'
>>* Many extensions work with the idea of rendering the records on the
>>current page.
>>
>>I have recently finished a typo3 portal using a dozen record types that
>>used pages as the global category/subcategory. Worked well.
>>
>>I'm not sure it's viable or appropriate to ask extension developers to
>>follow a standard of including any other specified db reln field for
>>categorisation????
>>
>>Thanks for all the good work you do by inciting conversation.
>>
>>cheers
>>
>>Stever
>>
> 
> 
> Hey Steve,
> 
> 
> I have found the old posting of Ernesto, that you are referring to.
> Currently I gather all information I can find.
> 
> * the graytree from Franz Holzinger
> * the pagetree proposal of Ernesto
> * the OWL matters
> * the tag clouds
> 
> I try to workout a concept, to see how far it is possible to bring all
> this ideas into one.
> 
> Regards
> 
> Elmar
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 



More information about the TYPO3-team-extension-coordination mailing list