collecting_society

uniqueness as float
most_similar_track as track_id uuid string

most_similar_track as uuid string? not as relation to another content?

I don't mind, doesn't make a big difference to me. If it makes sense, let it be a relation.

Thomas Mielke wrote:

EchoNest track IDs.

What is the exact purpose of the field?

I assume, the information of the most similiar track could be useful for the admins if there's a dispute. They wouldn't know what to do with that string.

most similiar track

I understand that, but there's also the good practise, that all fields should be handable via tryton client. A string even including semantics implicitly would be highly error-prone. You can't switch the relationship by a prefix. Either it's a relation to a Content and Tryton will offer search and everything, or it is a dumb string. Only a semantic relation to Content would be useful for humans.

If there are echonest tracks not covered by our database, wouldn't it be more reasonable to create the Creation in our database?
What is the echonest track id anyway? Is this id stable? I would not want to mix external information with our internal database "directly".
We had in mind, to add other identifications for a Content via a special table (including e.g. musicbrain id / discogs id / etc.).

uniqueness

Another question for uniqueness: do you use the "excerpt" to calculate this field? If yes, shouldn't we also defere the calculation of the ratio "before/after" to the external statistics module and just save the "before" value? As I understand, the "after" value might change after ingestion of other tracks. Via the statistics module, the current value could then be computed on a regular basis.

The purpose is to show both, artist and admin, if the creation has already been uploaded -- either by another artist or the same one. If most_similar_content is None but the fields most_similar_artist and most_similar_track are filled, maybe it's not necessary to show it to the artist but it can act as a random sample to check if the artist and track title are provided correctly.

For the web interface, creation form, the logic could be: "if similar_content is not None and uniqueness <= possible_dupe_threshold then display 'sounds like artist - track title' with a preview link"; furthermore: "if artist == similar_artist then print 'are you sure you haven't uploaded this track before?' else handle_possible_artist_dispute()"

Applied in changeset collecting_society|ca271193ab745fc4f00c0f9d59c237b4d6f0c571.