Settings and activity
153 results found
-
22 votes
Derek Brown
supported this idea
·
-
5 votesUNDER REVIEW ·
AdminAngela Nolet
(Senior Product Manager, Innovative Interfaces, Innovative)
responded
Derek Brown
shared this idea
·
-
2 votesUNDER REVIEW ·AdminAngela Nolet
(Senior Product Manager, Innovative Interfaces, Innovative)
responded
Derek Brown
shared this idea
·
-
2 votesDerek Brown
shared this idea
·
-
11 votesDerek Brown
supported this idea
·
-
3 votesDerek Brown
supported this idea
·
-
12 votesDerek Brown
supported this idea
·
-
11 votesDerek Brown
supported this idea
·
-
88 votes
https://portal.productboard.com/iii/15-vega-product-portal/c/869-meep-enhancement-winner-use-ils-bib-record-lists-for-showcase-creation
An error occurred while saving the comment Derek Brown
supported this idea
·
An error occurred while saving the comment Derek Brown
commented
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). -
25 votesDerek Brown
supported this idea
·
-
8 votesDerek Brown
shared this idea
·
-
7 votesDerek Brown
supported this idea
·
-
6 votesDerek Brown
shared this idea
·
-
22 votesDerek Brown
supported this idea
·
-
14 votes
An error occurred while saving the comment Derek Brown
commented
This would require having Polaris e-sources working as well for Vega unless there was direct integration between Proquest products, Vega, and library patron data... A follow up Idea Exchange that relates to the e-source method will be link here: https://ideas.iii.com/forums/951766-vega-discover/suggestions/47296727-e-source-targets-in-vega
Derek Brown
shared this idea
·
-
5 votesDerek Brown
supported this idea
·
-
12 votes
An error occurred while saving the comment Derek Brown
commented
This is a big one for us. Please and thanks!
Derek Brown
supported this idea
·
-
22 votesDerek Brown
supported this idea
·
-
7 votesUNDER REVIEW ·AdminAngela Nolet
(Senior Product Manager, Innovative Interfaces, Innovative)
responded
Derek Brown
shared this idea
·
-
39 votes
An error occurred while saving the comment Derek Brown
commented
Showcases + hero carousels please!
Derek Brown
supported this idea
·
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