Right now the owner of a content object can directly call kill on the contract. This corrupts the elv-master data model because we need the ContentObjectDeleted event to be thrown from the owning library in order to keep indexes in sync.
However, we can't immediately just disallow any account besides the library to call kill because - for other reasons - we took onlyOwner off of the delete content function in the library.
Long story short, we need to figure out the correct way to auth this.
Right now the owner of a content object can directly call
kill
on the contract. This corrupts theelv-master
data model because we need theContentObjectDeleted
event to be thrown from the owning library in order to keep indexes in sync.However, we can't immediately just disallow any account besides the library to call
kill
because - for other reasons - we tookonlyOwner
off of the delete content function in the library.Long story short, we need to figure out the correct way to auth this.