Copy editors of digital scholarship must take into account the medium of the project.
A digital publishing program like ours, which prides itself on being platform agnostic, offers exciting potential for variety in the look and feel of final publication formats but also ensures that some of the production processes typical within a press can never be completely standardized.
As I mentioned last week and will write more about in the future, we have a responsibility to host the projects we publish, and while that hosting environment might be centralized, the process of migrating a project there from its development environment is very much determined by its underlying structure. There isn’t a set of steps we can apply to all the projects in the production pipeline because each project requires a different approach.
The process of copyediting a project must take into account the format and structure of the project.
Likewise, the process of copyediting a project must take into account the format and structure of the project. SUP, like any other established press, has a pretty streamlined process for this stage of production when it comes to books. Page counts normally indicate a ballpark timeframe for how long copyediting will take, and most professional copy editors are already familiar with the file types they’ll be working with. They are presumed to know how to leverage the affordances of basic software like Microsoft Word to manage and track their work. In other words, in most cases, a trained copy editor with a knowledge or specialization in the subject area knows exactly how to handle a manuscript and get the job done.