Suggestion for efficiency of set registry?

qmayer

Maybe this has been suggested before, but I haven't been able to keep up with the board lately due to school.

Instead of the user having to wait for a page to load with the first 200 cards, just have 2 fields on the initial "edit set" page... one for the card number and one for the serial number. This would save server processing power by just cross-checking the cards you have input instead of looking at the 200 cards at a time. It will also help the people with slow connections by not having to load 200 records from a database. After they fill in the first 10 sets of fields (or however many would be on the first page), it will take them to a page to check to make sure the serials match the card in the PSA database.

Anything I missed? Thoughts?

FB

Sounds reasonable,

You may want to email BJ on this. But, my guess is that there has already been so much time and efforst put into the existing process - that a redesign is one of the farthest things on their minds. I know when user groups come to my area with ideas on how to make the system better - we cost it out and tell them it will take X amount of money and X amount of time away from your other projects - how do you want to prioritize? It usually ends up near the bottom.

qmayer

I don't think it would be that difficult. From what I gathered about how it works is that the server generates a list of the first 200 cards when you first login. It gives you fields to enter the serial and stuff. My method would be to have the user simply type in the card number and serial number, but still stick with the same server routine for cross-checking the serials. The new method is essentially just taking out the list of the 200 cards and having the user type in a few more numbers.