Kendra Hub Features
Kendra Hub Features
- Kendra Hub will streamline requesting and negotiating sync rights. It will integrate with existing 'one-stop music licensing' services so that rights holders can send and receive from one application to multiple services.
- Kendra Hub will enable songwriters and artists to detail and manage split agreements. It will integrate with existing split services so that rights holders can maintain split agreements from multiple services within one application.
- Users will be able to pre-clear sample easily and simply. Sample creators will be able to present a menu of costs per usage.
- Users will be able to easily make claim requests to multiple CMOs (copyright management organisations) to update/correct their metadata stores. This mechanism will also act as a basis for conflict resolution process to enable clearer and cleaner dispute management.
- Incoming transactional/sales reports from CMOs (copyright management organisations), record labels and sales/distribution outlets (such as YouTube and Spotify) will be aggregated within Kendra Hub allow for cross referencing and cross verification.
- Kendra Hub will integrate with social networks, such as Facebook and Twitter (and the rest), making it easier to publish updates to fans and collaborators.
- Kendra Hub will enable users to mark their trust of semantic assertions. These trust marks can be one way and also bidirectional. Bidirectional trust forms strong trust between users and their assertions.
- The Kendra Hub prototype is being build with a widely used, open source framework called Drupal. Drupal is going from strength to strength and has a huge developer community. Kendra Hub leverages technologies built and maintained by individuals and organisations within the Drupal community. The White House website is built using Drupal. The next version of this framework, Drupal 8, to be released this year, is an awesome production for an open source project.
- Kendra Hub will be available as a free Apple Mac application from the Apple App Store ensuring easy installation and updates.
- Installation profiles will be available for remotely hosted and local instances of Kendra Hub.
- Kendra Hub will enable users to store their data where they choose, be this locally or backed up to the cloud. Kendra Hub will connect to cloud services that support open APIs such as iCloud, Amazon S3, WebDAV, Dropbox, ownCloud and many others. You can decide where your data is stored.
- One installation of Kendra Hub will work for many users just as it will work for one user, be this on a shared laptop in the Gambian desert or hosted on the Internet on a server in New York.
- Kendra Hub will be fully multilingual. We will start with the main European languages, Chinese and Japanese.
- Kendra Hub is totally free open source software (FOSS). This means you can take the code at no cost and make changes at no cost. You can also contribute your code back to the main project.
- Kendra Hub users decide exactly who has permission to view, edit, suggest, comment, query, (you name it) on any part of the data that they own, using Smart Filter technology.
- Kendra Hub is built extensively, from the ground up, using Smart Filter technology. A Smart Filter can be either a search query, an access permission or a set of attributes. A Smart Filter can be infinitely complex. They are portable between different systems and are sharable between applications and users.
- Service providers can host Kendra Hub for their clients. Commerce hooks will be built in to enable hosting service providers to charge for services. (Saas = Software as a Service).
- Kendra Hub will be platform and operating system agnostic.
- Freedom to move your data where you want it. Freedom to choose which service providers you use.
Kendra Hub Data Topology
- Each Kendra Hub user will be able to create their metadata "world view". This dataset will be administered by the user.
- Every assertion (as in "I played bass on this song") that a user makes can contain permissions stating exactly who can view the assertion. The permission can be as simple or complex as needed using a Smart Filter.
- Trust is built up between users when assertions created by one user are verified by another user – as in "I agree with this assertion".
- Evidence can be attached to assertions and verified by other users – as in "I agree with this assertion".
- Each user can have any number of devices hosting their assertions. This can serve as a useful backup mechanism. When a user updates, adds or deletes an assertion on any of their devices then the changes are propagated to all their other devices. The policy here is set to last change wins. Of course, if there is a conflict then the user is alerted that something has gone wrong.
- All data in the system will be versioned so that the revision history of a song/track or artist entity will be viewable with permission.
- Users can elect to follow other users entirely or can accept new metadata (or updates) on a case by case basis.
- The Kendra Hub network is purely distributed. However, because all data (subject to permissions) can be synchronised/cached/mirrored, fast indexes can be created to optimise searches and function as signposts to authoritative resources.
Arbitration (Conflict Resolution)
- Kendra Hub should be able to assist with disputes for ownership of any item in the metadata cloud.
- People should be able to make claims for an item.
- If people are making excessive claims then that should be tracked and noted.
- Once an item has been claimed then it it should be marked as disputed. Then the parties should agree on ownership.
- Collaborative features will be either federated or distributed? What's the difference?
- Federated management of entities.
- When creating a relation between entities create a local entity (remote reference) that contains the link to the remote object. Cache data locally, allow to be augmented with additional data. Using Federated web technologies the remote reference subscribes to push updates from the remote object.
- Distributed management of entities.
- Perhaps using Git model to fork, pull requests and merge in changes? This would need some way to diff semantic objects.
Creating entities from external data
- Users should be able to create entities using external data. Importing an entity by entering a web address for a MusicBrainz song or SoundCloud artist. A link to that source data will be set up enabling later synchronisation.
- There are two aspects to this: Is the remote resource from a 3rd party, or is it a Kendra Hub or system supporting same data formats. If the remote resource is on a Kendra Hub system it can register for PuSH notifications.
Permission change evaluation
- We need to be able to evaluate the repercussions of a change to permissions for a given entity much in the same way as "display all x results" works in a search query.
Importing XML from DAWs
- Being able to import songs from DAWs (like Logic Pro and Pro Tools) is very important to getting industry adoption.
Ownership, money and control
- Tick box to say if someone can control the composition or the master. Consent needed for sync rights or used elsewhere. Either on or off. Unilateral decision.
Genre definitions by emerging meaning (out of scope?)
- Tag tracks by emotions: inspirational, uplifting
- Cluster technical features of songs (like BPM) by matching with emotion responses using machine learning.
- Between each internal module and external application/database we will need to map/transform the data (vocabulary/schema).
Buggy or inaccurate documentation? Need support? Need help programming? Please file an issue.
There are no related issues for this document.