Handle dependency evolution
Parsers and normalizers change. Depending on the change, respective data must be reprocessed. This should be done semi automatic.
-
maintain dependency versions as part of the backend container image -
store version information as part of the meta data -
allow normalizers to be repeated -
allow parsers to re-parse -
allow to rematch parsers -
after re-processing index, coe-repo, metadata have to be updated