Object Classification

Next topic

Author	Message
David Heath	Thursday 10 April 2003 9:32:12 am Hi, I'm currently evaluating eZpublish 3 for an application. One of the requirements of the application is to allow classification of articles by a number of fields, for example specifying the topic and country which the article is about. This should be available to the editor as a multiple-choice select box when they create the article. How could this be implemented in eZ 3? Is there some standard mechanism for classification? If not, what would be the best way to implement it? Should I create a new content class for each classfication type (e.g. country, topic) and then have the article object refer to the classification objects. Would I need to write some special code to present the user interface in the desired manner? If so, where should I find out more about customising that article user interface? Many thanks David Heath
Peter Bailey	Thursday 10 April 2003 11:17:46 am Any given content object can exists in multiple locations. You can have a folder for each classification, and include the article in to any folder that applies. Would that work? (there may be another way, I'm no eZp whiz)
Jan Borsodi	Friday 11 April 2003 6:03:14 am You can use regular objects for classifications, for instance you could create a topic and country class which holds the information on each type. You then create a folder for topics and countries and place objects in them. For editing objects you use something called remote IDs for placements, this means that for a specific remote ID a placement node ID is stored. Practically this means that you could display a dropdown with values taken from the topic or country list and let the user choose one of them. When the object is published it will be placed in the selected nodes. The only thing you need to do for this is an override template for the classes that require classification. See design/standard/template/content/edit_placement.tpl for an example of this, there's some commented code at the top. -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq

Author

Message

Thursday 10 April 2003 9:32:12 am

Hi,

I'm currently evaluating eZpublish 3 for an application. One of the requirements of the application is to allow classification of articles by a number of fields, for example specifying the topic and country which the article is about.

This should be available to the editor as a multiple-choice select box when they create the article.

How could this be implemented in eZ 3? Is there some standard mechanism for classification?

If not, what would be the best way to implement it? Should I create a new content class for each classfication type (e.g. country, topic) and then have the article object refer to the classification objects.

Would I need to write some special code to present the user interface in the desired manner? If so, where should I find out more about customising that article user interface?

Many thanks

David Heath

Peter Bailey

Thursday 10 April 2003 11:17:46 am

Any given content object can exists in multiple locations. You can have a folder for each classification, and include the article in to any folder that applies.

Would that work?

(there may be another way, I'm no eZp whiz)

Jan Borsodi

Friday 11 April 2003 6:03:14 am

You can use regular objects for classifications, for instance you could create a topic and country class which holds the information on each type. You then create a folder for topics and countries and place objects in them.

For editing objects you use something called remote IDs for placements, this means that for a specific remote ID a placement node ID is stored. Practically this means that you could display a dropdown with values taken from the topic or country list and let the user choose one of them.
When the object is published it will be placed in the selected nodes.

The only thing you need to do for this is an override template for the classes that require classification. See design/standard/template/content/edit_placement.tpl for an example of this, there's some commented code at the top.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

eZ debug

Timing:	Jan 18 2025 05:00:10
Script start
Timing:	Jan 18 2025 05:00:10
Module start 'layout'
Timing:	Jan 18 2025 05:00:10
Module start 'content'
Timing:	Jan 18 2025 05:00:10
Module end 'content'
Timing:	Jan 18 2025 05:00:10
Script end

Main resources:

Total runtime	0.0207 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0064	587.8906	152.6094
Module start 'layout'	0.0064	0.0045	740.5000	39.4141
Module start 'content'	0.0108	0.0071	779.9141	89.3047
Module end 'content'	0.0179	0.0028	869.2188	34.3047
Script end	0.0207		903.5234

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	13.1662	14	0.0002
Check MTime	0.0012	5.6453	14	0.0001
Mysql Total
Database connection	0.0015	7.2543	1	0.0015
Mysqli_queries	0.0036	17.1369	3	0.0012
Looping result	0.0000	0.0770	1	0.0000
Template Total	0.0021	10.0	1	0.0021
Template load	0.0009	4.3627	1	0.0009
Template processing	0.0012	5.6062	1	0.0012
Override
Cache load	0.0006	3.0904	1	0.0006
General
dbfile	0.0003	1.2481	8	0.0000
String conversion	0.0000	0.0483	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs