Norbert Nemec | 12 Jun 22:58

Generalized update feature?

Hi there,

I really like the update feature in tellico. However, I believe it could 
be much more powerful if it were generalized to a filter function.

Let me explain:

Currently, when update is called, tellico takes certain fields from the 
entry (typically some ID) and hands it to the script, which then returns 
the complete data and tellico decides which fields to update.

It would be much more flexible, if instead tellico just handed the full 
data of the selected entries to the script, the script would then pick 
out the necessary ID info, get the data from the web merge it with the 
original data and hand back the full data of the selected entries which 
tellico then uses as a replacement.

The same "filter" mechanism could then actually be used for all kinds of 
other actions, like normalizing the data to a standard form, removing 
duplicates, whatever.

Just an idea...

Greetings,
Norbert
Robby Stephenson | 13 Jun 07:37

Re: Generalized update feature?

On Thursday 12 June 2008, Norbert Nemec wrote:
> The same "filter" mechanism could then actually be used for all kinds of
> other actions, like normalizing the data to a standard form, removing
> duplicates, whatever.

I like the idea. Something similar has been on my list of architectural 
changes for a while, along with better threading, more robust backend, 
report formatting, etc. :)

I'm working on the KDE4 port with trunk right now, so I'm not doing any real 
behavior changes. It's on my radar though.

Thanks!
Robby

Gmane