434 Matching Annotations
  1. Jun 2016
  2. jis.sagepub.com.ezproxy.alu.talonline.ca jis.sagepub.com.ezproxy.alu.talonline.ca
    1. (2) Collaboration among colleagues. It is a verycommon practice in corporate research centers fora number of colleagues to be working on one ormore projects, each contributing expertise in adifferent aspect of the project. In interdisciplinaryfields such as environment, energy, or space re-search, scientists and engineers from a wide varietyof specialities often collaborate. It is not uncom-mon for chemists, chemical engineers, materialsengineers, biophysicists, and other specialists to beworking together in an interdisciplinary project.Husband-and-wife teams can also be included inthis category.

      Collegial collaboration

    2. ( 1 ) Teacher-pupil collaboration. This is a verycommon mode of collaboration in an academicsetting. The professor in a university departmentprovides the ideas and guidance, and sometimesalso the funds from a research grant, and theresearch assistant or student does most of thebench work. The resulting project report, con-ference paper, or journal article usually carries thenames of both the professor and the student. It isnot uncommon for a professor to be guiding severalstudents in different research projects at the sametime

      Teacher-pupil collaboration

    1. Friedlander argues that for digital humanities to thrive, "one component must be a set of organizational topics and questions that do not bind research into legacy categories and do invite interesting collaborations that will allow for creative cross-fertilization of ideas and techniques and then spur new questions to be pursued by colleagues and students"  [Friedlander 2009, 6]. As she suggests, the digital humanities need to move beyond large numbers of small, uncoordinated projects. Collaborative projects attract more resources and more attention. If properly designed, they also may be more sustainable, creating platforms on which new projects can be constructed. The plethora of boutique digital humanities projects risks the same fate as most digital learning objects. While intended for general use, they lack a common technical platform, common data structures, and common means to aggregate or decompose modules to a useful level of granularity [Borgman et al. 2008].

      Call not to be bound by legacy issues.

    1. Does mega-authorship threaten our concept of authorship in science? It would be easy, and fun, to write with a scandalized tone about how mega-authorship corrupts all that is good and decent about scientific publishing. But does it really matter? I think both yes and (mostly) no.

      thesis: a little yes, but mostly no megaauthorship doesn't do harm

    1. Of course, they will most likely all be co-authored pieces, but the significant point is that the REF rules, except in special cases, impose no penalty on genuinely co-authored work; they explicitly state that it is welcomed. In most cases, there is no disadvantage in submitting a co-authored item to the exercise (although there is some complication when co-authors submit in the same return); it is not as if it counts as half an output or less.

      The REF does not discount coauthorship

    2. he case for more collaborative work can be made. Indeed, most of us do it already, to some degree. We tend to discuss our ideas with colleagues and seek trusted opinions. We present talks at conferences and seminars, and use the feedback to develop ideas before publication. We solicit comments on drafts. Colleagues share a research environment that, if it is effective, contributes to the quality of all output. Yet when the work appears, the standard model is still sole ownership. A colleague could have given a lot of input, discussing ideas or providing comments on early drafts, yet their accepted reward is only to appear in the list of acknowledgements. This seems a paltry return on what can be a considerable amount of effort, an effort that is obviously a degree of collaboration. Perhaps one tries to mitigate the paltry reward by extracting a reciprocal amount of uncredited assistance in return.

      Bout how actual contributions to authorship of humanities work goes uncredited, except in acknowledgements

    1. In some domains, path-breaking work is nec-essarily the outcome of collaborative activity rather thanindividualistic scholarship, a fact reflected in the modestproportion of federal research funds which is allocated toindividual investigators rather than teams. Collaborationsare a necessary feature of much, though by no means all,contemporary scientific research.

      in some domains, collaboration is necessary. Hence the preference for team grants

  3. May 2016
  4. Apr 2016
    1. If, at the dawn of the web, I was to take a list of things the web would bring about and show them to a researcher, they might disagree on the level of interest people would have in things (what’s with the cat pictures, spaceman?) but there’d be little there to surprise them except for one item: the most used reference work in the world will be collaboratively maintained by a group of anonymous and pseudonymous volunteers as part of a self-organizing network.

      It would be nice if on this day, as we marvel about the rise of Wikipedia, we could turn some of our attention to the Wikipedias of the future. Where are opportunities for this mode of collaboration that we’ve missed? Why are we not confronted by more impossible things? How can we move from the electronic dreams of the 1970s to visions informed by the lessons of wiki and Wikipedia? Some people might think we’ve already done that. But I’m pretty sure we’re barely getting started.

  5. Jan 2016
  6. Dec 2015
  7. Nov 2015
  8. Aug 2015
  9. Jun 2015
  10. May 2015
    1. I first discovered the power of collaborative annotation

      Collins actually imagines a moment of shared marginalia in his poem. In a copy of A Catcher in the Rye that he borrows from a library as a boy, he finds the following: “Pardon the egg salad stains, but I’m in love.” The young Collins imagines the note to be written by a beautiful girl and feels himself in a sense falling in love with that other reader. Though we need not develop a dating service out of the modern technologies that allow for social reading, we can at least see the humanity that can be shared in the margin of a digital page: the teachable moments, the conversations that might occur. We have glimpsed such moments on other social media like Twitter and Facebook, but I argue they lack the depth of annotation, which brings together text, comment, and now, readers.

  11. Apr 2015
    1. Sixty percent of those surveyed said too little emphasis is placed on collaborations with other learners outside the classroom, while 46 and 40 percent, respectively, said there should be more emphasis on group achievement and working in teams. The two soft skills respondents said were important most often were problem solving, at 96 percent, and the ability to collaborate, at 95 percent.
    1. The blog post in which Ben Balter proposes that term was unpublished when I read it. But since the blog is hosted on a public GitHub repository I could not only read the post in draft form but also follow the discussion with invited reviewers and observe how that discussion influenced the draft.

      With Hypothesis this kind of thing becomes available for /any web page/.

  12. Mar 2015
  13. Feb 2015
  14. Jun 2014
    1. Technology leadership is not defined by patents, which history has repeatedly shown to be small protection indeed against a determined competitor, but rather by the ability of a company to attract and motivate the world’s most talented engineers. We believe that applying the open source philosophy to our patents will strengthen rather than diminish Tesla’s position in this regard.

      "Technology leadership is....defined by...the ability of a company to attract and motivate the world's most talented engineers."

      The key components of this applied "open source philosophy" seem to be about increasing input, visibility, and collective motivation by taking fear out of the interaction equation.

  15. May 2014
    1. Collaborate for God's sake!: EVERY organization dealing with data is dealing with these problems. And governments need to work together on this. This is where open source presents invaluable process lessons for government: working collaboratively, and in the open, can float all boats much higher than they currently are. Whether it's putting your scripts on GitHub, asking and answering questions on the Open Data StackExchange, or helping out others on the Socrata support forums, collaboration is a key lever for this government technology problem.

      Collaboration is clearly key, but it's not obvious what that means. The suggestion here is a good first step in an organization:

      • scripts on github
      • asking and answering questions on stackexchange
      • and (for data) joining the Socrata support forums

      What does it take to get organizations on this path?

      And what steps are next once the organization has evolved to this point?

  16. Feb 2014
  17. Jan 2014