Testing Set Uniqueness
• If this test fails, it means that the repository returned a proper OAI ListSets response containing set information, but one or more of the setSpec identifiers are duplicated. The Gateway cannot work properly with duplicate setSpec identifiers because those are used to differentiate the collections in the repository. The user will not be allowed to add the repository with duplicate setSpec identifiers.
I ended up to solve this by deleting content of tombstones tables straight in SQL, as pointed in this thread. But I wish there were a way to do that without putting hands on database.
EDIT: problem is still unsolved… I had to revert steps above because, without tombstones data, I cannot delete records from WorldCat. But then setSpec identifiers are duplicated again… Is this a bug in OMP? Any ideas to fix this?
@asmecher Yes, I’m sure it’s somehow related to tombstones, or at least they are messing with the result.
I made a backup of my SQL, deleted all tombstones data and the duplicated set was gone. Once I reverted the deletion, the error returned. In fact, I even tried editing OAIDAO.inc.php and commented the portion related to tombstones (lines 101-113): this also temporarily solved the issue.
Check it out below: (I already reverted changes to core code)
Unfortunately, the only way I found (sort of) to workaround this was editing OAIDAO.inc.php, as I mentioned above. I’m still expecting PKP staff could help me with a more definitive fix.