Associated resources for raster records look correct but for metashare records, it appears the "parent" record is being linked to itself as each of the associated resources, rather than the child record.
eg for the record VICMAP_TRANSPORT (7e00563bfd0ee4505f6c99fcfc3aaaa8647d008c) there are about 10 associated resources listed - this number looks about right, however they all have the parent record title and UUID - see the snippet of XML file below for one of these entries.
Vicmap Transport Scale: Various ( VICMAP_TRANSPORT )https://dev-metashare.delwp.vic.gov.au/geonetwork/srv/eng/catalog.search?uuid=7e00563bfd0ee4505f6c99fcfc3aaaa8647d008cWWW:LINK-1.0-http--relatedLink to Dataset that is part of this product
I have checked the source data (product_object.csv) and it has the correct associated ANZLIC ids - see below.
ANZVI0803002441|ANZVI0803002446
ANZVI0803002441|ANZVI0803002447
ANZVI0803002441|ANZVI0803002612
ANZVI0803002441|ANZVI0803002442
ANZVI0803002441|ANZVI0803002457
ANZVI0803002441|ANZVI0803003244
ANZVI0803002441|ANZVI0803003245
ANZVI0803002441|ANZVI0803002870
ANZVI0803002441|ANZVI0803002595
ANZVI0803002441|ANZVI0803002444
Associated resources for raster records look correct but for metashare records, it appears the "parent" record is being linked to itself as each of the associated resources, rather than the child record. eg for the record VICMAP_TRANSPORT (7e00563bfd0ee4505f6c99fcfc3aaaa8647d008c) there are about 10 associated resources listed - this number looks about right, however they all have the parent record title and UUID - see the snippet of XML file below for one of these entries.