Talis Aspire Reading Lists
Welcome to Talis Aspire Ideas Forum.
6 results found
-
Allow administrators to manually create or edit hierarchy nodes (schools, modules, courses)
Users with the node administrator permission will be able to create new or edit existing nodes (schools, courses, modules) in the hierarchy (i.e. the node name, code, description and parent).
5 votesThis should be in tomorrow’s release
-
Implement devolved permissions
On completion of this story, users would be assigned roles on login according to what is sent across in the SAML Response. These roles would be sourced from a central authority outside of Aspire.
Running in this mode, Aspire would no longer have control or responsibility over how roles are assigned to users, and would be merely taking a lead from information passed in the response. The process for a user assuming a role would occur outside the system boundary.
5 votesWe have now completed this story
-
Allow administrators to create new areas of the hierarchy via a bulk upload facility
This would allow administrators to add to the modules and structure already inside Aspire using the standard format already defined in the data conversion and tenancy implementation process.
This would not allow bulk changes or removals from the existing hierarchy.
4 votesThe Hierarchy upload functionality has been geenrally released
-
Improved VLE integration with IMS LTI
Story: As a University integration developer, I would like Talis Aspire to use IMS LTI to integrate with the VLE, so that we can create and view lists without leaving VLE, providing a seamless experience for our users and minimising administrative actions.
Background: IMS Global Learning Consortium has developed the LTI standard to offer standardised integration for service providers across multiple types of VLE. BasicLTI, a precursor to LTI, is supported by all major VLEs. In short, both standards prescribe a launch packet that holds contextual information about the approach, i.e. who, what role and where from. This allows the…
3 votes -
Record and allow reporting on empty lists, course or modules, or missing parts of the hierarchy
This will allow customers to detect dead ends for users and take action outside the system boundary to rectify.
Later we could think about what activities could occur within the system boundary, e.g. request a list, email notification etc.
2 votesWe have now created a new tenancy stats prototype, and we’ll be demoing it at the user group meeting on the 4th March. We have included the ability to report on empty nodes/modules, empty lists and also orphaned lists (i.e. those not attached to a module). There is also some basic stats reporting such as the amount of total lists in the system and the spread of resource types across the system.
-
Share local marketing collateral
Related to my idea on 'sharing experiences engaging with academics'- I've also been thinking about how Aspire is marketed to academics and students before- during and post-launch. Customers will be producing local marketing material- and Talis are also looking at generating material that customers could use. Would a place where all of this material could be gathered and shared be of interest?
0 votesThe Community Content & Experiences support forum handles this
- Don't see your idea?