Wanted List: Another Search Option

[decay]

So at current, if you want to search for older episodes, you have 3 options.

1. go to the episode and click search individually.
2. goto the wanted list and click the checkbox at the top to select all episodes on the page and click search all selected.
3. goto wanted page and click search all missing.

For someone like me who has 6000+ missing episodes on my library, the above 3 options basically allow me to search for either 1 episode, 15 episodes or 6000 episodes at a time. I want something in between the 15 and 6000, something flexible. So here are some potential solutions:

1. On the wanted list page, add a items per page input field where you can type what ever you want. Which means you can show 100 or 1000 per page if you want to. Then you can easily order them and select them all and click search all selected.
2. On the wanted list page, add a search X button, which will prompt to enter a number (say you enter 1000) and then it will search for that many items from top on the wanted list using the current order.

Then, it would also be nice to have a column on the Wanted list (that you can sort with) that shows the “Last Searched”, so it makes it easier for someone to go through their wanted list with blocks at a time by sorting using this Last Searched field.

Finally you could use the same logic to add some wanted list automatic search option that searches X episodes every night ordered by the said Last Searched column.

Can something like this be implemented? I believe the first question i asked for is an easy UI/Frontend task (since all the logic for this is already there), im not so sure about the difficulty of extra column and the automation request.

[markus101]

Configurable number of items per page is in the backlog:

Issue: Configurable episodes per page

And storing last searched:

Issue: Store last searched time for episodes

Which ties into:

Issue: Partial Backlog Searches - Limited number of episodes

[decay]

@markus101: thanks for linking them. Great to know that these are already mentioned and that im not the only one having the similar problems.

Should i be posting on the github pages rather than here? Or is it better to post here?

I see that the UI change (first one you linked) doesnt actually have a priority at all. And the others are on low priority. Is there any ETA on when someone will get around to addressing them, as some of them are almost a year old requests.

Cheers.

[markus101]

@decay

Should i be posting on the github pages rather than here? Or is it better to post here?

Here is probably best, we can add things there as required.

@decay

I see that the UI change (first one you linked) doesnt actually have a priority at all. And the others are on low priority.

Priority is a bit misleading, unless its high priority it likely won’t have one added, but we don’t want to remove it from anything that has it because it will send out alerts that just fill up inboxes.

@decay

Is there any ETA on when someone will get around to addressing them, as some of them are almost a year old requests.

Unless something is already merged in you won’t know when its coming (even then it will be in the next release which won’t have a date), we can’t reasonably give ETAs, so we don’t. Only 3 main contributors working in our spare time, which is always limited, so things can take months or longer, especially bigger things.