Professional Documents
Culture Documents
1177/1525822X08329697
WILLIE L. MCKETHER
University of Toledo
JULIA C. GLUESING
KENNETH RIOPELLE
Wayne State University
This article describes the process of discovery used to convert interview data into a for-
mat readable into MultiNet for social network analysis. Based on the 2005 doctoral dis-
sertation research of Willie McKether, the authors describe the steps used to collect and
store interview data in Microsoft Word, the preparation process for exporting the inter-
views to ATLAS.ti for coding, the coding process, and the conversion path that allowed
them to export the coded qualitative data from ATLAS.ti to SPSS and ultimately to
MultiNet for social network analysis. This study is significant because it describes a
replicable conversion technique that can be used by experienced scholars and those
unfamiliar with the range of network analysis programs and conversion possibilities.
OVERVIEW
whole networks and at the same time code for larger themes embedded in
their narrative data sets.
The various processes and network analysis programs that a population
of scholars uses to create network maps and generate network data can be
frustrating and daunting for social network newcomers. This is particularly
the case for qualitative researchers who use mostly ethnographic techniques
in their data collection strategies and want to examine networks embedded
in their narrative data, while at the same time, they want to retain and use
the narrative parts of their interviews, understanding that the various ways
of converting their data remain somewhat illusive. Although this duality in
data analysis is certainly not new, a structured approach to data analysis has
caught the attention of a growing number of researchers who use social net-
work analysis to examine qualitative data. This population of scholars
wants to pierce the veil of social structures and look inside the worlds of
their subjects to understand relationships; they not only want to examine
the valued relationships in their data, they also want to retain and examine
the context in which those relationships occurred.
Explicit and clear-cut descriptions of how researchers across disciplines
convert narrative interview data into a format readable into network analysis
programs are rarely found in methodological, focused scholarly literature.
There are some exceptions, including Schweizer’s (1991) study of political
reform in southern China in which he describes the processes used to examine
sixteen narrative interviews using UNICNET, SONIS, STRUCTURE, and
NETPAC; Bearman, Faris, and Moody’s (1999) study in which they describe
how they used PAJEK to examine fourteen life stories of Chinese villagers to
construct historical events related to agrarian revolts in a northern China; and
Mercer’s (2007) doctoral dissertation in which she describes the processes she
used to convert narrative data into a format readable into NETMINOR. But
few other studies explicitly describe the processes used to convert narrative
text into a format readable into social network programs.
These studies show that researchers have options when it comes to social
network programs and that there are many ways to reveal network data embed-
ded in narrative texts. These two important factors may account for the dearth
of articles that make conversion methods and techniques the primary topic of
discussion. Unlike the examples cited above, however, when specific conver-
sion processes are used for specific research questions and data sets and when
the processes are not explained so as to make them easily replicable for other
researchers, particularly for social network newcomers, the literature misses a
population that wants and needs to see the process as well as the end result.
Oral history programs are undertaken for various reasons, but typical rea-
sons are to fill the gap in a historical record or to document and preserve the
history of an individual, company, event, or time period (Sommer and Quinlan
2002:3). Ninety-six people were interviewed for the migration study. Each one
was asked the same set of open-ended questions in interviews that lasted not
more than 2 hours. Interviewees were also asked to provide specific names of
people, businesses, and organizations they had past relationships with and to
describe the nature of those relationships. Each person, for example, was
asked to provide the address (or cross streets) of where he or she lived either
growing up in Saginaw or on his or her arrival; who he or she lived with; the
names of his or her closest personal friends; the schools he or she attended;
the names of businesses he or she patronized; the names of people he or she
associated with in their fights for social, economic, and political justice; the
To convert the interviews into social network data using the process
described here, we used the following five software programs: Microsoft
Office Word, Excel 2003, ATLAS.ti 5.0; SPSS version 13, and MultiNet
version 4.44.1 The data conversion and processing involved five major
steps: (1) transcribing and storing interviews, (2) cleaning and preparing
data for importing into ATLAS.ti, (3) importing and coding the interview-
rich text files in ATLAS.ti, (4) creating the ATLAS.ti SPSS data extract,
and (5) creating an Excel MultiNet link file. Each of these steps is pre-
sented here in detail so that others can replicate the process in their own
studies.
The software programs—particularly ATLAS.ti., SPSS, and MultiNet—
were used because of their complementary functional features and because
of the authors’ years of experience with these programs. However, other
computer-assisted qualitative data analysis programs such as Ethnograph,
NVivo, and NUD*IST; statistical programs such as SAS; and network
analysis programs such as Pajek and UCINET can also be used.
FIGURE 1
Sample Microsoft Excel Comma Separated Node and Link Files
Figure 1 shows that ID1 and ID2 are the node IDs, indicating that ID1
has a relationship with ID2 in the format FROM ID1 TO ID2, with some
attribute, such as family member, friend, coworker, and so forth, repre-
sented by K33, K34 in the figure. The process for creating these files is
described later in the article.
FIGURE 2
Sample Microsoft Word Interview Folder
FIGURE 3
Relations Code File
Later in the process, these relations will be entered into ATLAS.ti as link
codes. This relation’s code file should not be confused with the linked data
file, which contains the FROM-TO ID numbers and a designated relation, as
depicted in Figure 1, called the comma separated variable MultiNet link file.
TABLE 1
Node File Numbering Scheme
Interviewees 001–096
Names of people mentioned in interviews 100–299; 700–1100
Names of churches 300–350
Church denominations 351–370
Names of organizations 400–450
Names of businesses 501–599; 670–699
Names of schools 601–659
Exporting data to ATLAS.ti. After all interviews were edited, cleaned, and pre-
pared in the first pass of reading and after node and relation codes were recorded
in Excel files in the second pass, the cleaned interview text documents were
imported into ATLAS.ti for coding and analysis. In ATLAS.ti terms, each of the
interviews became a primary document (PD) in a single ATLAS.ti hermeneutic
unit. Next, an ATLAS.ti code was created for every node and relation type with the
ATLAS.ti’s code manager, using the command “Create Free Code.”
ATLAS.ti code node format. The format used to create and enter nodes
is indicated below.
FIGURE 4
ATLAS.ti Node Codes
The “N_” at the beginning of the code name enabled nodes in ATLAS.ti to
be alphabetized in the code list and for them to be grouped together. As names
were added to the code list as nodes in ATLAS.ti, they were automatically
sorted in alphabetical order for easy reference. The “Lastname_Firstname”
format helped keep a clear distinction between the Lastname and Firstname.
See Sample ATLAS.ti Node Codes in Figure 4.
The “Lastname_Firstname” designations were nineteen characters or
less to meet MultiNet labeling limit requirements. The “_ID number” tag at
the end of the person’s name was the unique ID number assigned to a
person, place, or organization and allowed the list of nodes to be prepared
by ascending ID number in Excel. The “_” underscore formatting allowed
text columns to be easily parsed into text to columns and for sorting nodes
alphabetically by name and by ID number.
FIGURE 5
ATLAS.ti Link Codes
Similar to the node format, the “L_” at the beginning of the code name
enabled an alphabetical listing of Link relations in ATLAS.ti and kept them
grouped together. Additionally, as link relations were added to the link list
in ATLAS.ti, they were automatically sorted in alphabetical order for easy
reference. The “_ID number” tag at the end of the Link relation allowed the
list of all links to be prepared in ascending ID numbers in Excel. The “_”
underscore formatting allowed text to columns to be easily parsed in Excel
for sorting links alphabetically by name and ID number.
Coding the interview data for migration themes. In addition to the coding
for nodes and relations, the data were coded for the major themes in the oral
histories that described the migration experiences of the interviewees. A thor-
ough reading of the interviews produced the initial migration theme code list
in ATLAS.ti. To help with the coding process, a high-level word crunch fre-
quency was calculated in ATLAS.ti. The word crunch feature in ATLAS.ti
FIGURE 6
ATLAS.ti Code Family
provided a word count of all words used in the hermeneutic unit (all words
across all interview texts). Such an analysis allowed the initial code list to be
compared against the most frequently used words in all interviews as a check
to ensure the initial code list was representative at a high level of analysis with
major themes embodied in the interviews. Based on the word crunch analy-
sis, the initial code was revised to include minor themes not observed during
the first and second passes of reading the interviews.
The coding process was iterative and required several passes. To sim-
plify the coding process, the interviews were coded first using the interview
theme codes and then were coded using the node and link codes. Although
this process was slow and tedious, it helped ensure that both the qualitative
and quantitative objectives of the process received equal attention.
To facilitate the first pass of coding using the interview codes based on
major themes reflected in the eighty-eight interview codes, nine code
families were created in the ATLAS.ti program. See sample ATLAS.ti
code families in Figure 6 below. A code family is a feature in ATLAS.ti
that allows groups of codes to be classified under a single code or family
name.
The code families made the coding process much easier because the
codes in each of the families were generally based on the interview
questions, which were asked in a fairly similar sequence. The code families
therefore displayed the list of codes that roughly corresponded with por-
tions of the interviews that reflected those codes.
Coding nodes with relations. After the interviews were coded with the
interview theme code list, the interviews were coded using the node and
link relation codes. During this round of coding, as each interview was
read, every name, place, and organization was identified (hence, nodes),
and then the nature of the relationship determined and assigned an appro-
priate link relation. To assign a code or codes, a person’s name was high-
lighted and they were assigned the corresponding node code for that person
and then assigned one or more appropriate links to that node. The exact text
or quotation must be selected for both the node and the link because this
defines how ATLAS.ti will create its SPSS export data file. The text below,
for example, shows the friend relation (Link #052) interviewee HB (PD
002) has with William P. Wilson (Node 734).
FIGURE 7
SPSS Data File
FIGURE 8
MultiNet Link File
SPSS
Variable: PD K415 K67
Label: Primary Doc N_Wilson_734 L_Friend_052
creates an SPSS extract, it creates a variable called “PD,” which is the pri-
mary document number. In step 5, we will illustrate how to create a series of
SPSS statements to recode the ATLAS.ti PD numbers back to match the
original node numbers and thus establish MultiNet’s From or ID1 variable.
Likewise, all the ATLAS.ti node codes that are then created as SPSS
“K”_variables will be recoded to their originally assigned ID numbers to
become MultiNet’s TO or ID2 node variable.
/K33 'L_Aunt_011'
/K34 'L_Babysat_057'
/K35 'L_Barber_001'
/K36 'L_Beautician_002'
/K37 'L_Brother_007'
/K38 'L_BrotherinLaw_068'
/K39 'L_ChildhoodFriend_003'
/K110 'N_AFLCIO_Org_413'
/K111 'N_Aldridge_Katherine_029'
/K112 'N_Aldridge_William_050'
/K113 'N_Alinski_Sol_279'
/K114 'N_Allen_Bill_174'
BEGIN DATA.
0000100020001005700000026005700000031327097572300000000000000000 . . .
Note all the link relation codes will be grouped together as well as the
node codes.
IF PD = 2 ID1 = 1.
IF PD = 3 ID1 = 2.
IF PD = 4 ID1 = 3.
IF PD = 11 ID1 = 4.
This process, in effect, creates the MultiNet ID1 or FROM Node in the
Link File.
For example, if the ATLAS.ti PD represented by the SPSS variable PD
is equal to 2, then set the SPSS variable ID1 to be equal to 1. Thus, the
ATLAS.ti PD numbers are recoded to match the originally assigned Node
ID numbers.
Next create a series of SPSS IF statements to create the MultiNet ID2 or
TO node in the link file.
For example, K110, which is the ATLAS.ti created SPSS variable for the
node AFLCIO, will be recoded to match its originally assigned Node ID of
413. Thus, the ATLAS.ti/SPSS node variable numbers are recoded to match
the originally assigned node ID numbers.
Next, add a select statement to select just the records with ID2 greater
than 0. The purpose of this is to select only nodes that do have a link rela-
tion with another node.
USE ALL.
COMPUTE filter_$=(id2 > 0).
VARIABLE LABEL filter_$ 'id2 > 0 (FILTER)'.
VALUE LABELS filter_$ 0 'Not Selected' 1 'Selected'.
FORMAT filter_$ (f1.0).
FILTER BY filter_$.
This “Translate” command creates an Excel file with the FROM or ID1
variable and the ID2 or TO variable along with all relations or “K” variables
that are defined. There are now the two MultiNet network files necessary
for social network analysis: the NODE file with the IDs and names of the
nodes and the link file with the FROM TO IDs and the corresponding rela-
tions. See sample MultiNet files in Figure 9. In the link file variable ID1
(from node) values are the PD numbers matched to the assigned ID
numbers. The variable ID2 (to node) values are the node code numbers. The
link relation variables K33 (e.g., Friend) and so forth are 0 = No, 1 = Yes.
Because MultiNet will not read in labels that exceed nineteen characters,
each node label must contain less than that. Finally, the Excel files must be
edited to add the appropriate MultiNet header information, such as “begin
data” commands. After these edits are made to the Excel files, they can be
imported into MultiNet social network analysis.
Sample data analysis. To show how the conversion process works, we use
five sample interviews from the original data set to show how ego network
maps can be used individually as well as part of a whole network map.
Informants in the sample subset were part of the Saginaw cohort in that they
were either born in Saginaw or moved there with their parents between 1921
FIGURE 9
Sample MultiNet Node and Link Files
TABLE 2
Sample Demographics
and 1940. Each interview was conducted separately and at different times
throughout the study. See sample set demographics in Table 2.4
We selected this subset for two reasons: (1) The individuals had family
and friend relationships that spanned across several generations; and (2)
their network maps show how particular people or institutions were essen-
tial in bridging the social gap between African Americans in the racially
and geographically segregated community. All but one of the informants
grew up on the west side of the racially segregated city.
FIGURE 10
Ward Map of City
A DIVIDED CITY
Census and interview data revealed that Saginaw was a racially divided
city. Figure 10 is a ward map of the city and reflects how space was used to
keep the African American population segregated from other residents.
The Saginaw River runs through the heart of the city and separates it
both geographically and racially. With few exceptions, African Americans
lived in wards (indicated by the numbered boxes) on the east side of the
river, whereas whites lived almost exclusively in wards on the west side of
the river.
Census data in Table 3 illustrate that race-based residential segregation
increased as the African American population increased in Saginaw.
The data show, for example, that in 1920, 16% (fifty-four) of the 328
African Americans in Saginaw lived in wards on the west side of the city.
However, by 1940, only 2% (seventy-eight) of the city’s 3,315 African
Americans lived on the west side of Saginaw. African Americans in Saginaw
did not choose to segregate themselves; rather, as the African American pop-
ulation increased over time, so did efforts by white resistance groups, realtors,
and lending institutions to keep the growing African American population
confined to particular areas and wards of the city (McKether 2005).
TABLE 3
East–West-side Populations for Selected Years
Years
SOURCES: Thirteenth Census, 1910, vol. II, pp. 954–955; Fourteenth Census, 1920, vol. II,
p. 500; Fifteenth Census, 1930, vol. III, part 1, p. 1179; Sixteenth Census, 1940, vol. II, part
3, p. 859; Seventeenth Census, 1950, vol. II, part 22, pp. 22–81; Eighteen Census, 1960, vol.
1, part 24, pp. 24–82.
FIGURE 11
Generational Network Map
FIGURE 12
School Network Map
families on the west side of the city all had light skin. Understanding these
nested social relations clarified how the network allowed them to survive liv-
ing on the predominately white west side of the Saginaw River.
Social Ties among Migrants: The Role of Social Clubs and Church
Network maps based on the interviews also showed that parents of the sam-
ple Saginaw cohort established friendship bonds through social activities and
that some parents played a central role in linking families across the divided
community. For example, in response to the open-ended interview question,
“What did families do socially?” several members of the sample Saginaw
cohort indicated that families, mothers in particular, socialized and established
close friendship bonds through church affiliation and a local group known as
the Baker’s Dozen. The latter was a group of women who sponsored social
events in Saginaw and congregated to socialize and play bridge.
Figure 13 depicts a network map of the Baker’s Dozen and shows that
both Cleo Bowman and Gayle Browne-Terry said their mothers belonged
to the Baker’s Dozen social group. In their individual interviews, each pro-
vided the names of other mothers who belonged to the social group that
Gayle Browne-Terry characterized as “like extended family.”5 In addition,
this network map shows that the Baker’s Dozen group was composed of
FIGURE 13
Baker’s Dozen Network Map
African American women from both sides of the Saginaw River. For
example, Gayle Browne-Terry said that her mother, Stella Mumford, her
aunt, Minrose Browne, and Marie Claytor, all of whom lived on the city’s
east side, belonged to the Baker’s Dozen. In a separate interview, Cleo
Bowman indicated that her mother, Carrie Nash, as well as Gale Porterfield
(mother of Richard Porterfield and close friend of Stella Mumford) also
belonged to the social club.
The Baker’s Dozen network map is significant because it shows that
although African Americans were geographically segregated from one
another, parents fostered and maintained friendship relationships through
social organizations. The oral history interviews elaborated the context of
the network and provided the insight about how social conditions led to
friendships among the migrants’ children.
FIGURE 14
Childhood Friend Network Map
Based on responses to the interview question, “Who was your best child-
hood friend?” Figure 14 represents a childhood friendship network map. It
reveals that children of migrants, several of whose parents belonged to the
Baker’s Dozen, also became friends as children. The childhood friendship net-
work map, in particular, shows that Gayle Browne-Terry was a central node
(person) in the childhood network that spanned both sides of the Saginaw
River. In her interview, Gayle Browne-Terry, herself an east-sider, said that her
best childhood friends were east-siders Elinor and Carol Claytor (daughters of
Baker’s Dozen Marie Claytor) and west-siders Beverly and Barbara Bowman
(granddaughters of Baker’s Dozen Carrie Nash and daughters of Cleo
Bowman). Browne-Terry also said that cohort member Richard Porterfield
was one of her best childhood friends. In turn, Richard Porterfield said that
Cleo (Nash) Bowman and Charles Bowman were his best childhood friends.
This sample data set and analysis show that the process we used to
generate individual and whole network maps can increase the analytic
depth of interview data. Significantly, because the process allowed us to
code each interview for relationship as well as major themes embedded in
each of the interviews, we were able to capture data that could be read into
social network programs. Importantly, the process also allowed us to use
narrative portions of the same interview to provide context for the relation-
ships embedded in the data.
NOTES
1. Network maps for this article were generated with an older version (4.44) of MultiNet,
which was the most recent version available when we wrote the article. Since then, several
important updates have been made to MultiNet (now version 5.4), including the following: (1)
The nineteen-character limitation has been eliminated, allowing for node and link names to be
more descriptive; (2) a single Excel file containing both node and link data can be used to
import node and link data instead of two files; and (3) MultiNet version 5.4 now has an export
utility to convert files into the Negopy format that can be read by UCINET, thus making it eas-
ier to move data from one network analysis program to another.
2. Sample data files showing how the process works can be downloaded at Willie
McKether’s Web site at http://homepages.utoledo.edu/wmcketh/social.network.analysis.htm.
3. Kenneth Riopelle and Julia Gluesing at Wayne State University discovered and wrote the path.
4. All the interviewees signed a public disclosure form allowing their names and interview
transcripts to be held in the public domain. All interviews are part of a public library collec-
tion in Saginaw, Michigan.
5. G. Browne-Terry, personal communication, July 24, 2003.
REFERENCES
Bearman, P., R. Faris, and J. Moody. 1999. Blocking the future: New solutions for old prob-
lems in historical social science. Social Science History 23 (4): 501–33.
McKether, W. L. 2005. Voices in transition: African-American migration to Saginaw,
Michigan: 1920 to 1960. PhD diss., Department of Anthropology, Wayne State University,
Detroit.
Mercer, D. 2007. The informal transfer of tacit knowledge among municipal managers in
coordination situations. Ph.D. dissertation. University of Montreal.
Schweizer, T. 1991. The power struggle in a Chinese community, 1950–1980: A social net-
work analysis of the duality of actors and events. Journal of Quantitative Anthropology
3 (1): 19–44.
Sommer, B., and M. Quinlan. 2002. The oral history manual. Walnut Creek, CA: AltaMira.