I've attached a zip containing each plugin in a separate zip along with readme files as an install guide. At this stage we've only tested on simple conferences since none of our partner organisations have particularly complex conferences, so testing has been limited.
Our remit is only to archive the published papers, not recreate the the conference program and structure, so the export is fairly simplistic in its structure. However the program view is an alternative METS export I would like to see implemented but is not in scope for our current project. The METS used is a registered profile - the Australian METS Profile (see http://www.loc.gov/standards/mets/profi ... 00018.html
The Australian METS profile model is a three-tier hierarchical model, the core profile (the one registered on LOC), content profiles which will also be registered as they become available (e.g. journal, image, conference, etc) and implementation profiles (e.g. OJS, OCS). There is a little more information about this at http://www.nla.gov.au/australianmetsprofile/
but there is still more information to be added. Ultimately we want to register a conference profile with LOC but due to time constraints won't get to this until next year.
Our developer came across two issues when writing these plugins:
1. the path to the gateway should perhaps always include a path to a Scheduled Conference Path
[OSC URL]/index.php/CCD/*<scheduled conf path>*/gateway/plugin/ConferenceExportPlugin/
Since OCS export plugins are conference-based (not scheduled conference-based), the scheduled conference path in the URL is probably not needed - I'm not sure if this is an OCS issue. Our plugin takes as parameters a) id of a scheduled conference to export; b) no parameters to export entire conference; or c) the word "current" to export the latest scheduled conference
2. $PaperFile->getFilePath() returns the incorrect path for Galley files because
$galley->setType($row['type']); is missing (type is not even fetched from the DB)
We are currently working on an OJS gateway/export version which I can also forward if you're interested once complete.
Please let me know if you have any questions, we hope that we can progress this so that these plugins can be consolidated into the core OCS (and OJS) code. If not we would be happy to make them available as optional plugins if you prefer. Leo has kept to the same code style used so hopefully that makes life easier. If the plugins are consolidated into the core, that will also be good in that the DOM generator classes are currently duplicated across the separate plugins, so would obviously be good to not have to do that.