|
Jennie Drew
07-28-2004
10:16 AM ET (US)
|
In a decentralized publishing system I would see a Web editor's role as not just being a quality control step (that could potentially create a bottleneck to publishing content) but someone who could support regional and programme offices in producing content.
As Paul mentions this could be in monitoring new directions, gaps etc., but also in helping staff to plan and write material for the Web.
A web editor could also have a role in ensuring the Web is seen as one of a range of communications tools we have at IPGRI. This is not just a case of ensuring consistency of image across publications (CD, Web and print), but also considering the advantages or complimentarity of 'publishing' on the Web rather than viewing it as an afterthought.
|
|
Paul Neate
07-19-2004
09:02 AM ET (US)
|
Re: the Web editor
I see the Web editor as having oversight for the content of the Web site as a whole. At present, as Massimo has said, each group is responsible for the content it publishes, but no-one really has responsibility for the content of the Web site as a whole, for monitoring new directions, gaps, overlaps etc. There is a step in the publishing process that requires the attention of an editor, but this rarely happens.
|
|
Massimo Buonaiuto
07-19-2004
06:40 AM ET (US)
|
Comments about:
> Need for web editor
At the moment each group is responsible of the content it publishes.
What kind of duties should have this person?
Should this person ensure a sort of quality control?
How? As it is now, the author knows about the content published on the web site...
Should the web editor write articles for the web? This means centralization of inputting process, right?
|
|
Massimo Buonaiuto
07-19-2004
06:35 AM ET (US)
|
Comments about
>Opposition to centrally imposed tools, framework,
>approach -- want to do it their way
The "imposition" is due to:
- the content has to be published on the web using the corporate image of the institute
- the institutional content has to be accessible and available to EVERYBODY for multiple purposes (a news should be available for the web, for an newsletter sent via email, for the RSS system, etc.) and this requires centralization in a unique datasource (our databases)
- there is huge effort to centralize data within a single centralized "Institutional Databases", and decentralization process could run against it.
- different technology/framework, etc. require support and definition of its institutional life cycle: installation, customization, maintenance (backup, human resource allocation to support it, updates, training, etc.).
- approval process tools could not work on decentralized systems
- web master could find problems accessing decentralized systems
- several decentralized systems could create confusion of roles: content providers that spend time trying to find out bugs, customizations that produce content not compatible with institutional image, etc. etc. etc.
|
Massimo Curatella  07-16-2004
06:46 AM ET (US)
|
Managing a decentralized Web publishing systemCritical issues related to management of multiple publilshing units geographically distributed which presently operate often according to their specific needs and requirements. Lack of effective quality control and web publishing standards coherency.
Go back to the IGPRI-WEB Journal:
http://www.ikonosnewmedia.com/ipgriweb/
|
|
|
New Topic
My Topics
Views:
276
(Unique:
143
) / Subscribers:
0 | What's this?
