Technology
Academic Software Use Cases
Software must be reviewed for use with university accounts, systems, networks, and/or data; this is especially important for software used for instructional or research purposes. Academic software currently has two paths for submission - new software should be submitted through the new Academic Software Request process. Renewals of existing software should generally be submitted through normal departmental purchasing processes. Following is a more detailed listing of different types of software and which path should be used in different scenarios.
Definitions
In terms of the need to submit for review, software is considered either new, renewal, or reviewed. Specific to Learning Tool Integrations (LTIs) with Canvas, a textbook package is considered software. The definition for each follows.
- New: Software that has not been used within the past year by any University department, regardless of cost. This type of software should be submitted for review through the Academic Software Request form.
- Renewal: Software in use currently that will need to be renewed at some future date, regardless of cost. Renewals of this type of software should be handled through normal departmental purchasing processes.
- Renewal with Integration: Software that is currently in use, but for which an integration to the Canvas system or the Microsoft 365 system is desired. The software itself would be defined as a renewal, but would need to be reviewed before the integration can take place.
- Reviewed: Software that has been reviewed for use and complies with university policies, procedures, and standards. Reviewed software is listed in the Software Catalog as it completes review. This type of software may be approved for specific use cases or for general use - please see the "How to Request" section for details. Software reviewed for general use may be submitted though normal departmental purchasing processes without further review. Software reviewed for specific use should be submitted through the Academic Software Request form for a review of the additional use case needed.
Where to submit software requests
Following is a detailed listing of which software request path should be used for different types of software.
Type of Software | In use currently(or within previous year) | New, Reviewed, or Renewal | Where to Submit |
|---|---|---|---|
| Software listed in the Software Catalog | Yes | Reviewed | Utilize normal departmental purchasing processes at time of renewal (if there is a cost) |
| Software listed in the Software Catalog | No | Reviewed | Utilize normal departmental purchasing processes at time of renewal (if there is a cost) |
| Software not listed in the Software Catalog | Yes | Renewal | Utilize normal departmental purchasing processes at time of renewal |
| Software not listed in the Software Catalog | No | New | Submit through Academic Software Request Process form |
| Software/textbook for which a connection to Canvas is desired - if currently integrated with Canvas, as indicated on the LTI (Learning Tool Integration) list | Yes | Renewal with Integration | Submit through Academic Software Request Process form to verify the specific use case has been reviewed |
| Software/textbook for which a connection to Canvas is desired - if currently integrated with Canvas, as indicated on the LTI (Learning Tool Integration) list | No | New | Submit through Academic Software Request Process form to verify the specific use case has been reviewed |
| Software/textbook for which a connection to Canvas is desired - if not currently integrated with Canvas, as indicated on the LTI (Learning Tool Integration) list | Yes | Renewal with Integration | Submit through Academic Software Request Process form |
| Software/textbook for which a connection to Canvas is desired - if not currently integrated with Canvas, as indicated on the LTI (Learning Tool Integration) list | No | New | Submit through Academic Software Request Process form |
| Software for which a connection to Microsoft 365 is desired - if currently enabled, as indicated on the Microsoft 365 app consent list | Yes | Renewal | Utilize normal departmental purchasing processes at time of renewal (if there is a cost) |
| Software for which a connection to Microsoft 365 is desired - if currently enabled, as indicated on the Microsoft 365 app consent list | No | Reviewed | Utilize normal departmental purchasing processes at time of renewal (if there is a cost) |
| Software for which a connection to Microsoft 365 is desired - if not currently enabled, as indicated on the Microsoft 365 app consent list | Yes | Renewal with Integration | Submit through Academic Software Request Process form |
| Software for which a connection to Microsoft 365 is desired - if not currently enabled, as indicated on the Microsoft 365 app consent list | No | New | Submit through Academic Software Request Process form |
What is not in scope for the process?
Trial software, software that is being used temporarily as an evaluation for more permanent usage, is not in scope for the academic software request process if it is standalone software. If the trial software needs to integrate with other ISU systems, it should be reviewed through the Academic Software Request Process. Please follow the table above for guidance when ready to use such software more permanently.
Software used to communicate with scientific instruments, code and coding languages, and electronic resource subscriptions such as online journals and databases are specifically not in scope for this process. These items should be submitted as needed through normal departmental purchasing processes.