Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

Subheading/strapline:
"Working together to support the academic mission"

 

Earlier ideas/brainstorming:

Open Minds Embracing Open Solutions

Open-minded Community Embracing Open Solutions

Embracing Open Solutions with an Open-minded Community

Coming Together

Coming Together to Advance Open Source

Open House for Open Source

Moving Forward Together

Open Communities, Endless Opportunities

Open Solutions to Open Minds for Learning, Teaching, and Research

 

 

Tracks

Purpose: This field offers the category of the session to help attendees find sessions in their fields of interest.

Minimalist tracks for this year (to start):

  • Using
  • Developing
  • Beyond
Using

...

Tracks

  • Developing
  • Using
  • Growing
  • Beyond
Developing

Creating, Designing, Planning, Deploying, Enhancing. This track is for instructors, software developers, system engineers, and anyone that develops solutions, content, or the platforms that run, connect, or secure them.

Using

Teaching, Learning, Practicing, Researching, Running, Consuming. This track is for sharing case studies, effective practices, lessons learned,

...

or strategies to help your colleagues using Apereo software and other applications or services around the globe.

Developing

...

Growing

Advocating, Leading, Expanding, Governing, Connecting. This track is for promoting solutions, bridging communities, and increasing adoption of academic software, solutions, and practices.

Beyond

There are many ways to share knowledge and inspire solutions, and they don't always fit into tidy labels.  Choose this This track is for all other presentation proposals that go beyond "using" or " developing."  You're encouraged to break the mold, think outside the box, and embrace unique ways of opening minds to other topics.

...

titleSuggestions

...

,

...

using

...

,

...

 

The following are the tracks we used last year.

  1. Awareness and Advocacy
  2. Design and Development
  3. Deployment and Integration
  4. Expanded Solutions
  5. Getting Started
  6. Leadership and Future Directions
  7. Teaching, Learning, Portfolios, and Research
  8. Technical Management
Awareness and Advocacy

Open Source Software, as a movement, dates back to February 2, 1998 (2/3/98), yet even today, almost 15 years later, awareness and adoption are often hindered by assumptions, misconceptions and a general lack of knowledge regarding open source development, support and implementation. Significant resistance can arise across campuses from non-technical stakeholders, unfamiliar with the open source ecosystem. Presentations discussing non-technical issues around awareness and adoption of open source (as opposed to specific OS applications) are welcome. These presentations might include: the introduction of open source options to your campus; the procurement process for identifying and evaluating options (commercial and open); approaches for addressing common and unique concerns; lessons learned in the implementation, etc.

Design and Development

Sharing is critical among communities creating open software. Please share development projects, design approaches, usability and accessibility improvement plans and projects. Topics may also include best practices in design and development approaches that could be incorporated into software in the future.

Deployment and Integration

Presentations for people who need to make applications work on campus: developers, content providers, team leaders, and evangelists. In particular, we would like to highlight work that integrates community source projects within enterprise infrastructure, and with each other.

Expanded Solutions

For most organizations open source software is one important component of a complex ecosystem of systems and tools supporting teaching, learning and research. Please share your experiences and successes integrating solutions to expand the benefit to your faculty and students.

Getting Started

Sessions for newcomers: from faculty to developers, administrators to trainers, students to tech support. Learn the steps to evaluate, plan, deploy, promote, and support software on your campus.

Leadership and Future Directions

Open software is an element within your broader strategy and goals. How are institutions using open software to achieve strategic goals? What changes and opportunities on the horizon should be influencing the direction of the community? What other trends, advances and challenges should become part of our community planning and dialogue?

Teaching, Learning, Portfolios, and Research

Technology to improve the quality of teaching, learning, and research.  Please share case studies of effective teaching, research and collaboration practices as well as new approaches to technology-enabled teaching and research.

Technical Management

...

and growing.

 

...

Session Types

Purpose: This field is intended to explain the type of a session.

Available to be selected in the call for presentations form: 

  • Track Session

...

  • Showcase Night/Reception
  • Birds of a Feather Discussion
  • Pre-conference workshop (half day)
  • Pre-conference workshop (full day)

Behind the scenes:

  • Pre-conference workshop (half day, morning)
  • Pre-conference workshop (half day, afternoon)
  • Business meeting
  • Keynote/General Session
Track Sessions

...

Track Session

The conference session presentations will run for 45 minutes with an open format. Presentations can be information sessions, panel discussions, or other speaking events. For information sessions, we recommend 30 minutes for the presentation and 15 minutes reserved for audience questions and answers. We DO NOT require presentations to center on Apereo products or projects. When developing presentations, please consider the issues, opportunities, and innovations that are most central to best practices and/or success in technology-enabled teaching, learning, and research.

...

Please suggest a topic for informal collaboration and discussion. There is no need to prepare a presentation for these sessions. This is simply an opportunity for like-minded folk to meet and share.

Tech Demonstrations
Showcase Night/Reception

One evening during the conference community members will gather to eat, drink and share innovations. Please consider providing a demo of your work and discussing it with community members in an informal setting. The conference will provide a table and access to electricity . We unfortunately cannot provide a screen and projector for each table. If you would like us to assist you in coordinating this with the hotel for a fee, please note that on your submissionand wifi. If you need additional equipment, please indicate so in the "Abstract for Review."

Pre-conference Workshop

Please propose an in-depth, hands-on workshop to be offered the day before the main conference begins. Workshops can either be half-day (3 hours) or full-day (6 hours). They should be highly interactive, allowing attendees to explore, review, practice, or produce outcomes based on the topic and goals of the event. Please indicate whether the workshop will be offered for free or will require a fee. The typical fee is $150 for half-day workshops or $300 for full-day.

 

...

Level

Purpose:This field identifies the expected or recommended knowledge level of the attendee for the session.

  1. All
  2. Advanced
  3. Intermediate
  4. Beginner

 

...

Type

...

Purpose: In this past, this field identified the audience type. This year, we propose to offer both audience types as well as product types.

Last Year's Options:

  1. Administrator/Executive
  2. Advocate
  3. Development
  4. Faculty
  5. Identity Management
  6. Information Security
  7. Instructional Design
  8. Library
  9. Media/Multimedia
  10. Mobile
  11. Newcomer
  12. Other/All
  13. Student
  14. Support

This Year's Options:

- Audience, Project, and Interest

 

  1. Audience: Administrator/Executive
  2. Audience: Advocate
  3. Audience: Developer
  4. Audience: Faculty
  5. Audience: Instructional Designer
  6. Audience: Librarian
  7. Audience: Newcomer
  8. Audience: Other (is this needed? -AZ)
  9. Audience: Student
  10. Audience: Technical/Functional Manager
  11. Audience: User Support
  12. Project: 2/3/98
  13. Project: Bedework
  14. Project: CAS
  15. Project: Incubator
  16. Project: Other
  17. Project: Portlets
  18. Project: Sakai CLE
  19. Project: Sakai OAE
  20. Project: Sakai OSP
  21. Project: Student Success Plan
  22. Project: uMobile
  23. Project: uPortal
  24. Project: OpenRegistry
  25. Project: CIFER
  26. Project: Grouper
  27. Project: Shibboleth
  28. Project: Central Person Registry
  29. Interest: Accessibility
  30. Interest: Awareness and Advocacy
  31. Interest: Blended/Hybrid /Online Learning
  32. Interest: Getting StartedOnline/Self-Paced Learning
  33. Interest: Identity and Access ManagementCIFER
  34. Interest: Application SecurityDocumentation
  35. Interest: Federated IdentityGetting Started
  36. Interest: AuthorizationInterest: WebSSOIdentity and Access Management
  37. Interest: Integration
  38. Interest: Internationalization (i18n)
  39. Interest: Learning Analytics
  40. Interest: Media/Multimedia
  41. Interest: Mobility
  42. Interest: Security
  43. Interest: User Experience
  44. Interest: CIFER
  45. Interest: Shibboleth
  46. Interest: Central Person Registry
  47. Interest: Duraspace
  48. Interest: Self-Paced LearningInternet2
  49. Interest: User ExperienceKuali