Proposal for some improvements

[Reab4]

I've been working with URD for a while now and am very pleased. I see some room for improvements though. Below are some proposals of which I would like your opinion.

Referring to 'Browse Sets' -> 'Group Sets', there are 4 different pages:
'All Sets', 'Downloaded', 'Interesting' and 'Hidden'

I propose the following:

(1) - Rename 'All Sets' to e.g. 'New', 'Incoming' or 'Updates' because basically all new sets appear here which are not automatically filtered/blocked to hidden.
('All Sets' currently doesn't display all sets but actually only displays the non-hidden sets and (manually or auto-marked) non-hidden interesting sets.

(2) - In 'All Sets', the behavior of the global 'Remove this Set' icon. Proposal is to only move the non-interesting sets to hidden, unless there are only interesting/highlighted) sets, which are then forced to hidden (but kept highlighted).
It enables one to quickly hide the non-interesting sets.

(3) - Interesting sets in the 'All Sets' page should get some special treatment: they should not be removed after the expire date. This is because the user has indicated to track the set and may have a longer usenet server retention than the expiry-date set. I.e. the set may be retrievable even after the expiry date set. This in turn means that header data should continued to be gathered for this set e.g. in case of a large set which is being slowly uploaded over more days than set in the expiry setting.
...but perhaps this in already the case?

(4) - Downloaded files are currently marked as italic. For download NZB's there is currently no mark. I propose also to have some kind of mark, e.g. also italic but different color

(5) In the 'All Sets', 'Downloaded', 'Interesting' and 'Hidden' row also add an 'NZB' page similar to 'Downloaded'. I think this is a minor proposal.

[spearhead]

Thanx for your suggestions, we'll look into them...

Some first thoughts:
(1) mostly historical. Hidden was added later. You can easily change this yourself btw by editing the function/lang/xxx.php

(2) basically the "interesting" selection is for that.

(3) iff we do that it would probably become optional.

(4) you're right... shouldn't be too hard to do.

(5) when (4) is done, should be easy enough

[Reab4]

(1) indeed it was a minor suggestion.

(2) In that case I end up with a list of sets on the AllSets page of which a few are marked interesting and a lot are pending to be analyzed by me. When analyzed, the best would be to move the non-interesting to hidden (to make 'room' for the next update). Since the global button also moves the interesting files to hidden,  I then have to go to hidden again and manually move them back individually to interesting/AllSets. Or am I using this the wrong way? - How are you typically using this?

(3) fair enough

(4) gr8

(5) jolly-good

[spearhead]

I don't think there is a right or wrong way to use URD. I typically watch the age of the message in the group (sort by age helps) and look at it daily. I don't use the hide much except for automatically hiding. But anyway, I'll look into it... probably ends up as an other setting.

[Reab4]

(2) Regarding making it optional....Actually the behavior for the global 'remove set' which I propose is the same as the current one, with the slight difference that what now happens in one click will then happen in 2 clicks. The first click moves the non-interesting, the second click moves the remaining interesting. (unless there were only interesting sets).
But I'm already pleased that you're giving it some thoughts.

[spearhead]

4/5 are now done
3 is gonna be difficult as interesting is a per user setting. Could do this perhaps but it will probably slow down expiring data.
2 is partly interested, you can say whether interesting sets will be included in the remove. I may fiddle a bit with its behaviour tho.

You can already try them out in the svn version.

[Reab4]

Tried to copy (wget) it from the SVN trunc into a fresh dir. I'm not so good at this SVN thingy. Anyway, got this error after copying all settings from the old into the new dir and selecting BrowseSets>GroupSets:

Message:
Could not execute SQL query "SELECT *, (100 * "binaries" / GREATEST(1,"articlesmax")) AS "complete", (1256392923 - "date") AS "age", "date", usersetinfo."statusint" AS interesting, usersetinfo."statusnzb" AS "nzbcreated", usersetinfo."statusread" AS "alreadyread", extsetdata2."value" AS "bettername", extsetdata1."value" AS "imdblink", (CASE WHEN extsetdata3."value" IS NULL THEN '0' ELSE extsetdata3."value" END) AS "rating", (CASE WHEN extsetdata2."value" IS NULL THEN setdata."subject" ELSE extsetdata2."value" END) AS better_subject FROM setdata LEFT JOIN usergroupinfo ON (usergroupinfo."groupid" = setdata."groupID" AND (usergroupinfo."visible" = 1 OR usergroupinfo."visible" IS NULL) AND (usergroupinfo."userid" = 2)) LEFT JOIN usersetinfo ON ((usersetinfo."setID" = setdata."ID") AND (usersetinfo."userID" = 2)) AND (usersetinfo."type" = '0') LEFT JOIN extsetdata AS extsetdata2 ON (extsetdata2."setID" = setdata."ID" AND extsetdata2."name" = 'setname' AND extsetdata2."type" = '0' ) LEFT JOIN extsetdata AS extsetdata1 ON (extsetdata1."setID" = setdata."ID" AND extsetdata1."name" = 'link' AND extsetdata1."type" = '0') LEFT JOIN extsetdata AS extsetdata3 ON (extsetdata3."setID" = setdata."ID" AND extsetdata3."name" = 'score' AND extsetdata3."type" = '0' ) WHERE (1=1 AND (usersetinfo."statuskill" != 1 OR usersetinfo."statuskill" IS NULL) AND ( setdata.size >= ((SELECT CASE WHEN minsetsize IS NULL THEN 0 ELSE minsetsize END) * 1024 * 1024)) AND (usergroupinfo."maxsetsize" = 0 OR maxsetsize IS NULL OR setdata.size <= ( maxsetsize * 1024 * 1024)) ) AND ((1=1 ) OR usersetinfo."statusint" = 1) ORDER BY (usersetinfo."statusint" <> 1 OR usersetinfo."statusint" IS NULL) ASC, Date DESC" mysql error: [1054: Unknown column 'usersetinfo.statusnzb' in 'field list'] in EXECUTE("SELECT *, (100 * "binaries" / GREATEST(1,"articlesmax")) AS "complete", (1256392923 - "date") AS "age", "date", usersetinfo."statusint" AS interesting, usersetinfo."statusnzb" AS "nzbcreated", usersetinfo."statusread" AS "alreadyread", extsetdata2."value" AS "bettername", extsetdata1."value" AS "imdblink", (CASE WHEN extsetdata3."value" IS NULL THEN '0' ELSE extsetdata3."value" END) AS "rating", (CASE WHEN extsetdata2."value" IS NULL THEN setdata."subject" ELSE extsetdata2."value" END) AS better_subject FROM setdata LEFT JOIN usergroupinfo ON (usergroupinfo."groupid" = setdata."groupID" AND (usergroupinfo."visible" = 1 OR usergroupinfo."visible" IS NULL) AND (usergroupinfo."userid" = 2)) LEFT JOIN usersetinfo ON ((usersetinfo."setID" = setdata."ID") AND (usersetinfo."userID" = 2)) AND (usersetinfo."type" = '0') LEFT JOIN extsetdata AS extsetdata2 ON (extsetdata2."setID" = setdata."ID" AND extsetdata2."name" = 'setname' AND extsetdata2."type" = '0' ) LEFT JOIN extsetdata AS extsetdata1 ON (extsetdata1."setID" = setdata."ID" AND extsetdata1."name" = 'link' AND extsetdata1."type" = '0') LEFT JOIN extsetdata AS extsetdata3 ON (extsetdata3."setID" = setdata."ID" AND extsetdata3."name" = 'score' AND extsetdata3."type" = '0' ) WHERE (1=1 AND (usersetinfo."statuskill" != 1 OR usersetinfo."statuskill" IS NULL) AND ( setdata.size >= ((SELECT CASE WHEN minsetsize IS NULL THEN 0 ELSE minsetsize END) * 1024 * 1024)) AND (usergroupinfo."maxsetsize" = 0 OR maxsetsize IS NULL OR setdata.size <= ( maxsetsize * 1024 * 1024)) ) AND ((1=1 ) OR usersetinfo."statusint" = 1) ORDER BY (usersetinfo."statusint" <> 1 OR usersetinfo."statusint" IS NULL) ASC, Date DESC LIMIT 0,500")

[spearhead]

you've to update the db tables... commands are in update_db_1.0.1_1.0.2_mysql.sql

[spearhead]

3 is gonna be difficult as interesting is a per user setting. Could do this perhaps but it will probably slow down expiring data.

Actually (3) turned out to be quite easy. Performance hits seems to be minimum.

You can already try them out in the svn version. (be sure to update the database tables!)

[Reab4]

Yeah...eh...about updating the tables ...how do I do that.
I kind of gave up after fruitless efforts. I think I need another hint.

[spearhead]

If you haven't done a manual table update you might try to run the install/update.sh script
(optionally add the version you are updating from - for the current release that would be 1.0.1)

If you already update the tables before, your basically on your own.

cat install/update_db_1.0.1_1.0.2_mysql.sql
will show the commands

you can login to mysql with
mysql -u XXX -p YYY
where XXX is the username for mysql and YYY is the table URD uses (typically urddb)
details can be found in the file dbconfig.php
then copy all the commands from the mysql file that you haven't run before

cat install/update_db_1.0.1_1.0.2_mysql.sql  |mysql -u XXX -p YYY
might also work, it gives errors on lines  you had entered before.

If you need a hand PM a MSN/ICQ or whatever account and I can help you out...

[Reab4]

I couldn't get it to work and decided to wait for the next version (1.0.2). That install also could not get it right, even after editing the scripts.  I finally decided to remove the .installed file and let it rebuild the db from scratch. That seemed to do the trick.

[Reab4]

Have been working with 1.0.2 for a while now and am very pleased.
Thanks for the extended feature set and the good work in general!

[spearhead]

That's great to hear!
If you have any more ideas, issues, or whatever, don't hesitate to post them.