Conference day 1 discussion: unlabeled table B

We need an initial step that discusses what our needs are e.g. - do students need/want these features? -do faculty want to share their material?

Missing
-simplicity of use (importance of this as a starting point)
-do standards exist *important to put back on list - need to establish what would be needed as standards - need to begin with best practices
-how do instructors take this and put it into practice?
-how many of us are doing usability studies to see what faculty really want? How many universities consulted faculty when choosing systems?
-Who is paying for what has changed: printing, textbooks
-Organizational issue #3: stakeholders: CIO, faculty, students, library. IT & Lib. have different interpretations of faculty and staff
-Ramifications for what we are doing that are outside our own needs, e.g. single sign-on.
-Authentication is the tip of the iceberg. After single signon, what can you do, and how do we manage that?
-What is university's role in pushing these agenda? Not just how they support collaboration between IT, Lib but how do they push faculty to work differently. Who takes responsibility for copyright issues and enforcing particular legal interpretations.
-Archiving is such a can of worms should we initially just focus on the importance of building systems you can extract data from?
-Build metadata wizard that is as easy to use as possible and does what faculty do anyway e.g. to put up article fill out a form /author & title instead of typing that info onto a web page as a link.
-Faculty don't know what metadata is but they are interested in describing things
-Need syllabi builders and reading list builders that automatically create reading lists from filling out a form. Then it formats it for them and we get metadata
-Ability for CMS software to implement different policies for different communities of interest (e.g. Hum Div. requires syllabi be open but Med School doesn't')
-How can we integrate tools for creating metadata and to manage digital rights and making these a 'carrot' for faculty so they use it

FOR THE GLOSSARY:
-Middleware, API, SFX