When loading data via the JSON-LD loader, the related resources section in the report may not be populated correctly

[apeters]

The related resources section at the bottom of a report may show all, some, or no related resources when there should be. This is because of the load order of resources. If a resource (AA) is loaded before another resource (BB) that references it, then the related resource (AA) shows up in the related resource section of the report for resource (BB). If AA was loaded after BB, then AA won't show up in the related resource section of resource BB.

This is due to the "resourceinstanceto_graphid" column in the "resource_x_resource" table not being populated when using the JSON-LD loader.

This could be fixed by running this bit of sql after the load:

UPDATE resource_x_resource x
SET resourceinstanceto_graphid = r.graphid
FROM resource_instances r
WHERE r.resourceinstanceid = x.resourceinstanceidto
AND x.resourceinstanceto_graphid is null;