Feature #2634
Updated by Alexander Watzinger 3 months ago
Currently there are *7 different classes* for events which was the source After some consolidation and review of confusion all our current and inconsistent data entry. After some consideration previous cooperation databases, we decided to remove the classes *Event* (E5) and *Creation* (E64). The remaining Creation event. Creation event classes being *Activity* (E7), *Acquisition* (E8), *Modification* (E11), *Move* (E9), *Production* (E12) h3. Event *Event* (E5) classes will be transformed to *Activity* (E7). Initially we introduced *Event* (E5) to enter events without actors (e.g. a natural disaster). But beside the difference being more superficial it was also meant for authorship of Files (see #1934), e.g. a little awkward to use this class scan or a photograph, which is can still be done in the super class creator field of the other event classes uses, e.g. Events can't be chained with *continued* (P134) like the other ones. h3. Creation *Creation* (E64) classes will be transformed to *Production* (E12). After analyzing existing data we noticed that in File form. In most cases, the *Creation* Creation event was not used in the indented way, but used for the *Production* production of an artifact, e.g. the writing of a document (Source), which the *Production* Production event is for. Only drawback of the transformation We will be that *has created* (P94) will be removed. It was meant to track creators of a *Document* (E31) remove Creation form for now, but this can also be done while adding creators to a *Document* (called *File* in OpenAtlas, e.g. a scan or a photograph) directly in the UI. We might add *Creation* it again when implementing a more user-friendly version of authorship (#2570). Existing Creation events will be transformed to Production events (because this seemed to had been the intention in most existing cases anyway).