I’ve noticed an interesting side-effect to using Bibliocloud. If you use one of the features that presents data in a human-readable way, it completely alters your data-management-motivation levels.

Take websites. Over Christmas, I released the new Snowbooks.com website. From the design point of view, I hope it’s good: legible, navigable, easy on the eye, a great showcase for our wonderful books, and helpful for customers to be able to choose where they can shop.

Jan 09 2018 13 27 40

(As an aside, from the technical point of view, it was a complete joy to write. It’s a Jekyll app, which is a way to write static websites. That means you use the Ruby programming language to combine data about your books with templates for the website to create all the HTML files on your computer, then upload the finished files to the internet – you don’t rely on a server to draw together data on the fly. And it uses the response from a request to Bibliocloud’s API as its data source. As part of General Products’ Side Project Friday Afternoon Initiative, I’m preparing the code to be open sourced, so hopefully other people might consider writing adapters to other data sources. Drop me a line if you’re particularly interested!)

The point is that when I was developing this website, it made me want the pages to look good. I mean, I was spending time creating something which is our shop window. I wanted it to look as nice as possible. And, with that hat on, one’s eye is drawn to ugly blanks and missing data. Cue a big flurry of metadata updating, as I variously:

  • uploaded higher-resolution images when the one I was pulling from Bibliocloud was a bit on the fuzzy side
  • made sure everyone was credited, and in the correct order
  • made sure the latest reviews were front and centre

Screen shot 2018 01 09 at 13.57.08

and, most interestingly

  • came up with new series groupings of books which, post-publication, I decided sit together nicely on the page. Welcome to the world, Snowbooks Gothic, Snowbooks Fantasy Originals and friends!

Screen shot 2018 01 09 at 13.41.12

Which additionally appeared on websites around the world the next day, as ONIX carried the good news:

Screen shot 2018 01 09 at 16.27.36

It might be a bit extreme to spark up brand new series on a whim, but it’s interesting how seeing your data presented in a new way can inspire new ways of looking at the list. And now the books are related to each other in a new and discoverable way in our ONIX.

Catalogues

As a minimum, it certainly makes you notice where data completion could be improved. Treasured client Pharmaceutical Press used an XML export from Bibliocloud to populate their catalogue this week, and found the same thing as me: their bundled student packs now include images where previously the metadata hadn’t necessarily needed to be so rich. Their catalogue benefits from another image, and in the process, almost as a side-effect and certainly with no additional work, their metadata is that much richer.

Screen shot 2018 01 09 at 13.47.21

Advance information sheets

The classic part of the system that prompts this sort of work is the advance information sheet. We’re all guilty of only getting our data up to date when we need it for the sales conference – and it makes it so much easier to see data when it’s in a human readable format. I often output a whole bunch of AIs as a ZIP file in one go from Bibliocloud, and flick through them on Finder on my laptop, to get a sense of whether I’m pleased with the blurbs, the pricing and so on.

Ais

Crowdsourcing quality

When you put your data into a human-readable format, you hope there’s a chance that a human other than yourself might read it. This is great: the more eyes the better. This just in from prized and beady-eyed author Jonathan Green:

Screen shot 2018 01 09 at 14.22.25

The right format for the job

Bibliocloud is not just about getting data into a format suitable for computers to share: just as valuable is getting data into a format that works for your brain. I’m a sucker for a pretty picture, but I’m happy that it’s improved my metadata quality.

Archives

    Most popular

  1. Ruby code and why you should care
  2. A quick look at data visualisation and analysis
  3. Menial publishing jobs are destroying our future
  4. It's us in the industry who need to be able to code
  5. A manifesto for skills
  6. Learning how to code, the long way around
  7. Company news

  8. New website
  9. 2018 Customer survey report
  10. 2017 in review
  11. Sara O'Connor to join the team!
  12. And now we are five
  13. Prizes galore
  14. Product news

  15. 'Continuing to solve real problems': Futurebook 40, London Book Fair 2018 and the Works page
  16. How many authors is too many?
  17. Better ONIX fragments
  18. Advanced advance information!
  19. Schedules page
  20. Publishers hack their own bibliographic data
  21. Case studies

  22. Burleigh Dodds Science Publishing
  23. Zed Books
  24. IOP Publishing
  25. Code

  26. A publisher’s guide to APIs
  27. What publishers need to know about Ruby on Rails
  28. How APIs can make publishing more efficient
  29. A day in the life of a programmer
  30. eCommerce

  31. To go direct, publishers must mean business
  32. Don’t outsource your publishing business away
  33. Who has the balance of power over data?
  34. Inbound marketing
  35. The business case for going direct
  36. Why publishers must use direct sales
  37. ONIX

  38. A hidden benefit
  39. Thema Subject Codes Update November 2017
  40. ONIX. Not very standard
  41. Three ways to do more with ONIX
  42. A non-technical, beginners’ guide to ONIX for Books
  43. ONIX Changes
  44. BIC, Thema and artificial intelligence...
  45. How to create a catalogue automatically using ONIX and InDesign
  46. Skills

  47. Embrace the code
  48. Mechanical sympathy
  49. Publishers can learn a few things from programmers
  50. A taste of code
  51. Strategy

  52. Rejuvenation
  53. Why ‘easy’ publishing solutions hardly ever are
  54. The right tool for the job
  55. No computer system can fix a broken publisher
  56. Five things I've learned since moving into enterprise product management
  57. Managing expectations
  58. Start with Why – How to refine your publishing mission
  59. The real price of a strategy shift
  60. Technical debt
  61. Decisions, decisions
  62. Creative industries and the division of labour
  63. A company of one's own.
  64. Responsibility, Authority, Capability
  65. Sometimes, size matters
  66. The search for publishing's holy grails