User login

Technology Discussion

Short-term

Long-term

  • Working groups around design-concepts/ promote our work—use tech to work together and then publish ideas for peer review
  • On-line journal for working papers
  • Search tool by design-concepts—to inform colleagues on-campus, students
  • locally develop campus-based PBP to inform CPED—commit to post on website by Sept for further work at Duquesne convening
  • Proven & Promising Practices vs. Best Practices (hypotheses)vs. assertions as a framework (a research project)
  • deadlines for work  
  • CPED blog- public with guest bloggers
  • use web to pose questions to move us beyond where we are.
  • Resource/repository of cases, syllabi, textbooks, examples of capstones, videos, lesson plans
  • Principles—Wiki, on going conversation
  • RSS feed for notification/reminders
  • On-line journal—working papers, publishable, dissemination
  • access is important-not too techy
  • visual look to website—public vs. private—need to have a space for CPED private conversation
  • defining what an EdD should think, know and be able to do
  • utilizing web to connect partners and students to CPED network
  • consensus on outcomes

Brainstorming Ways to Use CPED website:

  • Scheduled synchronous discussions (—What makes online work successful is assuring dedicated time to go to the website and going to website?)
  • RSS feed to webmail
  • Updates every few weeks via email or RSS feed to email from site
  • Synchronous webinar that would be archived so that someone cold go back to topic
  • Small group work on objectives, self-organizing related to norms of interaction
  • Clear purpose for interaction, i.e., to define and set of standards— to develop by-laws?
  • Most work to date has been generated at tables in small groups, continue process online Access issues — make sure technology does not exclude low-tech users
  • Synchronous — only way for some to commit to being there.
  • Asynchronous — require responses within 24-48 hour period
  • Twitter — for minor questions
  • Use of portal, provide different ways to get in touch for urgent questions or concerns
  • Use portal for repository of archives and products of group work
  • Modify site so that there is a visual cue for public versus private access (e.g, different background)
  • Consider use of Wikis or Google docs for collaborative work
  • Create Ph.D. versus Ed.D you-tube video
  • Flexibility w/ ways participants drive content or format.
  • Consider seriously what is feasible, i.e., support for web-space  - who oversees it? Who is going to keep it current?
  • Text postings — 280—500 character limit  (drafting in Word then post will force clarity)
  • Use web-site for shared resources (e.g., cases, syllabi, problems w/ queries for help, interviews with students, sample lesson pans)
  • Juried online journal — to support work that needs to be done anyway (time to publish in our own forms)
  • Search tool that allows finding central concepts
  • Video — talk about what you do (allow for deep integration of CPED on campuses)
  • Inquiry — to allow for local conversations
  • Commitment by each institution to develop principles of best practice — axial and open coding — principle that evolves from each of our groups. (e.g., by September 15)
  • Rubric for innovation — levels of implementation (e.g., Use of advisory group could be implemented at different levels)
  • Blog — guest blog each month
  • Need bridges and links to collaborators — ways to connect partners into conversation
  • Use short videos created by grad students to demonstrate key elements (juried selection)