It’s been a long time coming, but here – just in time for Christmas – is a new Schedules page. Log in to Bibliocloud and go to /schedules, where you can click to preview the new version: Screen shot 2017 12 23 at 20.16.51

You will be able to flick back and forth between the current and the new version for a while – at least until the end of January 2018. And we’ve only made the first changes available for preview so far, meaning that this is a work in progress. Feedback is definitely welcome, as ever.

Here’s how the new page is looking: you’ll want to log in to your own account to see your own data.

Screen shot 2017 12 23 at 20.20.54

You can click through to the tasks page to see the detail behind the task counts.

This is the first stage in redesigning this page. Further development will make it possible to:

  • Add, edit, duplicate and delete schedules
  • Open a panel to view all tasks on a schedule, as well as potentially tabs for ‘Roles’, ‘Issues’ and other data relevant to a schedule.

We’d love to know:

  • Does this page help you answer the question of where you are with your schedules, and what needs doing?
  • Is there anything missing that is important for you?
  • What data would you find particularly valuable in the open-and-close panel for each schedule, to help you answer the questions important to your work?

Please email with your thoughts, or raise a support ticket.

By the way, this is the first product update blog post that we’ve included on Code:Read. Previously we’ve relied on the change log but feedback on our recent customer satisfaction survey suggested that clients would like more information about when new features are announced. So bookmark this blog in your browser, and subscribe to our RSS feed, too.

Many thanks from us all, and a very merry Christmas and happy new year!


    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. A manifesto for skills
  5. It's us in the industry who need to be able to code
  6. Menial publishing jobs are destroying our future
  7. Company news

  8. New website
  9. 2018 Customer survey report
  10. 2017 in review
  11. And now we are five
  12. Prizes galore
  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. How APIs can make publishing more efficient
  28. A day in the life of a programmer
  29. A publisher’s guide to APIs
  30. eCommerce

  31. Don’t outsource your publishing business away
  32. Inbound marketing
  33. Who has the balance of power over data?
  34. To go direct, publishers must mean business
  35. Why publishers must use direct sales
  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. BIC, Thema and artificial intelligence...
  42. Three ways to do more with ONIX
  43. How to create a catalogue automatically using ONIX and InDesign
  44. A non-technical, beginners’ guide to ONIX for Books
  45. ONIX Changes
  46. Skills

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

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