[atulbansal]

I am looking at syndicating multiple RSS feeds in a staging area. Not all rss stories are worth publishing, so this would be a place where I can browse through the aggregated entries and then press 'pligg this' to mysite, it would be a great first level filter.

Besides having Published and Unpublished, I could have another status for a story (e.g. not open to voting yet, needs moderation ) and all my RSS feeds would be entered with that status. Then I could go in and make them 'unpublished' or 'open to public for voting'.

Or, I could have two pligg sites, the first one will be private where I aggregate all feeds. I would press 'pligg this on public site' and it will go to the publis site.

Any ideas?

[onelessthang]

atulbansal -

I have been working on this concept for a week. I feel the best approach is to add either a separate table that the RSS feeds are imported into, and then have a mechanism that transfers them to the 'real pligg link table or add an addition field to the current link table and filter worthy\versus not worthy rss stories.

The difficulty is not this backend change(even though the change will take some time), the real difficulty is working it into the flow of your site. You will be sending people off of your site to read the article, what are the chances they come back to 'move' the rss story to a voting status. There will need to be an additional 'scoring' category for users.

I do agree with this concept, it will really help solidify a site that uses RSS feeds as having the most pertinent information, it is just figuring out how to get it all to come together from a user experience point of view, because now you are asking users to not only submit stories, but also qualify stories before they can be voted on, which is what the current voting system basically does.

As I get something up and running I will let the community know what I am doing. I have 4 other task that have higher priority right now, but this is something I want to get to before summer.

Just wanted to share my views on this subject,
Onelessthang

[atulbansal]

I think I have figured it out, still trying to make it work though. Will let you know how it worked by next week. Here is the sneak peak.

I added another status type called 'waiting' in the pligg_links table link_status field.

Then I copied shakeit.php to approve.php, added authentication code(so only god can access it) and pretty much replaced 'queued' with 'waiting'

Then I had to change libs/search.php to recognise 'waiting' by

Inserting
if ($this->filterTo == 'waiting') {$from_where .= " link_status='waiting' ";}
after
if ($this->filterTo == 'published') {$from_where .= " link_status='published' ";}
And then had to change lang.conf to add a section called waiting and added a vaiable called PLIGG_Visual_Breadcrumb_Queued='waiting'

So now when I login as God and goto approve.php, I see all stories with a status of 'waiting'. Noone else can see them.

Now all I have to do is hack the rss_import to import my feeds as 'waiting' !! I would like to be able to import with some status so the good feeds will go published and others will wait approval.

[sonaro]

What kind of traffic were you guys getting that your ISP had a problem?

[atulbansal]

This is not about traffic or ISP's complaning about it. It is about pre filtering the RSS feeds before opening them for voting. A pre-unpublished stage...

But I do hope that I run into traffic issues some day. That is a problem I look forward to.

[atulbansal]

The RSS feeds coming in with 'waiting' status was easy. Once you setup an rss feed from teh front end, go in the database and change the feed_status field of the feed_links table to waiting. All the stories now go in as 'waiting'. I can go to approve.php, edit the stories, tag them, discard or queue or publish.

Life is good!