Enhancement
Force always new
Issue description
It makes sense to disallow access to topic selection when choosing a counter player in the form. Some user groups may not access the whole range of counter players. In the case of a file, it simply has to be uploaded, no need to merge, since the file is recognized by its value (byte stream). In case of something else than a file, there is currently no way to recognize the topic as already existing.
Developer comments
Current use case for this: it should be possible to force a file upload (simplified selection) even if the uploaded file may be associated to more than one topic. In such a case there would be currently a select box, but the file should be always uploaded.
I think this only makes sense when there is a file to upload. A topic would need a subject identifier to be recognized as equal, but that can currently only be created after the statements are persisted. That would be too late because the duplicate topic would have already been created.
If the topic could be equipped with the computed subject identifier before the package is saved, that would be ideal. Server-side this is problematic, because the API only works on persisted information. If we let our thoughts go wild, a before form saved trigger could work (somehow, topic is not in the main form).
Rejection comment
I do not think this makes sense on such a broad scale given the technical and usability problems. Go back to the simple case of file upload.
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.