Modify

Opened 9 years ago

Last modified 8 years ago

#12111 new enhancement

Null/Untagged Content

Reported by: jabrault@… Owned by:
Priority: normal Component: TagsPlugin
Severity: normal Keywords: null untagged
Cc: Trac Release: 1.0

Description

We have the Tags plugin implemented with our Trac instance and have implemented a tag-based documentation page. Several people are creating new wiki articles daily, and some are forgetting to add tags. To be able to more easily track these pages down, I was wondering if there is any syntax for pulling out wiki pages that are not tagged (i.e. NULL). I have heard that there is no feature to be able to accomplish this. A syntax that I tested to see if this feature existed is below:

[[ListTagged(realm:wiki `NULL`)]]

I picture this similar to the searching of tickets from the "view tickets" tab. For example, owner = username AND keywords = fieldleftblank. to be able to find were that particular user didn't add keywords.

Attachments (0)

Change History (7)

comment:1 Changed 9 years ago by Steffen Hoffmann

Thanks for your request. As discussed before ListTagged cannot list un-tagged resources, and any other part of current TagsPlugin is similar. It works with tagged content, and leaves the rest alone.

Before developing new functionality inside the plugin I ask you, if custom TracReports dedicated to "untagged content" would do it too?

comment:2 Changed 9 years ago by Jason

It looks like we are utilizing TracReports for active and closed tickets per user. That seems like it could be a valid way of reporting on untagged wiki pages. Do you have any example syntax for what that might look like?

comment:3 Changed 9 years ago by Steffen Hoffmann

Just created and tested this one:

Untagged wiki pages by name

SELECT DISTINCT name FROM wiki
WHERE name NOT IN (
    SELECT DISTINCT name FROM tags
    WHERE tagspace='wiki'
)
ORDER BY name
Last edited 9 years ago by Steffen Hoffmann (previous) (diff)

comment:4 Changed 9 years ago by Ryan J Ollos

While I share the thought that the functionality may not be needed for TagsPlugin, you can imagine how easy it would be to write a custom macro for the reporter's Trac installation that utilizes the comment:3 SQL.

comment:5 in reply to:  4 Changed 9 years ago by Steffen Hoffmann

Replying to rjollos:

While I share the thought that the functionality may not be needed for TagsPlugin, you can imagine how easy it would be to write a custom macro for the reporter's Trac installation that utilizes the comment:3 SQL.

Sure, but making a plugin is yet on a different level, if he's not even going the TracReports way.

comment:6 Changed 9 years ago by Ryan J Ollos

See also #12530.

comment:7 Changed 8 years ago by Ryan J Ollos

Owner: Steffen Hoffmann deleted

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.

Add Comment


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

 
Note: See TracTickets for help on using tickets.