Allow ORT to track the name of a package curation proviers

[sschuberth]

For any place where curation data is displayed (like internal reports), it would be valuable to know the name of the provider where a curation comes from (e.g. for debugging, quality evaluation of providers etc.)

To support this, the current idea is to wrap PackageCurationData in a new class called AppliedPackageCurationData that also contains a property for the porvider name. That new class would then be used in CuratedPackage instead of using PackageCurationData there.

[sschuberth]

BTW, usually it would have been rather straight-forward to just add the provider name to PackageCurationData, but unfortunately that class is yet another example for a model class that is used for both the API and the serialization. Which means we cannot easily add properties that do not appear in the serialized format.

[fviernau]

@sschuberth have you had a look at ResolvedConfiguration? IIUC the curation lists there are already associated with the provider they originate from.

[sschuberth]

@sschuberth have you had a look at ResolvedConfiguration?

Yes, that's what we are currently trying to use, but it turned out to be rather cumbersome. Thus the idea for an alternative API / data structure.

But let's see, maybe we should indeed solve this on the user-side instead of making changes to ORT core, here.

[mnonnenmacher]

@sschuberth have you had a look at ResolvedConfiguration? IIUC the curation lists there are already associated with the provider they originate from.

The problem is that this information is lost when calling OrtResult.getPackages() to get the curated packages, so a user would have to reimplement the logic from the OrtResult.packages property to get the curated packages with provider information. And the implementation would depend on details of how the OrtResult class stores that information where it would be better if it was possible to just call a function.