collaboratively designed
The article states:“We know that students are savvy about gathering information. They use the Internet to find resources, to locate answers to questions, and to validate ideas through others. They get information through a network of resources and people. We must recognize this when we deliver services, and we need to become comfortable with not being the sole purveyor of information and services.”Perhaps we should think of ourselves as the managers of institutional data whose major job is to see the data used by others to satisfy their administrative and academic needs. Instead of putting major resources into developing applications that utilize the data, we could put our efforts into ways to deliver the data to others in a responsible and secure manner. This would set us up to embrace a student’s computer science project that provides on-line scheduling of classes instead of seeing it as yet another great idea in the big queue in the sky of applications to be developed and integrated into our ERP. This would also help to encourage student developed “Web 2.0” mini-applications targeted specifically at student needs—no need to go through the administrators to make their lives easier. I see a bigger and bigger rift developing between how our institutional applications “serve” the students and how the social networking applications “are” the students’.
Login to post comments 6110 reads