Here's the working example: This is a Database for tracking information about packages at a post office.
There's a table for the Customers (A customer can be a sender or a receiver)
There's a table for information about the packages, which point to a receiver and a sender.
However, the issue here is that there can be many packages for the same receiver/sender, with almost identical data.
For example, let's assume that at this post office, all the customers (senders) are mass producers of ONE good. Now to further exacerbate things, let's also assume that every receiver of goods from each individual shipper is unique. The issue here then, is that each sender is linked with only one receiver, and all the package info is identical. So in the package table you would have hundreds of package entries that are identical other than fields like date/time.
if there was a producer of wooden carved bears, the packaging info would be the same everytime, the only thing different would be the date/time and maybe a few other fields (like: Was the package Received/Sent properly?) .What is the best way to organize the database to reduce redundancy?