PKP Wiki - Recent changes [en]

OJS 2.4.2 Recommended Patches

2013-05-23T21:54:03Z

Added Bug 8233

Single Christian Dating Service

2013-05-22T21:58:41Z

CDL deleted page Single Christian Dating Service Vandalism: content was: "==<center>Single Christian Dating Service</center>== . . . . ==<center>[http://mystarsearch.com/forum/index.php?topic=3e7MjE3fHwxMzAwMDI0MzU3fHwxOTUyfHwoRU5..." (and the only contributor was "[[Special:Contributions/Larswil...

OJSdeStatisticsConcept

2013-05-22T20:33:57Z

Correct search ranking boost range (1.0-2.0)

OMP 1.0 Recommended Patches

2013-05-21T17:27:33Z

Alec protected "OMP 1.0 Recommended Patches"‎ ‎[edit=sysop] (indefinite) ‎[move=sysop] (indefinite)

OMP 1.0 Recommended Patches

2013-05-21T17:27:04Z

Created page; added bug #8227

New page

The following patches are recommended for OMP 1.0.

Please subscribe to the [http://pkp.sfu.ca/wiki/index.php?title=OMP_1.0_Recommended_Patches&feed=atom&action=history RSS feed] for this page to stay informed about important bug fixes for this release.

== Applying Patches ==

Patches can be applied to the codebase using the GNU Patch Tool (available on most *NIX platforms, and as a free download for Windows-based systems).

Each entry below links to the Bugzilla record for the bug in question. Patches are linked from there. Patches against OMP should be applied with the -p1 option from within the OMP installation directory; patches against the PKP library should be applied with the -p1 option from within the lib/pkp subdirectory.

== Patches ==

Note that security-related and other critical patches will be clearly identified as such; otherwise, patches should not be considered critical.

: [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=8727 Bug #8227]: Scrollable tab plugin may disrupt book view [https://github.com/pkp/omp/commit/fc59e438d98bce4ae08f80b7410b77fd48dc1569.diff patch]

XML Publishing

2013-05-21T17:02:09Z

‎DIGO (Draft In, Galley Out) OJS Plugin for XML HTML and PDF Output:

Main Page

2013-05-21T15:21:54Z

‎Active:

Tech Committee Agenda 22 May 2013

2013-05-16T21:48:17Z

A bit reshuffling.

Tech Committee Meeting Minutes 16 April 2013

2013-05-16T21:08:12Z

Technical Committee

2013-05-16T21:07:54Z

‎Current Members:

Tech Committee Agenda 22 May 2013

2013-05-16T17:56:42Z

Created page with "== Agenda == # New member introductions: Allan Bell (UBC), Bronwen Sprout (UBC) # Quick round of updates ## What have we all been working on? ## Any particular needs that the..."

New page

== Agenda ==
# New member introductions: Allan Bell (UBC), Bronwen Sprout (UBC)
# Quick round of updates
## What have we all been working on?
## Any particular needs that the group can help with?
# At-large membership: discuss poll results; identify top choices.
# 3 volunteers from members committee - status?
# Clarifying PKP '''priorities''' and '''methodologies''' so that this committee can begin to provide technical input and advice (see [http://pkp.sfu.ca/wiki/index.php/Technical_Committee#Mandate PKP Tech Committee Mandate]).
## Perhaps each of us can commit to editing a small portion of the PKP documentation that we've used in our work?
## New priorities-related document: [http://pkp.sfu.ca/wiki/index.php/General_Software_Milestones Software Milestones page] needs review
## Any other new documents we should be aware of?
## Overall need for better documentation and organization/accessibility of information. How can we improve it?
### James - update on new WP site?
### Google group thread on using blog format for organizing/storing documents
# Committee communication
## Google group
## IRC channel? chat.freenode.net, #pkp
# Anything else?

Technical Committee

2013-05-16T17:30:12Z

‎Meeting Agendas:

User:Damion

2013-05-16T00:46:00Z

User account Damion was created by Jmacgreg password sent by e-mail

@@ Line 21: / Line 21: @@
 : [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=8190 Bug #8190]: Correct urlencoding of DOIs [http://pkp.sfu.ca/bugzilla/attachment.cgi?id=3924 patch]
 : [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=8210 Bug #8210]: One-click reviewer access not validating [https://github.com/pkp/ojs/commit/1402eaa7c6bdcbb0be6388949f0bdff4877a15ac.diff patch]
-: [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=8225 Bug #8225]: Cannot create submission notes [https://github.com/pkp/ojs/commit/e225e504a557958c84080021133deebf8faf3c72 patch]
+: [http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=8225 Bug #8225]: Cannot create submission notes [https://github.com/pkp/ojs/commit/e225e504a557958c84080021133deebf8faf3c72.diff patch]

@@ Line 532: / Line 532: @@
 We recommend implementing this feature as an additional, optional search feature of the Lucene plug-in. This means that another search feature option will be added to the Lucene plug-in's configuration page. Ticking the corresponding configuration check box would activate the feature. If we implement the feature like this then it is probably not necessary to change OJS core. As soon as the feature has been enabled, the Lucene plugin will amend all search queries with an additional boost query that refers to the external field.
-The customized metrics report can be easily generated via the Statistics API and provided over HTTP so that it becomes available to remote indexing servers. It contains a list of all unique index object IDs (instId + '-' + articleId) and the corresponding metric boost value, normalized to values between 0.5 and 2.0. The metrics report can be implemented as an operation of the LuceneHandler class and will only be available when the corresponding search feature has been enabled in the plugin.
+The customized metrics report can be easily generated via the Statistics API and provided over HTTP so that it becomes available to remote indexing servers. It contains a list of all unique index object IDs (instId + '-' + articleId) and the corresponding metric boost value, normalized to values between 1.0 (no usage = no boost) and 2.0 (highest usage). The metrics report can be implemented as an operation of the LuceneHandler class and will only be available when the corresponding search feature has been enabled in the plugin.
 It has to be decided whether we'd like to use all-time metric data or whether we'd rather restrict usage data to those accrued over the last month or last year. In principle, this decision could be delegated to the journal manager by providing an additional configuration option in the plugin configuration.

@@ Line 11: / Line 11: @@
 This project implements an OJS plugin for producing NLM standard article XML, as well as pdf and HTML document versions for any article uploaded to an OJS journal.
-This plugin will have an enabled/disabled state, and will have one settings field for selecting a csl style from a dynamic list that pertains to the OJS journal.
+This plugin will have an enabled/disabled state, and will have a few settings fields.  One field will enable selecting a CSL style (that pertains to the OJS journal) from a dynamic list.  This controls the format of citations and bibliography entries.  Another setting will control whether a pdf version of the article intended only for reviewers is produced.  As well, an upload field is provided to send a header image for inclusion in pdf and html versions.  Finally, using the OJS file manager, Journal Managers can change the styling of displayed documents.
 When an author, copyeditor or editor uploads a new version (odt, docx, doc, or pdf format) of an article, this module (using a separate thread) submits it to the pdfx server specified in the configuration file.  The following files are returned in a gzip'ed archive file (X-Y-Z-AG.tar.gz) which is added (or replaces a pre-existing version in) the Supplementary files section.
-* document.pdf (may be generated if input format is not pdf)
+* document-new.pdf (new version of original pdf or other file format)
-* document.nlm.xml (NLM National Library of Medicine standard xml)
+* document-review.pdf (included for reviewers only, it has 1st page author information stripped out)
 * document.html and related graphics
 * document.bib (a bibtex text file of reference data)
@@ Line 23: / Line 24: @@
 If the article is being uploaded as a galley publish, this plugin will extract the xml and pdf versions when they are ready, and will place them in the supplementary file folder so that web options can be provided for viewing.
-We are doing this each time an article is submitted to enable the bibliographic reference work to be available at early stages of review and during copyedit.
+This process is triggered each time an article is submitted to enable the bibliographic reference work to be available at early stages of review and during copyedit.
 == XML Publishing Document Archive ==

@@ Line 47: / Line 47: @@
 * [[XML Publishing]]
 * [[Documentation Project]]
 ==== Proposed ====

← Older revision		Revision as of 21:08, 16 May 2013
Line 1:		Line 1:
−	'''Present''': Bart Kawula (OCUL), ~~QinQin~~ Lin (OCUL), Brian Gregg (Pitt), Jason Nugent (PKP), James MacGregor (PKP), Barbara Hui (CDL), Alec Smecher (PKP), Lisa Schiff (CDL)	+	'''Present''': Bart Kawula (OCUL), Qinqin Lin (OCUL), Brian Gregg (Pitt), Jason Nugent (PKP), James MacGregor (PKP), Barbara Hui (CDL), Alec Smecher (PKP), Lisa Schiff (CDL)

	'''Minutes''': Alec (PKP)		'''Minutes''': Alec (PKP)

@@ Line 1: / Line 1: @@
 == Agenda ==
-# New member introductions: Allan Bell (UBC), Bronwen Sprout (UBC)
+# '''New member introductions''': Allan Bell (UBC), Bronwen Sprout (UBC)
-# Quick round of updates
+# '''Quick round of updates'''
-## What have we all been working on?
+## What have we all been working on PKP-wise?
 ## Any particular needs that the group can help with?
-# At-large membership: discuss poll results; identify top choices.
+# '''At-large membership''': discuss poll results; identify top choices; make a plan for inviting nominees.
-# 3 volunteers from members committee - status?
+# '''3 volunteers from members committee''' - status?
-# Clarifying PKP '''priorities''' and '''methodologies''' so that this committee can begin to provide technical input and advice (see [http://pkp.sfu.ca/wiki/index.php/Technical_Committee#Mandate PKP Tech Committee Mandate]).
+# '''Reviewing our [http://pkp.sfu.ca/wiki/index.php?title=Technical_Committee#Mandate mandate], cont'd.'''
-## Perhaps each of us can commit to editing a small portion of the PKP documentation that we've used in our work?
+## Charge #1: provide technical input and advice on PKP’s software development methodologies and priorities. Last time the group came to the consensus that PKP priorities and methodologies are unclear. We are working towards fixing this so that we can begin to give input.
-## New priorities-related document: [http://pkp.sfu.ca/wiki/index.php/General_Software_Milestones Software Milestones page] needs review
+## James - overview of what priorities/methodologies documentation is available. How does the new WP site fit in and what's the status?
-## Any other new documents we should be aware of?
+## New priorities-related document (thanks Alec et al): [http://pkp.sfu.ca/wiki/index.php/General_Software_Milestones Software Milestones page] needs review.
-## Overall need for better documentation and organization/accessibility of information. How can we improve it?
+## Overall need for better documentation and organization/accessibility of information. Need for improving developer relations. How?
-### James - update on new WP site?
+## Discuss which format to use (blog? wiki?) for organizing/storing documents (e.g. agendas, meeting minutes, documentation). [https://groups.google.com/forum/#!topic/pkp-technical-committee/FcByQ7ESK7M See this Google group thread]
-### Google group thread on using blog format for organizing/storing documents
+# '''Committee communication'''
-# Committee communication
+## [https://groups.google.com/forum/#!forum/pkp-technical-committee Google group]
-## Google group
+## IRC? There is a #pkp channel on chat.freenode.net
-## IRC channel? chat.freenode.net, #pkp
+# '''Next meeting''': how about Tuesday 18 June, 9am?
 # Anything else?

@@ Line 27: / Line 27: @@
 * Lisa Schiff (CDL)
 * Bartek Kawula (OCUL)
-* QinQin Lin (OCUL)
+* Qinqin Lin (OCUL)
 * Brian Gregg (UPitt)
 * Allan Bell (UBC)

@@ Line 41: / Line 41: @@
 == Meeting Agendas ==
 [[16 April 2013]]
 == Meeting Minutes ==
 [[Tech Committee Meeting Minutes 16 April 2013]]