[Zope-PTK] "score" or "sortOrder" for PortalContent?

[Chip Vanek]

Yes, scores/ratings/.. would be changing often.  

I found that a ZODB centric implimentation would not
work and am searching for a better solution.  I have not
dived into the RSPP/RIPP stuff because it seems like in such flux.

Would RSPP/RIPP not have the same issue of exploding the ZODB?

Your comment on scores based on traversal is dead-on.

Chip

>-----Original Message-----
>From: alexande@cat-box.net [mailto:alexande@cat-box.net]On Behalf Of
>Steve Alexander
>Sent: Friday, May 19, 2000 11:50 AM
>To: Chip Vanek
>Cc: 'Kevin Dangoor'; zope-ptk@zope.org
>Subject: Re: [Zope-PTK] "score" or "sortOrder" for PortalContent?
>
>
>Chip Vanek wrote:
>> 
>> Hi,
>> 
>> I do think that this should be a standard part of PortalContents.
>> To allow reasonable flexability there should be two elements.  One
>> called "score or sortOrder" to represent derived importance based on
>> pageviews and date.  Another element called "rating" to hold explicit
>> user input on importance.  List views could be generated from one of
>> these "importance scores" or a weighted average.
>
>Will these scores be changing often?
>
>Maybe it would be best to better integrate RSPP (RIPP, whatever!) into
>PTK better, so that we have the option of storing "score" data in a
>different propertysheet to the dublin-core sort of portal data.
>
>Imagine having scores for stuff derived from how links are traversed
>during sessions (see www.everything2.org, neural net theory).
>
>--
>Steve Alexander
>Software Engineer
>Cat-Box limited
>