Django Music Publisher – Options and Alternatives
This article is the second replacement of the original one. The original laid out very precisely what would one have to do in order to turn Django Music Publisher into a Saas. Here is the short version.
One would need to solve registrations, billing, and a few other pretty standard things. Actually, making it visually unique may take more time than all of the back-end development.
Django Music Publisher uses Django CWR Toolset - Original Pack for CWR validation and generation. One would have to pay for the subscription licence or replace this functionality with their own code.
With the first instance of Django Music Publisher in actual production and our work on a Software-as-a-Service started, the initial replacement article was a shorter article comparing a service based on automated installations of Django Music Publisher and the SaaS. None of it is relevant any more.
Since it was written, a new stable version of Django Music Publisher was released with many new features. On the other side, the SaaS release is near, so this is the second replacement.
Currently, we are working on both Django Music Publisher and a commercial Software-as-a-Service (SaaS). The SaaS is based on Django Music Publisher and whenever there is a feature being added that falls within “original publishers of original works” bounds, it is being added in the latter and then imported into the SaaS. In this way, both remain in active development.
The SaaS goes way beyond Django Music Publisher in many aspects, although it has very clearly defined bounds of its own. It includes writers, original publishers, and administrators, but nothing territory-related (no sub-publishers). It has several plans and a number of configurable settings, but at the end of the day, it is extremely uniform for all customers.
Even vanilla (unmodified) Django Music Publisher may be a solution for some original publishers. On one hand, it has a simpler interface, and it has far fewer data fields. Using it may be faster and less prone to errors. On the other, with Django Music Publishing almost any combination of permissions is possible.
Django Music Publisher, being open source, can be freely extended. This ranges from a simple “branding” involving changing header, footer and colours, to adding completely specific features.
Without going into details, these two projects have very different roadmaps after the November 2018 releases.
There are several good, and many bad, online alternatives. With some, there is NDA in place, so I will name none. There are other approaches, from having the data in spreadsheet formats to an option of creating an in-house software. We offer various related services in either case.