The following improvements are available in the keywords management in version 2.0:

The 'id' attribute in the exported keywords.

When exporting the 'keywords' attribute of a GN4 object (for example, of a gn4:article), the resulting xml contains the id of the gn_KeywordsTable system table with the 'kwd' prefix.

For example:

<keywords>

  <item id="kwd14295">keyword 1</item>

  <item id="kwd3123">another keyword</item>

  <item id="kwd53277">main key word</item>    

</keywords>

'Create Keywords' privilege

In the GN4 schema (GN4Fixed.xsd) we added a new user/group privilege, called 'Create Keywords', which allows to users to create/delete keywords.

If the user has not this new privilege, he cannot create/delete/rename the keywords, but he can add the existing keywords to GN4 objects (both the keywords stored into the database and the ones suggested by Exalead).

To distinguish between the new keywords and the Exalead suggestions, the GN4 client applications add the 'suggested' flag attribute to the keywords.item tag (true means 'suggested by Exalead').

For example:

<article id="objxxxx" xmlns="urn:schemas-teradp-com:gn4tera">

  <keywords>

    <item suggested="true">new key</item>

  </keywords>

</article>

If the 'suggested' attribute is true, then the 'Create Keywords Creation' permission is ignored and the new keyword value is imported.

The 'cmd4 keywords' command, the Keywords WebPart in GNPortal and the UI keywords controls (both in clients and in portal) checks this new privilege.

Important: after updated the database, please check that this new privilege is selected for the 'Administrators' group of your GN4 system and for all other groups and users who need to create or delete keywords.

However, in the new GN4 installations, the standard 'Administrators' group is already created with this new privilege.

'accentInsensitive' flag for the 'keywordSet' object

We added to the GN4 schema (GN4Base.xsd) a new flag attribute, called 'accentInsensitive', to the 'keywordSet' GN4 object.

If this new attribute is set to true, then the UI keywords controls ignore the accents when showing the autocomplete suggestions, both in clients and in portal.