comparison doc/overview.txt @ 3904:91008ec8f9a0

retire "topic" usage "Topic" still appears in the locale files. I'm sure we need to support that for existing trackers. I *think* they don't care about any of the other changes that have been made. I also left Ka-Ping Yee's original design document unchanged. This takes care of sf feature request [SF#953161]
author Justus Pendleton <jpend@users.sourceforge.net>
date Sun, 16 Sep 2007 02:45:11 +0000
parents 284c26c1ef19
children e6073c2291c6
comparison
equal deleted inserted replaced
3903:a90fa2e08a0a 3904:91008ec8f9a0
145 asked to select exactly one of a number of categories 145 asked to select exactly one of a number of categories
146 or to fit it into a rigid hierarchy. Yet things 146 or to fit it into a rigid hierarchy. Yet things
147 only sometimes fall into one category; often, 147 only sometimes fall into one category; often,
148 a piece of information may be related to several concepts. 148 a piece of information may be related to several concepts.
149 149
150 For example, forcing each item into a single topic 150 For example, forcing each item into a single keyword
151 category is not just suboptimal but counterproductive: 151 category is not just suboptimal but counterproductive:
152 seekers of that 152 seekers of that
153 item may expect to find it in a different category 153 item may expect to find it in a different category
154 and conclude that the item is not present in the 154 and conclude that the item is not present in the
155 database -- which has them *worse* off 155 database -- which has them *worse* off
243 possessing the property to the item representing the chosen option. 243 possessing the property to the item representing the chosen option.
244 244
245 The *multilink* type is for a list of links to any 245 The *multilink* type is for a list of links to any
246 number of other items in the in the database. A *multilink* 246 number of other items in the in the database. A *multilink*
247 property, for example, can be used to refer to related items 247 property, for example, can be used to refer to related items
248 or topic categories relevant to an item. 248 or keyword categories relevant to an item.
249 249
250 For Roundup, all items have four properties that are not customizable: 250 For Roundup, all items have four properties that are not customizable:
251 251
252 1. a *date* property named **creation** 252 1. a *date* property named **creation**
253 2. a *link* property named **creator** 253 2. a *link* property named **creator**
312 # files = Multilink("file") 312 # files = Multilink("file")
313 # nosy = Multilink("user") 313 # nosy = Multilink("user")
314 # superseder = Multilink("issue") 314 # superseder = Multilink("issue")
315 # (it also gets the Class properties creation, activity and creator) 315 # (it also gets the Class properties creation, activity and creator)
316 issue = IssueClass(db, "issue", 316 issue = IssueClass(db, "issue",
317 assignedto=Link("user"), topic=Multilink("keyword"), 317 assignedto=Link("user"), keyword=Multilink("keyword"),
318 priority=Link("priority"), status=Link("status")) 318 priority=Link("priority"), status=Link("status"))
319 319
320 The **assignedto** property assigns 320 The **assignedto** property assigns
321 responsibility for an item to a person or a list of people. 321 responsibility for an item to a person or a list of people.
322 The **topic** property places the 322 The **keyword** property places the
323 item in an arbitrary number of relevant topic sets (see 323 item in an arbitrary number of relevant keyword sets (see
324 the section on `Browsing and Searching`_). 324 the section on `Browsing and Searching`_).
325 325
326 The **prority** and **status** values are initially: 326 The **prority** and **status** values are initially:
327 327
328 =========== ===================================== 328 =========== =====================================
447 out, for they can easily join in, and just as easily 447 out, for they can easily join in, and just as easily
448 look at the mail spool on an item to catch up on any 448 look at the mail spool on an item to catch up on any
449 messages they might have missed. 449 messages they might have missed.
450 450
451 We can take this a step further and 451 We can take this a step further and
452 permit users to monitor particular topics or classifications of items 452 permit users to monitor particular keywords or classifications of items
453 by allowing other kinds of items to also have their own nosy lists. 453 by allowing other kinds of items to also have their own nosy lists.
454 For example, a manager could be on the 454 For example, a manager could be on the
455 nosy list of the priority value item for "critical", or a 455 nosy list of the priority value item for "critical", or a
456 developer could be on the nosy list of the topic value item for "security". 456 developer could be on the nosy list of the keyword value item for "security".
457 The recipients are then determined by the union of the nosy lists on the 457 The recipients are then determined by the union of the nosy lists on the
458 item and all the items it links to. 458 item and all the items it links to.
459 459
460 Using many small, specific mailing lists results 460 Using many small, specific mailing lists results
461 in much more effective communication than one big list. 461 in much more effective communication than one big list.
550 associated with the active options) 550 associated with the active options)
551 - *multilink* properties appear as a group of selectable options 551 - *multilink* properties appear as a group of selectable options
552 (the filter selects the *intersection* of the sets of items 552 (the filter selects the *intersection* of the sets of items
553 associated with the active options) 553 associated with the active options)
554 554
555 For a *multilink* property like **topic**, 555 For a *multilink* property like **keyword**,
556 one possibility is to show, as hyperlinks, the keywords whose 556 one possibility is to show, as hyperlinks, the keywords whose
557 sets have non-empty intersections with the currently displayed set of 557 sets have non-empty intersections with the currently displayed set of
558 items. Sorting the keywords by popularity seems 558 items. Sorting the keywords by popularity seems
559 reasonable. Clicking on a keyword then narrows both the list of items 559 reasonable. Clicking on a keyword then narrows both the list of items
560 and the list of keywords. This gives some of the feel of walking 560 and the list of keywords. This gives some of the feel of walking

Roundup Issue Tracker: http://roundup-tracker.org/