Here is a list of possible modifications for Muse, developed by James and others:

  • Allow the K-20 community to come together around topically defined interest groups. This builds upon the successful "walled garden" Muse regional site approach.
  • Make it easy for K-20 practitioners to determine their Internet2 connectivity status.  Develop means by which key connectivity data is automatically collected, stored, and updated for every organization modeled within Muse.
  • Create a forum for the K-20 community to discuss the selection, implementation, and integration of the supporting infrastructure needed to fully realize the benefits of their institution's Internet2 connectivity.
  • Strengthen the ability for individuals and groups to communicate with each other within Muse.
  • Develop the ability for people to authenticate into Muse via federated access.  At present, very few SEGP entities are considering or part of a federated approach, however, a federated Muse will be attractive to early adopters and help illustrate what is possible.
  • Partner with MAGPI in developing an event calendaring and registration tool that would integrate with Muse, making it easier for K-20 practitioners to learn about and  participate in Internet2-enabled opportunities.
  • Scale Muse in ways that serve the social networking needs of the broad Internet2 community.  Bringing together all educational, research, and industry sectors and regions helps encourage quick, pervasive technology diffusion.
  • Create and "Amazon-like" rating system for collaborative tools, etc. Would allow Muse members to rate products and other resources, using both a star system and user feedback.
  • Provide a dynamic development follow that can emulate those features found in Facebook, MySpace, etc. that are particularly relevant to the Muse audience. An example would be a "What are you doing?" feature to assist education professionals is sharing and promoting their interests and discoveries.
  • Centrally administered tags to eliminate redundant tags. 
  • Consideration of mechanisms to eliminate redundant organization variations.
  • No labels