Usability: it would be nice if selected bucket was sticky

[Jane Sandberg]

A colleague of mine showed me a workflow involving record buckets. The colleague merged 2 bib records together, did some work on the resulting record, went back to the record bucket interface, and finally selected the bucket she was working with before. All this happened in the same tab. It would have been more convenient for this workflow if the dropdown remembered which bucket she had been working with last and automatically opened it.

I'm not sure this is desired behavior for everybody, but it does seem like an interface with *no* buckets selected isn't really helpful for anybody.

I'm adding the needsdiscussion tag, since I'm not sure if this would be the best solution for every workflow. What do you think?

[Elaine Hardy (ehardy)]

I have been considering this very thing lately. Having the bucket choice be sticky would certainly be convenient when I am doing database cleanup and am primarily working form one or two buckets. Especially if I accidentally close that tab!

[Elizabeth Thomsen (et-8)]

Sticky, please! Sticky buckets would be more convenient for anyone doing a project where they will be selecting and adding several records/items/patrons to a bucket, and I don't see a real downside to this.

If I have a sticky bucket and I want to add something to a different bucket, I would use the dropdown to choose the bucket I want. Without sticky buckets, I have to use the dropdown every time I need to choose a bucket.