1. Kypson AP, Morphew E, Jones R, Gottfried MR, Seigler HF. Heterotopic ossification in rectal cancer: Rare finding with a novel proposed mechanism. J Surg Oncol. 2003, 82:132-136
  2. Thompson K. Structure and function of bone tissue. Edinburgh: Elsevier Saunders; 2007
  3. Thompson K. Structure and function of bone tissue. In: Maxie M, ed. Jubb, kennedy, and palmer’s pathology of domestic animals. Edinburgh: Elsevier Saunders; 2007:2-24
  4. Feldmann H. Forty years of FEBS. London, UK; Blackwell Publishing; 2004
  5. Feldmann H. Forty years of FEBS. London, UK; Blackwell Publishing; 2004, 12:12-23

Open Journal Systems: A Complete Guide to Online Publishing

http://pkp.sfu.ca/ojs/docs/userguide/2.3.1/index.html

Part III. System Administration

1. Making Backups of Your System

http://pkp.sfu.ca/ojs/docs/userguide/2.3.1/systemAdministrationBackup.html

1. Making Backups of Your System

A full back up of an OJS or OCS installation should include three components: the OJS system files; the files/ directory you created on installation; and the database. There are many ways to make backups of these three components. Depending on the tools at your disposal you may be able to make backups entirely over the web via an administrative interface such as CPanel; or you may have to make backups via the command line. The following section demonstrates one way to back up files via the command line.

Note

All servers are different, and the backup process in your case may be different than what follows. If any of this confuses you or for some reason does not work, be sure to check the documentation that comes with OJS in the docs/ folder, as well as the support forum and FAQ. But also be sure to read your service provider and server documentation as well.

1.1. Backing up the OJS System Files

To find your system files, look for the config.inc.php configuration file; this will be in the directory where you originally installed OJS. Back up all files in this directory and all subdirectories. Assuming OJS is installed in /var/www/html/ojs and the backup should be placed in /root, the following example will compress the OJS system files to a file in /root/ called ojs-install.tar.gz:

$ cd /var/www/html/ojs  $ tar czf /root/ojs-install.tar.gz *

1.2. Backing up the Database

You will need to know the database name, username, and password; these can be found in the database section of your config.inc.php configuration file:

[database]    driver = mysql  host = localhost  username = pkpuser  password = password  name = ojs

Back up the database using the mysqldump tool, e.g. if the backup should be placed in /root/:

$ mysqldump -u pkpuser -p password | gzip -9 > /root/ojs-database.sql.gz

Of course, phpMyAdmin or other tools could be used to back up the database.

1.3. Backing up the files/ Directory

To find where the files/ directory is, look at the files_dir parameter in the config.inc.php configuration file:

[files]    ; Complete path to directory to store uploaded files  ; (This directory should not be directly web-accessible)  ; Windows users should use forward slashes  files_dir = /usr/local/ojs-files

Back up this directory and all of its contents, e.g. if the backup should be placed in /root/:

$ cd /usr/local/ojs-files/  $ tar czf /root/ojs-files.tar.gz

When these steps have been completed, you will have created three backup files, which can be found in /root. All three of these are required to restore a copy of OJS from backup.

 

2. Restoring Your System From Backup

This section gives a brief overview of how a system could be restored from the backups made in the previous section. This is only one way to restore a system: there are plenty of other ways, depending on the tools you have at your disposal, and just as important, on the way you backed the system up.

Note

All servers are different, and the restore process in your case may be different than what follows. If any of this confuses you or for some reason does not work, be sure to check the documentation that comes with OJS in the docs/ folder, as well as the support forum and FAQ. But also be sure to read your service provider and server documentation as well.

2.1. Restoring Files

To restore from backup, unpack the files and installation backups into their appropriate places:

$ cd /var/www/html  $ mkdir ojs  $ cd ojs  $ tar xzf /root/ojs-install.tar.gz  $ cd /usr/local  $ mkdir ojs-files  $ cd ojs-files  $ tar xzf /root/ojs-files.tar.gz

2.2. Restoring the Database

Re-create the MySQL database (dropping it first if necessary):

$ mysql -u root -p  Enter password:     Welcome to the MySQL monitor.  Commands end with ; or \g.  Your MySQL connection id is 103  Server version: 5.1.38 MySQL Community Server (GPL)    Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.    mysql> DROP DATABASE ojs;  Query OK, 0 rows affected (0.23 sec)    mysql> CREATE DATABASE ojs DEFAULT CHARACTER SET utf8;  Query OK, 1 row affected (0.00 sec)    mysql> GRANT ALL ON ojs.* TO pkpuser@localhost IDENTIFIED BY 'password';  Query OK, 0 rows affected (0.01 sec)    mysql>   

Load the database dump into the newly created database:

$ zcat /root/ojs-database.sql.gz | mysql -u pkpuser -p ojs23

Chapter 15. Upgrading and Migrating

Comprehensive upgrade instructions can be found in docs/UPGRADE. As with any major administration task, it is strongly suggested that you back up your complete installation before beginning. Upgrading is a two-step process:

  1. The code must first be upgraded. This will involve downloading a new copy of OJS, or downloading and installing a patch file. Both the full OJS package and the relevant patch file are available from http://pkp.sfu.ca/ojs_download.

  2. The database must be upgraded. This can be done using the tools/upgrade.php script.

See docs/UPGRADE for complete instructions.

If the installation has been customized in any way, it will be necessary to ensure that the customizations are properly migrated to the new version:

Chapter 16. Support; Development; Troubleshooting; Reporting Problems

Table of Contents 1eveca9sdTa+G9

1. Finding Solutions: PKP Support Forum
2. Getting Source Code: Access via Git
3. Reporting Bugs: Using Bugzilla
4. Future Plans and Current Procedures: The PKP Development Wiki

PKP uses a number of Open Source applications as part of the development process. Git and Bugzilla are used to track PKP source code and bugs, respectively; Mediawiki is used to track and discuss general development issues and roadmaps; and phpBB is used to run our support forums, which community troubleshooting and bug reporting generally happens.

The following sections describe specifically how these different applications are used by the PKP team, and how they can be used effectively by the community. In general, however, the forum is used as our interface to the larger PKP community, where most questions and problems are dealt with; the wiki is used as a "living" document pool; and the Git repository and Bugzilla are used by PKP and partner developers to coordinate development and testing. In practice, roles overlap somewhat. We encourage you to browse and

===================

1、目标和结果不清晰。
It is noted that your manuscript needs careful editing by someone with expertise in technical English editing paying particular attention to English grammar, spelling, and sentence structure so that the goals and results of the study are clear to the reader.

2、未解释研究方法或解释不充分。
In general, there is a lack of explanation of replicates and statistical methods used in the study.
Furthermore, an explanation of why the authors did these various experiments should be provided.

3、对于研究设计的rationale:
Also, there are few explanations of the rationale for the study design.

4、夸张地陈述结论/夸大成果/不严谨:
The conclusions are overstated. For example, the study did not show
if the side effects from initial copper burst can be avoid with the polymer formulation.

5、对hypothesis的清晰界定:
A hypothesis needs to be presented。

6、对某个概念或工具使用的rationale/定义概念:
What was the rationale for the film/SBF volume ratio?

7、对研究问题的定义:
Try to set the problem discussed in this paper in more clear,
write one section to define the problem

8、如何凸现原创性以及如何充分地写literature review:
The topic is novel but the application proposed is not so novel.

9、对claim,如A>B的证明,verification:
There is no experimental comparison of the algorithm with previously known work, so it is impossible to judge whether the algorithm is an improvement on previous work.

10、严谨度问题:
MNQ is easier than the primitive PNQS, how to prove that.

11、格式(重视程度):
In addition, the list of references is not in our style. It is close but not completely correct. I have attached a pdf file with "Instructions for Authors" which shows examples.
Before submitting a revision, be sure that your material is properly prepared and formatted. If you are unsure, please consult the formatting instructions to authors that are given under the "Instructions and Forms" button in he upper right-hand corner of the screen.

The list of references is not in our style. The style should be like this:
In the reference list, periodicals [1], books [2], book Sections [3], conference [4], and conference proceedings [5] should accord with the following examples:

  1. Kypson AP, Morphew E, Jones R, Gottfried MR, Seigler HF. Heterotopic ossification in rectal cancer: Rare finding with a novel proposed mechanism. J Surg Oncol. 2003, 82:132-136
  2. Thompson K. Structure and function of bone tissue. Edinburgh: Elsevier Saunders; 2007
  3. Thompson K. Structure and function of bone tissue. In: Maxie M, ed. Jubb, kennedy, and palmer’s pathology of domestic animals. Edinburgh: Elsevier Saunders; 2007:2-24
  4. Feldmann H. Forty years of FEBS. London, UK; Blackwell Publishing; 2004
  5. Feldmann H. Forty years of FEBS. London, UK; Blackwell Publishing; 2004, 12:12-23

When citing in the text, it should be like this:
Membrane is a selective and permeable barrier between two phases that expedites segregation of constituents on exertion of a dynamic force [1-3]…



12、语言问题(出现最多的问题):
有关语言的审稿人意见:
It is noted that your manuscript needs careful editing by someone with expertise in technical English editing paying particular attention to English grammar, spelling, and sentence structure so that the goals and results of the study are clear to the reader.
The authors must have their work reviewed by a proper translation/reviewing service before submission; only then can a proper review be performed. Most sentences contain grammatical and/or spelling mistakes or are not complete sentences.
As presented, the writing is not acceptable for the journal. There are problems with sentence structure, verb tense, and clause construction.
The English of your manuscript must be improved before resubmission. We strongly suggest that you obtain assistance from a colleague who is well-versed in English or whose native language is English.
Please have someone competent in the English language and the subject matter of your paper go over the paper and correct it ?
the quality of English needs improving.