Curriculm

For any CO (Curriculum Organizer) data set there are between 100 and 1000
learning outcomes. Given this I don't believe that it's not practical
evaluate each LO (Learning Object) on the fly which means that it needs to
be done before the search is run. 

Given this then there are four primary triggers for index updating.

A) When an LO is loaded (new or new version)
B) When an LO is removed
C) When the CO data is changed.
D) When the user asks for a regeneration (this may not be available in the
upcoming release as it's currently not supported by a use case).

The indexing will need to be an asynchronous event listener which simply
means that, like the current free text indexing, it will need to operate in
the background. The effect of which may mean that there is a delay
(sometimes perceivable, sometimes not) between the time of change and the
time that the LOs index information is updated.

Are their any problems, issues or further suggestions regarding this? 

-k.

-- 
If you don't test then your code is only a collection of bugs which 
apparently behave like a working program. 

Website: http://www.rocketred.com.au/blogs/kevin/




-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en