Short Description:
This short guidebook provides information about selecting a research topic and research questions, searching for literature, reading and understanding scholarly writing, and writing a literature review to synthesize what is known and what remains to be learned about a social problem. For students who appreciate the availability of resources on the internet, it also provides links to additional materials. It can be used with its companion textbook, Foundations of Social Work Research by Rebecca L. Mauldin and Matthew DeCarlo, or as a stand-alone guide.

Long Description:
As an introductory textbook for social work students studying research methods, this book guides students through the process of writing a literature review and determining research questions for a research project. Students will learn how to discover a researchable topic that is interesting to them, examine scholarly literature, and write a literature review. The guidebook is aligned with the Council on Social Work Education’s 2015 Educational Policy and Accreditation Standards. Students and faculty can download copies of this guidebook using the links provided in the front matter. As an open textbook, users are free to retain copies, redistribute copies (non-commercially), revise the contents, remix it with other works, and reuse for any purpose.

Word Count: 31630

ISBN: 978-1-64816-992-2

(Note: This resource's metadata has been created automatically by reformatting and/or combining the information that the author initially provided as part of a bulk import process.)

Background The recent emergence of the 2009 pandemic influenza A/H1N1 virus has highlighted the value of free and open access to influenza virus genome sequence data integrated with information about other important virus characteristics.

Design The Influenza Research Database (IRD, http://www.fludb.org) is a free, open, publicly-accessible resource funded by the U.S. National Institute of Allergy and Infectious Diseases through the Bioinformatics Resource Centers program. IRD provides a comprehensive, integrated database and analysis resource for influenza sequence, surveillance, and research data, including user-friendly interfaces for data retrieval, visualization and comparative genomics analysis, together with personal log in-protected ‘workbench’ spaces for saving data sets and analysis results. IRD integrates genomic, proteomic, immune epitope, and surveillance data from a variety of sources, including public databases, computational algorithms, external research groups, and the scientific literature.

Results To demonstrate the utility of the data and analysis tools available in IRD, two scientific use cases are presented. A comparison of hemagglutinin sequence conservation and epitope coverage information revealed highly conserved protein regions that can be recognized by the human adaptive immune system as possible targets for inducing cross-protective immunity. Phylogenetic and geospatial analysis of sequences from wild bird surveillance samples revealed a possible evolutionary connection between influenza virus from Delaware Bay shorebirds and Alberta ducks.

Conclusions The IRD provides a wealth of integrated data and information about influenza virus to support research of the genetic determinants dictating virus pathogenicity, host range restriction and transmission, and to facilitate development of vaccines, diagnostics, and therapeutics.

(This case study was added to OER Commons as one of a batch of over 700. It has relevant information which may include medical imagery, lab results, and history where relevant. A link to the final diagnosis can be found at the end of the case study for review. The first paragraph of the case study -- typically, but not always the clinical presentation -- is provided below.)

A 70-year-old man presented with a 10-month history of worsening cognition, speech impairment, ataxia, and dysphagia, as well as periodic episodes of brachial dystonia, choreiform movements, and facial grimacing. EEG studies were negative. MRI studies, including arterial spin labeling, showed only hyperperfusion of the right mesial temporal lobe. FDG-PET showed diffuse cortical hypometabolism (Figure 1A, white arrows) and relatively increased metabolism in the amygdala (Figure 1A, yellow arrows) and striatum (Figure 1A, orange arrow) bilaterally. Imaging studies of the chest, abdomen, and pelvis were negative. Despite therapy, the patient's disease proved refractory and he expired. A brain-only autopsy was performed 16 months following his initial presentation.

The focus of this book is on using quantitative research methods to test hypotheses and build theory in political science, public policy and public administration. It is designed for advanced undergraduate courses, or introductory and intermediate graduate-level courses. The first part of the book introduces the scientific method, then covers research design, measurement, descriptive statistics, probability, inference, and basic measures of association. The second part of the book covers bivariate and multiple linear regression using the ordinary least squares, the calculus and matrix algebra that are necessary for understanding bivariate and multiple linear regression, the assumptions that underlie these methods, and then provides a short introduction to generalized linear models.

The book fully embraces the open access and open source philosophies. The book is freely available in the SHAREOK repository; it is written in R Markdown files that are available in a public GitHub repository; it uses and teaches R and RStudio for data analysis, visualization and data management; and it uses publically available survey data (from the Meso-Scale Integrated Socio-geographic Network) to illustrate important concepts and methods. We encourage students to download the data, replicate the examples, and explore further! We also encourage instructors to download the R Markdown files and modify the text for use in different courses.

This lesson is part of the Software Carpentry workshops that teach how to use version control with Git. Wolfman and Dracula have been hired by Universal Missions (a space services spinoff from Euphoric State University) to investigate if it is possible to send their next planetary lander to Mars. They want to be able to work on the plans at the same time, but they have run into problems doing this in the past. If they take turns, each one will spend a lot of time waiting for the other to finish, but if they work on their own copies and email changes back and forth things will be lost, overwritten, or duplicated. A colleague suggests using version control to manage their work. Version control is better than mailing files back and forth: Nothing that is committed to version control is ever lost, unless you work really, really hard at it. Since all old versions of files are saved, it’s always possible to go back in time to see exactly who wrote what on a particular day, or what version of a program was used to generate a particular set of results. As we have this record of who made what changes when, we know who to ask if we have questions later on, and, if needed, revert to a previous version, much like the “undo” feature in an editor. When several people collaborate in the same project, it’s possible to accidentally overlook or overwrite someone’s changes. The version control system automatically notifies users whenever there’s a conflict between one person’s work and another’s. Teams are not the only ones to benefit from version control: lone researchers can benefit immensely. Keeping a record of what was changed, when, and why is extremely useful for all researchers if they ever need to come back to the project later on (e.g., a year later, when memory has faded). Version control is the lab notebook of the digital world: it’s what professionals use to keep track of what they’ve done and to collaborate with other people. Every large software development project relies on it, and most programmers use it for their small jobs as well. And it isn’t just for software: books, papers, small data sets, and anything that changes over time or needs to be shared can and should be stored in a version control system.