Why We Read Wikipedia

Wikipedia is one of the most popular sites on the Web, with millions of users relying on it to satisfy a broad range of information needs every day. Although it is crucial to understand what exactly these needs are in order to be able to meet them, little is currently known about why users visit Wikipedia. The goal of this paper is to fill this gap by combining a survey of Wikipedia readers with a log-based analysis of user activity. Based on an initial series of user surveys, we build a taxonomy of Wikipedia use cases along several dimensions, capturing users' motivations to visit Wikipedia, the depth of knowledge they are seeking, and their knowledge of the topic of interest prior to visiting Wikipedia. Then, we quantify the prevalence of these use cases via a large-scale user survey conducted on live Wikipedia with almost 30,000 responses. Our analyses highlight the variety of factors driving users to Wikipedia, such as current events, media coverage of a topic, personal curiosity, work or school assignments, or boredom. Finally, we match survey responses to the respondents' digital traces in Wikipedia's server logs, enabling the discovery of behavioral patterns associated with specific use cases. For instance, we observe long and fast-paced page sequences across topics for users who are bored or exploring randomly, whereas those using Wikipedia for work or school spend more time on individual articles focused on topics such as science. Our findings advance our understanding of reader motivations and behavior on Wikipedia and can have implications for developers aiming to improve Wikipedia's user experience, editors striving to cater to their readers' needs, third-party services (such as search engines) providing access to Wikipedia content, and researchers aiming to build tools such as recommendation engines.Comment: Published in WWW'17; v2 fixes caption of Table

Business schools inside the academy: What are the prospects for interdepartmental research collaboration?

Established literature about the role of business schools tends towards more parochial concerns, such as their need for a more pluralist and socially reflexive mode of knowledge production (Starkey and Tiratsoo 2007; Starkey et al 2009) or the failure of management’s professionalism project expressed through the business school movement (Khurana 2007). When casting their gaze otherwise, academic commentators examine business schools’ weakening links with management practice (Bennis and O’Toole 2005). Our theme makes a novel contribution to the business school literature through exploring prospects for research collaborations with other university departments. We draw upon the case of UK business schools, which are typically university-based (unlike some of their European counterparts), and provide illustrations relating to collaboration with medical schools to make our analytical points. We might expect that business schools and medical schools effectively collaborate given their similar vocational underpinnings, but at the same time, there are significant differences, such as differing paradigms of research and the extent to which the practice fields are professionalised. This means collaboration may prove challenging. In short, the case of collaboration between business schools and medical schools is likely to illuminate the challenges for business schools ‘reaching out’ to other university departments

Innovative collaborative design in international interaction design summer schools

[About the book]: Design is changing, and to educate the next generation of designers, these changes need to be addressed. In light of the growing role research and interdisciplinary collaboration play in contemporary design performance, Design Integrations calls for an innovative shake up in design education. Poggenpohl asserts that design research is developed through a typology within academic and business contexts, and follows different research theories and strategies. Such issues in design collaboration are explored in-depth, with essays on an inter-institutional academic project, cross-cultural learning experiences, and a multi-national healthcare project, demonstrating the importance of shared values, interdisciplinary negotiated process and clear communication for tomorrow’s designers

The NASA Astrophysics Data System: Architecture

The powerful discovery capabilities available in the ADS bibliographic services are possible thanks to the design of a flexible search and retrieval system based on a relational database model. Bibliographic records are stored as a corpus of structured documents containing fielded data and metadata, while discipline-specific knowledge is segregated in a set of files independent of the bibliographic data itself. The creation and management of links to both internal and external resources associated with each bibliography in the database is made possible by representing them as a set of document properties and their attributes. To improve global access to the ADS data holdings, a number of mirror sites have been created by cloning the database contents and software on a variety of hardware and software platforms. The procedures used to create and manage the database and its mirrors have been written as a set of scripts that can be run in either an interactive or unsupervised fashion. The ADS can be accessed at http://adswww.harvard.eduComment: 25 pages, 8 figures, 3 table

Management control systems across different modes of innovation: Implications for firm performance

© 2015 Elsevier Ltd. This study examines the use of management control systems (MCS) across different modes of innovation and the effects on firm performance. Specifically, this study draws on Simons' levers of control framework to investigate how top managers attempt to simultaneously balance exploration and exploitation, which place contradictory requirements on firms. Using data collected from a survey of top managers in 400 firms this study demonstrates that the patterns of use and interdependencies among control levers associated with enhanced performance differ depending on the mode of innovation. The findings show that control levers are independently associated with enhanced performance in firms that specialize in either exploration or exploitation, suggesting that levers operate as supplementary rather than as complementary controls in these contexts. However, in ambidextrous firms, diagnostic and interactive levers are shown to have interdependent effects on performance. Furthermore, some evidence suggests that both the combined and balanced use of these levers contributes to generating dynamic tension necessary for managing contradictory innovation modes

Missing Requirements Information and its Impact on Software Architectures: A Case Study

[Context & motivation] In the development of large, software-intensive systems, the system’s requirements are seldom, if ever, concluded upon prior to commencing with systems architecture. Research shows that, in order to manage development and domain complexities, instances of requirements engineering (RE) and systems architecting (SA) processes tend to inter-weave. [Question/problem] However, missing requirements information can cause one to create (or recreate) the needed information during different SA activities. While backtracking in the software development process is known to be costly, the costs associated with missing requirements in the SA process have not been investigated empirically. [Principal ideas/results] We thus conducted a case study where we investigated to what extent requirements or requirements attributes’ information found missing during the SA process and impact of those missing information on SA in terms of effort. The study involved five architecting teams that involve final year undergraduate and graduate students enrolled in the university course on SA, working on architecting a system falls under “banking” domain. Our result shows that, architects did find requirements and requirements attributes’ information missing while architecting. Among requirements information, architects found that, system functionality information, constraints information and system interaction (users/systems) information are missing in requirements at higher percentages. Within requirements’ attributes, architects found requirements priority, dependency and rationale missing at higher percentages. It is also found that, out of total time spent on architecting the system, effort given to recreate missing requirements information is higher for group3 (21.5%), group1 (18%), and group2 (17%) other than group4 (12.37%) and group5(10.18%). [Contribution] The anticipated benefits of the findings are, it can motivate researchers to venture into other areas of software engineering (such as coding, testing, maintenance, etc.) from the view point of missing requirements information and its impact on those areas. This knowledge could help software practitioners to decide what kind of information need to take care of, during RE process, that could possibly ease SA process and later development phases. To the best of my knowledge, this is the first work which focuses on, to what extent requirements and requirements’ attributes information found missing during SA; characteristics and impact of those requirements missing information on SA process in terms of effort