BIBFRAME descriptions created through conversion from MARC records containing 7xx (related title) fields often contain "stub records" representing associated resources (works and instances). These stub descriptions are wrapped within the main BIBFRAME description. The information contained within these secondary works and instances is often very limited and may not consist of more than a format type and OCLC ID.
However, the validation validates ALL bf:Work and bf:Instance descriptions contained within a file. Since the associated resources (bf:associatedResource: https://id.loc.gov/ontologies/bibframe.html#p_associatedResource) do not necessarily contain all the required and recommended properties they often cause the BF descriptions to fail validation.
Possible solutions: "Smart" conversions that go out to the linked associated description to retrieve the needed properties
OR look into a NOT option in SHACL so we can ignore resources that are linked to via bf:associatedResource.
BIBFRAME descriptions created through conversion from MARC records containing 7xx (related title) fields often contain "stub records" representing associated resources (works and instances). These stub descriptions are wrapped within the main BIBFRAME description. The information contained within these secondary works and instances is often very limited and may not consist of more than a format type and OCLC ID.
However, the validation validates ALL bf:Work and bf:Instance descriptions contained within a file. Since the associated resources (bf:associatedResource: https://id.loc.gov/ontologies/bibframe.html#p_associatedResource) do not necessarily contain all the required and recommended properties they often cause the BF descriptions to fail validation.
Possible solutions: "Smart" conversions that go out to the linked associated description to retrieve the needed properties
OR look into a NOT option in SHACL so we can ignore resources that are linked to via bf:associatedResource.