Since destructure_urn runs over each textpart being ingested, but works through each part of the URN hierarchy when it does so, we may end up with a small performance penalty calling the get_<kind>_metadata methods each time.
We should likely move those metadata functions out to a separate layer.
Since
destructure_urnruns over each textpart being ingested, but works through each part of the URN hierarchy when it does so, we may end up with a small performance penalty calling theget_<kind>_metadatamethods each time.We should likely move those metadata functions out to a separate layer.