Re: [Trac] TagsPlugin questions

[Steffen Hoffmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07.01.2013 19:11, Oblio wrote:
> Ok, so I just put TagsPlugin on my Trac v1 + Postgres installation, and
> I have some questions.
>
> First, since I already have quite a few tickets in my system and it the
> users were not using the "keywords" field with the expectation that it
> would be picked up by Tags. They happily used spaces in the
> construction of their data. So, my initial question is: can I configure
> TP to use commas instead of spaces for tag delimiters? I know that it
> used to, but I think it would make more sense for my use. If not, is
> there a way to skip ticket/keyword scanning?
No need for a special configuration. Comma-separated keywords should
work just fine out-of-the-box.

Depending on how many tickets are "many", and on what Trac db backend
you use, you may experience an suddenly increase of request processing
time on all ticket pages. This is due to uncached implementation of the
tags provider for ticket and a known performance issue [1], that is
currently worked on.

You may even see some related source changes in `trunk` development
branch soon, and I invite you to take part in this development by
testing and reporting back your findings as soon as the code is
available. You'll want to track changes of the corresponding ticket more
closely then. This requires only your username, if you're registered to
trac-hacks.org, or a valid email address. But I've to warn you, that
email addresses are only obfuscated in the usual manner after
trac-hacks.org has been upgraded itself to a more recent Trac version [2].

Thanks in advance for taking care to ask, and maybe provide even more
valuable feedback in the future.

Sincerely,

Steffen Hoffmann


[1] http://trac-hacks.org/ticket/4503
[2] http://trac-hacks.org/wiki/SiteUpgradeProposal
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlDrUkwACgkQ31DJeiZFuHelIQCgkSwIqb0PEQznFlmR/aowSoVI
n4wAoJL651LEsO6m3uN6mSIuMuG04ihT
=pWQO
-----END PGP SIGNATURE-----

[Oblio Leitch]

Ok, so TP uses both space and tab delimiters?  Is there a way to turn off space delimiting?

[RjOllos]

On Tuesday, January 8, 2013 5:22:17 AM UTC-8, Oblio wrote:

Ok, so TP uses both space and tab delimiters?  Is there a way to turn off space delimiting?

You can effectively accomplish that (for browsers with JavaScript enabled) using the KeywordSuggestPlugin:

http://trac-hacks.org/wiki/KeywordSuggestPlugin 

Make sure to set the multipleseparator configuration option. I haven't received any feedback on recent changes made to the plugin, so please let me know how it's working for you if you are able to test.

[RjOllos]

On Tuesday, January 8, 2013 5:22:17 AM UTC-8, Oblio wrote:

Ok, so TP uses both space and tab delimiters?  Is there a way to turn off space delimiting?

I may have misread this. KeywordSuggestPlugin will force the separator to be a specific character, but I don't think there is way to force TagsPlugin to treat a space-separated phrase such as "some tag" as a single tag.

[Steffen Hoffmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

No way, indeed. Calling it intentional or a defect doesn't matter here.

Personally I feel that "this tag" always comprises two tags, while only
something like "this_tag" must be considered as one. And TagsPlugin is
working exactly that way right now.

But you may still provide more insight into you specific use case here
to possibly make me/us start to think different.

Steffen Hoffmann

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlDt8QgACgkQ31DJeiZFuHcauQCdHjYTtp2rqThulBhehXHjzm3o
vyYAnjvPL3AeUWnYeHqATg0zW2aW8ywY
=8t4/
-----END PGP SIGNATURE-----

[Oblio Leitch]

Well, in my [use] case, I'm applying the plugin to a very active ticket system - there are already thousands of tickets. When I apply TagPlugin, the cloud that's created has lots of useless tags being generated by the keywords field in the existing tickets.  Tags like "-", "&", "7", "I", etc.  Yes, the keywords field shouldn't be used as a description field (eg "Defect: P & I Calc Date (Dormant)"), however, going through and changing all the keywords would be time consuming.  It would be helpful to simply change the delimiter to a comma.

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.

To post to this group, send email to trac-...@googlegroups.com.
To unsubscribe from this group, send email to trac-users+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

[Steffen Hoffmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10.01.2013 13:40, Oblio Leitch wrote:

> On Wed, Jan 9, 2013 at 5:36 PM, Steffen Hoffmann wrote:
>> On 09.01.2013 22:20, RjOllos wrote:
>>> On Tuesday, January 8, 2013 5:22:17 AM UTC-8, Oblio wrote:
>>>> Ok, so TP uses both space and tab delimiters? Is there a way to
>>>> turn off space delimiting?
>>> I may have misread this. KeywordSuggestPlugin will force the separator
>>> to be a specific character, but I don't think there is way to force
>>> TagsPlugin to treat a space-separated phrase such as "some tag" as a
>>> single tag.
>> No way, indeed. Calling it intentional or a defect doesn't matter here.
>>
>> Personally I feel that "this tag" always comprises two tags, while only
>> something like "this_tag" must be considered as one. And TagsPlugin is
>> working exactly that way right now.
>>
>> But you may still provide more insight into you specific use case here
>> to possibly make me/us start to think different.

> Well, in my [use] case, I'm applying the plugin to a very active
> ticket system - there are already thousands of tickets. When I apply
> TagPlugin, the cloud that's created has lots of useless tags being
> generated by the keywords field in the existing tickets.
> Tags like "-", "&", "7", "I", etc.
> Yes, the keywords field shouldn't be used as a description field
> (eg "Defect: P & I Calc Date (Dormant)"), however, going through and
> changing all the keywords would be time consuming.
> It would be helpful to simply change the delimiter to a comma.

See an existing development ticket for TagsPlugin [1], and consider
following-up if needed.

Steffen Hoffmann


[1] http://trac-hacks.org/ticket/9692

PS: I'd be delighted to not see more top-postings here. I makes comments
and follow-ups exceptionally painful too. Thanks in advance for taking care.

- --
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlDvPDEACgkQ31DJeiZFuHfUkQCgwJQFEq9FaOpsEd9cMwzZMZhz
NTwAn3+9fTN44qDXf/OGqsm8eEiDNK2c
=86HG
-----END PGP SIGNATURE-----