Workflow in Pleiades

Essential to the effectiveness of Pleiades (both as a widely applicable model and as a practical tool for maintaining the Atlas Project’s legacy) are robust mechanisms for reviewing and editing the proposals of community members. This editorial process depends upon clearly established roles for all members, by means of which various editing and revision capabilities are assigned. The community support software built atop Plone enforces these roles and facilitates the exercise of associated privileges and capabilities.

For this purpose, the Managing Editors of Pleiades (initially Talbert and Elliott) grant privilege-based roles to members of the community and subject their contributions to a structured editorial workflow. The Managing Editors, in consultation with the Advisory Board of the Ancient World Mapping Center, may add further managing editors as workload warrants and suitable colleagues are identified. This oversight role for the Center’s Advisory Board provides important institutional credentialing for the Pleiades community and ensures a sustainable, long-term management structure for it, firmly embedded in the governance of the Mapping Center.

The editorial workflow employed by the Pleiades Managing Editors is modeled on the procedures of the Classical Atlas Project, adapted for the more heterogeneous Pleiades community.

The Details

The Pleiades Editorial Work Flow is a topic of current discussion for the project team, via its discussion list. The present proposal is outlinded in the wiki as PleiadesWorkFlow.

The PleiadesWorkFlow makes reference to a number of UserRoles. These include, in brief form, descriptions of the privileges that each user can exercise.

The community is also developing a series of WorkFlowStories. These present both real and fictitious examples of Pleiades workflow in action.

Other Workflows for Comparison

Useful Info

??? yes, but we'll use state diagrams in UML plus ArchGenXML probably to create our workflow policy.