|
|||||||||||||
|
Adding to Your Editorial Tool Kit: Image Research and Permissions Date: Tuesday, March 24, 2009 To describe copyright law as complex is an understatement, but navigating these murky waters isn't impossible. The panelists at the March forum in San Francisco presented some best practices for tracking down and negotiating rights to content. Image Research Kris Ashley is an established copyeditor who also performs art and image research for book publishers. Veronica Oliva is an experienced permissions editor who currently works on college-level foreign language and trade books. Tim Cox is a technical editor who has experience obtaining permissions for content in computing and engineering from professional journals, individual artists, movie studios, and video game companies. When asked about her background as an image researcher, Kris said that "you don't need a degree in art history; an enjoyment of research and art, good Internet skills, and patience are all that are required." Most books need images. If you're lucky, the author or the publisher knows what he or she wants, but usually it's not that simple. Kris recommends querying and gathering as many search parameters as possible and then delving in to the numerous resources available. When looking for images, it's best to find at least two or three versions of what you want that are at a (minimum) resolution of 300 dots per inch (DPI). Most images are accompanied by caption and credit files. The caption file contains suggested information to include from the image house. The credit file contains the artist's name (and the photographer, if applicable) that must be included. When it's time to get down to work, Kris suggests knowing the following:
If you're a freelancer, Kris also highly recommends negotiating the rights in your client's name, not yours, to protect yourself from any legal trouble down the line. Permissions Veronica Oliva and Tim Cox came to permissions editing in unique ways. Veronica began her career as a copyeditor and became friends with the head of the permissions department at the company she was working for. "I am a nosy person. I want to know everything." So, getting to the bottom of securing rights seemed like a fit with her natural curiosity and enjoyment of working with people. Tim's work in publishing computer graphics textbooks required that he learn the ins and outs of acquiring permissions because most of the computer graphics content comes from the entertainment industrya proverbial can of worms. Veronica summarized the task of the permissions editor in a very simple statement: "We clear rights." The basic tenet of copyright law is that a person has the right to reproduce, distribute, perform, and display their work. As such, it is important to properly obtain the right to reproduce an intellectual-property owner's work. For Veronica, her job is to "keep my clients out of trouble." She offered some resources for those considering this role. Copyright law is complex. As Tim stated, "Copyright law is not one thing, but a bunch of elements grouped together. Lawyers refer to it as a 'bundle of sticks.'" Just a few of these elements are reproduction rights, translation rights, publication rights (not the same as reproduction rights), fair use issues, and the ever-problematic electronic rights. Both Tim and Veronica presented a few guiding principles for dealing with permissions rights:
Tim told the story of clearing rights to some images from Sony for a book on gaming. A higher-up feared some potential revenue losses from releasing these images until Tim asked a colleague who worked at Sony to convince the person that granting these rights would likely increase revenue.
******** Micah Standley is the associate editor of artistic publications for San Francisco Opera. He has written and edited for projects ranging from music and opera to veterinary medicine and quilting. He is also a freelance musician.
|
||||||||||||
home |
find the right editor |
membership |
about us © 1997–2024 Bay Area Editors' Forum. All rights reserved. ~~ Responsive CSS (beta) ~~ |