20.7 Endemic

Django-Music-Publisher 20.7 Endemic

New features

Index (home) page became clearer due to grouping of views. User manual was reorganised to follow the same structure. User manual links now lead to the relevant page in the user manual.

Basic CSV imports and exports for musical works, and JSON exports for releases were added. ISWCs can now be imported from CWR acknowledgements.

Processing of royalty statements was added. It is the most important new feature since the initial release. It can import statements in practically any CSV format. Processing is extremely fast.

Controlled writers with no society affiliation are now fully supported.

Increased default security

20.1.3

Bugfix release

Two bugs were fixed:

• During an automated deployment to Heroku, based on app.json, group fixture was not loaded.
• CWR acknowledgements from some societies were not processed correctly, the society was not recognized.

20.1.1

Security release

Django prior to 3.0.3 had a security issue. DMP did not use that part of the Django code, but it is always better to keep up.

Minor changes were made to documentation and docstrings.

20 Twenty

Django-Music-Publisher (DMP) 20 "Twenty"

It turned out that many music publishers have shown interest in DMP, but the installation process was not simple enough for them. Although installing DMP as a Django app via pip still works, the focus completely shifted to installing it as a complete project. Deploying to Heroku is now the default installation method.

All settings are now "flat", no dictionaries, lists, etc. Migration from the previous version might not be straightforward, but it had to be done. Database migrations are now squashed into two files. One with everything in the previous major version, and one with the differences since.

Django 3.0 makes the deployment much simpler, as it can now create a superuser from environment variables, so the version was bumped up. Sentry can now be used just by adding DSN to the settings.

Settings have been added that represent a global publisher agreement template. 50%/100%/100% is still the default, but anything less than that goes as well. As a consequence, writers can now also have mechanical and synchronization affiliations.

CWR 2.1 Revision 8 came out in late 2019, dealing with senders with 10-digit IPI name numbers. DMP was updated to comply. List of societies now includes all societies from CISAC.

Imported CWR acknowledgement files are now saved and can be previewed with basic syntax highlighting, that additionally, highlights rejected transactions and registrations.

One of the two JSON export formats was dropped, it was just confusing with no added value.

General documentation has been altered as well. It is now presumed that the reader knows something about music publishing and nothing about software development. Relevant videos from Music Pub Cartoons were added to the documentation.

Since CWR 3.0 specification came out with terminology more modern than in 2.x, DMP has been shifting as well. This process will continue until CWR 3.1 is fully supported.

19.7 Metanoia

Django Music Publisher version 19.7 Metanoia

Support for US publishers with entities in different PROs was dropped. If you need to manage multiple publishing entities, you need to run multiple instances of DMP and manage them separately.

Multiple recordings per work can be added. But medleys are still not supported, nor will ever be.

CWR 3.0 generation was added, though labeled as “experimental”. CWR 2.1 generation is still available, but it does not contain album data. Collecting societies decided not to use release/album data in work registrations any more. Django Music Publisher 19.7 maintained and extended the data structure dedicated to releases. It will become useful with additional modules.

CWR preview, for both versions, now includes basic syntax highlighting. CWR files are now zipped before the download.

All exports, two JSON formats and two CWR versions, are now based on a single data structure, which is becoming the default for other tools and services by the maintainer.

General documentation is now shorter, but more precise. User manual was rewritten and extended.

19.1.5

The last minor release in 19.1.

19.1.2

19.1.2

This update addresses the last of the detected bugs since CWR exporting capabilities have been added to the open source code and DMP Guru service came online.

Several publishers tested DMP Guru and registered hundreds of works successfully. They also asked some very important questions, which have been added to the FAQ.

Fixed bugs

CWR generation broke when an album was added without the data on the album label. Fixed.

No further bugs are known at this point.

Documentation

The FAQ has been significantly extended and reorganized. It also now includes questions related to DMP Guru, as this seems to be the dominant source of questions.

There are some further minor improvements to the documentation, mostly related to adding and editing works.

19.1.1

19.1.1

This release is based on feedback from users of Django Music Publisher through DMP Guru.

Fixed bugs

There were a couple of bugs related to the generation of CWR files in edge cases, fixed in this version:

• If release date was left empty, and there was some recording data, this would result in a badly formatted REC record.

• Titles and names were escaped as if they were HTML.

No further bugs are known at this point.

New features

There are several minor new features related to CWR exports. Now there is an internal note field, which can be changed even after CWR was created. This will add a little bit of clarity to the CWR files.

There are new filters for Works, allowing to filter works already in any of the CWR files or those in none, or based on acknowledgement files. In this way, it is easier to separate works not yet registered, as well as those that need a revision.

Documentation: Frequently Asked Questions

Documentation now features FAQ section. Most of the information in there is present in the User Manual, but as these questions were asked, they deserve to be answered.

There are some minor improvements to the documentation.

18.11 Santa Claus

18.11 - Santa Claus

This is a major release with many new options.

Here are most notable changes since 18.9 version:

Documentation

Documentation has completely been rewritten, now uses Sphinx, and is hosted on Read The Docs. As it is aimed at both music publishers and software developers, it has separate introductions for these groups, installation instructions, extensive user manual and the roadmap for future releases.

README has been reduced to a screenshot, shields and several links. With the new documentation, less is more here.

Doc strings are now very detailed and informative, resulting in a complete auto-generated technical documentation.

Continous integration and deployment

There are now 6 environments we are testing with. They now include typical combinations of database, Python and Django versions, as well as some additional settings. Test coverage is up to over 99%. We are getting there.

Settings have been updated and extended so they accept a lot of settings through environment variables. Upon success of all the tests, the master branch is automatically deployed to Heroku.

Interface improvements

Administration interface has had a lot of changes, though no new models have been added. The most notable difference is that recordings can now be added from the Album / Library CD interface, instead of opening each of the works separately. Also, from Artist interface, it is possible to add recordings and live performances of works.

JSON Export

Works can now be exported in JSON format, which can then simply be converted to various other formats by free online tools.

CWR Preview with Syntax Highlighting

With issues we have had with some societies who rejected valid CWR files (and admitted, apologized and fixed their validation and import procedures), CWR file preview with syntax highlighting has been added. Works only with CWR 2.1, using an external service for the actual highlighting.

CWR 3.0

CWR 3.0 Work registration export

CWR 3.0 work registration export has been added. Please note that CWR 3.0 specification is still not officially released. The purpose of this feature is to help with integration, and it is not ready for production.

Recording VS live performing artists

CWR 3.0 has added recording artist data to recordings, so the model has been extended accordingly. Please note that in CWR 2.0, as there is no such separation, both the recording artist and live perfoming artists get their respective PER records.

Artists now have ISNI numbers, though the validation is still not implemented.

Recordings, albums, etc.

CWR 3.0 has dropped the information about releases (e.g. albums) and Django Music Publisher will follow this. Currently, the only change is that catalog_number field has been removed. The data on albums is still maintained, as this information may still be valuable for future expansions towards recording-related rights.

Dropped support for Django 2.0

DMP hit a bug in Django, it was patched in 2.1, but not in 2.0, so the support for 2.0 was dropped.

Demo token integrated

We are looking for sponsors who would help out with financing the code that would remove the dependency on the external service. The service owner, also the maintainer of this repository, has made the service available for free for a month.

18.9.3

This is primarily a security release, as a dependency was diagnosed with a vulnerability.

Several minor fixes and improvements have been included, most notably the Acknowledgement
import process and related tests. Default societies now include Musicmark and ICE Services,
as Django Music Publisher has now successfully been used with both.