Edgewall Software
Modify

Ticket #695 (new enhancement)

Opened 8 years ago

Last modified 16 months ago

Keywords for wiki pages

Reported by: mario at ruggier.org Owned by:
Priority: normal Milestone: next-major-0.1X
Component: wiki system Version: 0.7.1
Severity: critical Keywords: tracobject
Cc: itamarost@…
Release Notes:
API 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

Change History

comment:1 Changed 8 years ago by mario at ruggier.org

  • Severity changed from normal to enhancement

comment:2 Changed 7 years ago by daniel

  • Milestone set to 2.0

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

comment:3 Changed 7 years ago by cboos@…

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 keywords custom 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 wiki table)
  • ...one could even consider that the keywords field is so important that it should be attached to any Trac object (adding it to the trac_object table)

comment:4 Changed 7 years ago by cboos

  • Milestone 2.0 deleted
  • Owner changed from jonas to cboos
  • Status changed from new to assigned

comment:5 Changed 6 years ago by cboos

  • Keywords object added

comment:6 Changed 6 years ago by cboos

  • Keywords tracobject added; object removed

comment:7 Changed 6 years ago by anonymous

Leaving the porn spam in the DB doesn't reflect well on the trac developer's care and loving of their DB... :)

comment:8 Changed 5 years ago by sid

You can also try the TagsPlugin to do part of this.

comment:9 in reply to: ↑ description Changed 5 years ago by cboos

  • Milestone set to 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 Changed 5 years ago by cboos

  • Owner cboos deleted
  • Status changed from assigned to new

(not currently working on that besides brainstorming...)

comment:11 Changed 22 months ago by cboos

  • Milestone changed from 1.0 to unscheduled

Milestone 1.0 deleted

comment:12 Changed 20 months ago by cboos

  • Milestone changed from triaging to next-major-0.1X
  • Severity changed from normal to critical

comment:13 Changed 16 months ago by itamaro

  • Cc itamarost@… added
View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will be changed from (none). Next status will be 'new'
The owner will be changed from (none) to anonymous. Next status will be 'assigned'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.