There are four areas where we can assist you when it comes to Common Works Registration:
This is usually the first step. Most of our current and potential clients have come with very bad data. Small publisher usually use Excel or some poorly built Access tool. Usually human errors are not detected. They persist and, even, worse, grow and spread. When larger sub-publishers receive such data, they put it into their systems without proper validation.
We have been correcting data-sets having from few dozen works to tens of thousands. 90% of issues in large data-sets are systemic and can be detected automatically, sometimes even fixed. Data that requires manual fixing can be separated and healthy data can immediately proceed to the next step (usually import into a database or direct conversion to CWR).
Invalid data can then further be separated by error type and sometimes even prioritized. And, as batches get fixed, they proceed to the next step.
Creating CWR files and dealing with issues
Registrations are usually the first step and, in order to create them in large batches, data must be converted to CWR or another format accepted by societies.
We can convert any data format that into CWR, providing that the initial file contains enough data for a minimal CWR. There is a free EBR and CSV conversion self-service at the moment on this site, but it is rather limiting.
Although we would recommend having a proper tool in the long run, fast registration or delivery of clean data in CWR format to the sub-publishers makes sense. We can create CWR files from clean data-sets and extend them with data from acknowledgment files.
Such data-sets can then, at a later point, be converted into a format that can be imported in virtually any tool.
Consulting on CWR
Many companies have created their own tools, but they keep failing when it comes to creation of acceptable CWR files. We can help in such cases, either through consulting or creating a micro-service that your tool can easily integrate with.
You send us the data, we send CWR file back and a list of works included, with explanations why some were rejected. We can deliver the data automatically to the societies that support it and receive acknowledgment files and then create reports.
It can be a stateless service, or it can have a database for tracking of versions of works delivered to different societies. RPC, SOAP, RESTful, GraphQL. You name it, we can code it.