Provide dataset unlink functionality to same level of permission/role as dataset link ["Publish Dataset"/Curator]

[mdmADA]

What steps does it take to reproduce the issue?

1. Make sure you have "Publish Dataset"/Curator permissions on at least one Dataverse/Collection.
2. Login to Dataverse
3. Link a Dataset to a Dataverse from 1.
4. Go to that Dataverse - the dataset is included
5. You want to unlink the dataset you just had permission to link
6. Ask a superuser to unlink it using the https://guides.dataverse.org/en/6.2/admin/dataverses-datasets.html#unlink-a-dataset API call.

• When does this issue occur?
  When a dataset is linked to a Dataverse.

• Which page(s) does it occurs on?
  All Dataverse pages to which a dataset has been linked

• What happens?
  See above.

• To whom does it occur (all users, curators, superusers)?
  Curators/Publish Dataset Permission

• What did you expect to happen?
  If you had the permission to link it, you should have the permission to unlink it.

Also, what if I am a dataset owner and I don't want anyone else to link my dataset to their dataverse? There should be a way to say [Allow dataset to be linked to other dataverses?: no] - maybe there is and I can't see it in the documentation.

Which version of Dataverse are you using?
6.2

Any related open or closed issues to this bug report?
#4454 which was closed

[DS-INRAE]

Hi,
sadly it is not really a bug but something not done, as I understand it, as the links were considered experimental for a while.
If you really need the links removed without waiting for this, you can use this command : https://guides.dataverse.org/en/latest/admin/dataverses-datasets.html#unlink-a-dataset but even in this API command it is superadmin only.
It'd be great to have it in the UI as you point out though ! I think you should also create an issue for the new Single Page Application for this here so it doesn't get overlooked : https://github.com/IQSS/dataverse-frontend

[DS-INRAE]

Also a specific first issue for the API would be great too because the UI integration is more likely to lag behind and the API part (allowing Curators/Publish Dataset Permission to use the command) will be a prerequisite for both user interfaces anyway :)