Friday, March 26, 2004

Conference day 1 summary notes, C. Stewart

facilitators

-termporal issues were not addressed
-imbalance in scope of issues
-should we have broad issues or specific issues? we should have a mix
-we should have as a goal to identify a project
-identify things that people can do right away
-concerns about what we actually want out of this meeting? would have been better to allow people to express their needs, then from that build a list of issues.
-shorter-term, reachable goals, what is the low-hanging fruit.
-Cliff's suggestions: linking (easy import of content), policy issues. Cliff's talk really had an impact on the groups.

new issues
-privacy issues
-policy issues: legal and cultural
-more than just IT and library collaborating
-dedication of resources, both time and money
-branding at the library or university level; where are issues coming from
-simplicity of use: how easy is it to use
-security and privacy issues: access to interactions and transactions.
-faculty and their involvement: importance in their role in adopting learning management systems, and an institutional reward structure to affect change
-students as the emerging consumer of the instruction content
-what is the pedagogical component, what about teaching philosophy
-clarifying language, priorities, goals
-how do we make a case to the highest level administration to make a case for this collaboration.
-branding, training, intermarriage
-accessibility to various formats
-what records will be kept and for how long? archiving, access, etc.
-learning objects and retaining information about who can use them so that it's immediately apparent what the rights situation is. Transparencecny
-portal creep: everyone is coming out with their own portal, who will have the top level
-technical issue: roles for librarians access (also a policy issu)
-lack of communication and trust relationship: at the institution, but also on a broader scale. No understanding of goals and needs of the various units.
-open source
-how to make learning objects discoverable; is this a library issue? Are we sharing perspectives about this? What kinds of selection criteria.
-research needs; getting faculty involved with providing students with what they're demanding. should we be building resource management tools.
-Content preservation; what should be preserved and what is ephemeral: course management systems aren't designed to be long-term. Long-term storage should be accomplished in a content management issue.
-Copyright as an area of concern
-Training issue and staff training, skills building; training and support
-Alignment of leadership: how resources are distributed, incl. staff.
-What would the changes to the library management systems and course management system have to be with regard to training?
-What are you training on? What is your documentation like?
-Policy issues: legal and cultural policy. Legal: FERPA, TEACH, etc. Cultural: specifying that these things happen with these triggers, etc.


NEGATIVE SPACE
-archiving
-experimentation
-open source

1. Archiving and preservation
2. Legal policy: copyright and privacy, FERPA, HIPAA, TEACH
3. Technical access: authentication and authorization (roles within the organization)
4. Metadata: where does it sit, where does it travel? who is creating, who is receiving?
5. Who are the stakeholders? Who is missing in this discussion? Who decides who sits at the table? How to align with leadership?
6. How should the Library,IT staff work together to support this integrated offering?
7. Training and support
8. Avoiding duplicate content purchasing
9. APIs and interoperability; open source.