Difference between revisions of "Proposed Plugins"

From PKP Wiki
Jump to: navigation, search
(Moved thesaurus plug-in over from wiki main page.)
 
(7 intermediate revisions by 4 users not shown)
Line 2: Line 2:
  
 
* Continuing Education Plugin (See [http://pkp.sfu.ca/ocs/pkp2007/index.php/pkp/1/paper/view/47 Glenn Hymel's conference presentation].)
 
* Continuing Education Plugin (See [http://pkp.sfu.ca/ocs/pkp2007/index.php/pkp/1/paper/view/47 Glenn Hymel's conference presentation].)
* OxS Document Conversion plugin (using ICE / Docvert / Google Docs)
 
* OxS OpenURL resolver plugin; to be ported to Harvester
 
 
* OJS Scholar's Portal / NLM plugin (from UofT)
 
* OJS Scholar's Portal / NLM plugin (from UofT)
* "most viewed articles" block plugin
+
* "Featured articles" block plugin
* "featured articles" block plugin
+
* "Most viewed articles" block plugin (''in the works JPA'')
 +
* Site-wide sidebar plugin in conjunction with the customBlockManager (''in the works JPA'')
 +
* Categories/countries plugins (assign a country or a category to a journal) (''in the works JPA'')
 +
* Browse by country/category/alphabetical (with above plugins) (''in the works JPA'')
 +
* Site statistics block plugin (''in the works JPA'')
 +
* Latest issues published block plugin (''in the works JPA'')
 +
* Site/journal homepage plugin (allow the arranging of blocks on the main section of a page, perhaps with drag-and-drop)
 +
* File conversion plugins (e.g. ICE, Docvert, Google Docs, XSLT aka XML galleys, GD, ImageMagick)
 +
* Auto-convert plugin (WAL): allows configurable hooks at points in the workflow (submission upload, review version, layout/galley upload) to create derived format(s) using source_id; trick is enabling 1:n from enabled conversion plugins
 +
* OpenURL plugin (OxS): allow specifying an OpenURL resolver on a per-user basis (or override-able journal default); HTML post-processor to rewrite COinS as OpenURLs
 +
* OpenURL plugin (Harvester): refactor current OJS resolver plugin to support OpenURL 0.1/1.0 syntax; fuzzy searching using lucene etc. if available; allow specifying a default OpenURL resolver for delegating failed requests (with a possible interstitial page, parameters like CrossRef, etc.)
 +
* Thesaurus (tematres integration): Integrates OJS with tematres (a thesaurus management software) letting your authors select keywords from a restricted corpus. URL: http://pkp.sfu.ca/support/forum/viewtopic.php?f=28&t=4800
 +
 
 +
Please see [[Lemon8-XML Roadmap]] for proposed plug-ins related to document parsing/export and citation parsing/lookup/output
 +
 
 +
----
 +
 
 +
* A Project Management module could be created and made available to all PKP software. It would combine the features of the Subscription Manager with that of a more general business manager. This module would allow hour figures or other costs to be associated with various parts of the workflow (e.g., a journal article's copyediting hours; a conference's keynote speaker's expenses; etc.). Each copyeditor, proofreader, layout editor, etc. would be required to enter the number of hours spent on their work. The hourly costs could be aggregated for a submission, multiplied by a dollar figure, and produce the cost of the article. This could be combined with each article's cost in an issue to produce a cost of issue report. An article's cost could be divided by its views to produce an interesting cost per view feature. This module would also help conference managers to keep careful account of the event's costs vs its funding.

Latest revision as of 07:51, 9 February 2011

Ideas for plugins in the near future or in recent development.

  • Continuing Education Plugin (See Glenn Hymel's conference presentation.)
  • OJS Scholar's Portal / NLM plugin (from UofT)
  • "Featured articles" block plugin
  • "Most viewed articles" block plugin (in the works JPA)
  • Site-wide sidebar plugin in conjunction with the customBlockManager (in the works JPA)
  • Categories/countries plugins (assign a country or a category to a journal) (in the works JPA)
  • Browse by country/category/alphabetical (with above plugins) (in the works JPA)
  • Site statistics block plugin (in the works JPA)
  • Latest issues published block plugin (in the works JPA)
  • Site/journal homepage plugin (allow the arranging of blocks on the main section of a page, perhaps with drag-and-drop)
  • File conversion plugins (e.g. ICE, Docvert, Google Docs, XSLT aka XML galleys, GD, ImageMagick)
  • Auto-convert plugin (WAL): allows configurable hooks at points in the workflow (submission upload, review version, layout/galley upload) to create derived format(s) using source_id; trick is enabling 1:n from enabled conversion plugins
  • OpenURL plugin (OxS): allow specifying an OpenURL resolver on a per-user basis (or override-able journal default); HTML post-processor to rewrite COinS as OpenURLs
  • OpenURL plugin (Harvester): refactor current OJS resolver plugin to support OpenURL 0.1/1.0 syntax; fuzzy searching using lucene etc. if available; allow specifying a default OpenURL resolver for delegating failed requests (with a possible interstitial page, parameters like CrossRef, etc.)
  • Thesaurus (tematres integration): Integrates OJS with tematres (a thesaurus management software) letting your authors select keywords from a restricted corpus. URL: http://pkp.sfu.ca/support/forum/viewtopic.php?f=28&t=4800

Please see Lemon8-XML Roadmap for proposed plug-ins related to document parsing/export and citation parsing/lookup/output


  • A Project Management module could be created and made available to all PKP software. It would combine the features of the Subscription Manager with that of a more general business manager. This module would allow hour figures or other costs to be associated with various parts of the workflow (e.g., a journal article's copyediting hours; a conference's keynote speaker's expenses; etc.). Each copyeditor, proofreader, layout editor, etc. would be required to enter the number of hours spent on their work. The hourly costs could be aggregated for a submission, multiplied by a dollar figure, and produce the cost of the article. This could be combined with each article's cost in an issue to produce a cost of issue report. An article's cost could be divided by its views to produce an interesting cost per view feature. This module would also help conference managers to keep careful account of the event's costs vs its funding.