eZ Community » Forums » Suggestions » Little big ehancement for keywords...
expandshrink

Little big ehancement for keywords datatype

Little big ehancement for keywords datatype

Monday 17 December 2007 8:43:10 pm - 4 replies

Here's a little enhancement suggestion for keywords datatype, that in my opinion would make a big difference in its functionality and usability:
http://ryba.ez-publish.net/index....l_relation_key_for_keywords_datatype

I have already submitted this as an enhancement proposition:
http://issues.ez.no/IssueView.php?Id=12275&activeItem=1

Hope more people like this idea,
Piotrek

Tuesday 18 December 2007 12:51:05 am

hi,

why don't you use the multiple relation option (started with enhanced object relation, not sure about the name of the attribute, but you can create several with a list of related object to check from)

Tuesday 18 December 2007 5:53:22 am

Hello Xavier,

Could you please provide any more details? I don't exactly see what you're proposing.

Naturally, object relations are very handy in various situations. But the key advantage of keywords attribute that I see is that it is lightweight, stored in a model that is very easy to perform operations on (fetching, conditioning). It is also very easy to manage actually: when it comes to few simple tag words, any interface other than coma separated text would be bothering in my opinion.

Anyways, I'd be grateful for any more details.
Thanks.

Wednesday 19 December 2007 1:28:27 am

Hi,

You have the same fetching tools on related objects as you have on keywords, isn't it ?

As for the input form (comma separated), my users are "creative' enough so I can be sure that any of them won't choose the same keyword but a slightly different one (typo included)

I've had better success with a check box list, but YMMV.

X+

Wednesday 19 December 2007 9:51:04 am

Xavier,

<i>You have the same fetching tools on related objects as you have on keywords, isn't it ?</i>
When it comes to core eZ API - yes. But if you want to operate on data directly (even if just for reads) than keywords seem much more efficient. However, I haven't studied the object relations' database architecture yet, it might be that I'm wrong. I'll try to confirm that soon.

<i>As for the input form (comma separated), my users are "creative' enough so I can be sure that any of them won't choose the same keyword but a slightly different one (typo included)</i>
I believe this is another important issue that you touched, but not necessarily directly related one. If you want to force quality check, than object relations would be a much better choice, but then it would be a closed system (unless I don't see something). On the other hand, as you say - keywords are very risky to be given away to public because of problem you described. But they do great when it comes to a system with content quality enforced outside of eZ Publish.

And I believe they could do much better with additional key blunk.gif Emoticon

Piotrek

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from