SPEC Kit 340: Open Source Software · 27
Software quality and reliability
Use of open data standards
Vendor responsiveness for vended products or a robust user community or user groups for OSS.
We try to insure that all components of our cyberinfrastucture, whether developed in house or not, work well together
to fit within the RUcore architectural framework. All tools and services can then be managed together and receive
upgrades/enhancements on the same schedule. Our commercial ILS, Sirsi/Dynix does not support this and one
IMPORTANT reason we are moving to Kuali OLE is the ability to integrate all our cyberinfrastructure into a coherent
platform where the focus can be an integrated approach to user needs.
Please select the correct statement about the use of OSS at your library. N=76
Our library is using open source software 74 97%
Our library is NOT using any open source software 2 3%
If your library is using open source software, you will continue to questions about OSS Policies.
If your library is NOT using any open source software, you will skip to the screen Library Doesn’t
Use OSS.
OSS POLICIES
9. Please indicate the kinds of policies your institution has related to OSS. Check all that apply. N=73
OSS Policy Content Formal,
written
library
policy
Formal,
written
parent
institution
policy
Informal
library
policy
Informal
parent
institution
policy
No
policy
N
Adoption of OSS developed elsewhere 5 1 25 7 43 73
Development of OSS in-house 3 4 20 10 44 73
Contributing resources to OSS projects 4 5 20 6 44 73
Technology transfer 2 23 4 8 34 69
Number of responses 7 24 32 16 59 73
Comments N=8
I am not aware of any official or documented policy regarding OSS at the institution at this time.
The library has policies and procedures for making library-produced open source code available outside the library. The
policies are currently under editorial revision and are expected to be released later in 2014.
Not aware of university policy though it may exist.
Our library informally supports and greatly encourages IT staff to use and contribute to OSS projects.
Software quality and reliability
Use of open data standards
Vendor responsiveness for vended products or a robust user community or user groups for OSS.
We try to insure that all components of our cyberinfrastucture, whether developed in house or not, work well together
to fit within the RUcore architectural framework. All tools and services can then be managed together and receive
upgrades/enhancements on the same schedule. Our commercial ILS, Sirsi/Dynix does not support this and one
IMPORTANT reason we are moving to Kuali OLE is the ability to integrate all our cyberinfrastructure into a coherent
platform where the focus can be an integrated approach to user needs.
Please select the correct statement about the use of OSS at your library. N=76
Our library is using open source software 74 97%
Our library is NOT using any open source software 2 3%
If your library is using open source software, you will continue to questions about OSS Policies.
If your library is NOT using any open source software, you will skip to the screen Library Doesn’t
Use OSS.
OSS POLICIES
9. Please indicate the kinds of policies your institution has related to OSS. Check all that apply. N=73
OSS Policy Content Formal,
written
library
policy
Formal,
written
parent
institution
policy
Informal
library
policy
Informal
parent
institution
policy
No
policy
N
Adoption of OSS developed elsewhere 5 1 25 7 43 73
Development of OSS in-house 3 4 20 10 44 73
Contributing resources to OSS projects 4 5 20 6 44 73
Technology transfer 2 23 4 8 34 69
Number of responses 7 24 32 16 59 73
Comments N=8
I am not aware of any official or documented policy regarding OSS at the institution at this time.
The library has policies and procedures for making library-produced open source code available outside the library. The
policies are currently under editorial revision and are expected to be released later in 2014.
Not aware of university policy though it may exist.
Our library informally supports and greatly encourages IT staff to use and contribute to OSS projects.
