Re: [Fwd: Re: [seul-edu] Software for journal publish]

[jeremy hunsinger <jhuns@vt.edu>]

>>
barring any original development, frameworks are the best way to go.  
though i use php and with that i use a second layer which gives us many 
of the same tools as a framework.
but as i tried to stipulate, the problem is that the tool is not the 
solution, as cms/portal systems are unlikely to suffice for this type of 
job.  the problem is that the community of users, between 
writers/reviewers/publishers already have standards and practices that 
don't map well onto those tools, and because of the profit oriented 
nature of publishing, strange fact that most academic publishing does 
not make profit, the tools that they use are usually in house 
developments, which is the case with the journals at our library, and 
the journals at john hopkins press, etc. and so as not to allow others 
to compete on that ground, the source is closed.  our system, or at 
least the code for one part of our system should be released in the next 
month or so.
>
> What do you think of the more generalized web frameworks?  Zope,
> OpenACS, et al.. are all pretty agnostic in terms of workflow and
> presentation.  They require customization work, but I think can be
> adapted to a wide range of requirements. Barring an open source
> release from your organization :), they seem like to best choice for
> the original poster.
>
> -- alan
>
> --
> Alan Chen
> Digikata LLC
> alan@digikata.com
> http://digikata.com
>
>
jeremy hunsinger
on the ibook
www.cddc.vt.edu
www.cddc.vt.edu/jeremy