Editorial and Production Workflow
This section speaks broadly to the question of how to incorporate each of the three different Manifold project conceptions into your workflow, with suggestions of where to delineate work between the author(s) and you, the publisher.
In this scenario the production workflow is largely unchanged from your existing procedures. When you have a final version of your Text (congruent with typeset-ready text or a final, copyedited manuscript) in an acceptable format, you can begin a new project in the system and upload that Text, along with general project and author information, cover and author images, and associated metadata (as appropriate). You will have the chance to review the material to make sure it has translated onto the platform as expected before pushing it live. Authors, in collaboration with you, may need to supply additional metadata and support media (avatars, banner suggestions), depending on your expectations.
As with the Open-Access model, the production process for Enhanced projects remains mostly unchanged from your existing procedures. In addition to loading a Text, you will also upload Resource files that augment and enhance the Text. This will involve a staff member reviewing the quality and usability of the materials as well as evaluating them for any permission concerns. Metadata input for Resources can be modest, though the platform does allow for a robust collection of information, depending on your needs and expectations. The placement of Resources in the Text(s) or in curated collections can be accomplished either by the author or in-house staff.
The iterative process precedes and stands apart from the standard production workflow. After an agreement on the nature of the project and the kinds of materials it will comprise is brokered with the author, the author can begin supplying Texts and Resources.
Manifold editions are smoothly integrated into the existing production processes so publishers considering Manifold won’t have to change their fundamental workflows to use it.
In the figure above, white tiles denote existing production processes, green tiles describe actions that occur on the Manifold platform, and dotted arrows suggest optional paths to pursue.
- Collaborating with authors on how to structure materials for the platform
- Vetting and editing materials to house standards and expectations for “gray” publications
- Advising authors on permission concerns
- Preparing and loading author materials into the system
- Trouble-shooting platform concerns
- Outline what level of attention you want to provide to “gray” publications—those that are in-process, still being thought through, drafty
- Sketch out a staff map of who will be involved, from interactions with the author, preparation of materials, editorial discretion, direct engagement with the platform:
- what is expected of them, and for what parts of the process?
- Will this be true of every project, or will different staff be used for different projects?
- How will you treat Resources versus Texts in terms of editorial oversight and vetting—will those concerns be decided by acquisitions, editorial, or production staff?
- Do you want to create a pipeline for iterative projects to flow through into standard production processes or should they remain completely distinct, with a handoff from one process to another?
- Staff skills that will be useful:
- Basic familiarity with HTML (and its structure)
- Understanding of how cascading style sheets (CSS) function
- Experience using content management systems (CMS)