Usecases » History » Version 3
Version 2 (Alexander Blum, 10/27/2019 01:37 PM) → Version 3/8 (Alexander Blum, 12/13/2019 09:03 AM)
# Webgui
## Artist (Author/Performer) ...
- wants to register works for copyright ownership.
- wants an easy way to report writer splits and compensation splits early on in the process.
- wants transparent reporting of royalty streams.
- wants to track derivative works, and also benefit if successful.
- wants an easy and standard way to report which songs I am performing live to all interested parties.
- wants a method to authenticate the information credited to their work submitted by additional creators, collaborators, or other third parties.
- wants the ability to update ownership information changes over time.
- wants to know, if a song can be covered for free (e.g. creative commons or public domain)
- wants to know the conditions about licensing a sample from another's creation
- *(Later)* wants public and private methods to contact other creators.
- *(Later)* wants to have an complete view of all their metadata.
- *(Later)* wants a simple overview of the music industry.
- *(Later)* wants easy payment distribution between musicians.
- *(Later)* wants to export his/her repertoire to switch collecting society.
- *(Later)* wants to import his/her repertoire from music directories (e.g. Musicbrainz).
## Publisher
- *(Later)* wants to administer the repertoire of its clients.
## Visitor
- wants full internationalization and localization support.
## DJ
- wants Music Recognition Tech for compiling playlists of originals used in DJ mix repertoire uploads.
# API
## Repertoire
### Potential Licencee
- wants to check via third party software, if a playlist can be played for free (e.g. creative commons or public domain).
### DSP
- wants to know the music owners and their % split (which must sum up to 100%) and have the most up-to-date information. ...
- wants to know the following Info for licensing, registration and reporting:
- Track Title
- Track Version
- Track Artists
- Album Title
- (Parent) Label
- Track Timing
- Date of Recording
- Authors
- Publishers
- *(Later)* Administrators
- *(Later)* Splits (Publisher/Administrator)
- wants to know the following Catalog/Rights Info for each Sound Recording:
- Title
- Artist
- ISRC
- Label
- Territory
- *(Later)* Ownership Share %
- wants to know the following Reporting Info for each Sound Recording:
- Title
- Artist
- ISRC
- Label
- Ownership Share
- Territory
- Usage
- Revenue
- wants to know the following UX (listeners) Info for each Sound Recording:
- Title
- Artist
- Album
- wants to know the following Catalog/Rights Info for each Composition:
- Title
- Writer
- ISWC
- HFA Song Code
- Publisher(s)
- Territory(s)
- *(Later)* Ownership Share(s) %
- wants to know the following UX (listeners) Info for each Composition:
- Title
- Writer
- wants a catalog of recordings for copyright filtering service (e.g. UGC fingerprint) with identifiers of the same type used by the recording/work creators to accurately report usage information.
- wants to find the link between recordings and compositions, if it already exists.
- wants to find the interested parties that are the writers of a composition.
- wants to find the society affiliations of a writer.
- wants to find all the interested parties, both writers and publishers, that have a claim for a work.
- *(Later, Write)* wants to submit the link between recordings and compositions.
### Publisher
- wants to have a standardised way to access Composition Data:
- Song Title
- Composer(s)
- Publisher(s)/Administrator(s)
- ISWC
- Copyright Year (optional)
- wants to have a standardised way to access Recording Data:
- Song Title
- Artist
- ISWC
- ISRC
- Composer(s)
- Publisher(s)/Administrator(s)
- Release Date
- Copyright Year
- Lyrics (optional)
- *(Later)* Language
- *(Later)* wants an easy way to identify other publishers contributing to a collaboration irregardless of which PRO or society they are with.
### Label
- wants to check right holders before publishing a foreign recording.
### Collecting Society
- wants to map between the same assets being reporting on from different sources *("rosetta stone")*.
- *(After API Implementation)* wants to get information about details of a creation represented by another collecting society (query forwarding).
- *(Later, Write)* wants automated notifications when certain data are missing from song registrations or when conflicting data is complied I need to identify an authoritative source.
### Playlist Creation Site
*e.g. Jamendo*
- wants to reference creations in playlists of their users.
### DJ
- *(Later)* wants a complete database of all recordings with accurate and linked song metadata so all DJ performance music data can accurately be identified and reported to to PROs/NROs.
### Administrator
- *(Later, Write)* wants to import/export list and details of musicians' creations.
### Music Directory Service
- wants to verify/synchronize repertoire data.
## Licensing
### Potential Licencer
- wants to check via third party software the licensing conditions for an utilisation: Price, License, Licence Version, based on concrete tariff details.
### DSP
- needs to report the following Reporting Info for each Composition:
- Creation ID
- Usage
- Revenue
- Message ID (?)
### Label
- wants to license a new release
### Collecting Society
- *(After API Implementation)* wants to know the licensing conditions for an utilisation of a creation represented by another collecting society.
### DJ
- wants Music Recognition Tech for reporting playlists in DJ live events.
### Bar/Club Owner
- wants to register utilisations for playback via Black Box.
### Administrator
- *(Later)* wants to access the utilisation statistics of his/her clients.
### Radio Broadcaster
- wants to monitor the broadcast stream to register utilisation.
# File Processing
- DSPs want to obtain a copy of the audio file to be able to create an internal fingerprint for identification of usage or violation of copyright
## Artist (Author/Performer) ...
- wants to register works for copyright ownership.
- wants an easy way to report writer splits and compensation splits early on in the process.
- wants transparent reporting of royalty streams.
- wants to track derivative works, and also benefit if successful.
- wants an easy and standard way to report which songs I am performing live to all interested parties.
- wants a method to authenticate the information credited to their work submitted by additional creators, collaborators, or other third parties.
- wants the ability to update ownership information changes over time.
- wants to know, if a song can be covered for free (e.g. creative commons or public domain)
- wants to know the conditions about licensing a sample from another's creation
- *(Later)* wants public and private methods to contact other creators.
- *(Later)* wants to have an complete view of all their metadata.
- *(Later)* wants a simple overview of the music industry.
- *(Later)* wants easy payment distribution between musicians.
- *(Later)* wants to export his/her repertoire to switch collecting society.
- *(Later)* wants to import his/her repertoire from music directories (e.g. Musicbrainz).
## Publisher
- *(Later)* wants to administer the repertoire of its clients.
## Visitor
- wants full internationalization and localization support.
## DJ
- wants Music Recognition Tech for compiling playlists of originals used in DJ mix repertoire uploads.
# API
## Repertoire
### Potential Licencee
- wants to check via third party software, if a playlist can be played for free (e.g. creative commons or public domain).
### DSP
- wants to know the music owners and their % split (which must sum up to 100%) and have the most up-to-date information. ...
- wants to know the following Info for licensing, registration and reporting:
- Track Title
- Track Version
- Track Artists
- Album Title
- (Parent) Label
- Track Timing
- Date of Recording
- Authors
- Publishers
- *(Later)* Administrators
- *(Later)* Splits (Publisher/Administrator)
- wants to know the following Catalog/Rights Info for each Sound Recording:
- Title
- Artist
- ISRC
- Label
- Territory
- *(Later)* Ownership Share %
- wants to know the following Reporting Info for each Sound Recording:
- Title
- Artist
- ISRC
- Label
- Ownership Share
- Territory
- Usage
- Revenue
- wants to know the following UX (listeners) Info for each Sound Recording:
- Title
- Artist
- Album
- wants to know the following Catalog/Rights Info for each Composition:
- Title
- Writer
- ISWC
- HFA Song Code
- Publisher(s)
- Territory(s)
- *(Later)* Ownership Share(s) %
- wants to know the following UX (listeners) Info for each Composition:
- Title
- Writer
- wants a catalog of recordings for copyright filtering service (e.g. UGC fingerprint) with identifiers of the same type used by the recording/work creators to accurately report usage information.
- wants to find the link between recordings and compositions, if it already exists.
- wants to find the interested parties that are the writers of a composition.
- wants to find the society affiliations of a writer.
- wants to find all the interested parties, both writers and publishers, that have a claim for a work.
- *(Later, Write)* wants to submit the link between recordings and compositions.
### Publisher
- wants to have a standardised way to access Composition Data:
- Song Title
- Composer(s)
- Publisher(s)/Administrator(s)
- ISWC
- Copyright Year (optional)
- wants to have a standardised way to access Recording Data:
- Song Title
- Artist
- ISWC
- ISRC
- Composer(s)
- Publisher(s)/Administrator(s)
- Release Date
- Copyright Year
- Lyrics (optional)
- *(Later)* Language
- *(Later)* wants an easy way to identify other publishers contributing to a collaboration irregardless of which PRO or society they are with.
### Label
- wants to check right holders before publishing a foreign recording.
### Collecting Society
- wants to map between the same assets being reporting on from different sources *("rosetta stone")*.
- *(After API Implementation)* wants to get information about details of a creation represented by another collecting society (query forwarding).
- *(Later, Write)* wants automated notifications when certain data are missing from song registrations or when conflicting data is complied I need to identify an authoritative source.
### Playlist Creation Site
*e.g. Jamendo*
- wants to reference creations in playlists of their users.
### DJ
- *(Later)* wants a complete database of all recordings with accurate and linked song metadata so all DJ performance music data can accurately be identified and reported to to PROs/NROs.
### Administrator
- *(Later, Write)* wants to import/export list and details of musicians' creations.
### Music Directory Service
- wants to verify/synchronize repertoire data.
## Licensing
### Potential Licencer
- wants to check via third party software the licensing conditions for an utilisation: Price, License, Licence Version, based on concrete tariff details.
### DSP
- needs to report the following Reporting Info for each Composition:
- Creation ID
- Usage
- Revenue
- Message ID (?)
### Label
- wants to license a new release
### Collecting Society
- *(After API Implementation)* wants to know the licensing conditions for an utilisation of a creation represented by another collecting society.
### DJ
- wants Music Recognition Tech for reporting playlists in DJ live events.
### Bar/Club Owner
- wants to register utilisations for playback via Black Box.
### Administrator
- *(Later)* wants to access the utilisation statistics of his/her clients.
### Radio Broadcaster
- wants to monitor the broadcast stream to register utilisation.
# File Processing
- DSPs want to obtain a copy of the audio file to be able to create an internal fingerprint for identification of usage or violation of copyright