I'm currently using Sierra with the regular webPAC, and we're in the very early days of migrating to Polaris with Vega Discover. I have 35 Create Lists that are relegated to a list on our WebPAC. I look forward to the browsable shelves after our migration, especially tying into using the Polaris records!

If we were only adding on Vega Discover to Sierra, I would definitely use this Create Lists > Showcase feature!

It seems like it could be very useful to create a Showcase based off of a specific Create List search in Sierra.

This is extremely helpful. I use Create Lists in Sierra most times to find materials for a showcase. This is extremely helpful and a time saver.

REQUEST: 
Sierra Libraries can access Create Lists for creating Showcases.
Polaris Libraries can access Record Sets for creating Showcases.

FEATURE DETAILS
Job Story: As a Showcase Admin, I can use existing bibliographic record lists from my ILS to create Showcases in Vega Discover.

Acceptance Criteria: 
Sierra Libraries can access Create Lists for creating Showcases. This will require utilizing the bibID links for linking to materials as Sierra does not have Rollups. 
Polaris Libraries can access Record Sets for creating Showcases. This will require utilizing the bibID links for linking to materials as Polaris does not have Rollups.

From original idea: https://ideas.iii.com/forums/951766-vega-discover/suggestions/46646182-use-existing-create-lists-record-sets-from-ils-f

We would greatly appreciate having this capability incorporated into our system.

Currently, we implement a similar process through a scheduled nightly SQL job in our self-hosted Polaris environment. This job refreshes Bib Record sets, ensuring that our content carousel data remains up-to-date. Extending this functionality to our record sets populating the Vega suite of products would be highly advantageous.

It's important to emphasize that having a standardized, non-customized SQL job running nightly would be immensely beneficial. This would allow us to seamlessly import our automation for transforming bib record sets into carousels, streamlining the process and ensuring consistency.

Example of one of our carousels that fed onto our Polaris PAC and previous website:

--Re-add for New Large Print::
insert into polaris.polaris.BibRecordSets (BibliographicRecordID, RecordSetID)
Select DISTINCT br.BibliographicRecordID, 95102 --RecordSetID after the coma, change as needed
From polaris.polaris.CircItemRecords cir (nolock) --Item information to specify collection and first available date
Join polaris.polaris.BibliographicRecords br (nolock) -- Bibliographic Information, which will be used in the Record Set
on cir.AssociatedBibRecordID = br.BibliographicRecordID
where cir.FirstAvailableDate between (Getdate()-30) and getdate() --The -30 indicates 30 days ago, change as desired
and br.PublicationYear > (YEAR(CURRENT_TIMESTAMP)-2)
and cir.AssignedCollectionID in (23,24,25) --Place the desired CollectionIDs within the parenthasis, separate with a coma for multiple CollectionIDs

We are excited about the potential of Showcases in Vega, but we need a way to create them from our ILS data. We have a lot of staff-created lists and record sets in PowerPAC that we use for content carousels and other features. It would be very helpful if we could use them to generate Showcases automatically, instead of having to manually enter each record. This would save us a lot of time and effort, and make Showcases more appealing and useful for us.

Being able to use record sets to populate showcases would be very helpful.

Ability to use Create List to Generate New Items list in Vega

Provide ability for staff to generate a specific list of titles using Create List (i.e. New Items) that can be viewed by patrons. Create List offers the ability to determine desired results to include in a New Items list (and allows us to block titles from being included in the results). This approach for promoting New Items would provide local control for promoting items that the facet approach does not provide.

Being able to utilize the functionality of the existing ILS - instead of having to create a list and recreate lists in Discover - would be very valuable.

I would like to be able to export a list to Showcases. However, having to keep a list for a Showcase would be frustrating. We already have trouble running out of available lists, so we would not be able to set aside one (or probably multiple) lists for Showcases.

Coming from a library that has been using Record Sets in Polaris for years to build lists for carousels it is time-consuming to recreate the wheel to now put these into Saved Searches for Showcases. I would much prefer option 2 that Derek listed.

We've rolled our own discovery layer and agree that using bib record sets is the simplest way to allow staff to maintain showcases / carousels / recommended lists. For us to consider using a vendor's discovery layer, this would be one of the bare minimum features.

The removal of bibliographic record set imports from Polaris’ Content Carousel has made it difficult for our staff to maintain their existing catalog lists within Vega’s Showcases. Please allow libraries the ability to use advance search capabilities within Vega Discovery to help build better Showcases (Saved Searches lists). Two methods that would work best for our library:
1) Expand on Advanced Search through Vega (Currently on the roadmap, but we are unaware of what will come from this feature).
2) Allow importing of Bibliographic Record Sets as Saved Searches or Showcases (This is what would make our librarians’ lives the easiest).