From: Reini U. <ru...@x-...> - 2001-09-17 09:45:24
|
Steve Wainstead schrieb: > This gentleman volunteers to add a ticket tracking system. I dunno. > Thoughts? I'm not really familiar with the term "ticket tracking". I'm currently implementing a big B2B E-Commerce site with session tracking and user-auth, so I probably know the problem and implementation. To me "ticket tracking" seems to be an identification/authentification method for asynchronous communication, mostly by e-mail. A unique tag bound to a user or session. Joe, could you please elaborate what this system should do in more detail? Do you want to add a parsable tag in the HTML code to be able to grep and filter it? Or a page column in the DB? something like: "list all pages where finance == approved", "search in all pages where finance != approved" html: <!-- tag: finance:approve --> or something visible. ticket plugin: filter all multipage queries (search, list, ...) by a user-defined filter. > On Sat, 8 Sep 2001, Joe Edelman wrote: > > Hello. I'm a new person interested in hacking on phpWiki. > > > > I have a bit of an agenda, though: I want to use it as an intranet for a > > non-profit I'm putting together, so I want to add some business/intranet > > features. > > > > The only thing I want to add that's not already on your 1.3 to-do list is a > > ticket tracking system. I'd like to be able to embed tickets in wiki pages, > > using a syntax like "((finance:approve))", and then have them visible from a > > ticket tracking system. This could be seen as an extension of what you're > > already doing with search and "CategoryCategory" tags: a new mechanism for > > letting people list and sort pages by certain criteria. > > > > I'm also interested in and willing to help with user authentication and the > > weblog/templating facility you describe. > > > > It seems like I can do these tickets using this new plugin system that Jeff > > has made, although it needs to be extended in a small way. > > > > I'm not quite sure how to proceed: can I assume that Jeff's changes will > > probably become the HEAD? Should I write a proposal about how I might > > implement these tickets, then, and post it to the mailing list fpr review? -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |