Some famous composers are missing, how can one contribute to the database list ?

[Etx17]

I'm looking for Nadia or Lili Boulanger, and couldn't find it in composer/list/search/nadi.json

I got other composers on previous requests that i was looking for, but some are missing.
Is there a way to contribute to the list in order to get an exhaustive list ?

Willing to contribute
Etienne

[ishay-shaer]

I am also willing to contribute. Extensive as the database currently is, there's a lot of room for data to be added, some well-known composers, especially women composers, are missing entirely, and some data is out of date (e.g. Harrison Birtwistle died in 2022 but his 'death' property is still 'null').
I couldn't find a way to contribute data. Could anyone guide me?
Thanks,
Ishay

[adrianosbr]

Hi Ishay,

Thank you so much for your interest! For now, there's no API endpoint to insert or edit data. We're moving very, very slowly on that, but I think it will be ready by Q1 2025. Fingers crossed!

Thanks again,
Adriano

[pjpops]

Is there any update on being able to contribute? As others have mentioned, a lot of the data is now out of date, with some 'new' composers and their works missing. Would be great to keep this great project alive.

[adrianosbr]

Hi! The project’s a bit on hold right now. I’m planning to get back to it next year, once I have more control over my schedule. Thanks so much for your interest!

…

On Thu, Jun 26, 2025 at 12:46 PM pjpops ***@***.***> wrote: *pjpops* left a comment (openopus-org/openopus_api#10) <#10 (comment)> Is there any update on being able to contribute? As others have mentioned, a lot of the data is now out of date, with some 'new' composers and their words missing. Would be great to keep this great project alive. — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABVDHSHAQLXMQEZR74TGF5D3FQIUHAVCNFSM6AAAAABPJ7H5QKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAMBYHE2DKNRYHE> . You are receiving this because you commented.Message ID: ***@***.***>

[KingCharlesVI]

Hi! The project’s a bit on hold right now. I’m planning to get back to it
next year, once I have more control over my schedule. Thanks so much for
your interest!

On Thu, Jun 26, 2025 at 12:46 PM pjpops @.***> wrote:

pjpops left a comment (#10)
#10 (comment)

Is there any update on being able to contribute? As others have mentioned,
a lot of the data is now out of date, with some 'new' composers and their
words missing. Would be great to keep this great project alive.

—
Reply to this email directly, view it on GitHub
#10 (comment),
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABVDHSHAQLXMQEZR74TGF5D3FQIUHAVCNFSM6AAAAABPJ7H5QKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAMBYHE2DKNRYHE
.
You are receiving this because you commented.Message ID:
@.***>

I'd be happy to contribute to this issue but the codebase layout is confusing to me.

[adrianosbr]

Yeah, it’s pretty old — and not super clear, to be honest. On Thu, Jul 3, 2025 at 11:12 AM KingCharlesVI ***@***.***> wrote:

…

*KingCharlesVI* left a comment (openopus-org/openopus_api#10) <#10 (comment)> Hi! The project’s a bit on hold right now. I’m planning to get back to it next year, once I have more control over my schedule. Thanks so much for your interest! On Thu, Jun 26, 2025 at 12:46 PM pjpops *@*.***> wrote: *pjpops* left a comment (#10 <#10>) #10 (comment) <#10 (comment)> Is there any update on being able to contribute? As others have mentioned, a lot of the data is now out of date, with some 'new' composers and their words missing. Would be great to keep this great project alive. — Reply to this email directly, view it on GitHub #10 (comment) <#10 (comment)> , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABVDHSHAQLXMQEZR74TGF5D3FQIUHAVCNFSM6AAAAABPJ7H5QKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAMBYHE2DKNRYHE . You are receiving this because you commented.Message ID: *@*.***> I'd be happy to contribute to this issue but the codebase layout is confusing to me. — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABVDHSE5LELXVPYYBTRVTRD3GU24JAVCNFSM6AAAAABPJ7H5QKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAMZSGQZTENBSGY> . You are receiving this because you commented.Message ID: ***@***.***>

[juaamol]

Hello

I found this project while I was working on a personal project.

I got the dump.json but then changed some things to fit my needs. Basically I removed some fields i don't use and added a field "instrumentation" because i hardly found APIs that linked "work <-> instruments-used" on the web. Also fixed some birth/death dates.

Do you think I should send a pull request with the .json (or a github link to it)? Given that i kept the "complete_name", mixing original dump.json with the new field I have could be easy.

---

As a side note, perhaps keeping dump.json data in the repository (depending on how big it is, it could be splitted into a folder composers with [composer-name].json ) could make it easier to contribute through Pull Requests. But perhaps this is too naive due to my lack of experience in these regards so idk.