OJS OCS OMP OHS

You are viewing the PKP Support Forum | PKP Home Wiki



OCS 2.0 user interface

OCS development discussion, enhancement requests, third-party patches and plug-ins.

Moderators: jmacgreg, michael

Forum rules
Developer Resources:

Documentation: 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.

Bugzilla: You can access our Bugzilla report tracker here.

Search: 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 subforum.

OCS 2.0 user interface

Postby Rebecca Sullivan » Thu Jul 19, 2007 9:05 am

We haven't migrated to OCS 2.0 yet, and will wait one year because we need more flexibility than is currently available.

1. presentation formats
- it is imperative that we are able to allow people to select from multiple presentation formats, not just single-paper or multiple-paper presentations. Our conference also allows workshops, roundtables, graduate masters sessions, and performances.

2. presenter information
- again, we need to be able to request a lot more information that is currently possible. We need fields for name, title/status/rank, department, institution, and a brief bio. It would also help if we could have a radio button field for presenters to identify themselves (professor / post-doc / PhD / MA / professional / independent scholar / sessional or lecturer). We also need the ability to make these fields required entry.

3. bilingualism
- all field names and instructions must be bilingual French/English for our association. Any built-in instructions to the system need to at least have the option of appearing in either or both official languages.

4. sorting and exporting information
- it would be a major benefit for us to be able to export only select entries, instead of all entries as is currently the case in OS 1.0.


I haven't been able to do as much in-depth work in OCS 2.0 as I would have liked but these were my primary concerns after browsing through and talking with reps from PKP. The first three issues in particular are necessary, not optional, for us to be able to properly manage our annual conference.

Thanks so much - great work thus far!
Rebecca Sullivan
 
Posts: 1
Joined: Thu Jul 19, 2007 9:03 am

Postby asmecher » Thu Jul 19, 2007 12:57 pm

Hi Rebecca,

Thanks for the feedback! We'll be addressing points 1, 3, and 4 soon (hopefully for release this fall); point 2 will become much easier once point 3 is addressed, because 3 will involve an overhaul of the metadata storage system that will coincidentally make adding further fields simpler.

Regards,
Alec Smecher
Public Knowledge Project Team
asmecher
 
Posts: 8591
Joined: Wed Aug 10, 2005 12:56 pm


Return to OCS Development

Who is online

Users browsing this forum: No registered users and 0 guests