Metadata Mayhem: Choose Your Own Disaster

First things first, what's your familiarity with book metadata? [[Meta-what?]] I know what metadata is, but what the heck does that have to do with [[books]] I'm a metadata pro and I'm ready for a [[disaster]].

Metadata means data about data. Books can have over a hundred metadata points. Examples include the title and subtitle, the synopsis (back cover blurb), author's name and short bio, marketing data, etc. At Ooligan Press, this metadata is entered into an information management and distribution system called CoreSource. CoreSource distributes book metadata to more than 450 channels, including several retailers and libraries. Because of the vast size of this system, when errors sneak into the metadata, they can persist for a long time. It's difficult to trace the cause of the error (was it entered incorrectly or was there an error in how it was distributed or is it an error in how the channel is receiving the metadata) and even more difficult to get the resolution to spread. Are you ready for your first metadata disaster? [[Choose your level!]]

Book metadata includes any data points that describe the book. Examples include the title and subtitle, the synopsis (back cover blurb), author's name and short bio, marketing data, etc. At Ooligan Press, this metadata is entered into an information management and distribution system called CoreSource. CoreSource distributes book metadata to more than 450 channels, including several retailers and libraries. Because of the vast size of this system, when errors sneak into the metadata, they can persist for a long time. It's difficult to trace the cause of the error (was it entered incorrectly or was there an error in how it was distributed or is it an error in how the channel is receiving the metadata) and even more difficult to get the resolution to spread. Are you ready for your first metadata disaster? [[Choose your level!]]

[[Super easy]] [[Easy]] [[Medium]] [[Difficult]] [[Extra difficult]] [[Just bizarre]] (text-color:black)[[[Haunted level->haunted]]]

You enter a title's metadata into CoreSource. You've double-checked every last piece of data and gotten a second and third opinion. Everything distributes flawlessly. [[Celebrate]] [[Double-check]]

When your team does the pre-sales call with your account rep, the rep recommends you add keywords. You're confused because you definitely added keywords when you set up the title asset. What do you do? [[Check the title asset on CoreSource]] [[cry...]]

A few weeks after you've entered your newest title into CoreSource, you notice that the ebook (Kindle) and print listing are displaying as separete products on Amazon. Ideally, the products would appear as two different versions on the same product page so that readers can easily select the version they'd like to purchase. What do you do first? [[Cry->cryunlimited]] [[Check the assets in CoreSource]] [[Start support ticket]] [[Contact your account manager->mediumlevel]]

The author of your forthcoming title (We'll call it Book X) emails you to let you know that the synopsis for the book is outdated at their local library and a major bookstore in the UK. [[Who cares? It's only affecting two places->Ignore it; it's close enough]] [[Check CoreSource]] [[Reach out to the retailer in the UK]] [[Cry!]]

Are you sure? [[Yes]] [[No... ->First things first]]

Okay, [[Choose your level!]]

You go up to your colleagues and tell them all about this rare and amazing thing that just happened. They look at you with glazed eyes and nod politely because they're not sure who you are or what you're talking about. It's okay. Real heros don't always wear capes. Or have friends. You go home and celebrate with your cat. He's your biggest fan. <img src="https://images.pexels.com/photos/7725975/pexels-photo-7725975.jpeg" height="1260" width="750"> (text-color:white)[END] [[Would you like to try another level?->Choose your level!]]

No, it's really all correct. But then a week later, you have to update a line in the author bio. It takes 2 months to show up correctly. In that time, the author bothers you relentlessly and your coworkers judge you. [[Quit]] and possibly go live in the woods [[It's a thankless job, but someone's gotta do it]]

That's probably for the best. There's really no such thing as a super easy level. [[Would you like to try again? ->Choose your level!]]

If you enjoyed that, this is the right career for you! Would you like to try an [[Easy]] disaster?

The good news first: The problem is easy to identify The bad news: You transposed two titles and the keywords for the title in question ended up in another title asset. What do you do? [[Fix it immediately. Tell no one.]] [[Fix it and use it as a teachable moment.]] [[Comb through both titles carefully to make sure there are no other errors]]

Sure, why not? Everyone deserves a nice cry once and a while. But once you've gotten your feelings out, what's the first step you want to take to solve the problem? (text-color:red)[~~cry...~~] [[Check the title asset on CoreSource]]

Sure. It's early enough in the process that it doesn't make too much of a difference. Are you forgetting something? Oh yeah! I should [[Comb through both titles carefully to make sure there are no other errors]] [[No, I fixed it, we're good]]

Store this anecdote away for the next time you need to make a friend feel better. Or when you get a promotion and you're training your successor. Dream big. Are you forgetting something? [[No, I fixed it, we're good]] Oh yeah! I should [[comb through both titles carefully to make sure there are no other errors->Comb through both titles carefully to make sure there are no other errors]]

You find a few errors and fix them. It was embarrassing, but at least you don't have to deal with bigger issues down the line. Human error is part of the job. The more you learn about the process, the more likely you are to think systemically when there are issues and work preventatively rather than reactively. You did great! [[Want to try your luck at a harder level?->Choose your level!]]

...for now. But in another few weeks, other strange errors start to crop up and you can't figure out why. You spend hours tracing them back to their source, which of course, is you. There were other pieces of metadata that got mixed up between the two titles. You manage to sort it all out, but the metadata has been distributing for weeks and it's going to take a while to correct itself. [[F*ck this, I'm out of here]] [[Let me try again ->Easy]] [[I want to pick a different level ->Choose your level!]]

This is just too complicated! [[Fair enough]]

When you're doing your weekly metadata checks, you notice that an ebook retailer is showing your book's key selling points instead of the main description under the synopsis field. The synopsis is essential for piquing your readers' interest while the key selling points are helpful for letting people in the book trade (booksellers, librarians, publicists, reviewers, etc.) how to promote your book. Basically, you need to fix this issue ASAP. What's your first step? [[Cry]] [[Check the title entry in CoreSource->Don't Cry]] [[Start a support ticket->Don't Cry1]]

Crying is encouraged in metadata. But because this is the difficult level and time is of the essence, this will be the only time you're allowed to cry. Do you want to change your mind? [[Yes->Difficult]] [[No->C1]]

It's good to get your feelings out. But once you've gotten that sweet, sweet catharsis, what's next? (text-color:red)[~~Cry~~] [[Check title entry in CoreSource->C2]] [[Start a support ticket->C3]] [[Investigate other books on the same website->End-no support]]

Sure, that works. On average, support takes about 1-3 days to respond. While you're waiting, what do you do? (text-color:red)[~~Cry~~] [[Check title entry in CoreSource->CST1]] (text-color:red)[~~Start a support ticket~~] [[Investigate other books on the same website->CTS4]]

Ding ding ding! We have a winner! The plot thickens. You discover that 75% of your books on this retailer's website are displaying the key selling points instead of the synopsis. Now you just have to figure out why. Where do you go from here? [[Cry->they already cried]] [[Have a drink]] [[Contact account manager]]

Great idea! No matter how hard we try, sometimes mistakes sneak into the metadata. In this case, you're checking two fields: description and audience settings. Audience settings control where the information flows out to. For most fields, this is set to 'Unrestricted' so everyone can see it. For marketing and publicity fields, however, it should be set to Book Trade so that it only feeds to certain channels that booksellers, librarians, and other people in the trade look at. In this case, everything looks correct. What do you want to do next? (text-color:red)[~~Cry~~] (text-color:red)[~~Check the title entry in CoreSource~~] [[Start support ticket->CT1]] [[Investigate other books on the same website->End-no support]]

Sure, that works. On average, support takes about 1-3 days to respond. While you're waiting, what do you do? (text-color:red)[~~Cry~~] (text-color:red)[~~Check the title entry in CoreSource~~] (text-color:red)[~~Start support~~] [[Investigate other books on the same website->CTS4]]

Great idea! No matter how hard we try, sometimes mistakes sneak into the metadata. In this case, you're check two fields: description and audience settings. Audience settings control where the information flows out to. For most fields, this is Unrestricted so everyone can see it. For marketing and publicity fields, however, it should be set to Book Trade so that it only feeds to certain channels that booksellers, librarians, and other people in the trade look at. In this case, everything looks correct. What do you want to do next? (text-color:red)[~~Cry~~] (Text-color:red)[~~Check the title entry in CoreSource~~] (Text-color:red)[~~Start a support ticket~~] [[Investigate other books on the same retail site->CTS4]]

Drinking is also encouraged in metadata. After you've had your drink of choice, it's time to [[contact your account manager->Contact account manager]]

Your account manager gets back to you later in the same week. She lets you know that CoreSource has changed the way they do ebook metadata, and that you should no longer put Book Trade narratives (key selling points included) in the ebook asset. Even though it's only one retailer that's pulling in the wrong data, it's not a good look when most of your books are showing publicity highlights instead of a synopsis. It's certainly not going to entice readers to buy your book. Now that you know the problem, what's your solution? [[Do nothing. It's only affecting one retailer]] [[Document the process change, but don't change anything in CoreSource]] [[Delete key selling points for your frontlist titles]] [[Delete key selling points for all your ebook assets]]

You think I've forgotten? You've already cried once; you don't have time to cry again. [[Come on, get outta here->End-no support]]

You think I've forgotten? You've already cried once; you don't have time to cry again. [[Come on, get outta here->CTS4]]

In the middle of your third glass of wine, you get an email from CoreSource support. They're looking into the issue, and they'll get back to you. It's time to [[contact your account manager->Contact account manager]]

Alright, it's your choice. I will warn you, these things have a way of biting you in the ass later. Okay, okay, I give. [[Let me try again ->Contact account manager]] [[I'll burn that bridge when I get there]]

Always a good idea to document the process, especially when it changes. If you're a large publisher and/or you don't have a dedicated metadata team, going through all your titles can be daunting. It might be beneficial to fix your frontlist titles, however. Good point Let's [[delete key selling points]]! I stand by my decision. I'm going to [[Do nothing. It's only affecting one retailer]]

Good idea. If you're a mid-size or larger publisher, or you don't have a dedicated metadata team, going through your whole backlist would be quite an undertaking. Are you forgetting something? [[Nope! It's time to clock out!]] [[Hmmm...something's not right]]

You're a small publisher with a backlist of under 100 titles, 25% of which don't have an ebook asset at all. It takes a few hours, but the problem is eliminated, and it's gratifying to watch the issue clear itself up over the next few weeks. Are you forgetting anything? [[Nope! It's time to clock out!]] [[Hmmm...something's not right]]

Great idea! No matter how hard we try, sometimes mistakes sneak into the metadata. In this case, you're check two fields: description and audience settings. Audience settings control where the information flows out to. For most fields, this is Unrestricted so everyone can see it. For marketing and publicity fields, however, it should be set to Book Trade so that it only feeds to certain channels that booksellers, librarians, and other people in the trade look at. In this case, everything looks correct. What do you want to do next? [[Cry->DCT1]] (text-color:red)[~~Check title entry in CoreSource~~] [[Start a support ticket->DCT2]] Hang on, is this affecting other books on the same retail site? [[Investigate->End-nosupportnocry]]

Sure, that works. On average, support takes about 1-3 days to respond. While you're waiting, what do you do? [[Cry->DCS1]] [[Check title entry->DCS2]] (text-color:red)[~~Start a support ticket~~] [[Investigate other books on the same retailer site->End-supportnocry]]

Sure, that works. On average, support takes about 1-3 days to respond. While you're waiting, what do you do? [[Cry->DCTS1]] (text-color:red)[~~Check title entry in CoreSource~~] (text-color:red)[~~Start a support ticket~~] [[Investigate other books on the same website->End-supportnocry]]

Ding ding ding! We have a winner! The plot thickens. You discover that 75% of your books on this retailer's website are displaying the key selling points instead of the synopsis. Now you just have to figure out why. Where do you go from here? [[Cry->they haven't cried NS]] [[Have a drink->No support]] [[Contact account manager]]

It's good to get your feelings out. But once you've gotten that sweet, sweet catharsis, what's next? (text-color:red)[~~Cry~~] (text-color:red)[~~Check title entry in CoreSource~~] [[Start a support ticket->CT1]] [[Investigate other books on the same website->CTS4]]

Ding ding ding! We have a winner! The plot thickens. You discover that 75% of your books on this retailer's website are displaying the key selling points instead of the synopsis. Now you just have to figure out why. Where do you go from here? [[Cry->they haven't cried]] [[Have a drink]] [[Contact account manager]]

It's good to get your feelings out. But once you've gotten that sweet, sweet catharsis, what's next? [[Have a drink]] [[Contact your account manager->contactsupport]]

When you log back onto your email to contact your account manager, you notice an email from CoreSource support. They're looking into the issue, and they'll get back to you. Your account manager gets back to you later in the same week. She lets you know that CoreSource has changed the way they do ebook metadata, and that you should no longer put Book Trade narratives (key selling points included) in the ebook asset. Even though it's only one retailer that's pulling in the wrong data, it's not a good look when most of your books are showing publicity highlights instead of a synopsis. It's certainly not going to entice readers to buy your book. Now that you know the problem, what's your solution? [[Do nothing. It's only affecting one retailer]] [[Document the process change, but don't change anything in CoreSource]] [[Delete key selling points for your frontlist titles]] [[Delete key selling points for all your ebook assets]]

It's good to get your feelings out. But once you've gotten that sweet, sweet catharsis, what's next? (text-color:red)[~~Cry~~] (text-color:red)[~~Check title entry in CoreSource~~] (text-color:red)[~~Start a support ticket~~] [[Investigate other books on the same website->CTS4]]

It's good to get your feelings out. But once you've gotten that sweet, sweet catharsis, what's next? [[Have a drink->No support]] [[Contact account manager]]

Great idea! No matter how hard we try, sometimes mistakes sneak into the metadata. In this case, you're checking two fields: description and audience settings. Audience settings control where the information flows out to. For most fields, this is set to 'Unrestricted' so everyone can see it. For marketing and publicity fields, however, it should be set to Book Trade so that it only feeds to certain channels that booksellers, librarians, and other people in the trade look at. In this case, everything looks correct. What do you want to do next? [[Cry->DCST1]] (text-color:red)[~~Check title entry in CoreSource~~] (text-color:red)[~~Start a support ticket~~] [[Investigate other books on the same retail site->End-nocrysupport]]

It's good to get your feelings out. But once you've gotten that sweet, sweet catharsis, what's next? (text-color:red)[~~Cry~~] [[Check the title entry in CoreSource->CST1]] (text-color:red)[~~Cry~~] [[Investigate other books on the same retail site->CTS4]]

Ding ding ding! We have a winner! The plot thickens. You discover that 75% of your books on this retailer's website are displaying the key selling points instead of the synopsis. Now you just have to figure out why. Where do you go from here? [[Cry->they haven't cried]] [[Have a drink]] [[Contact account manager]]

It's good to get your feelings out. But once you've gotten that sweet, sweet catharsis, what's next? (text-color:red)[~~Cry~~] (text-color:red)[~~Check title entry in CoreSource~~] (text-color:red)[~~Start a support ticket~~] [[Investigate other books on the same retail site->CTS4]]

Some people just want to see the world burn, I guess. Meme "everything's fine" Would you like to try another level? [[Sure]] [[I'm exhausted! Get me out of here!]]

(text-color:red)[~~Choose your level~~] (text-color:red)[~~super easy~~] (text-color:red)[~~easy~~] (text-color:red)[~~medium~~] (text-color:red)[~~difficult~~] (text-color:red)[~~extra difficult~~] (text-color:white)[[[You should have thought about that before you made bad choices->First things first]]]. <div class="tenor-gif-embed" data-postid="14850927" data-share-method="host" data-aspect-ratio="1.79775" data-width="100%"><a href="https://tenor.com/view/anime-studio-ghibli-ghibli-movies-quotes-gif-14850927">Anime Studio Ghibli GIF</a>from <a href="https://tenor.com/search/anime-gifs">Anime GIFs</a></div> <script type="text/javascript" async src="https://tenor.com/embed.js"></script>

[[Would you like a cat picture before you go->Fair enough]]

You're good for a while, but then you go on vacation and your coworker creates a few new title assets using the old process. They put key selling points in the ebook asset, which then feeds out to that pesky retailer who displays the synopsis as the key selling points all over again! It's not a huge mess, but it still takes you time to notice and sort it out, and of course it takes a few weeks for the corrections to show up externally. [[Alright, alright, I get it.]] [[F*ck this, I'm out of here]]

You forgot to document the new process! Software is always evolving and it's important to keep up with the changes so that you don't end up repeating the same mistakes. [[Alright, alright, I get it.]]

You write up the new process in your handbook and you're all set! [[Would you like to try a different level ->Choose your level!]] [[I'm exhausted! Get me out of here!]]

Crying is encouraged in metadata. It's good to get your feelings out. You might also try throwing soft objects across the room or screaming into a pillow. Whatever helps you get the frustration out. [[Throw something]] [[Scream into a pillow]] [[No I'm good, let's get back to work->Medium]]

Always a great idea to go back to the source and see if anything was entered incorrectly. In this case, you pull up the ebook asset and the print pdf asset to compare them side by side. Both assets look accurate in terms of title and author. What's next? [[Start support ticket]] [[Contact your account manager->mediumlevel]]

Support gets back to you to say they've gotten in touch with Amazon to fix the issue. It may take a few days before you here anything. What do you do in the meantime? [[Cry->cry2]] [[Contact account manager->mediumlevel]] [[Check the assets in CoreSource]]

Not a bad idea. Your account manager connects you with a metadata specialist who checks over your CoreSource entries but doesn't find any mistakes. They suggest you check in with KDP to see if there's a discrpency in how the metadata was entered there. [[Check KDP->KDP1]] [[Ask the account manager if there's anything else you can try->Account manager]]

Well, you're at work. You can't really throw something. You decide to channel your cat and you gently push your lamp off your desk. It hits the carpet with a soft thump. Unfortunately, the cord from the lamp catches on the edge of your coffee mug and it tips over, spilling all over your desk and dripping onto the floor. You stare at the growing pool of coffee and can't help but appreciate the parallels. The coffee drenching your perfectly organized desk just as incorrect metadata spreads out into the far reaches of the digital world, obscuring all your hard work. You sigh quietly and then leave your office to go for a walk. You [[may]] or [[may not]] come back. <div class="tenor-gif-embed" data-postid="12118512" data-share-method="host" data-aspect-ratio="1.36111" data-width="100%"><a href="https://tenor.com/view/stain-coffee-stain-stain-less-no-stain-stain-free-gif-12118512">Coffee Stain GIF</a>from <a href="https://tenor.com/search/stain-gifs">Stain GIFs</a></div> <script type="text/javascript" async src="https://tenor.com/embed.js"></script>

Your boss overhears your muffled screams and, after deciding not to ask why you brought a pillow to the office, asks if there's anything they can do to help. [[Explain the situation and assure them you have everything under control->this is fine]] [[Explain the situation and ask for their advice->help]] [[Deny everything->gaslight]]

You tell your boss what's going on, but assure them you've already got a support ticket in and you'll get this figured out in no time. Your boss reminds you that the book will undergo a few more changes before it's finalized and this would be a good issue to sort out now before it gets any harder to track down the root cause. They ask again if you want their help. [[Take their advice->help]] [[Continue to insist that everything is fine->no really]] <div class="tenor-gif-embed" data-postid="5263684" data-share-method="host" data-aspect-ratio="1.80451" data-width="100%"><a href="https://tenor.com/view/this-is-fine-fire-house-burning-okay-gif-5263684">This Is Fine Fire GIF</a>from <a href="https://tenor.com/search/this+is+fine-gifs">This Is Fine GIFs</a></div> <script type="text/javascript" async src="https://tenor.com/embed.js"></script>

Your boss asks if you've checked to make sure the assets match in CoreSource. If you haven't done so already, you do this and tell them that everything looks like it matches. Then they ask you if you've checked Kindle Direct Publishing since that has to be entered separately. You hadn't thought of this. [[Tell them of course you looked at KDP, you're not an idiot->bluff]] [[Tell the truth->let them help]]

You tell your boss you have no idea what they're talking about, there was no noice, this isn't a pillow. Essentially, you gaslight them. But you tell one lie too many when you tell them that all the metadata is distributing perfectly. Your boss definitely doesn't believe you because metadata never distributes perfectly. They ask you again what's going on. [[You cave and tell them what's going on->help]] [[You continue to lie, hoping they'll leave so you can get back to solving the problem->asshole]]

Your boss leaves you alone to concentrate and you breathe a sigh of relief. But you better start that support ticket now since you told them that you'd already done it. [[Start support ticket]] [[Nah, I've got another idea->Medium]]

Your boss asks follow up questions about what KDP suggested that you can't answer. After ten minutes of listening to you lie out of your ass, your boss gives you a final, searching look and then decides not to contradict you. They tell you that they'd like a status report at the meeting tomorrow and then walk out of your office. You may have lied your way out of this one, but now you've got a suspicious boss and a tighter deadline. What do you do next? [[Scramble to check the KDP record->KDP1]] [[Continue to live on the edge & do nothing->okay, seriously, why are you here?]]

Together you look at KDP and find that the formatting of the title is different in KDP than it is in CoreSource. You contact the project team and confirm the correct format and change them all to match. You'll check again in 48-72 hours to see if that fixed the issue. [[Check back]] [[I'm sure it's fine]]

You check again in a few days and see that the two listings are still not linked. At this point, there's nothing else to do but reach out to either KDP or your account manager to see what's going on. [[KDP]] [[Account manager]]

It's not fine. Months pass and the issue hasn't resolved. By the time pub date rolls around, this has turned into a major problem. You lose. <div class="tenor-gif-embed" data-postid="24194168" data-share-method="host" data-aspect-ratio="1.84971" data-width="100%"><a href="https://tenor.com/view/boo-gif-24194168">Boo GIF</a>from <a href="https://tenor.com/search/boo-gifs">Boo GIFs</a></div> <script type="text/javascript" async src="https://tenor.com/embed.js"></script> [[Start over->First things first]]

KDP support gets back to you within a few days and reports that they linked the listings and it should be good from here. This is pretty frequent in book metadata. Sometimes you have to give a little nudge to get things moving. It's a vast, complicated, and mysterious system. Much like the vast and unknowable universe. This could be the end of this level unless you're up for another challenge. [[I'm ready to be done ->Choose your level!]] [[That wasn't too bad. I could be up for another challenge->side quest]]

Your account manager takes a close look at your metadata for the two assets. In addition to a mistake in KDP's metadata that resulted in the title being shared inconsistently accross platforms, they notice that your formats aren't linked in CoreSource. Listings usually find each other, but linking them by ISBN is an extra step to ensure the assets are tied together. [[That's ridiculous, can't you just ask Amazon to link the listings->KDP]] [[Seems like a lot of work->you're a lot of work]] [[That makes sense]]

The title formats have been corrected, but now Amazon is categorizing your mystery novel as a horror novel! Amazon categories are influenced by the [[BISAC->what's that?]] codes you enter in the metadata, but they have their own algorithim for categorizing books. In this case, when you went back and added the subtitle consistently across all metadata entry points, it triggered something in Amazon's system that made it think your book is a horror novel. Where would you like to start? [[Check the CoreSource title asset for probably the hundredth time->asset]] [[Reach out to account manager]]

BISAC codes are "the Subject Heading applied to a book can determine where the work is shelved in a brick and mortar store or the genre(s) under which it can be searched for in an internal database" according to Book Industry Study Group. They are standard in the United States publishing industry and supplemented by keywords that publishers use for SEO (search engine optimization). Retailers and libaries use the BISAC codes as a guide to run books through their own internal (often unique) categorization system. For example, libraries often use dewey decimal or Library of Congress headings. Indie bookstores use broader genres that are more curated toward their local audience. For example, an indie bookstore in one city might have a section dedicated to mushroom identification guides whereas another bookstore in a different city might have books on mushroom identification guides but it's not a big enough local interest to warrant an entire section.

Have you ever considered that you're a lot of work? <div class="tenor-gif-embed" data-postid="14625931" data-share-method="host" data-aspect-ratio="1.2749" data-width="100%"><a href="https://tenor.com/view/whatever-you-say-whatever-nevermind-idk-not-sure-gif-14625931">Whatever You Say Whatever GIF</a>from <a href="https://tenor.com/search/whatever+you+say-gifs">Whatever You Say GIFs</a></div> <script type="text/javascript" async src="https://tenor.com/embed.js"></script> [[Start over->First things first]]

You link the formats following the specific instructions given by your account manager. Now you know to do this going forward to keep all formats connected to each other as they make their way out into the world. After all, it's dangerous to go alone. <div class="tenor-gif-embed" data-postid="24669440" data-share-method="host" data-aspect-ratio="1.35021" data-width="100%"><a href="https://tenor.com/view/congratulations-gif-24669440">Congratulations GIF</a>from <a href="https://tenor.com/search/congratulations-gifs">Congratulations GIFs</a></div> <script type="text/javascript" async src="https://tenor.com/embed.js"></script> This could be the end of this level unless you're up for another challenge. [[I'm ready to choose another level->Choose your level!]] [[I'm ready for a challenge ->side quest]]

Great idea. Do you want to delete them from just your frontlist titles or backlist titles too? [[Just frontlist. I've got other fires to put out->frontlist]] [[I'll do the backlist too ->backlist]]

Frontlist it is. This is a task that will probably take you about 2 hours depending on how many titles you have. If you're a mid-size or larger publisher, or you don't have a dedicated metadata team, going through your whole backlist would be quite an undertaking. Great work! [[Would you like to try a different level ->Choose your level!]] [[I'm exhausted! Get me out of here!]]

This makes a lot of sense if you're a small publisher with a backlist of under 100 titles, 25% of which don't have an ebook asset at all. It takes a few hours, but the problem is eliminated, and it's gratifying to watch the issue clear itself up over the next few weeks. Great work! [[Would you like to try a different level ->Choose your level!]] [[I'm exhausted! Get me out of here!]]

You feel better after your walk and you head back to the office with a renewed sense of purpose. What do you want to start with? [[Check the assets in CoreSource]] [[Start support ticket]] [[Contact your account manager->mediumlevel]]

You decide to call it a day and go home to cuddle your cat. Sometimes in metadata, you just need a hard reset. [[Go back to work the next day refreshed->Medium]] [[Quit and go live in the woods->quit]]

You just published an anthology that has 33 contributors and 2 editors who compiled and arranged the entries. You decide to put the editors as the main contributors and the full list of authors in the main description. Amazon has all 33 contributer listed in the author field and doesn't include either of the editors. What do you do? [[Start a support ticket]] [[Ignore it; it's close enough]]

Why did you even click on this level? <div class="tenor-gif-embed" data-postid="12409850" data-share-method="host" data-aspect-ratio="1.32886" data-width="100%"><a href="https://tenor.com/view/sabrina-funny-slap-cat-gif-12409850">Sabrina Funny GIF</a>from <a href="https://tenor.com/search/sabrina-gifs">Sabrina GIFs</a></div> <script type="text/javascript" async src="https://tenor.com/embed.js"></script> [[Go back->Choose your level!]]

Support comes back and tells you that they've submitted a request with Amazon to correct the issue. You go and look at it and now all of the the contributors are credited as editors. The two editors are listed at the bottom of the list, but one of them is credited as an author. [[Submit another support ticket]] <div class="tenor-gif-embed" data-postid="23205485" data-share-method="host" data-aspect-ratio="1.33333" data-width="100%"><a href="https://tenor.com/view/facepalm-hopeless-really-seriously-embarrassed-gif-23205485">Facepalm Hopeless GIF</a>from <a href="https://tenor.com/search/facepalm-gifs">Facepalm GIFs</a></div> <script type="text/javascript" async src="https://tenor.com/embed.js"></script>

You explain in more detail what the issue is and what you would like resolved. A week later, support emails you back to say that your ticket has been updated. You look at the title in question on Amazon and are dismayed (to put it lightly) to see that all 33 contributors are still listed in the author field. To make matters worse, they are all attributed as editors and one of the editors is attributed as the author. [[Submit another support ticket->ticket]] [[Check Kindle listing]]

A week goes by and nothing happens. [[Submit another support ticket->supportticket4]] [[Check Kindle listing]]

The Kindle listing lists just the two editors, but one of them is attributed as the author. You take a screenshot to send with your next support ticket. [[Find out what happens next->supportticket4]]

Another week goes by and then you get an email that your support ticket has been updated. Filled with a sense of dread but trying to remain hopeful, you head to Amazon. The contributors are no longer listed as editors, but all 33 of them are still there. One of the editors is still credited as an author on both listings. [[Once more unto the breach]]

You submit another support ticket, describing the issue in painful detail. Finally, two weeks later, the paperback listing correctly lists both editors! You look at the Kindle listing and it's correct except that one of the editors is listed as an author. What's next? [[I'll take the win where I can get it]] [[Be a perfectionist, try to get the Kindle listing corrected->perfectionist]]

Good job! Sometimes, metadata is just bizarre and we don't know why. [[You can't win them all]] [[Would you like to play another level->Choose your level!]]

You go back and forth with support for a few more weeks. They finally email you the following: 'As ASIN XXXXXXXXX was published under KDP, we’re unable to make any changes or provide more information about this titles. Please contact the KDP team which is how it was submitted.' [[You can't win them all]] [[Would you like to choose another level->Choose your level!]]

But this guy's proud of you: <img src="https://cdn.pixabay.com/photo/2023/02/21/15/15/cat-7804480_1280.jpg" width="500">

Metadata is not for everyone, better to quit while you're ahead. [[Choose another level?->Choose your level!]]

The BISAC codes are correct in CoreSource. What's next? [[Reach out to account manager]] [[Reach out to Amazon directly]]

The account manager loops the metadata specialist in. They reach out to Amazon directly and tell you to check back if it's not corrected in 72 hours. You decide to give it a full week and then check it. It's still categorizing the paperback as a horror title. You reach out to your metadata specialist directly. They've grown used to seeing your problems in their inbox. [[Find out what the metadata specialist says->2nd attempt]]

It's best not to reach out to a retail channel directly. If you force them to update metadata for one channel, it can break the automatic feed between your title management system, which means manually updating that channel every single time you update your metadata for any of your titles. [[Retreat to safety]] [[Reach out to Amazon anyway]]

Good choice. Click [[here->asset]] to go back to the title asset page. Click [[here->side quest]] to go back to the beginning of the quest. And click [[here->quit]] to give up.

<div class="tenor-gif-embed" data-postid="24704058" data-share-method="host" data-aspect-ratio="1.79775" data-width="100%"><a href="https://tenor.com/view/blender-fire-explode-explosion-exploding-gif-24704058">Blender Fire GIF</a>from <a href="https://tenor.com/search/blender-gifs">Blender GIFs</a></div> <script type="text/javascript" async src="https://tenor.com/embed.js"></script> Now you've done it. You blew it all up. As you stare hollowly at the descruction you've caused, you know you'll regret this moment for the rest of your life. [[Time machine->Reach out to Amazon directly]]

You scour CoreSource and find no evidence of the outdated description in either the ebook or print asset. Your working theory for what happened is that the outdated description stuck somewhere further down the data stream and unfortunately, no amount of screaming into the voice of CoreSource is going to unstick that data. [[Reach out to the retailer in the UK]] [[Go into full on sleuthing mode]]

You check KDP and find that the formatting of the title is different in KDP than it is in CoreSource. You contact the project team and confirm the correct format and change them all to match. You'll check again in 48-72 hours to see if that fixed the issue. [[Check back]] [[I'm sure it's fine]]

<div class="tenor-gif-embed" data-postid="6207127" data-share-method="host" data-aspect-ratio="1.34831" data-width="100%"><a href="https://tenor.com/view/get-out-leave-gtfo-get-out-of-here-gif-6207127">Get Out Leave GIF</a>from <a href="https://tenor.com/search/get+out-gifs">Get Out GIFs</a></div> <script type="text/javascript" async src="https://tenor.com/embed.js"></script> [[Go back from whence you came->First things first]]

You dig further into the lie. You successfully convince your boss that everything's fine and go through all the steps to solve the problem that you know of, including starting a support ticket and checking the assets in CoreSource. A week later, you can't figure out what's going wrong with the metadata and support hasn't gotten back to you with anything concrete. Your boss brings the issue to you and expects answers, but you have none to give. You wish you could go back in time and figure this out without such a time crunch on your shoulders, but you can't. You're doomed. This is metadata purgatory and you'll have to wade through a sea of unresolved support tickets to get back into your boss's good graces. Essentially, you lose. <div class="tenor-gif-embed" data-postid="18744235" data-share-method="host" data-aspect-ratio="1.77778" data-width="100%"><a href="https://tenor.com/view/brooklyn99-papers-workpressure-office-workplace-gif-18744235">Brooklyn99 Papers GIF</a>from <a href="https://tenor.com/search/brooklyn99-gifs">Brooklyn99 GIFs</a></div> <script type="text/javascript" async src="https://tenor.com/embed.js"></script> [[Start over->First things first]]

404 Not Found. This pathway is not available. You need to learn to cry while you're working. That's the final test. [[Try again->Extra difficultalt]]

The retailer tells you that they can fix their listing but they got the data from a third party. What do you do next? [[Contact the third party]]

You're basically working back up the data stream to see where things went wrong. But the third party (we'll call them Nelson) never gets back to you. For now, it feels like you've hit a deadend on the retailer side of things. What do you want to do? [[Check the library side of things]] [[Search your internal documents->Gentle Sleuthing]]

Crying is encouraged in metadata. It's good to get your feelings out. You might also try throwing soft objects across the room or screaming into a pillow. Whatever helps you get the frustration out. Once you've gotten your feelings out, what would you like to do? (text-color:red)[~~Start a support ticket~~] [[Contact account manager->mediumlevel]] [[Throw something]] [[Scream into a pillow]]

The metadata wizard nudges Amazon again and gives you the same time frame within which to check back. Again, you wait a week. Again, the metadata is incorrect. [[Reach out again->3rd attempt]] [[Screw this, I'm storming the castle myself->Reach out to Amazon directly]] [[Triple-check CoreSource]]

The metadata wizard calls down the Amazon representative and it's now out of your hands. A few weeks later, you find out that this is probably part of a larger problem with Amazon and other retailers displaying inaccurate data descriptions. You start to believe it's all a conspiracy. You don't know where you can turn for comfort in the great existential wasteland that is your life. You go home. You turn on your lights. Your cat is there. [[Pet your cat]] [[Feed your cat]]

It's really all good. You're not hallucinating. [[You give up and reach out to your metadata specialist again->3rd attempt]]

Your cat nips at your fingers. You've forgotten to pay the cheese tax. [[Feed your cat]]

You feed your cat dinner and a few pieces of shredded cheese as a treat. He crawls into your lap and falls asleep purring. You turn on the TV and settle in, leaving your problems behind. After all, the metadata hasn't followed you home. It doesn't know where you live. You're safe here. <div class="tenor-gif-embed" data-postid="25525934" data-share-method="host" data-aspect-ratio="1" data-width="100%"><a href="https://tenor.com/view/cat-sleeping-pet-stroke-sleepy-gif-25525934">Cat Sleeping GIF</a>from <a href="https://tenor.com/search/cat-gifs">Cat GIFs</a></div> <script type="text/javascript" async src="https://tenor.com/embed.js"></script> [[Care to play another round? ->Choose your level!]]

You start searching through the book's shared Google drive, searching through tipsheets, press kits, marketing plans, every scrap of outward-facing content that was created for the book project. You eventually come upon something labelled [[CIP data->What's this?!]]. One big reason publishers submit a CIP application is to get the CIP data block that goes on the copyright page before the book goes to print. With the supply chain issues that wreaked havoc on the publishing industry in 2020 - 2022, many printers began asking for material much earlier. Print dates were shifted up to accomodate this, and the CIP application shifted accordingly. All this to say, the CIP application for Book X contains the old description. It was sent out mere weeks before the description was updated. What do you do with this information? [[Connect with the Editorial department.->Editorial]] They're the ones who submit CIP applications. [[Look at the Library of Congress records to confirm your suspicions]] [[Panic in the face of the vast metadata multiverse]]

You recall a case from a few months ago where a different author for a different book brought it to your attention that the description for their book was wrong on Google Books. You tried a few times to get CoreSource to correct it, but they eventually gave up and told you that the metadata was coming from a third party source and was beyond their control. Where do you want to sleuth first? [[Check Book X on Google Books->Google books]] [[Check the library side of things]] <div class="tenor-gif-embed" data-postid="4704059" data-share-method="host" data-aspect-ratio="1.85185" data-width="100%"><a href="https://tenor.com/view/spn-supernatural-castiel-misha-collins-gif-4704059">Spn Supernatural GIF</a>from <a href="https://tenor.com/search/spn-gifs">Spn GIFs</a></div> <script type="text/javascript" async src="https://tenor.com/embed.js"></script>

The more libraries you look at, the more confused you become. Sometimes, both the print and ebook record for Book X looks exactly as it should. Other times, both are hopelessly outdated. But then, bizarrely, you find a few cases where one of the records is correct and the other is outdated. It finally starts to click. You realize that there's another source of data out there. Multiplying. Spreading. Propogating more mistakes as it interacts with each new retailer or library. But what could the source of this be? [[Ask a librarian]] [[Panic->Panic in the face of the vast metadata multiverse]] [[Go deeper into sleuthing mode->Gentle Sleuthing]]

The Editorial department submits a correction request with the Library of Congress. Since the data block can take so long to recieve in the first place, you can count on this being a long drawn out process. What do you want to do next? What do you mean? It's out of my hands! [[Time to party]] [[Brainstorm how to eliminate this issue in the future->brainstorm]]

Sure enough, the Library of Congress entry is the same outdated description you're seeing on several library websites and the UK bookstore that started this whole mess. But why does Library of Congress have the outdated data in the first place? [[Hint->it has something to do with CIP]]

It's dangerous to panic alone. Here, have a buddy: <div class="tenor-gif-embed" data-postid="14392590" data-share-method="host" data-aspect-ratio="1.39888" data-width="100%"><a href="https://tenor.com/view/cat-galaxy-shocked-waah-gif-14392590">Cat Galaxy GIF</a>from <a href="https://tenor.com/search/cat-gifs">Cat GIFs</a></div> <script type="text/javascript" async src="https://tenor.com/embed.js"></script>

<div class="tenor-gif-embed" data-postid="17332939" data-share-method="host" data-aspect-ratio="1.08108" data-width="100%"><a href="https://tenor.com/view/supernatural-dean-winchester-jensen-ackles-happy-jump-gif-17332939">Supernatural Dean Winchester GIF</a>from <a href="https://tenor.com/search/supernatural-gifs">Supernatural GIFs</a></div> <script type="text/javascript" async src="https://tenor.com/embed.js"></script> [[Try another level?->Choose your level!]]

You team up with the Editorial department and the publisher to look at the production timeline. The metadata gets entered almost a full year before the publication date. The point at which the description gets updated is after pre-sales where we recieve feedback from the sales representatives about our metadata. This is about 7-8 months before pub date. The book goes to print about 3 months before pub date. CIP data usually gets submitted 6 months before the book goes to print, which is before pre-sales. You can move the CIP application any later but it will compromise the garauntee of getting the data block in before the print date. Or you can build in the option to submit a change request to LoC earlier in the event that the description changes. What do you do? [[I want to move the CIP application later in the process->CIP]] [[I want to build in a mechanism for submitting change requests earlier->change]] [[I want to keep searching for a better solution->research]]

There's really not a good answer to this one and to me, that's simultaneously the most frustrating and the most exciting thing about working with metadata. It's a lot of trial and error. It's a lot of tinkering. You're an engineer and an artist. If you make the "wrong" choice, the metadata errors can persist for years. But, if you stumble upon a new understanding of how something works, it can save you countless mistakes in the future. Sometimes it feels like a total toss up, but you can't make the argument that the work doesn't matter. Metadata is the (text-color:purple)[matter] that connects authors and readers in the evergrowing world of new content. Books matter. Metadata matters. <img src="https://cdn.pixabay.com/photo/2016/03/25/20/06/maine-coon-1279572_1280.jpg" width="825"> Thanks for playing!

There's really not a good answer to this one and to me, that's simultaneously the most frustrating and the most exciting thing about working with metadata. It's a lot of trial and error. It's a lot of tinkering. You're an engineer and an artist. If you make the "wrong" choice, the metadata errors can persist for years. But, if you stumble upon a new understanding of how something works, it can save you countless mistakes in the future. Sometimes it feels like a total toss up, but you can't make the argument that the work doesn't matter. Metadata is the (text-color:purple)[matter] that connects authors and readers in the evergrowing world of new content. Books matter. Metadata matters. Cats matter. <img src="https://cdn.pixabay.com/photo/2023/03/12/20/43/ai-generated-7847819_1280.jpg" width="800"> Thanks for playing!

There's really not a good answer to this one and to me, that's simultaneously the most frustrating and the most exciting thing about working with metadata. It's a lot of trial and error. It's a lot of tinkering. You're an engineer and an artist. If you make the "wrong" choice, the metadata errors can persist for years. But, if you stumble upon a new understanding of how something works, it can save you countless mistakes in the future. Sometimes it feels like a total toss up, but you can't make the argument that the work doesn't matter. Metadata is the (text-color:purple)[matter] that connects authors and readers in the evergrowing world of new content. Books matter. Metadata matters. <img src="https://cdn.pixabay.com/photo/2021/12/23/07/32/book-6888850_1280.jpg" width="825"> Thanks for playing!

You look up Book X on Google Books. The description is outdated there as well. You scroll down and see that the description says 'Provided by the publisher.' You start to wonder if you're the problem. . . <div class="tenor-gif-embed" data-postid="26994473" data-share-method="host" data-aspect-ratio="1.77778" data-width="100%"><a href="https://tenor.com/view/its-me-im-the-problem-taylor-swift-problem-taylor-im-the-problem-gif-26994473">Its Me Im The Problem GIF</a>from <a href="https://tenor.com/search/its+me-gifs">Its Me GIFs</a></div> <script type="text/javascript" async src="https://tenor.com/embed.js"></script> [[Next]]

You go to your local library, where the ebook description is correct but the print description is outdated, and ask where they get their metadata. They tell you that they get their print metadata from the Library of Congress, but their ebook data comes from Overdrive. You know CoreSource pushes metadata to Overdrive, which makes sense because the ebook data is correct. But as far as you know, Library of Congress isn't connect to CoreSource in any way, shape, or form. You thank the librarian and leave the library in a daze. You're not sure what your next move is. [[Look at the Library of Congress records to confirm your suspicions]]

Okay, I did put that last one in there just to use that gif. But in all seriousness, you start to do some digging into where Google Books gets their data. You find out that many books are entered or scanned through the Library Project. Basically, it's getting its data at least in part from libraries. [[Check the library side of things]]

CIP stands for Cataloging in Publication record. According to the Library of Congress, it is "a bibliographic record prepared by the Library of Congress for a book that has not yet been published. When the book is published, the publisher includes the CIP data on the copyright page thereby facilitating book processing for libraries and book dealers." This data block includes the LCCN (Library of Congress Control Number), which many libraries use to categorize your book. One big reason publishers submit a CIP application is to get the CIP data block that goes on the copyright page before the book goes to print. With the supply chain issues that wreaked havoc on the publishing industry in 2020 - 2022, many printers began asking for material much earlier. Print dates were shifted up to accomodate this, and the CIP application shifted accordingly. All this to say, the CIP application for Book X contains the old description. It was sent out mere weeks before the description was updated. [[Connect with the Editorial department.->Editorial]] They're the ones who submit CIP applications. [[F*ck this, I'm out of here]]

Several weeks after Book X has launched, you get a mysterious email from the author. Mostly, it's gibberish. They've always been a little odd. You click the link they've sent and it takes you to a retailer in [[Canada. . .->canada]]

You stare at the listing for a full thirty seconds before you can figure out what you're even looking at. The title and author's name are correct, but the cover is totally different. It's a concept that the cover designer brought in the beginning of the process, long before any of the other metadata struggles you've had with this book. It got rejected without ever being finalized. Yet here it is. Like a fragment of a nightmare, staring at you from this bookstore's otherwise cheery and inviting page. But it gets [[weirder...]]

You scroll down and read the book description, which, despite all the other struggles you've had getting the book description to update consistently across retailers and libraries, is perfectly up-to-date. Not a comma out of place. You scroll back up to inspect the options for purchase: ebook, paperback, and hardcover. The hardcover is odd because you never printed the book in hardcover, but bookstores sometimes have defaults like these set. It's not that weird. ...at least that's what you tell yourself, trying to ignore the pit of dread in your stomach. Which listing do you want to explore? [[ebook]] [[paperback]] [[hardcover]]

The ebook listing takes you to an affiliate site that sells ebook directly. The cover is correct on the affiliate site, but you gasp at what you see under the description. It's the key selling points. This is an issue you fixed several month ago. Why are the key selling points showing? Panic-stricken, you close out of the affiliate site and type the link to Book X's page on that site directly into the search bar of a new tab. It loads slowly as you feel your pulse quicken and sweat begins to creep down your back. When it finally loads and you scroll down, you breathe a sigh of relief. The description is correct. Must be some weird Canadian version of the site. You scroll back up and find that the cover, just for a moment, flickers to show the old cover, the one that never made it past the concept stage. Then it returns to normal. But you won't return to normal. An idea has possessed you. The metadata. It's haunted. [[paperback]] [[hardcover]]

The paperback listing, which is the page you thought you were already on, leads you to an entirely different book. You don't recognize it at first, but after a moment of staring at it, you start to see something familair. Then your own face is staring back at you in the middle of a black screen. You hear a thump and leap to your feet. Your cat comes running out from under your desk. You bend down and see that the computer has come unplugged. You breathe a sigh of relief. You feel so silly. It was just the cat. He's watching you from the kitchen now, his eyes gleaming in the otherwise dark room. You frown. When did it get so late? How long have you been chasing errors down the metadata rabbit hole? You turn back to your computer. Something moves across the screen and then you swear you see a figure reflected in the screen as if somene is standing right behind you. Your cat meows from the kitchen, a long, mournful sound in the otherwise empty house. You slowly turn around and see your bookcase. You can see how it might look like a figure looming in the background. You shake your head and start toward the kitchen to feed your cat. Behind you, the computer flickers back on. [[hardcover]] [[ebook]]

You click the hardcover listing, fully expecting the page not to even load because you never entered a hardcover asset into the metadata. But it does load. And you're shocked to see a totally different book appear on the screen. It looks vaguely familiar but you can't immediately place it. Then it comes to you: this was one of your comp titles. You can't even imagine how this mistake could have happened. You've never seen anything like it before. As you're staring at the cover, you see something move out of the corner of your eye. You look at the top of screen just in time to catch the letters of the author's name changing for the briefest of seconds. You swear you see the word RUN. But then you blink and it's back to normal. [[paperback]] [[ebook]]