Who We Are

 


In this section you will find information describing the history of MERLOT and the active staff and volunteers who build, support, and contribute to MERLOT's success.  Full time staff are supported by active volunteers who participate in day-to-day activities that benefit the MERLOT community.
 
For details, please select one of the following:
MERLOT History - How MERLOT got started
MERLOT Staff - Current staff and positions
MERLOT Volunteers - MERLOT volunteer structure
Editorial Boards - Who supports MERLOT's academic disciplines?
Project Directors - What is the role of a MERLOT Partner and Project Director?
MERLOT Partners - MERLOT has many partners including System, Campus, Corporate and Organization partners.
 
 

MERLOT History

The MERLOT project began in 1997, when the California State University Center for Distributed Learning (CSU-CDL at www.cdl.edu) developed and provided free access to MERLOT (www.merlot.org). Under the leadership of Chuck Schneebeck, CSU-CDL's Director, MERLOT was modeled after the NSF funded project, "Authoring Tools and An Educational Object Economy (EOE)". Led by Dr. James Spohre and hosted by Apple Computer, and other industry, university, and government collaborators, the EOE developed and distributed tools to enable the formation of communities engaged in building shared knowledge bases of learning materials.
 
In 1998, a State Higher Education Executives Organization/American Productivity and Quality Center (SHEEO/APQC) benchmarking study on faculty development and instructional technology selected the CSU-CDL as one of six best practices centers in North America. Visitations to the CSU-CDL by higher education institutions participating in the benchmarking students resulted in interest in collaborating with the CSU on the MERLOT project. The University of Georgia System, Oklahoma State Regents for Higher Education, University of North Carolina System, and the California State University System created an informal consortium representing almost one hundred campuses serving over 900,000 students and over 47,000 faculty. SHEEO was the coordinator for the cooperative of the four state systems.
 
In 1999, the four systems recognized the significant benefits of a cooperative initiative to expand the MERLOT collections, conduct peer reviews of the digital learning materials, and add student learning assignments. Each system contributed $20,000 in cash to develop the MERLOT software and over $30,000 in in-kind support to advance the collaborative project. The CSU maintained its leadership of and responsibilities for the operation and improvement of processes and tools.
 
In January, 2000, the four systems sponsored 48 faculty from the disciplines of Biology, Physics, Business and Teacher Education (12 faculty from each of the four systems) to develop evaluation standards and peer review processes for on-line teaching-learning material. In April, 2000, other systems and institutions of higher education were invited to join the MERLOT cooperative. In July, 2000, twenty-three (23) systems and institutions of higher education had become Institutional Partners of MERLOT. Each Institutional Partner contributed $25,000 and in-kind support for eight faculty and a project director (part-time) to coordinate MERLOT activities. The CSU continued its leadership of and responsibilities for the operation and improvement of processes and tools.
 
 
MERLOT Staff

 

Gerry Hanley, Executive Director

Tel: 562-951-4259

Gerry is responsible for the leadership, strategic directions, overall management, and sustainability of MERLOT

Sorel Reisman, Managing Director 

Tel: 562-619-2388

Sorel is responsible for overseeing and managing MERLOT's operational processes and activities.

Jane Moore, Director of Editorial and Professional Development Services

Tel: 847-297-9474

Jane is responsible for managing the Editorial Boards, is Editor of Teacher Education, and the liaison from MERLOT to the Emerging Technologies Conference.  She is also responsible for the  Grapevine and From the Vineyard.

Barbra Bied Sperling, Manager of Technical and Software Development   

Tel: 562-951-8488

Barbra is responsible for all product development, enhancements  and maintenance of the MERLOT website.

David Risner, Software Engineer

David is responsible for the technological development and implementation of MERLOT, including the redesign of the MERLOT Content Builder and Web Services

Bryan Tu, Software Engineer

Bryan is responsible for the technological development and implementation of MERLOT, including peer review management system and MERLOT maintenance.

Jason Stanton, Webmaster and Social Media Coordinator

Jason is responsible for MERLOT's Social media presence and maintaining MERLOT user relations and experiences.

 

 

MERLOT Volunteers
 
Members of MERLOT communities are vital to its success. Community Members help grow the MERLOT collection by contributing materials, and adding assignments and comments.  Additionally, they introduce others in the discipline to MERLOT by presenting at conferences, authoring articles about MERLOT, and encouraging others to use and contribute to MERLOT.
 
Volunteer community Members work with  MERLOT staff to develop policies and practices that govern MERLOT's operations.  These volunteers are:

A) Editorial Boards
Editorial boards are the cornerstones of MERLOT. They lead the development of MERLOT's discipline communities - one Editorial Board for each community - and are comprised of:

  1. An Editor
  2. Associate Editors
  3. Peer reviewers
Editors, Associate Editors, and peer reviewers are nominated by System Partners, Campus Partners, and the MERLOT Management Team. Many peer reviewers are those who volunteer their own time to review for MERLOT.  All MERLOT editorial board members are faculty with:

Each editorial board is responsible for:

Here is a complete list of  MERLOT editorial boards and associated editors.

 

B) Project Directors

The MERLOT Leadership Council is comprised of all of the Project Directors from System and Campus Partners, along with Editors from each of the MERLOT Discipline Communities.  Project Directors have critical responsibilities in managing their institution’s participation in MERLOT and MERLOT’s connection to their institution’s academic technology initiatives.  Responsibilities of Project Directors include participation in MERLOT’s governance activities, selection of Editors and editorial board members, supervision of editorial board members, and management of their institutions’ partnership with MERLOT.   MERLOT provides Project Directors with online tools and analytics to assist them in monitoring their members' participation in MERLOT.

A complete list of Project Directors can be found here.