04.10.2014 Views

1 GRADUATE COUNCIL MEETING 9 May 2012 102 Kern Graduate ...

1 GRADUATE COUNCIL MEETING 9 May 2012 102 Kern Graduate ...

1 GRADUATE COUNCIL MEETING 9 May 2012 102 Kern Graduate ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

APPENDIX B, PAGE B1<br />

Proposed Revision of <strong>Graduate</strong> Council Policy on Doctoral Committees<br />

Background and Justification<br />

The current policy on doctoral committees, which was revised most recently in <strong>May</strong> 2011,<br />

includes a requirement for an Outside Field Member to serve on each doctoral committee. The<br />

Outside Field Member is intended to represent another field (outside the student’s major field) to<br />

provide a broader range of disciplinary perspectives and expertise. This requirement can be met<br />

by any number of criteria, including membership in another graduate program; formal<br />

training/highest degree in another field; research expertise based upon record of scholarly work<br />

in another field; etc., and has no basis in budgetary relationship.<br />

After the revised policy was implemented, The <strong>Graduate</strong> School Dean’s Office and <strong>Graduate</strong><br />

Enrollment Services fielded many queries from programs regarding the interpretation of “outside<br />

the student’s major field,” which eventually led to a request for a formal interpretation by the<br />

Committee on Academic Standards.<br />

The Committee did not intend to change the current policy, but simply wished to establish a<br />

standard method for interpreting and operationalizing the policy (with nearly 200 graduate<br />

programs, including an increasing proportion of multidisciplinary and intercollege programs, an<br />

effective policy that can be implemented is especially critical). However, the Committee noted<br />

that two different ideals consistently are advanced for doctoral committee membership: 1) The<br />

first is intellectual and served by the Outside Field Member, whereby a different, or “outside,”<br />

perspective from the student’s major field is brought to a student’s dissertation committee so as<br />

to enrich the student’s research and professional development. 2) The second is protective,<br />

intended to prevent/discourage potential conflicts of interest that may be based on any number of<br />

underlying factors ranging from power imbalances between an untenured, junior faculty member<br />

from the same administrative unit as a senior, tenured faculty member, to personal relationships<br />

between the student’s advisor and another member of the committee. This second role is not<br />

addressed by the Outside Field Member.<br />

In order to reasonably achieve these two different but equally important ideals, the Committee<br />

decided that designating two different positions for doctoral committees would be both fair and<br />

comprehensive: the Outside Field Member (as it exists in the current policy) and an Outside Unit<br />

Member, whose primary appointment would be from a different administrative unit than that in<br />

which the student’s dissertation advisor holds his/her primary appointment. With respect to these<br />

two committee positions:<br />

• The graduate program would have considerable latitude over the designation of the<br />

Outside Field Member. The member of the <strong>Graduate</strong> Faculty serving in this role, and the<br />

field that he/she would represent that is outside of the student’s major, would be listed on<br />

the committee appointment form, and could qualify as representing another field through<br />

any number of means (graduate degree in another field; research expertise demonstrated<br />

through scholarly record; membership in the graduate faculty of another doctoral<br />

program, different from the student’s major; etc.).

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!