Open dvstans opened 4 years ago
For now, have just prevented ownership change with published data.
If we go with the idea that DataFed is not for publishing data and that can be done with a data catalog won't we avoid having to solve these issues. If we narrow the feature scope of DataFed to private projects etc some of these issues can be removed.
For a production quality service, I would prefer to limit the scope as much as possible and further explore this issue possibly in a development version.
Yes, if we remove the catalog feature, this issue is irrelevant.
Currently, ownership change only applies to data and not collections. This will prevent proper changing ownership of data inside published collections since the destination collection will be different. For the time being, deny changing ownership of published data - but must account for the destination collection being published (update moved records pub/cat tags). Eventually, allow for moving of collections (retain contained collections) and permit this on published data.