Konzept #341

Creation/Edit of foreign creations

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

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

100%

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

Description

Context

  • A web user creates a new Creation X and tries to add an original/derivative Creation Y.
  • Y does not exists, so he wants to add it.
  • The new Creation Y should be specified by the name of the Artist and Creation.

Question

Should the form field of the Artist be another Dropdown list with a database query?

  • If yes, the whole creation creation process is even more complex, as this would a third layer of object specification.
  • If no, the creation could not be related to any existing artist for sure, as the best we have is a matching name, which could very well be a false positive.

Related issues

Blocks collecting_society - Konzept #324: Should objects of others be editable, if you have created it? Erledigt

History

#1 Updated by Alexander Blum over 4 years ago

  • Blocks Konzept #324: Should objects of others be editable, if you have created it? added

#2 Updated by Meik Michalke over 4 years ago

  • Assignee changed from Meik Michalke to Alexander Blum

i would lean towards "yes", if only to make typos less of a problem. this will of course lead to wrong relations because the web user might just pick the wrong artist.

in conjunction with #324#note-10 the workflow could be like this:

  1. the web user picks one artist from the list of known artists
  2. the artists either accepts the creation or rejects it (until then it remains unclaimed)
  3. should it be rejected, all other known artits by the same name get the creation listed in their profile for review and possible claim or reject

in addition to 1., the web user should also be given the option to not select one of the known artists, either because "i'm not sure which one" or because he knows the right one is still missing in the database. both cases would lead to 3. directly.

#3 Updated by Alexander Blum over 4 years ago

  • Assignee changed from Alexander Blum to Meik Michalke

I'll try to combine a list of known artists with a conditionally visible field for a new artist.

I'd propose the creation to be autocommited, claimed but not revised, as this would be the current mechanism to handle possibly false data and have the users attention on it via the "to revise" list on the dashboard.

I think, it is already tracked, who created the creation, so it would also be possible to visually separate creations created by others on the dahsboard. Maybe I'll add another flag for this to simplify the database requests.

Is this ok?

To be complete, there would also be the case, where another web user being a member of the same artist creates a new to be revised creation. Should this also be flagged with "created by others", or not?

#4 Updated by Meik Michalke over 4 years ago

  • Assignee changed from Meik Michalke to Alexander Blum

Is this ok?

yes, ok.

To be complete, there would also be the case, where another web user being a member of the same artist creates a new to be revised creation. Should this also be flagged with "created by others", or not?

if this web user has some administrative privileges over the artist, s/he should not be considered "other".

#5 Updated by Alexander Blum over 4 years ago

  • Status changed from Feedback to Erledigt
  • % Done changed from 0 to 100

ok

#6 Updated by Alexander Blum about 2 years ago

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

#7 Updated by Alexander Blum about 2 years ago

  • Project changed from repertoire to collecting_society

Also available in: Atom PDF