Carousel: Mapping for manual carousels
Bug #1902542 reported by
Terran McCanna
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Won't Fix
|
Wishlist
|
Unassigned | ||
Bug Description
When creating a carousel from a bucket, you have to take the additional step of manually creating a carousel mapping for it.
It would streamline the process if the mapping was created automatically (like it is when creating an automatic carousel). My preference would be to automatically create the bucket-carousel with the visibility being at the creator's workstation level, and then it could be modified if needed.
| Changed in evergreen: | |
| status: | New → Confirmed |
| tags: |
added: admin-pages opac-carousel removed: carousel |
Revision history for this message
| Terran McCanna (tmccanna) wrote | #1 |
| Changed in evergreen: | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
3.10 Update:
I'm actually going to retract my wish list request because there are times when we may want to leverage some of the carousel functionality without having the carousel display in the public OPAC.
For example, now that we have the ability to access carousel contents through an API call from a third party site, this gives us the option of creating multiple manual carousels that we only want to display individually in different pages on a web site, but don't want to clutter up the OPAC page.