CWR Library

Python library for Common Works Registration was the first coded part of our music rights software. It is a low-level Python library, and all services based on it are made with Django.

When music is being created, the composition and lyrics (the work) come before the recording, or, very rarely, simultaneously. But never after. Thus the first major part of a musical rights management software must be the publishing part. And the first part of the publishing part must be the creation of data needed for registration.

Collecting organizations must allow import from CWR, although they may allow other means of registration of musical works. As a consequence, our system allows only CWR-compliant data. Strict validation is performed when data is created, edited or imported, without exceptions.

This guarantees that we can always create valid CWR files accepted in all PROs. Using the same data for other relevant systems, such as YouTube’s Content ID, then just comes naturally.

Free CWR Tools

Another reason why CWR library was first is that a software needs to be tested as soon as possible in real life situations.

We have repeatedly seen new online services promising and failing. We needed various sources of data in different formats, ranging from single works, simple Excel files to valid and accepted CWR files, as well as faulty ones. So, we devised a set of free tools that are just thin wrappers around our CWR library, fulfilling exactly this need. The fact is that they are unique and have been used by increasing number of people for learning and exploring CWR, as well as for creating registrations and processing acknowledgements,

Six months later, with GDPR kicking in, we were forced to do some changes. Some of these tools now have a subscription-based advanced version, and we have few new ones. But none of them saves any of the data on our servers.

First Services

The third reason is to be able to perform Data Conversion Services that so many publishers need badly: To get their data in order. To create valid CWR files they can send to their sub-publishers or directly to collecting organizations. To deal with acknowledgements, including rejects and conflicts. And, as soon as possible, both to start getting some money in and to learn and collect more data for next phases of development.

This service has lead to a revolutionary tool/service for US pubishers: EBR+ to CWR Conversion. Available through a web interface and through Dropbox App, it convert EBR files, optionally extended with additional columns for data on mechanical and synchronization rights, as well as agreements, into CWR files accepted world-wide.

We have few other conversion tools being tested, that include DDEX (MWN, RIN), conversion from exports from various services, etc.

REST API Service

Our REST API Service is a set of stateless API endpoints that allow CWR validation, generation, parsing, acknowledgement processing, etc. They are aimed at companies who are making their own software tools and don’t want to waste time on this. Or, quite often, got stuck.

Data Management Tool

We have two music publishing software solutions being built, a ‘full’ one, that is far from being finished, if ever. And a limited one, which is used in our data management service. None if them is available for licencing. Yet.