<h1 class="title">Artist</h1> <p>This module adds the concept of an <code>Artist</code> as an Odoo model.</p> <div class="contents topic" id="table-of-contents"> <p class="topic-title">Table of Contents</p> <ul class="simple"> <li><a class="reference internal" href="#context" id="id1">Context</a></li> <li><a class="reference internal" href="#artists" id="id2">Artists</a><ul> <li><a class="reference internal" href="#partner" id="id3">Partner</a></li> <li><a class="reference internal" href="#members" id="id4">Members</a></li> <li><a class="reference internal" href="#known-issues" id="id5">Known Issues</a></li> </ul> </li> <li><a class="reference internal" href="#contributors" id="id6">Contributors</a></li> <li><a class="reference internal" href="#more-information" id="id7">More information</a></li> </ul> </div> <p>An artist is a general designation for an entity in the entertainment. It can be a humorist, a stage band, an orchestra, a painter, etc.</p> <p>The term artist does not represent a person. It designates a group of people (members). It may however be composed of one person.</p> <a name="context"></a> <h2><a class="toc-backref" href="#id1">Context</a></h2> <p>When designing the module, there was a choice to be made:</p> <ol class="arabic simple"> <li>either a new kind of object for representing artist</li> <li>or otherwise extend <cite>res.partner</cite></li> </ol> <p>One reason for seperating an artist in a separate model is the ambiguity between the commercial entity that owns the artist and the artist itself.</p> <p>Also there is a distinction between the contacts at the commercial entity and the members of the artist.</p> <a name="artists"></a> <h2><a class="toc-backref" href="#id2">Artists</a></h2> <p>The module defines the form view of an artist.</p> <img alt="static/description/artist_form.png" src="static/description/artist_form.png" /> <a name="partner"></a> <h3><a class="toc-backref" href="#id3">Partner</a></h3> <p>The field <cite>Partner</cite> of an artist designates the commercial entity (i.e. for invoicing purposes).</p> <a name="members"></a> <h3><a class="toc-backref" href="#id4">Members</a></h3> <p>An artist can have one or more members.</p> <p>Members are contacts. Each of theme has a role.</p> <img alt="static/description/artist_member_list.png" src="static/description/artist_member_list.png" /> <a name="known-issues"></a> <h3><a class="toc-backref" href="#id5">Known Issues</a></h3> <p>The module defines views for artists, roles and tags. However, it does not add menu items for accessing these. We encourage you to add the appropriate menu entries and access rights in a separate module depending on your use case.</p> <a name="contributors"></a> <h2><a class="toc-backref" href="#id6">Contributors</a></h2> <ul class="simple"> <li>Numigi (tm) and all its contributors (<a class="reference external" href="https://bit.ly/numigiens">https://bit.ly/numigiens</a>)</li> </ul> <a name="more-information"></a> <h2><a class="toc-backref" href="#id7">More information</a></h2> <ul class="simple"> <li>Meet us at <a class="reference external" href="https://bit.ly/numigi-com">https://bit.ly/numigi-com</a></li> </ul>