Table 2 comment cards

• Build instead of buy
• How can new ideas be spread?
• Support
• Cross-Training
• Actually does what they say it does
• Data Integrity
• Version control
• Better standards
• Systems that can safely fail (think threading)
• Asynchronous workflow
• User centered design (and someone who knows how to do it)
• More contact between groups
• Influence thinking in non-IT depts. In library system.
• Better browsing
• Service definition vs. org structure
• Integrate service offerings
• How do we know if we're doing a good job?
• Communication-Spreading ideas between IT groups, influencing thinking in non-IT groups
• Integrated system (modular, Customizable, flexible, stable, specialized) Build or buy?
• System should have: version control, data integrity, deep support, less ambiguous standards, multiple independent environments
• Modular system (integrated)
• Customizable
• Humanities research support
• Parallel vs. Interdependent work flows per circumstances
• Don’t fear specialization and it's inevitable consequences.
• Balance flexibility with stability

Excel file listing all comments