Caution: This documentation is for eZ Publish legacy, from version 3.x to 5.x.
For 5.x documentation covering Platform see eZ Documentation Center, for difference between legacy and Platform see 5.x Architecture overview.

Keywords

Summary

Stores keywords.

Properties

NameInternal nameSearchableInformation collector
Keywords keywords Yes. No.

Description

This datatype allows the storage of keywords for an object. The keywords must be specified as a comma separated list of words and/or phrases. This datatype can be used to connect objects of the same type based on their keywords. It is typically useful when it comes to creating interfaces that allow the user to quickly browse other pages with related content (for example "see also" or "related pages" list of hyperlinks). If two objects share at least one common keyword, the objects will be connected behind the scenes. The system will create the necessary entries in the "ezkeyword" and the "ezkeyword_attribute_link" database tables. Please note that this datatype does not generate object relations, it simply uses its own tables in the database to connect the objects. The following screenshot shows the class attribute edit interface for this datatype.

Class attribute edit interface for the "Keywords" datatype.

Class attribute edit interface for the "Keywords" datatype.

Object attribute edit interface

The following screenshot shows the object attribute edit interface for this datatype.

Object attribute edit interface for the "Keywords" datatype.

Object attribute edit interface for the "Keywords" datatype.

Raw output

The ".content" of an ezcontentobjectattribute object using this datatype returns an ezkeyword object.

Balazs Halasy (21/02/2005 2:39 pm)

Balazs Halasy (09/03/2006 8:47 am)


Comments

  • Keywords configuration

    It would be extremely convenient to have the ability to configure basic keyword parameters, such as amount of keywords per attribute (for example 10, the rest being cut off) and maximum length of a single keyword (for example 50 characters). Even global declaration would be great, even though per class configuration would be outstanding.

    Otherwise it is a bit risky to allow public access to edit attributes based on this datatype...
    • Re: Keywords configuration

      Hi, please use http://issues.ez.no for such requests (you can post an enhancement there). The comment system is not the right place for this. Thanks!