OCS development discussion, enhancement requests, third-party patches and plug-ins.
Moderators: jmacgreg, michael
The OJS Technical Reference
and the OJS API Reference
are both available from the OJS Documentation
page. While these are OJS-specific, the OCS codebase is similar enough to OJS they should be of help. There is also an [url=http://pkp.sfu.ca/ocs_documentation[/url]OCS Documentation[/url] page with some more general documentation that might also be of interest.Git:
You can access our public Git Repository here
. Comprehensive Git usage instructions are available on the wiki
You can access our Bugzilla report tracker here
You can use our Google Custom Search
to search across our main website, the support forum, and Bugzilla.
Questions and discussion are welcome, but if you have a workflow or usability question you should probably post to the OCS Conference Support and Discussion
subforum; if you have a technical support question, try the OCS Technical Support
Any recommendations on how to augment the metadata section so that we can capture additional data as part of our conferences. We have additional fields we need to collect and I'm not sure if there are any plug-ins or other mechanisms for supplementing the basic data that is currently being collected. Low priority request at this point however for our next conference we really need to supplement the basic data collection. I'm hoping there is something out there that is configurable rather than having to delve into the depths of the code to write custom patches that won't survive upgrades in software releases.
- Posts: 7
- Joined: Fri Jan 28, 2011 12:56 am
There's currently no way to do this without touching the code, although it has been requested before. See http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=1360
, and please feel free to CC yourself for future updates.
- Posts: 4161
- Joined: Tue Feb 14, 2006 10:50 am
Return to OCS Development
Who is online
Users browsing this forum: jhbbigtli and 1 guest