I'm new to EE, and have a project with a lot of database relationships. For example, the company offers a "Service", in certain "Zip Codes".
So I see in EE, I can create channel fields, etc, and create the relationship between a Service and the (many) zip codes to which it applies.
In the admin area, the client would be able to CRUD Zip codes, Services, and map the two appropriately. However, some fields that are default in EE, like "URL", don't make any sense for a "Zip code" entry. It can be ignored, and still works, but not ideal for a non-technical client to use. Also things like Expiration dates, and the other tabbed fields don't make sense.
My question is twofold:
Is this appropriate way to use EE, or it is better (though more tedious) to build a custom module to manage "non-content" based entities?
Is there a way to customize the "Channel" screen to hide the unnecessary fields and focus the user a bit on what they need to enter?
I'm just trying to get a sense of how to approach this task and how EE was meant to be used.