I am starting work on a D7 based web application that requires a number of entities, including some generic ones like Person, Place, and Organization. I would like to create a Drupal Contrib module that provides definitions for commonly used Entities, so they may be re-used and perfected by many D7 sites.

The idea would be to provide re-usable entities with fields that are often needed (e.g. a Person entity would have default fields of name, age, address fields etc). Developers would need the ability to remove a default field or add a new custom field, which should be accomplished not using a UI but rather by coding. If the developer alters the field configuration, would a new entity type or bundle be created, or would the entity have a single bundle with fields modified at module installation time? Each entity would have its own sub-module within the main module, which would allow a given site to only enable the default entities it needs.

Can you describe how this might be accomplished? Essentially the entities used by one module would be provided by another module - with the ability to change the field configuration from the default. Does this make sense or sound workable?

Comments

bojanz’s picture

Issue summary: View changes
Status: Active » Closed (outdated)