Problem: publisher published two identical data sets

[trentmc]

One of our data launch partners asked:

I accidentally published two identical data sets:

https://market.oceanprotocol.com/asset/did:op:Ac3a39F843316c83Db11a9E6D703a7473c26aCe0
and
https://market.oceanprotocol.com/asset/did:op:fd28195e3d30d5a63a87A2502030CE648FFa4884

How do I go about removing the second one from the marketplace?

[mihaisc]

The solution would be to add an isRetired flag. The publisher can 'retire' the asset (basically just an update to the ddo with the isRetired=true ). In all our queries we would need to add this flag to ignore the ddos with it.
In the first implementation we allow the publisher to retire only when there is no pricing created on the asset, if there is a pool created then it becomes more complex

[mihaisc]

already discussed more extensively here #445, and will also be part of v4