idiss: minutes 2/20/04

["Andrew R. Bonamici" <bonamici@darkwing.uoregon.edu>]

Dear IDISSTF:

Here are minutes from our first meeting; please feel free to suggest 
clarifications/addiitons etc.

ARB
====
Integration of Digital and Instructional Support Services (IDISS)
Meeting Number One 2/20/04
10 - 11:30 am West Conference Room

In attendance:  Colleen Bell, Andrew Bonamici, Sara Brownmiller, Kellie Ann 
Garsed-Donnelly, Carol Hixson, Lesli Larson

Welcome

Small Group expectations (see below)

1. Review charge; identify outstanding questions; develop shared 
understanding of scope & expected results.

---
Charge:
    * Develop a plan to integrate the wide range of media, educational 
technology and instructional support services within the UO Libraries
    * Develop plans for an online portal to simplify access to currently 
disparate services (e.g., FITT, IMG, ISC, IR, MDLS, classroom support, etc.)
    * Make recommendations for ongoing management of integrated services

Expected Results:
    * A seamless approach to a complex array of interrelated services
    * Higher visibility for library expertise
    * More efficient use of library resources

Discussion:
Even though these services touch on many areas, we are not expected to 
integrate everything, or turn this into a library-wide reorganization effort.

Let's not use the term "portal," which connotes specific kinds of 
enterprise-level functionality. Prefer something like "gateway" or 
"clearinghouse" [or perhaps "guide"???]

Library faculty and staff are an important target audience for IDISS - we 
need to know a lot more about what is available within our own 
organization, & sometimes even within our own departments. Many of our 
customers approach through back doors, and we need to be able to make 
better referrals.

---
How to proceed?

Identify overlaps (but don't necessarily make plan to eliminate them)

We will start with an inventory of:
o	services being offered
o	who is providing them
o	who is using them
o	fees being charged, if any, to whom, for what
o	level of activity (scope, quantities, etc.)
o	other categories?


We will get advice & feedback from teaching/research faculty, making sure 
to include some who make no use of these services, some who are mid-level 
users, and some who are heavy users.

We will have periodic open forums within the library to keep library 
faculty and staff apprised, involved, informed of the IDISS process. This 
will simultaneously begin increasing awareness of the services. We will 
invite our teaching faculty advisors to these sessions

There was considerable discussion about services that are "free" to 
faculty/departments, mainly CRN-related work, and those that are fee-based, 
all or in part. We recognized that nothing is really free -- sometimes the 
costs are absorbed by the general fund (or other permanently budgeted 
funds). We should define what is "free," examine whether or not these 
principles are being interpreted consistently,  and assess the 
sustainability of this principle.

Similarly, should we address the need to generate revenue for 
revenue-dependent units? Rather than focus on revenue generation per se, we 
would prefer to address need for stable funding in our overall 
recommendations re. ongoing management.

Is it our responsibility to do all of this work? What about developing 
systems that the campus can share?  Example is Virage - SOJC and Yamada 
Language Center are being trained to do their own encoding, but the Library 
& Computing Center manage the central system). One of the attractions of 
the attraction of Cornell model is that it includes consulting as well as 
direct production.

Where/when do we refer people directly to other campus units? Example: if 
we get a call from a humanities department for help developing a learning 
object, should we refer them back to Wired Humanities Project (Digital 
Teaching Units)?


2) Review current library & campus issues & developments:
- Faculty Clearinghouse (FCH) project:
o	the group agreed that these are different efforts; parallel but not 
hierarchical, &  complementary. Much of the IDISS content will be 
replicated in the Faculty Clearinghouse project for faculty who approach 
the services that way, but we still want to create a more visible Library 
presence. Also, because of the instructional focus of the FCH, some 
research-oriented &/or internal services may not be emphasized.

-	Ed Tech RFPs: Andrew will send out copies of this RFP & application form
o	Warpinski/Tomlin faculty development program: details forthcoming
-	FITT Group web page  <http://darkwing.uoregon.edu/~jqj/edtech/fitt.html>
o	FITT Group e-mail list archive:
-	Also, Ed Tech Report Fall 2003


Steps:
1.	inventory what we have (see inventory categories above)
2.	identify what might be missing.
3.	examine in context of mission ( library & campus)
4.	develop integration plan that conforms to mission, keeping in mind the 
increasing importance of assessment in educational practice (& accreditation)
5.	then develop gateway/presentation piece as deliverable (including 
usability testing)

What are some ideas for assessing and tracking on use & effectiveness of 
the services we are offering? How to measure?


 3) Follow-up assignment:
- Come up with list of services/activities to be included in the inventory, 
preparatory to brainstorm at next meeting.

NEXT MEETING:
Friday Feb 27, 10 - 11:30 am West Conference Room

FORTHCOMING: ARB will invite Kathy Heerema to the March 12 meeting to 
discuss status of the Faculty Clearinghouse project.


 =================================

Here is Shirien's excellent list of courtesies and expectations for small 
group work:

UO Library System
Small Group: Expectations of Members

    * Be creative.
    * Advocate for and represent the needs of your area.
    * Let go of that advocating when you see that the needs of the whole 
may be better served by a plan different than yours.
    * Be flexible.
    * Be polite and courteous.
    * Let others talk.
    * Don't make the group coax you to talk.
    * Work for the good of the whole team, as well as the whole project.
    * Use the group's time carefully and considerately.
    * Don't sidebar: wait to share with the whole group.
    * Let your strengths add to the vibrancy and health of the group.
    * Read email and papermail, listen to phone messages each day, and 
respond that day, if asked a question. If you can't answer the question, 
call the person and tell them when they can expect an answer.
    * Assume that others are competent.
    * Read minutes of meetings if you missed one.
    * Come to meetings, be on time, let us know if you aren't coming.
    * Do assignments, volunteer for them.

ADDITION:
"David's Rules of Order"
Dave Frohnmayer, President
University of Oregon

1.  Everything is confidential (unless otherwise agreed)

2.  Speak for yourself (no passive voice, "people are saying that...")

3.  Everyone is equal (ideas count, not rank)

4.  No monologues (get to the point)

5.  No sidebars (pay attention to speakers-no rolled eyes, knowing winks or 
whispered conversations)

6.  No hidden agendas

7.  No personal attacks  (issues, not personalities)

8.  Turn issues into "Problem Statement".  Make everyone "own the problem," 
only then will they own the solution (Rule #8).  After consensus, no 
distancing from the group.