Information Modeling with Drupal 7

In this session, we will refresh your knowledge of the core entities in Drupal 7 (user, node, comment, taxonomy term, taxonomy vocabulary, file), and provide examples of API calls to define and query core and custom entities. We will also touch on useful contributed modules to work with and extend entities, for example the Entity API, Entity Reference, Entity Translation, and RESTful Web Services modules.

With entities and fields in core, Drupal 7 has come a long way towards a full-blown modeling framework from its humble beginnings as a piece of hard-wired community software. Unfortunately, compared to information modeling languages like EXPRESS or current architectural patterns like ActiveRecord, Drupal has chosen its own vocabulary with content types, entities and bundles. This makes it hard even for seasoned information modelers when working on their model using the mechanisms Drupal 7 provides.

Speaker(s): 
Track: 
Coding and Development
Experience level: 
Intermediate

Comments

A lot of attention to the possibilities of using entities is needed because entities are possible in D7... but used only by a few I think..
There is more in Core than you know! But we should know and thus hear about it!

A lot of attention to the possibilities of using entities is needed because entities are possible in D7... but used only by a few I think..
There is more in Core than you know! But we should know and thus hear about it!

Sounds very interesting. I do not know EXPRESS or ActiveRecord, do I need to?

These are industry standard approaches to information modelling. While EXPRESS is an actual ISO standard, ActiveRecord is used as software pattern in many frameworks, most notably Ruby on Rails.
I will briefly mention their concepts, but will concentrate on the parlance used in Drupal.