taxonomy structure

Previous topic

Setup & design

Next topic

Author	Message
nicholas hemley	Tuesday 27 November 2007 7:59:19 am Hello, is it possible to associate content with a taxonomy structure, please? i.e. can it be categorised in any way? Cheerio, Nic Hemley
Paul Leclercq	Tuesday 27 November 2007 3:39:32 pm Personnally, I don't know of anypre built taxonomy algorithms, But it must be possible to build one by using external scripts or by building your own. Ezpublish should be pretty well fit for the creation of taxonomy algorithms since you can use the native node system to classify your species in a parent/child systems, by creating specifique classes. A good of classified infrmation as a tree is the administration interface content navigation menu: which can be enhanced by using the ajax version: http://ez.no/tw/developer/contribs/hacks/dynamic_content_stucture_menu_ajax Although it is probably possible to build one in a more optimised and quick version by using creating more advanced extensions specifically for classifiying and fetching the tree of your species. Here is a guide on how to create an operator which can be used for exemple to fetch your data: http://ez.no/ezpublish/documentation/development/extensions/template_operator Or to create a full view, which could include more advanced or external scripts: http://ez.no/ezpublish/documentation/development/extensions/building_an_ez_publish_module
Xavier Dutoit	Wednesday 28 November 2007 12:58:14 am Hi, You can either represent "tags" as additional location (a contrib by Damien I think allows to do that easily). or use the related objects (that's what I usually do). As of the 3.9, the related objects attributes offers check box lists to let you choose one or several tags. X+ http://www.sydesy.com

Author

Message

nicholas hemley

Tuesday 27 November 2007 7:59:19 am

Hello,

is it possible to associate content with a taxonomy structure, please? i.e. can it be categorised in any way?

Cheerio,
Nic Hemley

Paul Leclercq

Tuesday 27 November 2007 3:39:32 pm

Personnally, I don't know of anypre built taxonomy algorithms, But it must be possible to build one by using external scripts or by building your own.

Ezpublish should be pretty well fit for the creation of taxonomy algorithms since you can use the native node system to classify your species in a parent/child systems, by creating specifique classes. A good of classified infrmation as a tree is the administration interface content navigation menu:

which can be enhanced by using the ajax version:
http://ez.no/tw/developer/contribs/hacks/dynamic_content_stucture_menu_ajax

Although it is probably possible to build one in a more optimised and quick version by using creating more advanced extensions specifically for classifiying and fetching the tree of your species.

Here is a guide on how to create an operator which can be used for exemple to fetch your data:
http://ez.no/ezpublish/documentation/development/extensions/template_operator

Or to create a full view, which could include more advanced or external scripts:
http://ez.no/ezpublish/documentation/development/extensions/building_an_ez_publish_module

Xavier Dutoit

Wednesday 28 November 2007 12:58:14 am

Hi,

You can either represent "tags" as additional location (a contrib by Damien I think allows to do that easily).

or use the related objects (that's what I usually do). As of the 3.9, the related objects attributes offers check box lists to let you choose one or several tags.

X+

http://www.sydesy.com

eZ debug

Timing:	Jan 18 2025 18:35:26
Script start
Timing:	Jan 18 2025 18:35:26
Module start 'layout'
Timing:	Jan 18 2025 18:35:26
Module start 'content'
Timing:	Jan 18 2025 18:35:27
Module end 'content'
Timing:	Jan 18 2025 18:35:27
Script end

Main resources:

Total runtime	1.0944 sec
Peak memory usage	4,096.0000 KB
Database Queries	59

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0057	587.8906	152.6094
Module start 'layout'	0.0057	0.0030	740.5000	39.4141
Module start 'content'	0.0086	1.0845	779.9141	574.6641
Module end 'content'	1.0931	0.0012	1,354.5781	12.1875
Script end	1.0943		1,366.7656

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0034	0.3077	16	0.0002
Check MTime	0.0014	0.1296	16	0.0001
Mysql Total
Database connection	0.0007	0.0652	1	0.0007
Mysqli_queries	1.0403	95.0555	59	0.0176
Looping result	0.0014	0.1282	57	0.0000
Template Total	1.0598	96.8	2	0.5299
Template load	0.0021	0.1944	2	0.0011
Template processing	1.0577	96.6501	2	0.5289
Template load and register function	0.0003	0.0229	1	0.0003
states
state_id_array	0.0019	0.1774	1	0.0019
state_identifier_array	0.0015	0.1330	2	0.0007
Override
Cache load	0.0018	0.1630	25	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0004	0.0380	3	0.0001
Fetch class attribute name	0.0010	0.0897	5	0.0002
XML
Image XML parsing	0.0010	0.0942	3	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0011	5	0.0000
General
dbfile	0.0008	0.0728	21	0.0000
String conversion	0.0000	0.0006	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
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
7	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
4	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
2	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 18 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs