Opened 21 years ago
Last modified 4 years ago
#695 new enhancement
Keywords for wiki pages
| Reported by: | mario at ruggier.org | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | next-major-releases |
| Component: | wiki system | Version: | 0.7.1 |
| Severity: | major | Keywords: | tracobject |
| Cc: | itamarost@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
It would be nice to see a keywords field for wiki pages, same as the one for tickets. This list of manually chosen keywords can serve multiple purposes:
- for searching and ranking, grouping, …
- to automatically generate the "See also" list of links at the bottom of a page, listing all other pages that share 1 or more of the keywords. Currently this seems to be done manually, so if a wiki page changes such that it should not be related anymore, then one would have to hunt down and change all other pages that "See also" to it.
Attachments (0)
Change History (14)
comment:1 by , 21 years ago
| Severity: | normal → enhancement |
|---|
comment:2 by , 21 years ago
| Milestone: | → 2.0 |
|---|
comment:3 by , 21 years ago
In the TracObjectModelProposal,
the specific object fields and custom fields management
logic would be promoted from the Ticket module
to the generic Module.
Implementation of #695 in this model could be done
in several ways, depending what the consensus says
about a keywords field:
- if it is generally seen as being not that important,
a trac administrator could nevertheless add that
field very easily for his own trac environment
by creating a
keywordscustom field for Wiki objects - if it is seen as a good idea for the wiki pages
in general, the field could be made a specific field
of the Wiki object (adding it to the
wikitable) - …one could even consider that the
keywordsfield is so important that it should be attached to any Trac object (adding it to thetrac_objecttable)
comment:4 by , 20 years ago
| Milestone: | 2.0 |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
comment:5 by , 20 years ago
| Keywords: | object added |
|---|
comment:6 by , 20 years ago
| Keywords: | tracobject added; object removed |
|---|
comment:7 by , 20 years ago
Leaving the porn spam in the DB doesn't reflect well on the trac developer's care and loving of their DB… :)
comment:9 by , 19 years ago
| Milestone: | → 1.0 |
|---|
Replying to mario at ruggier.org:
… to automatically generate the "See also" list of links at the bottom of a page, listing all other pages that share 1 or more of the keywords.
This could probably be done by a generalization of the TicketQuery macro, although that wouldn't be trivial: it should be the union of matches for each of the existing keywords. We probably need a query language for that, maybe derived from Python expression like Genshi does?
{{{
#!query
distinct(x for x in resources('wiki:*') for k in self.keywords if k in x.keywords)
}}}
comment:10 by , 19 years ago
| Owner: | removed |
|---|---|
| Status: | assigned → new |
(not currently working on that besides brainstorming…)
comment:12 by , 15 years ago
| Milestone: | triaging → next-major-0.1X |
|---|---|
| Severity: | normal → critical |
comment:13 by , 15 years ago
| Cc: | added |
|---|



It's a neat idea though… every 'resource' in trac (2.0+) could be 'taggable/keywordable' a'la del.icio.us … that'd be pretty cool