![]() ![]() Ask yourself what words and ideas the customer is likely to use when typing his query into a search engine. When writing a description for a book’s metadata, an excellent tactic is to put yourself in the shoes of the customer. Beyond that, the way an eBook is described offers competitive ground that, used strategically, confers distinct advantages. For example, the precise title, accurate spelling of the author’s name, and a 13-digit ISBN in the metadata can make the difference between a customer choosing your edition of that classic novel or buying one from a competitor. There is plenty of evidence to support this emphasis, including hard sales figures and success stories from our long experience in eBook distribution. Publishers metadata needs to be complete and maximized to give your titles the best chance of discoveraibility. ![]() Here at Vearsa we emphasize the importance of metadata to optimize sales. In our experience the answer to this dilemma lies in metadata - the numbers, words and phrases that are attached to an eBook listing, communicated down the value chain, and used by search engines such as Google and retailers like Kobo. Publishers of eBooks then, face particular challenges in helping customers discover books they may enjoy yet don’t think to search for. ![]() Online, a customer must already have some idea of what she wants, even if it is just a genre or a topic area. Online customers must already have some idea of what they want. Online, however, those traditional, visual hints are altered, and tactile cues are missing altogether. The admonition to never judge a book by its cover notwithstanding, the truth is that many a reader first notices a favourite book because of the cues presented by its cover design, size, colour or overall presentation. Customers in a physical space will often wander among the shelves, going to a specific topic area, browsing the selection and pulling out a book here or there because its title sounds interesting or its artwork grabs attention. If the talker is using a website API it is suggested to store the raw response from the server.Īll caches automatically expire 7 days after insertion.Choosing a book from the shelves in a library or bookstore is a very different experience from selecting an eBook online. pickle) it is suggested to store it as json or similar text format encoded with utf-8. The data attribute is binary to allow for compression and efficient storage of binary data (e.g. There are Searches that can be queried by the search term and they have a relation to zero or more seriesĮach series and issue have a boolean `complete` attribute which is up to the talker to decide what it means.ĭata is returned as a tuple ( or ) or a list of tuplesĪn issue consists of an ID, an series ID and a binary data attribute which is up to the talker to determine what it means.Īn series consists of in ID and a binary data attribute which is up to the talker to determine what it means. There are series that can be queried individually by an "Series ID" and they have a relation to zero or more issues There are issues that can be queried individually by an "Issue ID" and they have a relation to a single series Simplify ComicCacher to store a single binary data field and ID(s) If the ComicCacher is to be a generic cache for talkers it must assume ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |