Handling updates to different assets

[dbirman]

User story

As a user I might modify the state of a QCMetric in a different asset than the one that I loaded in the portal. Should the portal push that update back to the original asset?

I think we do have to sync at upload time, otherwise if we rely on the indexer to sync assets we run the risk of having someone update two different assets and then we need to do merges (in practice the merge is trivial since everything is timestamped, but form a user's perspective it might not be obvious what happened).

[tbd]

[saskiad]

Can we make some specific examples?

e.g. evaluate raw asset and apply evaluation to specific or all of its derived assets. This one is obvious to me. The opposite is not.
Would this always be related assets - e.g. same subject, raw/derived - or are there other examples you have in mind

[dbirman]

Can we make some specific examples?

e.g. evaluate raw asset and apply evaluation to specific or all of its derived assets. This one is obvious to me. The opposite is not. Would this always be related assets - e.g. same subject, raw/derived - or are there other examples you have in mind

Let's say we have three assets: raw, derived_0, and derived_1, each of which has one QCEvaluation attached to it, qc_raw, qc_derived_0, and qc_derived_1. If we create these assets in order we end up with:

• raw: quality_control.json includes qc_raw
• derived_0: quality_control.json includes qc_raw and qc_derived_0
• derived_1: quality_control.json includes qc_raw, qc_derived_0, and qc_derived_1

The issue like you said goes in two directions. If I open the raw asset in the QC portal and make a change, this should get propagated down to the derived_0 and derived_1 assets. But the same is true in the other direction, if I open the derived_0 asset and modify the qc_raw evaluation then I need that to propagate back up to the raw asset and to the derived_1 downstream asset.

It's only ever in the same asset chain.