C3S Tracker: Issueshttps://redmine.c3s.cc/https://redmine.c3s.cc/favicon.ico2019-03-16T20:24:11ZC3S Tracker
Redmine collecting_society - Webfrontend #861 (Neu): Add default contributions for artistshttps://redmine.c3s.cc/issues/8612019-03-16T20:24:11ZAlexander Blum
<p>Would be nice, but would require javascript hacks to load default settings after loading of the form.</p>
collecting_society - Webfrontend #855 (Neu): add ajax request for edit permission for foreing art...https://redmine.c3s.cc/issues/8552019-03-16T13:08:42ZThomas Mielke
<p>... if there was no email provided while adding a foreign track.</p>
<p>Alternative: Ajax call -- query write permissons -- maybe makes more sense because dependend on this you can show the edit option, not only add.</p>
collecting_society - Userfeedback #792 (Neu): 'Select file...' button for picture upload needs tr...https://redmine.c3s.cc/issues/7922018-11-17T12:55:27ZThomas Mielke
<p>no clue yet how to inject a translation there.</p>
collecting_society - Datenbank #731 (Neu): Add Artist.contribution function fieldhttps://redmine.c3s.cc/issues/7312018-11-06T20:14:00ZAlexander Blum
<p>The contributions should be also available from the artists.</p>
collecting_society - Webfrontend #693 (Neu): Add change button for datatable sequences with one e...https://redmine.c3s.cc/issues/6932018-11-05T14:42:52ZAlexander Blum
<p>Introduce "change" button (remove + add)</p>
<ul>
<li>max_len = 1 => buttons remove/change</li>
<li>max_len = 1 + min_len = 1 => buttons change</li>
</ul>
collecting_society - Webfrontend #623 (Neu): Add dispute interfacehttps://redmine.c3s.cc/issues/6232018-07-01T19:23:10ZAlexander Blum
<p>Artists/Releases/Creations/Content need to be disputable, to delegate a dispute between web users to administrator staff.</p>
<a name="Links"></a>
<h1 >Links<a href="#Links" class="wiki-anchor">¶</a></h1>
<ul>
<li><a href="https://redmine.c3s.cc/projects/repertoire/wiki/Specification#Disputes" class="external">Specification</a></li>
<li><a href="https://redmine.c3s.cc/projects/repertoire/wiki/Workflows#Dispute" class="external">Workflow</a></li>
</ul>
<a name="Notes"></a>
<h1 >Notes<a href="#Notes" class="wiki-anchor">¶</a></h1>
<ul>
<li>maybe add additional comment field for communication with disputing users (opposed to administrator comments)</li>
<li>maybe add wizards to automatically resolve/dismiss the request by administrators within tryton</li>
</ul>
<a name="Views"></a>
<h1 >Views<a href="#Views" class="wiki-anchor">¶</a></h1>
<a name="Dispute-List"></a>
<h2 >Dispute List<a href="#Dispute-List" class="wiki-anchor">¶</a></h2>
<ul>
<li>datatable sequence (maybe template first, but most lists should be datatable sequences in the end)
<ul>
<li>date</li>
<li>code</li>
<li>reference -> Link to Show / Modal?</li>
<li>case</li>
<li>state (default sort)</li>
<li>show -> link to dispute show</li>
</ul></li>
</ul>
<a name="Dispute-Confirmation"></a>
<h2 >Dispute Confirmation<a href="#Dispute-Confirmation" class="wiki-anchor">¶</a></h2>
<ul>
<li>text (implications)</li>
<li>case (Select)</li>
<li>reference (Readonly / Link?)</li>
<li>comment</li>
<li>submit -> link to dispute show (+ flash message)</li>
</ul>
<a name="Dispute-Show"></a>
<h2 >Dispute Show<a href="#Dispute-Show" class="wiki-anchor">¶</a></h2>
<ul>
<li>code (header?)</li>
<li>case</li>
<li>state</li>
<li>reference</li>
<li>comment</li>
<li>text (implications "no money", "contact information", etc)</li>
<li>"undispute" (if web_user started it)</li>
</ul>
<a name="Dashboard"></a>
<h2 >Dashboard<a href="#Dashboard" class="wiki-anchor">¶</a></h2>
<ul>
<li>section "disputes (number)" -> link to dispute list</li>
</ul>
<a name="Object-Lists"></a>
<h2 >Object Lists<a href="#Object-Lists" class="wiki-anchor">¶</a></h2>
<p>(artists/releases/creations/content)</p>
<ul>
<li>rows
<ul>
<li>grouped by dispute state</li>
<li>disputed: highlighted?</li>
<li>show dispute button -> link to dispute show</li>
</ul></li>
<li>filter: Disputed? (blocked by datatables lists?)</li>
</ul>
<a name="Object-Show"></a>
<h2 >Object Show<a href="#Object-Show" class="wiki-anchor">¶</a></h2>
<p>(artist/release/creation/content)</p>
<ul>
<li>dispute button -> link to dispute confirmation (content: only rejected)</li>
</ul>
collecting_society - Webfrontend #593 (Neu): Add js hightlight for searcheshttps://redmine.c3s.cc/issues/5932018-06-04T16:11:07ZAlexander Blum
<p>Especially if the searchterm in datatables extends to hidden cloumns, the result set might be confusing for the users. To improve this, we could implement or include some highlighter library, to highlight the matching part. If that part is hidden, we could try to autoshow the details section.</p>
collecting_society - Webfrontend #394 (Neu): Add js/css inclusion via registryhttps://redmine.c3s.cc/issues/3942017-04-17T04:07:58ZAlexander Blum
<p>Js/Css might be better included via registry instead of templates.</p>
collecting_society - Webfrontend #393 (Neu): Add backlink field in sessionhttps://redmine.c3s.cc/issues/3932017-04-17T04:05:42ZAlexander Blum
<p>Add a field 'backlink' in the user session for redirects, e.g. to 'show release' after adding a creation to the release via 'show release'.</p>
collecting_society - Schnittstellen #364 (Neu): Add autoregistration via c3sMembership apihttps://redmine.c3s.cc/issues/3642017-04-17T02:16:10ZAlexander Blum
<p>Autoregistration via c3sMembership api should be possible.</p>
<p>This means an autoregister view to</p>
<ul>
<li>accept a token via URL (+ email?), e.g. /register/EMAIL/TOKEN</li>
<li>ask the membership db for the token (+ email?) via api</li>
<li>if the token is accepted
<ul>
<li>create the user using the provided information in the response</li>
<li>log the user in</li>
<li>provide user feedback via flash message</li>
</ul></li>
<li>if the token is not accepted
<ul>
<li>redirect to /</li>
<li>provide minimal user feedback via flash message</li>
</ul></li>
</ul>
collecting_society - Webfrontend #351 (Neu): Abstraction of uploadshttps://redmine.c3s.cc/issues/3512017-04-17T00:58:39ZAlexander Blum
<p>Uploads with jQuery-File-Upload should be a configurable part of portal, if reasonable - maybe as a service, or as a part of deform.</p>
collecting_society - Webfrontend #335 (Neu): Add additional email headers in the mail servicehttps://redmine.c3s.cc/issues/3352017-04-11T23:17:08ZAlexander Blum
<blockquote>
<p><strong>Meik:</strong><br>
on a "nice to have" basis, i really like the option of filtering mails by headers (like mails from redmine). so it could be neat to have something like</p>
<ul>
<li>X-C3S-repertoire-artist: a0000000132 (i.e., if there's a particular artist this mail is intended for; same for release/creation)</li>
<li>X-C3S-repertoire-issue-type: (validation|error|claim|profile|...) (some expendable code what kind of automatic mail this is)</li>
</ul>
</blockquote>
collecting_society - Webfrontend #334 (Neu): Add claim interfacehttps://redmine.c3s.cc/issues/3342017-04-11T23:08:18ZAlexander Blum
<p>The user should be enabled to claim Artists, Releases and Creations.</p>
<a name="Links"></a>
<h1 >Links<a href="#Links" class="wiki-anchor">¶</a></h1>
<ul>
<li><a href="https://redmine.c3s.cc/projects/repertoire/wiki/Specification#Claims" class="external">Specification</a></li>
<li><a href="https://redmine.c3s.cc/projects/repertoire/wiki/Workflows#Claim" class="external">Workflow</a></li>
</ul>
<a name="Notes"></a>
<h1 >Notes<a href="#Notes" class="wiki-anchor">¶</a></h1>
<ul>
<li>Check information leakage (e.G. no email) on claims</li>
<li>State 'revised' seems to be obsolete now</li>
<li>Stage 'demanded' went into commit workflow (created vs uncommitted)</li>
<li>ACL needs to be applied
<ul>
<li>e.g. if a release is claimed for artist X, the web user needs to have admin rights for artist X</li>
<li>if no object exists, for which some object can be claimed, a claim should not be possible (no button)</li>
</ul></li>
<li>Already claimed objects should not be claimable again (e.g. if there's a dispute)</li>
<li>Maybe there should be a dispute link for claim requests, which resulted in a dispute?</li>
</ul>
<a name="Views"></a>
<h1 >Views<a href="#Views" class="wiki-anchor">¶</a></h1>
<a name="Claim-List"></a>
<h2 >Claim List<a href="#Claim-List" class="wiki-anchor">¶</a></h2>
<ul>
<li>datatable sequence (maybe template first, but most lists should be datatable sequences in the end), default list: offered objects
<ul>
<li>object (which object)</li>
<li>for (for what object)</li>
<li>dependencies (artist -> releases, release -> creations; maybe only on confirmation view?)</li>
<li>control: remove</li>
</ul></li>
</ul>
<a name="Claim-Confirmation"></a>
<h2 >Claim Confirmation<a href="#Claim-Confirmation" class="wiki-anchor">¶</a></h2>
<ul>
<li>text (implications)</li>
<li>object (Readonly / Link?)</li>
<li>for (Readonly / Link?)</li>
<li>submit -> link to claim list or dispute show (+ flash message)</li>
</ul>
<a name="Dashboard"></a>
<h2 >Dashboard<a href="#Dashboard" class="wiki-anchor">¶</a></h2>
<ul>
<li>section "claim offers (number)" -> link to claim list</li>
</ul>
<a name="Object-Show"></a>
<h2 >Object Show<a href="#Object-Show" class="wiki-anchor">¶</a></h2>
<p>(artist/release/creation)</p>
<ul>
<li>claim button -> link to claim confirmation</li>
</ul>
collecting_society - Webfrontend #328 (Neu): Add commit interfacehttps://redmine.c3s.cc/issues/3282017-04-11T21:02:29ZAlexander Blum
<p>Artists, Releases and Creations should be commitable. The act of commiting should be conscious and make it clear, that further changes afterwards possibly imply dispute processes.</p>
<a name="Links"></a>
<h1 >Links<a href="#Links" class="wiki-anchor">¶</a></h1>
<ul>
<li><a href="https://redmine.c3s.cc/projects/repertoire/wiki/Specification#Commits" class="external">Specification</a></li>
<li><a href="https://redmine.c3s.cc/projects/repertoire/wiki/Workflows#Commit" class="external">Workflow</a></li>
</ul>
<a name="Notes"></a>
<h1 >Notes<a href="#Notes" class="wiki-anchor">¶</a></h1>
<ul>
<li>visibility (adjust queries!)
<ul>
<li>own uncomitted objects should only be addable to other own uncommited objects</li>
<li>one should never be able to view/add uncommited objects of others</li>
</ul></li>
<li>default list: all uncommited objects</li>
<li>translation
<ul>
<li>Entwürfe / Drafts</li>
<li>Entwurf veröffentlichen / Publish draft</li>
</ul></li>
<li>commit list/confirmation: one form controller with two stages</li>
<li>web user should be able to distinguish private/public fields (after commit)</li>
</ul>
<a name="Views"></a>
<h1 >Views<a href="#Views" class="wiki-anchor">¶</a></h1>
<a name="Commit-List"></a>
<h2 >Commit List<a href="#Commit-List" class="wiki-anchor">¶</a></h2>
<ul>
<li>datatable sequence (add/delete)
<ul>
<li>object -> link to show? modal with details?</li>
<li>dependent objects -> link to show? modal with details?</li>
<li>controls: delete</li>
</ul></li>
<li>next button -> link to commit confirmation</li>
</ul>
<a name="Commit-Confirmation"></a>
<h2 >Commit Confirmation<a href="#Commit-Confirmation" class="wiki-anchor">¶</a></h2>
<ul>
<li>text (implications)</li>
<li>rendered object text (must be saved/logged)</li>
<li>publish button -> link to commit list (+flash message)</li>
</ul>
<a name="Dashboard"></a>
<h2 >Dashboard<a href="#Dashboard" class="wiki-anchor">¶</a></h2>
<ul>
<li>section "drafts (number)" -> link to commit list</li>
</ul>
<a name="Object-Lists"></a>
<h2 >Object Lists<a href="#Object-Lists" class="wiki-anchor">¶</a></h2>
<p>(artists/releases/creations)</p>
<ul>
<li>rows
<ul>
<li>grouped by commit state</li>
<li>uncommited: highlighted?</li>
<li>revised: "certificate" seal?</li>
<li>publish -> link to commit list (with probably only this object)</li>
</ul></li>
<li>filter: Draft/Published? (blocked by datatables lists?)</li>
</ul>
collecting_society - Datenbank #311 (Neu): Add general dispute workflowhttps://redmine.c3s.cc/issues/3112017-04-09T02:47:51ZAlexander Blum
<p>There are different workflows right now</p>
<ul>
<li>Content.dispute (bool)</li>
<li>Creation.state (on_approval, approved, rejected)</li>
</ul>
<p>There should be a generalized <a class="wiki-page" href="https://redmine.c3s.cc/projects/collecting_society/wiki/Workflows#Dispute">workflow</a> to handle all kinds of disputable objects.</p>
<p>We need a dispute object.</p>