Ticket #2296 (closed defect: fixed)

Opened 9 years ago

Last modified 9 years ago

Keywords metadata should be indexed too

Reported by: madarche Owned by: madarche
Priority: P2 Milestone: CPS 3.5.2
Component: CPS (global) Version: 3.5.1
Severity: normal Keywords:
Cc:

Description

Keywords metadata, introduced in #495 for SEO, should be indexed too, so that internal search on those keywords could return the matching documents to the user doing the search.

Having the keywords not indexed confuses users.

Change History

comment:1 Changed 9 years ago by madarche

  • Status changed from new to assigned
  • Owner changed from gracinet to madarche
  • Milestone changed from CPS 3.5.3 to CPS 3.5.2

comment:2 Changed 9 years ago by madarche

  • Status changed from assigned to closed
  • Resolution set to fixed

Fix pushed.

comment:3 Changed 9 years ago by gracinet

  • Status changed from closed to reopened
  • Resolution fixed deleted

There's a big shortcoming: in case that voc is i18n, then the users would expect the localized version of the "msg" instead of the key to be indexed. And this must be done wrt to document language, not necessarily current users'.

This is of course a much wider problem : fields are not supposed to know wether they are used for vocabulary values. How to avoid duplication of the reference to the vocabulary then ? Will we be forced to create a CPS Vocabulary Key Field, which has been avoided so far ? And of course the l10n itself should be done in CPSCore.

Feel free to create another ticket for that and close this one again.

Other examples of similar problems : in CSV directory exports (had the caller pass the titles), in CPSCollector exports (not CPSSchemas based yet). In short : in anything meant for the end user that does not go through the normal UI (layouts, widgets).

comment:4 Changed 9 years ago by madarche

  • Status changed from reopened to closed
  • Resolution set to fixed

No, this is about Keywords metadata, and not Subjects metadata. Keywords are not to be translated.

Note: See TracTickets for help on using tickets.