batch import will lost link with parent met if choose to generate the UUID

[aperi2007]

Hi,

using the r7850 version

I notice that try-ing a batch-import and setting "Generate UUID for inserted metadata"

it lost the link between parent and child metadata.

infact it generate a new UUID also for <parentIdentifier> but doing this it lost the link with the parent metadata that will have another UUID (also it generated new)

I'm sure this feature will work correctly some trunk version ago...

[aperi2007]

Hi,

I tested again with r8040, I can confirm the problem.

The option "Generate UUID for inserted metadata" break the link between parent and child metadata.

[aperi2007]

Hi,

I'm try-ing to understand how to resolve the ticket #533. but I don't know so well the geonetwork code. I'm try to find what java file is the involved file in the batch import and generate a new UUID for every metadata imported, so I can't try to develope a patch.

I guess a solution could be to change the function use to generate the UUID, instead to use the "UUID.RandomUUID()" function that generate a completely randomic UUID. I think should be better to use the "UUID.fromString(stringa-name)" function that generate an UUID using a string .

Using as string-name the actually FileIdentifier to be overlapped, this should be grant the maintaining of the link between parent and child with the new UUID generated.