Month: May 2018

Server update, 2018-05-30

React migration resumes with this server release which features rewritten area search results page and fixes a few regressions in editing forms. Thanks to reosarevok who added support for crediting label in relationship. Beatport, Musopen (score) and six other databases are now handled as external links. Some more small issues have been addressed too, including web service/collection bugfix, release display improvement, and other external links updates. The git tag is v-2018-05-30.

Sub-task

  • [MBS-9719] – Convert the area search results page to React

Bug

  • [MBS-9675] – Lyrics language dropdown missing while creating works from the relationships editor
  • [MBS-9676] – Cannot select work attributes on non-English localisations
  • [MBS-9704] – 400 Bad Request error when requesting user-tags (or user-ratings) and user-collections
  • [MBS-9710] – Release editor: Add a new recording: You haven’t made any changes!
  • [MBS-9715] – Non-standard barcode entering broken

New Feature

  • [MBS-9630] – Extend relationship credits to labels

Task

  • [MBS-9565] – Update the CD Baby logo used in the sidebar
  • [MBS-9609] – Update the Bandsintown logo used in the sidebar
  • [MBS-9646] – Normalize Bandcamp URLs to https
  • [MBS-9670] – Update the Facebook logo used in the sidebar
  • [MBS-9700] – Extend BnF URLs auto-select, cleanup and validation to instruments

Improvement

  • [MBS-6130] – Clean and validate Beatport URLs
  • [MBS-8629] – Hide part works from release view
  • [MBS-9326] – Add Beatport links to the sidebar
  • [MBS-9614] – Match musa24.fi with the “purchase for download” release-URL relationship type
  • [MBS-9618] – Extend setlist.fm URL auto-select and validation to series/festivals
  • [MBS-9682] – Allow selection of “download for free” with Google Play
  • [MBS-9684] – Add DRAM to the other databases whitelist
  • [MBS-9685] – Auto-select, clean and validate Musopen URLs as score download for free for works
  • [MBS-9694] – Add TouhouDB to other database whitelist
  • [MBS-9697] – Add the Library of Congress Name Authority File to the other DBs whitelist
  • [MBS-9698] – Add SNAC to the other dbs whitelist
  • [MBS-9702] – Add Prog Archives to the other DBs whitelist
  • [MBS-9717] – Add NDL Authorities to the other DBs whitelist

GDPR compliance

The General Data Protection Regulation is a complex EU regulation that stipulates many points for protecting private data of users on the Internet. Even though this is an EU regulation, it has a worldwide impact due to the nature of the Internet. This regulation comes into effect today, May 25, 2018 and is the reason why so many companies have sent you mail in the past few weeks about updating their privacy policies.

The MetaBrainz Foundation with its collection of projects is also affected by this regulation. We’ve been learning and adapting our sites to be compliant with the regulation – sadly this regulation isn’t entirely black and white and there is an incredible amount of room left for interpretation of these rules.

The good news is that this regulation is roughly in line with our established practices: We’ve always held private information in a high regard and applied the sort of rules to ourselves as we wish to have our own private data treated. Luckily, this makes our compliance effort considerably easier. We’ve made two significant changes to how we treat your data and also adopted terminology as used in the GDPR in order to use the same languages that many other sites are now adopting. Please keep reading to find out the exact details of what we are doing to comply.

However, we do ask for your compassion and help in our process of complying with the GDPR. As we already mentioned, the GDPR is a complex set of rules that are not fully clarified yet. We’ve taken action on the steps that are clear to us and we’re following ongoing conversations on points that are in gray zones or unclear to us. We’ve made our best initial effort on compliance and promise to keep working on it as the picture becomes more clear. If you believe that we could improve our compliance, please contact us and let us know what we can do to improve. It would also help us if you could provide concrete discussion or examples to help us understand and take action on your suggestion.

Finally, below is the link to our GDPR compliance statement, implementing the regulations as we understand them and how they affect your data in our ecosystem. Where possible, we provide links for deeper understanding, links for you to examine our relevant code and links to tickets to follow the process of improving our compliance.

MetaBrainz’ GDPR Compliance Statement

 

Server update, 2018-05-09

This bugfix release mainly addresses UI regressions from the previous server release. Thanks to reosarevok, it now handles license links for works and SoundCloud links for places. Another change is that emails sent with a hidden address from the website by other editors are now using noreply@musicbrainz.org like other emails from the website do. The git tag is v-2018-05-09.

Bug

  • [MBS-9658] – /instruments page breaks if a new instrument type is added but not used
  • [MBS-9673] – Entity search options in the header are no longer translated
  • [MBS-9693] – Tags without vote are not immediately visible
  • [MBS-9705] – Overview tab link is now appended with /show
  • [MBS-9708] – Querying area containments is very slow

Task

  • [MBS-9639] – Extend Soundcloud relationship to places
  • [MBS-9688] – Add autoselect and cleanup for work license rel
  • [MBS-9692] – Normalize VocaDB and UtaiteDB URLs to HTTPS
  • [MBS-9696] – Replace @users.musicbrainz.org with noreply@musicbrainz.org in hidden email From field