(Note: from the presented notes, it appears that 'epistolary events' should refer to 'episodes', i.e. the collections of '(atomic) actions'.)
The present box on the Role was not very useful because a single Epistolary Event could be broken up into several actions, and a person may well have been around for some but not all actions. With the new distinction between Epistolary Events + Letter Actions, this worry should be taken away.
Add trigger field to indicate what triggered an epistolary event/episode: 'death of a bishop' etc. This should probably be a new model 'WorldEvent' or something like that.
Add field related letters
Add field keywords (Not sure whether this is a good idea, as a list of strings will be difficult to compare across events. Maybe we should use episodes for this)
- Add field relevant Latin terminology (Taken up in #21)
- Add field location/space (Taken up in #24)
- Add instigator field: useful for when a letter is sent, but not necessary written. (Taken up in #23 )
(Note: from the presented notes, it appears that 'epistolary events' should refer to 'episodes', i.e. the collections of '(atomic) actions'.)
presentbox on the Role was not very useful because a single Epistolary Event could be broken up into several actions, and a person may well have been around for some but not all actions. With the new distinction between Epistolary Events + Letter Actions, this worry should be taken away.triggerfield to indicate what triggered an epistolary event/episode: 'death of a bishop' etc. This should probably be a new model 'WorldEvent' or something like that.related letterskeywords(Not sure whether this is a good idea, as a list of strings will be difficult to compare across events. Maybe we should use episodes for this)- Add field(Taken up in #21)relevant Latin terminology- Add field(Taken up in #24)location/space- Add(Taken up in #23 )instigatorfield: useful for when a letter is sent, but not necessary written.