1 / 6

CI.III.2

CI.III.2. Raquell Holmes, Doug Gregor, Eytan Adar, Gavin La Rowe, Caroline Haythornethwaite, Donna Cox, Roger Leenders, Lada Adamic. CI Challenges in adoption, deployment, utilization of a Cyberinfrastructure (Education Outreach Training).

yetty
Download Presentation

CI.III.2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. CI.III.2 Raquell Holmes, Doug Gregor, Eytan Adar, Gavin La Rowe, Caroline Haythornethwaite, Donna Cox, Roger Leenders, Lada Adamic

  2. CI Challenges in adoption, deployment, utilization of a Cyberinfrastructure(Education Outreach Training) - "Build it and they will come" just doesn't work - Everyone uses their own formats, software, interoperability between software packages and scalability are major issues. Standards. - Building for usability is very hard: that last 50 yards to a community is through the interface, and getting interfaces right is very hard. Communities themselves don't necessarily know what they want. And if we build something that we think they want, they'll reject it.

  3. Challenges - Cost of switching or adopting new tools is too high - Long term support: how does this benefit research-based developers. Cyberinfrastructure needs to be "persistent." - Reward structure: software maintenance. - Communication within CI community may not be sufficient to get people to define the core issues needed to make CI work for SNA.

  4. List Of SNA helps Social networks as a methodology rather than a field of it’s own Suggesting links where they did not exist before for communities of researchers Key dissemination people for education about cyberinfrastructure (get buy-in from key influencers) Govt report, Tornatzsky, Fleischer (old book) Identifying mechanisms for support (don’t have to bug developers, find someone local in your collaboration network who can help) Tip grant funding to provide continuing support after initial development phase (if commercialization doesn’t happen)

  5. A scenario Challenge: Communities themselves don't necessarily know what they want. And if we build something that we think they want, they'll reject it. Approach - Shows where dissemination points are for other fields. When you identify those people, you can get better information about what the community wants/needs and better buy-in. - Mining data for key people: one approach not sufficient (ISI: citations, ego-centric). Need other approaches to identifying people and needs (those who act doesn’t equal those cited, the CEO vs. IT team of companies for adoption.)

  6. Is this really your network?

More Related