123 results found
-
SAML integration
Our institution currently uses both Sierra authentication and SAML-based Single Sign-On (SSO) for user authentication and access management. While Sierra authentication is supported within Vega, the platform does not currently support direct SAML integration.
To align with the institution's identity management standards and provide a seamless user experience, we request the addition of SAML SSO support in Vega. This enhancement would enable users to authenticate using the institution's existing SAML identity provider, reducing reliance on separate authentication mechanisms, simplifying user access, improving security, and ensuring consistency with other enterprise applications.
Business Justification
Provides a true Single Sign-On experience for users.…
1 vote -
Additional fields from Sierra Patron authentication records
Currently, the following fields are retrieved from Sierra patron records during user authentication:
Name
Email address
Card numberIt is required that the Faculty and Department fields also be retrieved and made available during the authentication process.
The inclusion of these additional data elements will enable more meaningful statistical reporting and analysis. For example, it will allow the institution to determine how many students from a specific faculty or department attended a particular event, workshop, or training session.
Furthermore, this enriched data can be exported to Excel and integrated with third-party analytics and reporting platforms such as EBSCO Panorama and…
1 vote -
Allow cancellation for sessions with shared registration
Currently, it is not possible to cancel individual session dates if the registration mode is set to "Patrons register once and attend all sessions (course/series)."
Even though we'd like patrons to sign up for an entire series at once, we still may need to cancel individual sessions dates without cancelling the entire series.
1 vote
- Don't see your idea?