When reviewing the database schema graphs (https://musicbrainz.org/doc/MusicBrainz_Database/Schema) we noticed the following are missing:

 

Part of downloadable dumps (higher priority):

Artist credit schema

A small diagram showing how artist_credit, artist_credit_name and artist work together, plus mentioning artist_credit_gid_redirect.

 

Edits schema

An example of how the edit tables go together. edit, edit_data, edit_note, edit_note_change, edit_artist (for example), vote?

 

Tag schema

An example of how the tag tables go together. work (shortened), work_tag, tag. genre (and genre_alias) should probably be included, but there's no FK (match is on name and ad-hoc) - it would need either a hand-added connection, or just specify the connection in writing in the docs.

 

Not part of downloadable dumps (lower priority):

Collection schema

An example of how collections work (probably just with one entity type since they're the same for all). editor_collection, editor_collection_gid_redirect, editor_collection_type, editor_collection_collaborator, editor_collection_release (for example).

 

Subscriptions schema

A small diagram showing either an example of subscriptions, maybe editor (simplified), editor_subscribe_artist, artist (simplified), or all subscription possibilities (not that many anyway).

 

FAQ-style diagrams (lower priority):

"How do I get a composer for a track"?

track, recording, l_recording_work, work, l_artist_work

 

"How do I get a genre for an artist"?

If we don't add genre to the tag schema above, then we could have artist, artist_tag, tag, genre, genre_alias here.

 

"How do I get concerts for an area"?

area, area_containment ( maybe? ), place, l_area_event, l_place_event, event.