The researcher used an inductive process, seeking out details and discovering patterns as they emerged throughout the electronic portfolio process. Technical background and attitudes toward technology, as reported in the computer literacy questionnaire, were compared to student perceptions of the portfolio process. The process of designing the portfolio was investigated from the perspective of the course professor and the research designer to determine strengths and weaknesses in organization and presentation. Technological processes within the real-life context of a college computer lab were examined for problematic hardware and software issues. The electronic portfolio process was described and analyzed on an individual basis with no clear set of anticipated outcomes.
This study was exploratory in nature, attempting to promote further understanding of an innovative technology. The technical background of the individuals participating in the project was diverse, requiring non-standardized methods of investigation (Patton, 1980, p. 88). Strengths and weaknesses of the process and technical problems encountered by the participants varied according to the individual's background and interest in technology. Lincoln and Guba (1985) discussed the use of qualitative methods as being adaptable when dealing with multiple realities. Participants in this study represented multiple realities in terms of attitude toward and expertise in technology.
Detailed information was obtained through the participant’s descriptions to further understand and improve the process of creating electronic portfolios. The researcher interacted closely with some of the students involved in the study. The researcher observed and actively assisted personally in portfolio preparation within the lab setting with the first group of participants. The study was guided by the following questions:
1. What effect does incorporating technology have on the development of a portfolio for teacher candidates?
2. To what extent does the electronic portfolio process encourage self-assessment and reflection?
3. In what ways does the electronic portfolio provide evidence of student learning and achievement in line with course objectives?
4. What are the problems encountered in putting together the portfolio electronically?
5. What do students perceive as the strengths and/or weaknesses of creating a portfolio electronically?
6. What are the course professor's perceptions concerning the effectiveness of the electronic portfolio as a tool for assessment?
Previous to this study, the paper portfolio binder had been established as the primary assessment for the reading methodology course in this university teacher preparation program. Students were expected to collect paper documents, photographs, graphic examples, and audio-visual artifacts as evidence of meeting course objectives. Providing evidence of reflective practice was considered a significant component of the portfolio process. The electronic portfolio provided a computer framework for documenting the meeting of course criteria and providing evidence of self-reflection and self-assessment. A template was designed to accommodate the use of digital text, graphics, audio, and video files in order to provide multimedia evidence of the achievement of course objectives. Students wrote cover sheet reflections explaining, describing, and defending the artifacts they chose as evidence of their achievement.
The electronic portfolio project was constantly evolving
during the course of this study due to revisions in state credential standards
and adjustments made because of technical problems. The initial template
was presented to the first group of students in an interactive web design
based on hypertext markup language (HTML). The course objectives were linked
directly to state certification standards on the World Wide Web (WWW).
After determining that some students considered the web design complicated
and confusing, the researcher created a second alternative template using
an interactive multimedia authoring program, Hyperstudio. The software
featured tools for inserting text boxes, graphics, audio, and video, as
well as provide interactive functions which allowed for linking within
the program, to other software programs, and to the internet. The second
semester course objectives were modified to incorporate revised state certification
standards and the implementation of Reading Instruction Competency Assessment
(RICA).
In addition, the course professor and the computer lab
technician were asked to provide observational data, opinions, and insights
into the portfolio process through interviews, phone conversations, and
e-mail correspondence. A field journal was kept in order to provide an
historical record of the researcher's involvement in the process of developing
templates for the multimedia computer portfolio. The researcher provided
a narrative of significant developments, changes, and problems that occurred
during the study. E-mail correspondence between the course professor and
the researcher was analyzed to provide additional historical data. The
researcher provided additional technical help and advice within the computer
lab setting, as well as through e-mail correspondence with some of the
participants.
Open-ended interviews with volunteer student participants were conducted after the completion of the course portfolio by the researcher (see Appendix B). A flexible question guide was followed and responses were audio-taped and transcribed. Interviews, which lasted approximately 30 to 45 minutes, were conducted after the student completed the reading methods course. The one on one interview was scheduled at the participant’s convenience and was held on campus in an available school of education classroom. The interviewer took notes during the course of each interview and asked for responses to be clarified or expanded upon when it was considered useful to the study. Additional responses or clarification were accomplished through e-mail correspondence. The researcher initially explained the purpose of the interview and requested permission to tape the interview. The researcher attempted to remain open to issues of personal interest to the participant and ask questions to further develop emerging topics and patterns. Participants were encouraged to expand upon the interview questions and talk about their experiences openly and freely. All interview text was imported into the qualitative software package, Ethnograph (Seidel, 1998), for analysis.
Electronic portfolios were examined after the participants had completed the course and had received their course evaluations from the professor. Portfolios of all participating students were collected on a zip disk and transferred to a CD-ROM disk. Student generated reflective cover sheet texts within the electronic portfolio framework were imported into the qualitative software for analysis along with interview and e-mail text. The cover sheet texts were examined primarily for evidence of self-reflection and self-assessment. Texts from the portfolios were examined for reference to personal perceptions and attitudes toward the electronic portfolio project. The researcher made no attempt to evaluate the quality of the electronic portfolio artifacts as assessment in reference to the achievement of course objectives.
An open-ended e-mail interview with the course professor was conducted after the portfolio project was completed (Appendix D). The course professor was asked about her expectations for the electronic portfolio project and her reasons for using technology in teacher preparation. She was asked to describe design changes and technical adjustments made during the course of the project. She described how she assessed the portfolio products and what she perceived student attitudes to be throughout the portfolio process. Adjustments in software design, as well as curricular changes in the portfolio format, were documented throughout the study. Data on the initial design phase of creating a template for the electronic portfolio organized around course objectives was obtained through e-mail correspondence and records of informal conversations with the course professor. A research journal was used to record field procedure notes. Throughout the study, the researcher kept a thorough narrative of the technical processes, the problems that occurred with software and hardware, the changes made to improve the templates and electronic resources, and the course revisions made for subsequent terms. In addition, a semi-structured interview with the computer lab technician was taped and transcribed.
An informed consent form was provided for everyone participating
in the study (Appendix E). Participants were
granted the right to withdraw from the study at any time. Interview participants
received a CD-ROM of their electronic portfolio for helping provide their
perspective on the portfolio experience. Data obtained throughout this
study was collected and saved in digital format in order to be used as
evidence in a multimedia computer presentation.
The data analysis software package, Ethnograph, v. 5.0 (Seidel, 1998), was used to manage narrative documents and transcripts, allowing for storing, browsing, indexing, and coding of all text. Ethnograph allowed the researcher to explore documents and search for patterns and themes that emerged from the text. As the data was explored, text annotations were coded and an index system was established. Data for this study included research questions, emerging ideas, categories of people, interview text, field notes, e-mail responses, open-ended questions, portfolio analysis text, and other documents related to the electronic portfolio project. Search tools within the software were used to link, explore, and ask questions in order to determine relationships and establish hierarchies within the data.
Transcriptions of the interviews from all participating students provided the text for the initial coding and indexing of data. Other text imported into the software program included student generated cover sheet text from within the portfolios, as well as text from the researcher’s e-mail and research journal. Text from interviews and e-mail correspondence with the course professor and the computer lab technician provided additional data. Most of the data was imported from Microsoft Word documents, although some of the cover sheet text was taken directly from the text of the Hyperstudio portfolios. The Ethnograph editor’s reformat function was used to convert data files into the 40 character, hanging indent format required by the software for analysis. Additional preparation of the data was made by editing the text to include identifiers which were followed by a colon (:) and contextual comments which followed the plus (+) sign.
Imported text from a student interview is presented in the following example (Figure 1). The student’s name, as well as the key terms from the interview questions, are contextual comments following the plus (+) sign. "CP1:" refers to the researcher asking the first question and the "Q1:" refers to the student’s answer. "CP1a:" refers to a follow-up question to clarify the student response.
Figure 1. Example of interview text from Ethnograph.
+Lisa – Interview – Fall Group
In addition to interview text, the cover sheet text was imported for analysis. The electronic portfolio framework was designed to give students an opportunity to include artifacts as evidence of achieving course objectives. For each objective, students prepared a cover sheet providing support for their choice of artifacts as evidence of their competence in meeting established criteria. Students reflected upon each course objective and assessed their proficiency in each area. Once the cover sheet reflections were imported into Ethnograph, an additional parent code for teaching was added to the family tree structure to accommodate expanded discussion of literacy, learning, curriculum, and instruction.
Determination of the coding hierarchy remained flexible throughout the study. The level one parent code words were based on the following themes:
Table 1. Key Terms for Interview Questions in Relationship to Original Parent Code Words
|
|
|
|
#1 Process
#3 Methods #7 Time #12 Enjoyable #13 Advice |
#2 Evidence
#8 Resources #14 Improve #15 Paper |
#4 Purpose
#5 Objectives #16 Self-reflect and Self-assess |
#6 Unable
#9 Skills #10 Support #11 Problems |
Table 2. Primary Coding System
|
|
|
|
|
Approach
Methods Need Help Advice Attitude
Decisions |
Content
Packet Paper Portfolios |
Evidence
Objectives Goals Competence Proficiency
Personal Purpose Fulfill Reflect Criteria Sense |
Experience
Background Platform
Internet/Web Problems Programs
Strength Technical Use in Teaching Multimedia |
Literacy
Research Resources Standards Strategies Theory Curriculum 2nd Language Community Learning Style Lessons Literature Meaning Reading RICA Special Needs With Technology Phonics Influence Teaching Child Assess Class Management |
Table 3. Words Used in the Coding of Student Attitudes
|
|
|
|
Accomplish
Appreciate Confident Easy Faster Final Product Artistic Creative Energy Game Good Job Helpful Motivated Patience Success Personal Aesthetic |
Difficult
Frustrated Intimidate Irritate Not Comfortable Problems Time Consuming Scared Stress Lack of Background Worry Technical Problems Need Training |
Change
Do Again Help in Job Prep in Teaching Responsible |
Comfortable
Excited Enjoyable Fun Happy Pleased Proud |
Figure 2. Example of coded segment of text file.
+Barbara - Interview - Spring Group 1
Figure 3. Code counts for references to technical processes.
Code Word | Count | Code Word | Count | Code Word | Count | Code Word | Count |
HOST |
1
|
OWNER |
2
|
ARTISTIC |
4
|
EASY |
8
|
APPROACH |
1
|
DECISIONS |
2
|
FUN |
4
|
RECORD |
8
|
EVIDENCE |
1
|
TECHBACK |
2
|
WEBSITE |
4
|
VIDEO |
9
|
PRODUCT |
1
|
KIDSBOOK |
2
|
LABTECH |
4
|
PICTURES |
9
|
HAPPY |
1
|
TECHLOGIST |
2
|
CREATIVE |
4
|
DISKS |
10
|
READLANG |
1
|
ASSIGNMENT |
2
|
SAVEFILE |
4
|
BUTTONS |
10
|
ACCOMPLISH |
1
|
SUCCESS |
2
|
FIRSTEXP |
4
|
ORGANIZE |
10
|
ASSESS |
1
|
RESOURCES |
2
|
IMPORT |
4
|
PACKET |
11
|
CONTENT |
1
|
2
|
IMPROVE |
4
|
SKILLS |
11
|
|
SCARED |
1
|
DESIGN |
2
|
ELECTRONIC |
4
|
LINK |
12
|
WEBACCESS |
1
|
TEMPLATES |
2
|
LAB/LRC |
4
|
ZIP |
12
|
RNNINGREC |
1
|
TECHNOLOGY |
2
|
SOLVE |
5
|
PROBLEMS |
15
|
PROFESSOR |
1
|
RICA |
2
|
IBM/WIN |
5
|
HYPER |
15
|
EXPLORE |
1
|
CAPTURE |
2
|
PUTOGETHER |
5
|
TRANSFER |
20
|
ENJOYABLE |
1
|
NOTES |
3
|
MAC |
5
|
CUT/PASTE |
30
|
PREPTEACH |
1
|
TEXT |
3
|
HOME |
5
|
TYPE |
30
|
TEACHEXP |
1
|
PROCESS |
3
|
HTML |
5
|
TECHNICAL |
36
|
INCORPORAT |
1
|
TYPETEXT |
3
|
ARTIFACTS |
5
|
SCANNED |
68
|
LEARN |
1
|
ANIMATE |
3
|
OBJECTIVES |
5
|
||
STRATEGIES |
1
|
FRUSTRATED |
3
|
GRAPHICS |
6
|
||
SIMPLE |
1
|
OTHERCLASS |
3
|
REFLECT |
6
|
||
DIFFICULT |
1
|
DRAWING |
3
|
INTERNET |
6
|
||
COMPKNOW |
1
|
PROGRAMS |
3
|
COPY |
6
|
||
TRAINING |
1
|
USEINTEACH |
4
|
COLLECT |
7
|
||
POSITIVE |
2
|
WORDPROCES |
4
|
AUDIO |
8
|
||
COMPCLASS |
2
|
OTHERS |
4
|
TIME |
8
|
Combined searches for code words provided specific information in reference to files and lines each imported transcript. An example of a combined search for the code word, "experience," is provided in Figure 4.
Figure 4. Combined search results for experience code word.
Combined Search Results Search Code EXPERIENCE
Figure 5. Example of summary output of advice code word.
PLAY | ADVICE | LISA |
1
|
304
|
306
|
3
|
3
|
STARTEARLY | ADVICE | LISA |
1
|
313
|
314
|
2
|
5
|
PLANAHEAD | ADVICE | LISA |
1
|
314
|
332
|
19
|
24
|
ADVICE | ADVICE | PAULA |
1
|
244
|
249
|
6
|
6
|
STARTEARLY | ADVICE | PAULA |
1
|
244
|
245
|
2
|
8
|
IMMERSE | ADVICE | PAULA |
1
|
245
|
249
|
5
|
13
|
Frequency data for the code word, " assessment," generates a report as it appears in Figure 6. The count for each file is stated along with the percent across all files (top number) and the percent within the file (bottom number).
Figure 6. Example of frequency count for assessment code word.
File:LISA
Figure 7. Example segment output of aesthetic code word.
With Kids-Parent = AESTHETIC
Triangulation of multiple data sources involved comparing the perspectives of people from different points of view, particularly the student participants, the course professor, the computer lab technician, and the researcher (Patton, 1980, pp. 330-331). Participants in the study were asked to review findings and give feedback during the course of the study in an effort to validate the accuracy of the information and determine whether it matches reality (Merriam, 1988). Member checks were conducted throughout the study through telephone, e-mail, and postal correspondence in order to clarify any conflicting statements or confusing data.
An audit trail was established and maintained to facilitate
an external audit to establish levels of dependability and confirmability
of this study (Lincoln
and Guba, 1985). This research conformed to the audit trail classifications
made by Halpern (1983)
in an attempt to provide reliability and enhance dependability (Cited in
Lincoln and Guba, 1985, pp. 382-392). Raw data was collected and sufficient
evidence was provided concerning data reduction and analysis. Data reconstruction
and synthesis established hierarchies of concepts and categories. Process
notes were maintained; intentions and dispositions were recorded; and valid
instruments were developed. The audit trail included audio-tapes of interviews,
transcriptions of interviews, hard copies of all documents coded by the
qualitative software package, including e-mail correspondence and text
from the researchers diary. Data imported into the software package, Ethnograph,
resulted in the generation of the following documents: the research codebook,
individual code counts, and code searches using segment, summary, and frequency
outputs.
An assumption in this study was that all participants answered interview questions about their perceptions and actions truthfully, freely, and frankly. It was assumed that the interviews, observations, and collection of electronic portfolios provided a complete and useful database of information upon which interpretations and conclusions could be drawn.
Limitations of the study included the lack of generalizability of findings beyond the specific research setting. The transferability of the research findings to another situation cannot be validated, although providing sufficient information might make findings applicable to a new situation depending on the degree of similarity (Lincoln and Guba, 1985). The reliability of this study was limited because it would be impossible to replicate in another context.
An additional limitation of the study related to the objectivity
of the researcher. Patton
recommended "empathic neutrality" (1980, p. 55). He stated that empathy
"is a stance toward the people one encounters, while neutrality is a stance
toward the findings" (1980, p. 58). He stated that the neutral researcher
needs to be non-judgmental while trying to report what is found in a balanced
way. This study was limited because participation in this study was completely
optional and voluntary. Data obtained from the students who volunteered
to be interviewed and willingly agreed to have their portfolios analyzed
may not be representative of an entire class of teacher candidates.
Copyright 1999 by Carla Hagen Piper