Monday 23rd October - SLC4 and onwards

[g105b]

• Summarised the upcoming milestones SLC 4, 5, 6.
• They have all been previously discussed.
• Problems exposed with the way data is inconsistent - Richard John Birkin, John Richard Birkin, etc. Need a way to rectify the data within TS.

Future thoughts

PRS data is not linked to sales data in any other way than song title.

This reminds us that PRS are only concerned with writers, not recordings.

PRS = ISWC. Everyone else = ISRC. It's a known issue within the music industry that these don't match up, even though the usage of a product always means the writer getting paid. Therefore we do need a TS Entity that embodies the publishing and master copyrights (and any other copyrights that come from the song/tune/track), so that we don't rely on matching directly to song title or artist title - rife with problems.

By doing this, we will pave the way for "TS Album / TS Collection", but the TS Tune is the building block, because a TS Album/Collection will be full of TS Tunes.

Off the back of this, we'll be able to filter by how much each album earns, or how much each artist has earned in a period.

Over-simplification: a checkbox next to each product in the table, which when checked, displays a dropdown of actions - for example, "Merge all artists to ...", "Put these products in an album".

What we need to concentrate on is doing this automagically, without having to ask the user. Just like how we do it with the album artwork - we can ask Spotify or other APIs to fill in the blanks when we've got some unambiguous data.

Create new product

When a new product is being made (before there's necessarily even a recording), the label needs a way to organise everything - what are we going to call this product, what are its IDs (UPC, etc)?, what is its artwork?

All of this would usually be done within a Dropbox folder or something similar. So why not make Trackshift the place to organise things that will inevitably be uploaded here anyway?

New feature: output/export this data. A single page that can be shared publicly, that holds all of this information on a TS Product, that can be sent to a distributor.

This page can be filled with existing products' data as the label sales data is uploaded.

Login

This is getting more and more important. We want to allow users to log in using Authwave to persist their data forever.

The implementation will be easy, but the knock on effects are more important: we need to change the way small tweaks of functionality are made, changing our approach from tweak-n-push to fully tested deployments each time - we can't ever "rewind" the code from this point on.