Add Event type to standard distro

[jri]

The DM Standard Distribution should come with an Event type as the basis for calendaring applications.

Besides From and To date/time an Event should have a Name, a Description, a Location, Organizers (many), and Participants (many). As Location everything that has an Address should be applicable. Organizers/Participants? should be Persons or Institutions.

This could be realized in a separate dm4-events module.

[Jörg Richter <jri@…>]

In 9959ffed3dc14efe69dd50710231fc1e9061d18e/deepamehta:

Add dm4-events module (#902).

See #902.

[Jörg Richter <jri@…>]

In 4aad20644f1aa1d6aa9ad9c3b6772e07bd6c4b5e/deepamehta:

Event model: add Address, Notes, and URL (#902).

See #902.

[Jörg Richter <jri@…>]

In 7cd661c0e2ca8a53e4a22c933a308dcabb70cfe8/deepamehta:

Event model: add Address, Notes, and URL (#902).

See #902.

[jri]

In 7cd661c0e2ca8a53e4a22c933a308dcabb70cfe8:

"Event" model: add Participant (#902).

A "Participant" association represent that a Person/Institution? is participating (that is contributing) to an event.

"Participant" is not explicitley defined as a Event child. Participant associations are created manually be the user.

See #902.

[Jörg Richter <jri@…>]

In 03825bbceb9f322cb4579d56b2235d5881c1af71/deepamehta:

Add dm4-events and dm4-datetime to distro.

See #901.
See #902.

[Jörg Richter <jri@…>]

In 9a625fb4671ad7ebd57feb52e0c40921880ab62a/deepamehta:

Make Event icon little larger.

See #902.

[Jörg Richter <jri@…>]

In 3f632d6e764a3eff58772f0e73624ce980e33df8/deepamehta:

Add Events (REST) service: getParticipants (#902).

Retrieve all participants (= Persons) of an event:s

GET /event/{id}/participants

See #902.

[Jörg Richter <jri@…>]

In bc21164f271703bce5b9c95fc05df397c6a41d67/deepamehta:

Events service: getEventsByParticipant() (#902).

Retrieve all events a person participates in:

GET /event/participant/{id}

See #902.

[Jörg Richter <jri@…>]

In 64437c368b0c651541861609ea277907390d6b32/deepamehta:

Events module: rename service API methods (#902).

getEventsByParticipant() -> getEventsOfParticipant()
getParticipants() -> getParticipantsOfEvent()

The REST API is unchanged.

See #902.

[JuergeN]

I have just playes a little with events. Here are my observations:

• Even though I had argued to name the months by numbers, I must say that identifying them by name would make it a lot easier and safer to read. Especially because of the different German and anglo-american date formats. I would suggest to use abbreviations (Jan., Feb., Mar., etc.)

• I would enhance the aggregation definition between Event and Address with a custom assoc definition called 'Location' (or likewise). One of the reasons for this is also to solve the missing input field labels in the detail panel. IMO it is really not a good UI design that we offer input fields without any descriptor (eg. 'From' and 'To' date field). In my understanding this descriptor should come from the custom assoc. definitions. I would be very happy, if we could give this a try.

• Changing the input fields for date and time into a one-liner would be a nice improvement.

[jri]

Thanks for feedback!
These are good points.
I'll will find a solution :-)

[Jörg Richter <jri@…>]

In c566338e82c4640765255db11bf835f79ca035b9/deepamehta:

Events module: rename service API methods (#902).

See #902.

[Jörg Richter <jri@…>]

In 0abd17ec44b977acbf5a6c83d9c5b4b90ad48f73/deepamehta:

Share Address topics for Events (#902).

To assign an existing Address topic (e.g. of an Institution) to an Event:

1. reveal the Address topic
2. associate the Address topic with the Event topic. DM sets the association's type and role types automatically then.

If an Address has been assigned to the Event already that association is deleted automatically. (The Address topic is not.)

Thus you can now share Address topics between e.g. Institutions and Events. You must not re-enter an Event address again if the Event takes place at an Institution for which an Address has been entered already.

However, its not yet perfect:

• The association that is deleted automatically disappears from the canvas only after reloading.
• The newly assigned Address appears in the Event's details only after reloading.

See #902.

[Jörg Richter <jri@…>]

In 8a047184792479c5a813e58803b6dbb7c4ba85ab/deepamehta:

Show associated Address in Event details (#915).

When an Address topic is associated with an Event topic the new address appears in the Event's details immediately. No reload is necessary.

See #902.

[Jörg Richter <jri@…>]

In 195ba5ccdfd5f02e906c0742fefceec63923b97b/deepamehta:

More associations are auto-typed (#931,#916,#902).

When an association is created manually it is automatically retyped in further contexts:

Person - Institution -> Organization Association

Person - Event -> Participant

See #931
See #916
See #902

[jri]

For the user the "From" and "To" datetime fields are not distinguishable. They should have labels.

[Jörg Richter <jri@…>]

In f2b77e4d3f6c8104f1fdf4f331350922c97489ee/deepamehta:

Events: add "From" and "To" labels (#902).

In the detail panel the "From" and "To" DateTime? fields are labeled accordingly.

See #902.