List of User Defined Keywords

[armsys]

How to produce (export) a complete list of User Defined Keywords?

[kinook]

Using SQLite

SELECT * FROM UserKeyword ORDER BY 1;

http://www.kinook.com/Forum/showthre...?threadid=2825

See http://www.sqlite.org/sqlite.html for changing the output format and writing results to a file.

[armsys]

Kinook,
Thanks for your rapid reply. Insired by ashwken's database design, I believe exposing the User-Defined Keyword (UDK) in UR is a needed feature. UDK is the only visible zone in UR allowing users to exert control over the classification/categorization of Info Items. To enhance the robustness and clarity of the UR database design, a well-documented list of UDK produced within UR is indispensable. Furthermore, the systemmatic exploitation of the UDK will boost the efficiency and quality of the intelligence generated by UR's Search. Just my two cents.

Armstrong

[kinook]

What exactly do you mean by "well-documented list"? You can include the Keywords (user-defined) attribute when exporting items to CSV and XML formats. We're also exposing that attribute for display in the Related Items and Item Attributes panes in the next version.

[armsys]

By well-documented list, I mean a list of UDKs together with respective detailed narration/definition to eliminate any potential confusion and/or misrepresentation.

As of today, the UDK is only assigned to each Info Item, whereby the UDK is exposed together with other attributes.

My prayer is an a la carte list of UDKs for a urd. Each UDK such as Rabbit's Foot embraces totally different meaning to different UR users. Therefore, a well-documented list of UDK is essential.

Armstrong

[kinook]

It's still not clear to me exactly what you're asking for. You want to associate a description with each user-defined keyword? Why not just make the keyword long enough to describe itself?

[armsys]

Originally posted by kinook
You want to associate a description with each user-defined keyword?

Yes.

Originally posted by kinook
Why not just make the keyword long enough to describe itself?

I can appreciate your point, namely, making UDK self-evident.
On the other hand, for example, TI could stand for Technical Issues, Technical Instititue, and Texas Instruments. When managing thousands of Info Items with the same UDK, abbreviations such as TI mentioned above will be preferred. That's the main reason for a UDK list or table.

Armstrong