[chandler-users] Is Chandler the Successor to Lotus Agenda?

[Jim Cook]

Please see my responses interleaved below.

At 03:55 PM 3/24/2008, Carl Lemp <carl.lemp at snet.net> wrote:

>To everyone interested in auto-assignment of items:
>It sounds like there are at least a few of us that have been 
>patiently waiting for Chandler to take on some of the capabilities 
>that Agenda had so long ago.  I posted similar questions a few weeks 
>ago and Grant Baillie of OSAF has contacted me about building a 
>plug-in for auto-assignment of items to collections.  If he can 
>point me in the right direction to get started, I'm willing to give 
>it a shot.  Here was his first set of questions:
>
> >So far as person-week estimates go, I guess it depends on which items
> >you want to make auto-assignments on (e.g. the quick entry field?
> >incoming mail? any newly created item?). Can you elaborate on what you
> >had in mind, especially w.r.t. where you would expect to find
> >collection names, and how the synonyms would be set up?
>and my answer:
>Ideally, I'd like all items to be auto-assigned either as they are 
>added or, on demand if there is no easy way to hook into events 
>generated when an item is added.  I looked through the Chandler wiki 
>and saw a couple of references to rule based collections and there 
>have been a couple of references to rules by Mimi on the user 
>list.  If rule based collections are planned or have already been 
>worked on, is there anything to start from there since what I'm 
>looking for is just a specific type of rule based collection?
>
>What I picture as a first step is a Properties item on the 
>right-click menu for the collections in the side-bar.  On a 
>properties dialog, I could add names/phrases to match (synonyms) for 
>that collection and enable auto-assignment for the collection name 
>and/or the synonyms.  Something like the syntax and capabilities of 
>Google's advanced search page would be convenient and easily 
>understood by everybody; only using Triage status and item type 
>instead of Language and File Type.  Any items that matched would be 
>assigned to the collection.  In addition to ensuring that an item 
>showed up everywhere it was relevant, this would allow me to treat 
>collections as views into the database of items.  To work well as a 
>view, the rules would have to be applied to every item in the 
>database so that I could define a new collection for an existing 
>database and Chandler would search the entire database to assign all 
>matching items to the new collection.
>An now a few questions for anyone who's interested in this feature:
>
>Does this fit with everyone elses expectations of the way 
>auto-assignment should behave?

Yes.  I would like new items to be auto-assigned to existing 
collections, and existing items to be auto-assigned to new 
collections.  I imagine collections to work like views in 
SQL.  Having become engaged in this thread, I've started thinking 
about putting all my stuff in SQL, but the user interface would be a 
query browser, which would probably be too cumbersome for routine use.

>How complicated would you need the assignment rules to be?

I'd like them to be flexible (ideally, as complicated as I need them to be).

>Do you need the unassign actions from Agenda (When item is assigned 
>to X, unassign it from Y.)?

I'd like assignments to persist until collections are removed.

>Regards,
>
>Carl

<snip>





=
Jim Cook <jimcook at panix.com> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
Url : http://lists.osafoundation.org/pipermail/chandler-users/attachments/20080324/5a2ca301/PGP.pgp