coralnet icon indicating copy to clipboard operation
coralnet copied to clipboard

Metadata edit performance: Ask for a search before showing any results

Open StephenChan opened this issue 6 years ago • 3 comments

Currently, after the user clicks "Metadata", they get a metadata grid of ALL their images. The grid is somewhat slow to load and rather sluggish to interact with once you get to a few hundred images. And some sources have thousands.

It would be better to make the user submit a search before showing anything, so if they have thousands of images, they can apply some filters first to minimize bombardment on their browser. (The Patches page already behaves like this, so we just copy that behavior.) We could possibly only make the user do this if they have over ~300 images, but... that's going to be true for most of our serious users anyway.

StephenChan avatar Jun 01 '18 22:06 StephenChan

I dunno. This issue seems a bit hacky. I meant, it seems like a in use-case to want to view/edit all rows. In which case this is useless. Pagination seems like a better solution. In particular if paired with a “select all across all pages” button.

beijbom avatar Jun 16 '20 05:06 beijbom

I guess this is more of an 'interim solution' idea if pagination was too complicated. But if we don't implement 'select all across all pages' yet, I think pagination should be pretty simple to implement, in which case I agree this issue shouldn't be needed.

StephenChan avatar Jun 16 '20 09:06 StephenChan

Another possibility that may be easier than pagination is to make the initial sql call to request the meta data info with say limit=50 and then add a "see rest" button which will make the query without the limit. That would make the database query faster and at least initial displays fast.

On Tue, Jun 16, 2020 at 2:43 AM StephenChan [email protected] wrote:

I guess this is more of an 'interim solution' idea if pagination was too complicated. But if we don't implement 'select all across all pages' yet, I think pagination should be pretty simple, in which case I agree this issue shouldn't be needed.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://urldefense.com/v3/__https://github.com/beijbom/coralnet/issues/130*issuecomment-644657164__;Iw!!Mih3wA!VfUKFABCA6Lv_ytUzNg6Sycrpsnw2deE2ACxhBhHNHNaSyvyn8qNPqU4nEk-zeme$, or unsubscribe https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABKA5AOMZZD3R3YDH4IGBQTRW45FTANCNFSM4FC5TIZQ__;!!Mih3wA!VfUKFABCA6Lv_ytUzNg6Sycrpsnw2deE2ACxhBhHNHNaSyvyn8qNPqU4nIDpMgX8$ .

kriegman avatar Jun 16 '20 14:06 kriegman

Done in PR #493. Again, lazy interim solution.

StephenChan avatar Nov 16 '23 04:11 StephenChan