Well, that’s an intriguing headline.

Perhaps an even more stunning headline is Publishers Hack Their Own Bibliographic Software and the Software Provider Rejoices.

There was jubilation in the Bibliocloud office yesterday when Nick Barreto at Canelo sent an email about his shiny new tool that helps his team search Bibliocloud data from inside Slack.

It’s a fairy tale of well-built software supporting a forward-thinking publisher to streamline their workflow, so they can focus on the publishing.

In fact, it is the story of Biblicloud itself – publishers knowing what tools they need, having or gaining the coding skill to make those tools, and making them happen. No need to spend vast sums of money training developers that don’t understand the domain. Just spend a bit of time and get it done.

How can your team save time? Get the information to where they already are. Nick’s solution should save his team much clicking. We are so proud to have software that can support extension and improvement and innovation.

On top of that, Nick has made the code for the Slack integration open source, so that any other Bibliocloud customer can use it. This is exactly the kind of community we want our customers to be a part of, exactly the kind of community we want publishing to be. Let’s spend less time on drudge so we can spend more time selling books.

So, join us in celebrating Nick and all #publisherswhocode. We look forward to sharing and creating more innovation and automation with you in the future.

Archives

    Most popular

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

  8. New website
  9. 2018 Customer survey report
  10. 2017 in review
  11. Prizes galore
  12. And now we are five
  13. Sara O'Connor to join the team!
  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. What publishers need to know about Ruby on Rails
  27. A publisher’s guide to APIs
  28. A day in the life of a programmer
  29. How APIs can make publishing more efficient
  30. eCommerce

  31. To go direct, publishers must mean business
  32. Why publishers must use direct sales
  33. Inbound marketing
  34. Don’t outsource your publishing business away
  35. Who has the balance of power over data?
  36. The business case for going direct
  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. How to create a catalogue automatically using ONIX and InDesign
  44. ONIX Changes
  45. BIC, Thema and artificial intelligence...
  46. Skills

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

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