More identifiers is more better, and currently the only way to link OL items to MBIDs is to use hyperlinks rather than specifying IDs together with other IDs. While obviously not everything in MusicBrainz will (or should be) represented in Open Library, there is a significant amount of audiobooks that are catalogued in both places. There are also several OL Authors who also happen to do music or other work that warrants a MusicBrainz entry for them, as well as musicians who also happen to be authors.
Done; as with #8898, note the work IDs won't have any effect yet since we don't have a UI for associating work IDs, but I added them to the work.yml and they will take effect whenever we do!
Describe the problem that you'd like solved
More identifiers is more better, and currently the only way to link OL items to MBIDs is to use hyperlinks rather than specifying IDs together with other IDs. While obviously not everything in MusicBrainz will (or should be) represented in Open Library, there is a significant amount of audiobooks that are catalogued in both places. There are also several OL Authors who also happen to do music or other work that warrants a MusicBrainz entry for them, as well as musicians who also happen to be authors.
Proposal & Constraints
Allow MusicBrainz identifiers/IDs (MBIDs) for
Additional context
Proposed YAML to be included:
author.yml
:work.yml
:edition.yml
:Stakeholders