If I add an item for Vivaldi Four Seasons guitar transcription and the database currently contains metadata for a symphony edition, then I will not be able to have useful information for my item. I would need to create a new metadata row with a title like "Four Seasons (guitar)". Over a certain period of time, the database would accumulate a lot of sheets with title variations.
To avoid this, I can use a schema that uses a one-to-one relationship between Item and Sheetmusic. That way, when a user wants to add a sheet music, they will probably end up typing the entire information out anyways.
I could also then use a "trade like this item" sort of link that prepopulates the data for the user.
If I add an item for Vivaldi Four Seasons guitar transcription and the database currently contains metadata for a symphony edition, then I will not be able to have useful information for my item. I would need to create a new metadata row with a title like "Four Seasons (guitar)". Over a certain period of time, the database would accumulate a lot of sheets with title variations.
To avoid this, I can use a schema that uses a one-to-one relationship between Item and Sheetmusic. That way, when a user wants to add a sheet music, they will probably end up typing the entire information out anyways.
I could also then use a "trade like this item" sort of link that prepopulates the data for the user.