Boonex Spy:limits to X records and dont remove the contents deleted

Hello everyone,
following the many information requests of our customers and friends of this community we have decided to write this topic and we hope that you provide your opinion. Thanks in advance!

The module Boonex Spy allows to see all the actions/news about the members.

PREMISE

We have created an extensions called IBDW SpyWall that uses the default table called bx_spy_data of Boonex Spy to read the news about the profiles.

Well, our module SPYWALL bypasses the news about a content removed (SpyWall not displays the news: ProfileXYZ posted a Video ABCD, if this video is not present still). So our module, excludes the contents removed (this requires time and resource, it's clear but it's not the big problem).

THE ISSUE

Many, many our customers ask to us why this module limits the news to XXXX records (by default 1000).

This is in effect a first problem. Why dont limit to the last week, month, years, etc...

Also, other BIG BIG trouble....if I've in my Spy settings, the Number of records to keep set to 1000 (for example)

and my community is very large, this value is too small. Then I can increase this value, ok, but in the most cases, to have all the news for example of the last month, I must set this value to 1000000. But this can't be considered a value that is a good value for each period (because the number of records needed depends of the number of members and of the numbers of actions of each member, also these two values will increase day by day).

Also, this table could contains many records referred to contents not presents in the site (photos, videos, events).

This is this is a waste of records and also on click we'll see "THIS CONTENT IS NO LONGER AVAILABLE".

What does have information about content that was added, but now no longer exists?????


I want thanks AlexT for the answer: Alex says that Boonex Spy is an history

OK, BUT:

1) Why the history tracks the addition of a content and not the removing?

2) The name Spy it does not suggests a history of actions, but a warning of what happens in the community (but it's a personal opinion)


At this point we ask: WHAT DO YOU THINK??


We think that the delete button of each content (Photos, Videos, Events, Groups, etc..) must delete also the relative records in bx_spy_data (as in the adding of content, the record is added).

So, this change is not expensive because it's needed just a delete query (so, maybe, Boonex Staff could consider to apply it in D7.0.7).

This change have many effects:

1. the table is cleared of contents not available (advantage for the DB resources)
2. this allows to skip to see pages of contents no longer availables
3. also our module has an advantage (just in performance because already this problem is bypassed by spywall, but thanks to a check that is NOT necessary if you apply this change).

Finally, a management of the records via the date of publishing, Wethink can improves the module Boonex Spy.

Sincerily

You're right I think that this change should be done for Dolphin 7.0.7...

Yes, thank you for your opinion!

Yes, deleted posts should delete the Boonex spy table data record too - agreed. It makes sense. Our record limit is set to 10000000 as we have a large active community.

Yes, I totally agree with ilbellodelweb.  Why not just limit to EACH member. For example, each member should show maybe 50 latest posts. Anything before the 50th post can be removed automatically.  It's ridiculous to have a limit to "all" but individuals. I have a couple of members use their wall SOOO much that keep removing other members walls!!  This whole concept is a mess!!

Thank you for bringing this up.  This needs to be fixed!

maybe 50 is too much. How about each shows 25 :) 

I do not understand why this cannot be implemented in 7.0.7.

Its pretty reasonable to ask that anytime content (even users) is deleted from the site, ALL traces of it are removed as well. Example: If you delete a photo, it should remove ALL files related to that photo (thumbs, originals, etc.). Of course this would include removing it from the 'spy' tables as well.

Why not make it where you can an option to set how many days to keep 'spy' data OR  how many records? So, If I only wanted 10 days worth, anything older than 10 days would automatically get purged. If I only wanted 500 records, anything more is purged..

I agree with this approach.  However, I would also add that the administrator of the site should be able to choose how many latest posts should be displayed on each profile.

For each profile? mmm

this can be more hard to obtain, I think it's expensive....the query in this case will increase the resource requests

http://www.boonex.com/trac/dolphin/ticket/2586

http://www.boonex.com/trac/dolphin/ticket/2585

 Excellent! I think I have missed a step though as my Spy module settings in admin now shows: 'EMPTY'. Any ideas? Do I need to uninstall and reinstall Spy module - if so, we have thousands of Spy entries and do not want these to be deleted, any ideas? Thanks! 

 Please wait for the official upgrade patch. If you want to test it - use Dolphin 7.0.7 Beta clean install, but don't touch your production Dolphin installation until official 7.0.7 release.