Data sets define where a Party's data is stored. A data set specifies a particular entity type which may be connected to a party. This may be an entity type provided by another module, or one defined along with the data set.

For example, a Party installation for a library might have Data Sets created for the Profile2, User, and LibraryCard entity types.

Using hats you can define data set rules that allow different parties access to different data sets.

For now, the Party module comes with 4 submodules that provide data sets:

• Party User - Uses Drupal's core user module to attach the party entity to a user and provide the defined profile fields when editing this party. When this module is enabled, you can configure it at admin/config/party/user to create a party when a user registers, and to show other data sets on the user registration/creation form.
• Party Profile - Uses the powerful Profile2 module to attach profile types to parties. These are great for quick bundling (creating multiple profile2 types) and providing other nice features that profile2 provides.
• Party Commerce - Attaches drupal commerce customer profile types to parties. This is incredibly useful for non-profits who want to track donors and members, and e-commerce operations who want a CRM for managing customers and sales!
• Party Node - Attaches content types to parties

Setting Up Data Sets

You can set up some simple data sets by installing the party_user and party_profile modules. You can add fields to the user entity, and add profile types right from the data set screen to get started. Once you have fields for all of your data sets ready, you are ready to use hats to set up data set rules.

To manage Data Sets, go to Admin > Community > Manage Data Sets. This shows a list of all the Data Sets that are defined. From here you can manage the fields and settings of existing Data Sets, or add data sets where the module that provides the entity type allows it.