Konzept #254

Define the cascades for creative objects

Added by Alexander Blum over 4 years ago. Updated about 2 years ago.

Status:ErledigtStart date:
Priority:NormalDue date:
Assignee:Alexander Blum% Done:

100%

Category:-Estimated time:0.50 h
Target version:Repertoire 1) Testing phase I

Description

The cascades of creative objects needs to be defined.

The context is the perspective of tryton administration users. Web users are never able to delete anything.


Related issues

Related to collecting_society - Konzept #270: Behaviour after user deleted an object? Erledigt
Related to collecting_society - Datenbank #298: Cascades? Erledigt

History

#1 Updated by Alexander Blum over 4 years ago

  • Priority changed from Normal to Hoch

#2 Updated by Alexander Blum over 4 years ago

  • Description updated (diff)
  • Status changed from Neu to Feedback
  • Assignee set to Meik Michalke
  • Priority changed from Hoch to Normal

#3 Updated by Alexander Blum over 4 years ago

  • Related to Konzept #270: Behaviour after user deleted an object? added

#4 Updated by Alexander Blum over 4 years ago

#5 Updated by Meik Michalke over 4 years ago

  • Assignee changed from Meik Michalke to Alexander Blum

except for the content itself, we're collecting metadata here. the question arises whether there is actually a reasonable use case for deleting artists or releases from the database, once they were added and validated.

as long as the data in question is correct, it should not be deleted. there could be cases where additional information might lead to updates or corrections. but that would keep the data in the database.

i'd say the only valid case for a complete removal is data that is proven to be completely made up, e.g., releases and artists that do not exist. in those cases, assuming that also the releases and creations are bogus, a complete recursive removal seems reasonable. that is to say, as long as the content can't be reassigned to different relases/artists (which, however, would rather make it an issue of first case).

since this would imply we won't ever need to update fingerprint information of the content, it could also be deleted.

#6 Updated by Alexander Blum over 4 years ago

  • Assignee changed from Alexander Blum to Meik Michalke

i'd say the only valid case for a complete removal is data that is proven to be completely made up, e.g., releases and artists that do not exist. in those cases, assuming that also the releases and creations are bogus, a complete recursive removal seems reasonable. that is to say, as long as the content can't be reassigned to different relases/artists (which, however, would rather make it an issue of first case).

Ok, so there's the possibility of deletion (maybe only for some tryton administrators). The recursiveness should be made clear in some documentation then. The same holds for no recursion, as it would be hard(er) to find all creations after deletion of a release. But, if I understand you right, we stick to full recursion?

since this would imply we won't ever need to update fingerprint information of the content, it could also be deleted.

I don't want to touch the archives, if not neccessary. The handling of those trash files is more expensive, than to life with trash on the archives. To prevent later fingerprinting, it's easy to ask the database, if the file is still valid.

#7 Updated by Meik Michalke over 4 years ago

  • Assignee changed from Meik Michalke to Alexander Blum

But, if I understand you right, we stick to full recursion?

yes, if we are sure the entry is complete bullshit. if not, no deletion at all.

I don't want to touch the archives, if not neccessary.

i don't want to, either. the question is whether we are legally allowed to keep the copies if it turns out someone uploaded, e.g., a compilation he made up, using songs of other artists. when we know it's really fake and we don't have permission from the original artists, we might not have the necessary license to keep a copy of the material, because it was illegal in the first place.

i don't know if that's the best of all thinkable examples, but what i try to say is that there might be cases where a deletion from the archives is necessary. but i wouldn't make it an urgency at the moment.

#9 Updated by Alexander Blum over 4 years ago

  • Status changed from Feedback to Erledigt

the question is whether we are legally allowed to keep the copies, if it turns out someone uploaded, e.g., a compilation he made up, using songs of other artists

I see. The ticket for the legal question is #322 (I included this usecase), which may result in tickets to implement deletions on archives in the script for archive administration.

This ticket is about the cascades for the objects implemented in tryton. The cascades are defined for now, so I close this one.

#10 Updated by Alexander Blum over 3 years ago

  • % Done changed from 0 to 100

#11 Updated by Alexander Blum about 2 years ago

  • Target version changed from 1) Testing phase I to Repertoire 1) Testing phase I

#12 Updated by Alexander Blum about 2 years ago

  • Project changed from repertoire to collecting_society

Also available in: Atom PDF