Manual Carousels Should Retain Link to Original Bucket

[John Amundson]

Evergreen 3.5.3

Currently, when a user creates a carousel from a bucket, the process copies the user's bucket into a new one with a very descriptive name, (for example, "System-created bucket for carousel 197 copied from bucket 1257746").

Any future changes made to the original bucket are not reflected in the carousel.

Instead of creating a new auto-generated bucket, the link to the original bucket should be retained so that users can easily add, remove, and rearrange content.

The disconnect between the carousel and the original bucket is not obvious or intuitive to the user.

An alternative would be to keep the current method but allow manual carousels to be refreshed, which would initiate a fresh copy from the original bucket into system generated one.

[Terran McCanna (tmccanna)]

I agree this would be better behavior.

[Jane Sandberg (sandbergja)]

Here is a branch that implements John's first recommendation (not creating a duplicate "System-created bucket", and reflecting all changes made to the original bucket in the carousel): user/sandbergja/lp1920234-no-duplicate-system-generated-buckets

...and a link: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/sandbergja/lp1920234-no-duplicate-system-generated-buckets

...and some notes for testing:

1. Create a record bucket
2. Add some records to it
3. Create a carousel from your bucket
4. In Local Administration > Carousel Library Mappings, set up your new bucket to display in your library's public catalog.
5. Confirm that your records are displaying in the carousel.
6. Remove some records from your bucket, and add some new ones.
7. Refresh the public catalog in your browser, and note that the carousel contents have updated according to the changes you made to your bucket.

[Terran McCanna (tmccanna)]

This is an excellent usability improvement, thank you!

(Testing was done as part of the New Devs Working Group as well as additional testing on my own.)

One thing I noticed while testing is that this change allows the creation of multiple carousels tied to a single bucket - I think this is actually a feature rather than a bug, because it will allow each carousel clone to be displayed on a different org unit home page but still be updated in one bucket.

My sign off is at: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/mccanna/lp1920234-no-duplicate-system-generated-buckets-signoff

[Terran McCanna (tmccanna)]

Committed to 3.12 - Thanks, Jane!