Welcome to FedMS, the Federated Delegate and Event Management System¶
Building blocks¶
Everything is built around content entities. The following types are relevant:
Other entity types like users, nodes, media, taxonomy terms, webform submissions, and more are also in use, but not really relevant for the FedMS application.
With these components, events like conferences or training courses can be fully managed. This covers the promotional content, the participant information and communication, as well as the workflow on what needs to be done by whom at what time, so that the whole event can be successful.
Group types¶
Organisation¶
Each company or otherwise combined number of people is a group of type organisation.
There is the owner of the Drupal instance, which is the main organisation (always group with ID 1).
All other organisations will exist as clients or service providers, each of which can but doesn't have to have their own Drupal instance.
Each organisation has a number of users as their members, in most cases those are employees of the company.
Event¶
Each event is a group of its own. An event is always contained within the organisation which owns (=sponsors) the event.
Each event has an Event details entity attached to it. As those events detail types can be created and maintained by the site owner, they can buuild their data model for different event types themselves. The event group is static, but the attached event detail entity is customizable.
Each event has a number of users as their members. Those are hosts, service providers, speakers, tutors, attendees, and what not.
Session¶
Each session is a group of its own. A session is always contained within the event it belongs to.
Like with event details, each session has a Session details entity attached to it. Those session detail types are also customizable.
Each session has a number of users as their members. Those are hosts, service providers, speakers, tutors, attendees, and what not. Every session member is also an event member, but not the other way round.
Event detail types¶
Event detail entities can have any number of different types. Each event has exactly one event detail entity attached to it.
The types and their fields can be defined and maintained by the site owner / customer.
Session detail types¶
Session detail entities can have any number of different types. Each session has exactly one session detail entity attached to it.
The types and their fields can be defined and maintained by the site owner / customer.
Attachment types¶
Attachment entities can be cusomizable content types that store any combination of data, e.g. if sessions require slides from the speaker upfront or a video recording afterwards, those documents, files, or other data formats can be defined as attachment types and their entities then attached to events or sessions.
The types and their fields can be defined and maintained by the site owner / customer.
Tasks¶
A single task has the following data:
- group, either an event or a session
- assignee, the user who needs to fulfil that task, has to be member of the group
- milestone, a taxonomy term under which the tasks get grouped for the event or session
- dates for when the task will show up as being actionable and by when it has to be completed
- entity, which is one of attachment, node, webform, or webform submission
Tasks get created automatically following a customizable set of rules, which are defined by the site owner as task patterns.