#83
- Created on2005-07-13 23:50
- Reported by
- StatusMigrated
- PriorityNormal (3)
- Assigned to
- Milestone
- Plan Level-
- Due Date-
Ideas for better context selection
When I create a project, I'd like to pick a default context to use for its next actions. My "update online portfolio" project is all computer context, for example.
I'd love for Tracks to make intelligent guesses about the proper context for actions. Don't most next actions begin with a verb? The guesser could assume that actions are worded "[verb] [direct object] [prepositions] [indirect object]". When a verb keyword is matched, it triggers the appropriate context. The user should be able to define verb-context pairs. E.g.:
What do you think?
I'd love for Tracks to make intelligent guesses about the proper context for actions. Don't most next actions begin with a verb? The guesser could assume that actions are worded "[verb] [direct object] [prepositions] [indirect object]". When a verb keyword is matched, it triggers the appropriate context. The user should be able to define verb-context pairs. E.g.:
- Items beginning with "call" or "phone" trigger the calls context, such as "call Johnson about lack of TPS reports."
- Ditto for "email".
- Words like "buy", "fetch", and "drop off" trigger the errands context.
- Because Kelly's hobby is woodworking, she has created a woodshop context, and defined its trigger verbs as "build", "saw", and "varnish".
What do you think?
Leave a comment
on 2005-07-17 06:42 *
By Anonymous
Status changed from New to Accepted
Status changed from New to Accepted
It's a great idea. Adding an option to set a default context on a per-project basis would be easy, and a nice feature. The 'guessing' feature you've suggested would be really cool, but I think it would be really difficult to implement because of the possible scope of keywords. Still, it would be really nice, so I'll give it some thought.
The guesser must be fed keyword-context pairs by the user before it's any use. You could include sample keywords to go with the other sample content if you wanted to.
I figured that its first, imperfect implementation would consist of checking the next action's first word, and if it matched a keyword, would be assigned to the appropriate context. Getting better from there is great, but even that little could be a big help.
I can't code, but if I were tackling the guesser, I'd start by finding any open-source grammar checkers, and seeing how they decide what the verb is, since most of the keywords I've come up with are verbs.
I figured that its first, imperfect implementation would consist of checking the next action's first word, and if it matched a keyword, would be assigned to the appropriate context. Getting better from there is great, but even that little could be a big help.
I can't code, but if I were tackling the guesser, I'd start by finding any open-source grammar checkers, and seeing how they decide what the verb is, since most of the keywords I've come up with are verbs.
Migrated to GitHub issue #1550