h1. Source workflow

#1064 In conception phase, draft by Stefan:

Due to the increasing complexity and additional features regarding written sources and their interconnections we need to reorganise the respective UI.
It should be easy to distinguish between:
 
*Core*

# *Content:* Source Content (summary of the content), Source Translation, Source Transliteration on one hand and further linked entities like the 
# *Information Carrier* (physical object like the letter, paper, papyrus etc.)
# *References* bibliographic references (e.g. Edition of the charter, further bibliography) and external references
# *Identification* %{color:green}All written sources are custodied in a library/archive/museum, are identified with a univocal identifier. I propose that these concepts Archive and identifier stay in relevant place (similar to Name/title). Maybe through E15. I understand that could be via artifact, but I would like more straight. If it must be done in artifact, also it lacks this concept. Alternatively, it will be useful some example in Manual%

*Entities referred to by the content*

# Actors mentioned in the content
# Places mentioned in the content
# Events mentioned in the content

*Entities involved in creation of the source*

# Creators/writers/involved actors of the information carrier
# Place of creation
# Date of creation %{color:green}Could be different of artifact creation date%

*Linking between event entities from the content*

# Activity including location where it took place and involved actors along with dates
# Acquisition including place/property that changed ownership along with new and old owner plus dates

*Further links*

# Move of information carrier/physical object in case of e.g. letter exchange along with date and start/end location

*One thing more*

# Feature #1970: %{color:green}Sub Documents for sources%