Editorial Team

Editorial Team


  1. Dr. Najid Ahmad, School of Economics,Dongbei University of Finance and Economics, Dalian, China
  2. Prof. Eşi Marius, Stefan cel Mare University of Suceava, Romania., Romania
  3. Dr. Dunya Ahmed Abdullah Ahmed, Center for Women, Supreme Council for Women. Bahrain.

Section Editors

  1. Dr. Giovanni Martinotti, Department of Neuroscience and Imaging, University of G.d’Annunzio, Chieti-Pescara, Italy., Italy
  2. Dr. Abdolmajid Bahrainian, Department of clinical psychology, Shahid Beheshti University of Medical Sciences, Tehran, Iran.
  3. Dr. Sambulo Ndlovu
  4. Dr. Mohammad Reza Iravani, Department of Social work, Islamic Azad University, Isfahan, Iran.
  5. Dr. Magdy Shayboub A. Mahmoud, Faculty of Computers and Informatics. Suez Canal University, Egypt.
  6. Prof. Ljupco Sotiroski, Faculty of Law, State University “Goce Delchev” , Stip, Macedonia.
  7. Dr. Santosh Kumar Behera, Department of Education, Sidho-Kanho-Birsha University, West Bengal, India.
  8. Mouna Hdia, Department of Management, University Paris II, Ponthéon- Assas, Paris, France
  9. Muhammad Luqman, Center for Economics Research, Shandong University, Jinan, China

Under Construnction * similarities. * * As in a MVC structure, data storage and representation, user interface * presentation, and control are separated into different layers. The major * categories, roughly ordered from "front-end" to "back-end," follow: * - Smarty templates, which are responsible for assembling HTML pages to * display to users; * - Page classes, which receive requests from users' web browsers, delegate * any required processing to various other classes, and call up the * appropriate Smarty template to generate a response; * - Action classes, which are used by the Page classes to perform non-trivial * processing of user requests; * - Model classes, which implement PHP objects representing the system's * various entities, such as Users, Articles, and Journals; * - Data Access Objects (DAOs), which generally provide (amongst others) * update, create, and delete functions for their associated Model classes, * are responsible for all database interaction; * - Support classes, which provide core functionalities, miscellaneous common * * As the system makes use of inheritance and has consistent class naming * conventions, it is generally easy to tell what category a particular class * falls into. * For example, a Data Access Object class always inherits from the DAO class, * has a Class name of the form [Something]%DAO, and has a filename of the form * [Something]%DAO.inc.php. * * To learn more about developing OJS, there are several additional resources * that may be useful: * - The docs/README document * - The PKP support forum at http://forum.pkp.sfu.ca * - The technical reference (and other documents), available at * http://pkp.sfu.ca/ojs_documentation * * @file index.php * * Copyright (c) 2013-2016 Simon Fraser University Library * Copyright (c) 2003-2016 John Willinsky * Distributed under the GNU GPL v2. For full terms see the file docs/COPYING. * * @ingroup index * * Bootstrap code for OJS site. Loads required files and then calls the * dispatcher to delegate to the appropriate request handler. */ // Initialize global environment define('INDEX_FILE_LOCATION', __FILE__); require('./lib/pkp/includes/bootstrap.inc.php'); // Serve the request $application =& PKPApplication::getApplication(); $application->execute(); ?>