You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At times when creating our JSON-LD for a repository object we have entity reference fields where we don't want the targeted taxonomy term, we want the value stored in a term's field. Examples include rights statements URIs (see @elizoller 's comment), genre terms, or subjects where we would rather our RDF refer to the external URI rather than our internal one.
which would then have a 'sameAs' (or close match, whatever the predicate is...) jump over to the actual rights statement URI, we could have the simpler:
I'm working on a PR that adds a Data Converter class that allows us to use the rdf mapping config to specify what field in the target should be used for the transformation as well as refactors the EntityReferenceItemNormalizer to allow for this case. I just need to clean it up a bit and hopefully add a test or two before I submit it.
The text was updated successfully, but these errors were encountered:
At times when creating our JSON-LD for a repository object we have entity reference fields where we don't want the targeted taxonomy term, we want the value stored in a term's field. Examples include rights statements URIs (see @elizoller 's comment), genre terms, or subjects where we would rather our RDF refer to the external URI rather than our internal one.
Instead of
which would then have a 'sameAs' (or close match, whatever the predicate is...) jump over to the actual rights statement URI, we could have the simpler:
I'm working on a PR that adds a Data Converter class that allows us to use the rdf mapping config to specify what field in the target should be used for the transformation as well as refactors the EntityReferenceItemNormalizer to allow for this case. I just need to clean it up a bit and hopefully add a test or two before I submit it.
The text was updated successfully, but these errors were encountered: