29: Datenbankschema
Titel
Datenbankschema
Beschreibung
Ich als Administrator*in möchte, dass ein gut strukturiertes Datenbankschema zum Speichern der Informationen für die App verwendet wird, damit Redundanzen vermieden werden und eine einfache Erweiterung möglichst ist.
Akzeptanzkriterium
Es existieren folgende Tabellen mit den genannten Attributen
AppInformation (key (enum: group, art_at_university, imprint), text, editor, created_by, created_at, updated_by, updated_at)
Artist (id, name, year_born, year_death, info_text, editor, created_by, created_at, updated_by, updated_at)
Artwork (id, number, name, published, year_painted, type, canvas, artist_id, owner_id, acquired, info_text, cover_image_id, audio_guide_id, video_link, latitude, longitude, location, address, editor, created_by, created_at, updated_by, updated_at)
ArtworkMedia (id, artwork_id, media_id, index)
Exhibition (id, title, start_date, end_date, published, cover_image_id, editor, created_by, created_at, updated_by, updated_at)
ExhibitionArtwork(id, artwork_id, exhibition_id, index)
Media (uuid, description, category (enum: image, audio-guide), file_name, type (MIME), editor, created_by, created_at, updated_by, updated_at)
Owner (id, name, editor, created_by, created_at, updated_by, updated_at)
Edited by Lukas Arnold