hooked-in charters using local cei:date can lead to errors in ordering

[NTsch]

There are quite a few cases of charters with a "hooked-in" version of the same charter that has a different/wrong date, for example:

main entry: IlluminierteUrkunden/1365-01-99_Paris.cei.xml <cei:dateRange from="13660199" to="13660199">1366-01-99 (nv. st.)</cei:dateRange>

hooked-in entry: IlluminierteUrkundenFrankreich/1365-01-99_Paris.cei.xml <cei:dateRange from="13650199" to="13650199">1365-01-99</cei:dateRange>

As a result, the two entries also appear in different spots in the sorted collection. A possible workaround would be to overwrite hooked-in entry dates with the main entry dates.

[GVogeler]

I see two options:

1. sort by mixing hooked-in charters with original charters
2. update cei:issued in hooked-in charters when the referenced charter is published.

First option is probably too expensive as is has to be decided on each single entry in the list, from which source the date has to be fetched. Second option would include an additional service to be triggered in the publication process. This has to be done in publication of a private collection and in publication of a single charter by the moderator.