Music Publishing Software - Batch Registration for Music Publishers
In the previous article, differences in needs among music publishers are described. In this one, the focus is on different types of software that support batch registrations of musical works, primarily in Common Works Registration format.
For a very long time, there was basically only two commercial software products that were used by music publishers, a very expensive on-site solution and ordinary spreadsheet software - Excel or one of the alternatives.
However, in the last few years, there have been dozens of new offerings, mostly software-as-a-service, aka “cloud” solutions, but also smaller tools (most notably mine) and open source solutions.
In most cases, useless solutions were made by a single person or a small team for a specific label and/or publisher and then put on the market. When they realized that other publishers have different needs, they tried to turn these solutions into more general ones. This approach, as opposed to a well-planned project, rarely works, even with good developers. And good developers are scarce.
Some of these solutions have been on the market for a few years now, although it is hard to imagine how anyone got any value for the money they paid. And we see new ones sprouting regularly.
Specialized single-feature tools
When it comes to registrations of musical works, there are few tools in this category, and most of them are on this website (see free, subscription and development tools), although publicly accessible databases (e.g. ISWC Net) may fall in this category as well.
While they do not offer a complete solution, it is actually possible to use these tools together with spreadsheet software (e.g. Excel) for world-wide CWR registrations. A few clients are doing it this way, the key tool in the workflow being EBR to CWR.
When it comes to registration of musical works, there are four open-source projects worth mentioning, described in another article.
Django Music Publisher is the only one with a database and user interface. It can be deployed with no technical skills.
The other three are under-the-hood libraries for the creation and parsing of CWR files. All of them require technical skills to set up.
Software as a Service (SaaS)
This has become a de facto standard when we think of a web-based business application. And when it comes to software solutions that allow CWR registrations, there are specialized solutions that primarily focus on registrations and more general ones, where registration is just one of many features.
Most of those registration-related features in services that primarily do something else are useless. The reason is that in all those cases, the registrations have come as an afterthought. By the moment the need for such a feature was realized, there was a lot of unvalidated and incomplete metadata in these systems.
It is hard to go back to paying clients and tell them that their metadata, often meticulously put into the system, is worthless. Another reason is that many have not even tried to do it properly.
Even some services, with the basic purpose of registering, do not do CWR properly. Although, things are getting better rapidly. Unlike the previous group, these services must get it right. It may be complicated, but it is their job.
In one of the next articles, the rationale for using specialized tools will be covered. But, generally speaking, you want the tools that do one thing or one tightly connected group of things well, not one tool that does many things poorly.
Locally installed systems
Such systems really belong in the previous century. Buying one today can only be seen as a desperate move. If your needs are complicated, there is really only one vendor, unless you choose to dive into development yourself. If you are considering the latter, then you are in the right place, as many articles cover that path.