Parts architecture

Project
Part content type

Common content bundle for all parts.

This is similar to how Commerce has products and variations.

Part variation ECK

Part types w/ specific fields.

Part field references content type.

Most variations have a part number.

Part type taxonomy

Hierarchical organization of part types.

Many vocabularies for different variation fields.

TODO: Associate part type with part variation eck.

Questions

Should a part have a default variation? For when a user adds an inventory item.

Part variation types seem out of sync with part type taxonomy, is this ok?

How do I add the node and eck to a search index?

Should part type have defined levels (like animal kingdom)?

IE: Part type category (drivetrain/cockpit/etc), Part type (shifter/derailleur), Part subtype (shifter type, brake type).