Kendraio App MusicBrainz integration (bounty)

[dahacouk]

Our second bounty is to integrate the open-source music encyclopedia MusicBrainz into Kendraio App. Kendraio App is our low-code bi-directional dashboard 'data browser' application. Within Kendraio App we've built Kendraio Player, a proof-of-concept for a multi-service music streaming player using web monetisation technology, funded by Grant for the Web towards their mission to create a healthier internet.

We want this integration to enable Kendraio App users to search and browse, and also upload information to MusicBrainz. To participate, we would like talented full-stack JavaScript developers to propose how they would integrate MusicBrainz with Kendraio App. For a ready-made example see https://app.kendra.io/musicbrainz/musicbrainzSearchArtists, and you can see how easy it is to create flows that connect to APIs.

• Timeframe: 2 weeks
• Bounty: $500 USD (paid out via https://opencollective.com/kendraio -- so you need to have an account here to be paid)

We're rewarding the individual (or group) that carries out this bounty in a transparent, interoperable, and easy to use way.

See how our first bounty went at Kendraio Player Audiotarky integration. And see Radhy's writeup of his experience at Afterthought on integrating Audiotarky API into Kendraio App.

Deliverables

• A proposal written out before work starts and agreed upon beforehand in our Google Drive.
• Interfaces created in Kendraio App using Flows where a user can:
  • Look up information about a particular MusicBrainz entity ("give me info about The Beatles")
  • Browse MusicBrainz to find entities connected to a particular entity ("show me all releases by The Beatles")
  • Search for entities matching a specific query ("show me all artists matching the query 'Beatles'").
• Interfaces created in Kendraio App using Flows where a user (artist) can:
  • Upload information about a specific music release to MusicBrainz via Kendraio App.

Technical details and source code

• Kendraio App: https://github.com/kendraio/kendraio-app
• MusicBrainz development resources: https://musicbrainz.org/doc/Development
• MusicBrainz API: https://musicbrainz.org/doc/MusicBrainz_API
• MusicBrainz GitHub: https://github.com/Borewit/musicbrainz-api

Evaluation

• The bounty will be evaluated by the Kendraio Team and advisors.
• Evaluation will be based on the completion of the task, as well as on how transparent, interoperable and easy to use it is.
• The more you can commit to documenting and talking about your experience with Kendraio App the more excited we will be to work with you.

Requirements

Candidates should have some existing experience with JavaScript and web APIs. Must be willing to document and talk about their experience of working on the tasks in this bounty.

Process

Once a candidate has put themselves forward, our Kendraio developers will mentor them exclusively for 2 weeks (or more, by mutual agreement). If after the agreed-upon period tasks remain open, another candidate may be given the opportunity instead.

About Kendraio

Kendraio App is a general framework for creating low-code applications. Kendraio App was originally created to service the creative/music industry to enable easy asset and rights management both locally and on third-party platforms. But what we've ended up creating is a generic data browser that plugs into remote APIs and enables highly configurable low-code interfaces to be built. And we'll use this framework as the basis of this project. Please check out these links before accepting this mission: Kendraio App demo, Kendraio App on GitHub, Kendraio App documentation, Kendraio App website. As you create this project your feedback will influence the direction and capabilities of the Kendraio framework.

The Kendraio App lets users build interfaces from blocks. The blocks themselves are plumbed together with modern JavaScript, TypeScript, and are configured using JSON. We have various backend APIs, and proxy endpoints hosted using Vercel's serverless platform.

[ghost]

Hey, I'm interested in this, I have experience with developing JavaScript apps and some small experience using the MusicBrainz API in my own personal projects (displaying data from MusicBrainzs and ListenBrainz on a web page using JavaScript). I'm confident that I can get this made to your standards within 2 weeks, and I can definitely document it and talk about it (though I have no social media, so I can't really post anything related to it if that is what you are looking for. I see on your last bounty the developer wrote an article about his experience, I can do so as well.)

[dahacouk]

Hi Lila, thanks for dropping by! Could you give us an idea of how you would like working with Kendraio? Have a read through some of the articles at https://medium.com/kendraio. Please browse the videos in https://www.youtube.com/c/kendraio/videos and you'll get a sense of the aspirations, capabilities and history of Kendraio. And please review our recently published website at https://www.kendra.io that will give you an idea of the scope of the project and tooling.

Also, can you give us an idea of how you'll approach this? I'm especially interested in publishing new releases to MusicBrainz from Kendraio App. You can start a new Google Doc in your own drive where you can document all this and I'll get you to move it into our public folder once we've reviewed it – so just post a link here once you've got somewhere.

In terms of the timeline we can be quite flexible so don't worry about having to complete in exactly 2 weeks. If it's going well we'll be more pleased just to get stuff working.

[ghost]

Sorry, unfortunately, something came up so I can't work on this anymore. Thanks for the opportunity anyways and I hope you can find somebody else soon!

[dahacouk]

Some discussion about this MusicBrainz integration bounty has started in the MusicBrainz forum after the founder of MusicBrainz, @mayhem, posted a blog post about this.

The discussion seems to suggest that we could use the Release Editor Seeding in the first instance, as there may not be any APIs to directly add new data into MusicBrainz, perhaps partly because of the complexity of the validation? This would initially simplify the scope at least. @davidsonl are you still interested in running with this bounty with a slightly new scope?