MEMBERS: General Artist Help

In the Artist section, you define the basic parameters of your Artist Profile. A "nickname"is your screen name. It is used to quickly identify your biographical data. When you submit a work to a call for submissions, you will be able to quickly choose the bio you want to associate with your submission by its nickname. A "display name," on the other hand, is how you want your name to appear in print. When you submit a work to a call for submissions, your display name will be used.

Your Artist Profile can have may have multiple contact references. This contact information might be your website, telephone number, or email address.

You can also upload an Artist Profile image that can be harvested for social media posts. At this time, you may only attach one image file to your Artist Profile.

ORGANIZERS: Formatting Information

The following codes are available for formatting the information for opportunity organizers. In most cases, formatting requires the element to be encapsulated. For example:

Typing     ''Bird, bird, bird, b-bird's the word    will not only italicize "Bird, bird, bird, b-bird's the word," but also everything that follows it. In this example, if you want to only italicize "Bird, bird, bird, b-bird's the word," you must also "close" the formatting element with two grave accents like this:    ''Bird, bird, bird, b-bird's the word''

Remember, with the exception of bulleted lists, formatting codes have an opening mark and a closing mark.

Sending Emails

ORGANIZERS: Submission Form Builder Guide

In every New Music Engine opportunity submission form, some default fields are always required and included; however, you can add additional fields in the Submission Form Builder. The default fields are:

Title
Composer(s)
Instrumentation Description
Approximate Duration

Important Anonymous: Selecting Anonymous will only hide composer's name from adjudicators. If you wish to hide other fields, see "Admin Only" option below.

Each added form element has a number of options including:

• Required: Selecting "Yes" for this form element indicates that the element must be completed for the submission form to be considered complete. Artists submitting do not have to complete the form on one visit, but may return to edit their submission until you place the opportunity into "Close" status after the deadline has passed.
• Admin Only: Selecting "Yes" indicates that this field will only be available to managers of this opportunity call. These fields will not be distributed to judges in judging rounds. This allows you to collect some data, like a biographical sketch, that you ultimately need for promotion but not data you want your adjudicators to see while considering submissions.

Additionally, most opportunities also request program notes, biographical data, and performance notes. These basic attributes are automatically listed, but you can easily delete, edit, or reorder any of the submission form elements. Use the Submission Form Builder to add additional custom input form elements on the submission form of your opportunity. You can choose from five different types of Submission Form Elements to add: Text Values, Numeric Range, Comments Field, URL Field and File Upload.

Submission form elements will appear on the submission form in the same order as they appear in the builder. To change the order of submission form items, simply drag the rows to put them in the desired order.

Some Examples:

ORGANIZERS: Opportunity Announcement Builder Guide

Organizers use this section to setup Announcements and Actions that will appear once the opportunity has been placed in "Post Production" status. IMPORTANT: Announcements and/or actions entered in this section will not appear until the opportunity has been placed in "Post Production" status.

Announcements

There are three types of Announcements:

Actions

Use Actions to gather more information from creators of accepted submissions. Creating an action item is just like adding a form element to a submission form. Examples of use include, asking submitters to provide an image for a concert program, their birth year, a set of PDF instrumental parts, or just a confirmation that they understand they have been selected. Use Actions to collect information from creators that you don't want to collect at the time of the submission.

When a submitter logs into New Music Engine, an alert will appear in the notification frame on the left-hand side of the screen. When the submitter clicks on that alert, they will be directed to a page that contains their submission information, Acceptance Message, and these Actions. Submitters whose works were rejected will not see these actions.

Example

ORGANIZERS: Embed Information

Using the code below, you can very easily embed this call into your own webpage design in three easy steps:

• Make sure your webpage uses JQuery. The page must include the minimum jQuery build, which can easily be downloaded here: https://jquery.com
• Simply copy all of the code below into the body of your HTML design template.

<div id="NME_category_categoryID" class="NME_category_categoryID" style="display:none;"></div> <div class="NME_category_name NME_category_nameClass" style=""></div> <div class="NME_categoryStubWrap"> <div class="NME_categoryImageCol"> <img src="" class="NME_category_image NME_category_imageClass" /> </div> </div> <div class="NME_categoryStubWrapCols"> <div class="NME_categoryStubElementCol NME_category_ElementLabels">Prize:</div> <div class="NME_category_prize NME_categoryStubDataCol NME_category_stubClass"></div> </div> <div class="NME_categoryStubWrapCols"> <div class="NME_categoryStubElementCol NME_category_ElementLabels">Deadline:</div> <div class="NME_category_displayDeadline NME_categoryStubDataCol NME_category_stubClass"></div> </div> <div class="NME_categoryStubWrapCols"> <div class="NME_categoryStubElementCol NME_category_ElementLabels">Fee:</div> <div class="NME_category_fee NME_categoryStubDataCol NME_category_stubClass"></div> </div> <div class="NME_categoryStubWrapCols"> <div class="NME_categoryStubElementCol NME_category_ElementLabels">Open To:</div> <div class="NME_category_openTo NME_categoryStubDataCol NME_category_stubClass"></div> </div> <div class="NME_category_ElementContentDivider"></div> <p class="NME_category_headerClass">Call for Submissions</p> <div class="NME_category_content NME_category_contentClass"></div>

• Place the following code inside the <head> tag on your webpage. This styling text can be edited to suit your design and needs, and you can also simply copy it into any stylesheet associated with the webpage.

<style> /* CSS Document */ /* Standard CSS for static Category (Opportunity) pages */ /* /* Available Elements <div id="ma_category_name"></div> <div id="ma_category_content"></div> <div id="ma_category_displayDeadline"></div> <div id="ma_category_type"></div> <div id="ma_category_receiptType"></div> <div id="ma_category_fee"></div> <div id="ma_category_prize"></div> <div id="ma_category_openTo"></div> <div id="ma_category_categoryID">30024</div> */ .NME_categoryStubWrap { /* Wrapper for Opportunity Stub */ margin:auto; overflow: hidden; width: 90%; } .NME_categoryImageCol{ /* Column for the Image */ width: 90%; padding: 5px; text-align: center; } .NME_categoryStubWrapCols { width: 100%; overflow: hidden; } .NME_categoryStubElementCol { /* Column for element labels (e.g., "Deadline") */ float: left; width: 35%; padding: 5px; text-align: right; } .NME_categoryStubDataCol { /* Column for the elements */ float: left; width: 60%; padding: 5px; } .NME_category_nameClass { /* class for the Title of the Opportunity */ text-align:center; color: rgba(153, 26, 41, 1); font-size: 175%; margin: 15px 0px 10px 0px; line-height: 120%; } .NME_category_ElementLabels { /*For static elements like "deadline, etc..."*/ color: rgba(81, 126, 214, 1); text-align:right; padding-right: 5px; font-weight: bold; } .NME_category_headerClass { /* class for the "Submission Guidelines" */ color: rgba(153, 26, 41, 1); font-size: 125%; margin: 15px 0px 10px 0px; line-height: 120%; margin-left: 15%; } .NME_category_stubClass { /* class for the Stub Elements (e.g., Prize, Deadline, etc...) */ color: #3a445d; } .NME_category_stubClass::after { content: "\00a0"; /*adds a space in case an ID element is empty */ } .NME_category_imageClass { max-width: 240px; width: 95%; padding: 5px; } .NME_category_ElementContentDivider { /* Space between Opportunity Stub and Submission Content */ clear:left; margin-top: 20px; } .NME_category_contentClass { /* class for submission guidelines/main content of opportunity */ display:inline-block; color: rgba(29, 44, 77, 1); margin-left: 15%; } .NME_submissionList { /* class to accepted submissions */ overflow: hidden; } @media only screen and (max-width:1000px) { .NME_categoryStubWrap { /* Wrapper for Opportunity Stub */ margin:auto; overflow: hidden; width: 100%; max-width: 700px; } .NME_categoryStubElementCol { /* Column for element labels (e.g., "Deadline") */ float: left; width: 35%; padding: 5px; max-width: 150px; text-align: right; } .NME_categoryStubDataCol { /* Column for the elements */ float: left; width: 60%; padding: 5px; max-width: 500px; } } </style>

Note that you can edit the CSS however you want, and you can move other elements around in the code to suit your needs. The only thing you can't do is change <div> ID names or move the link to the javascript file (It must be stated AFTER the DIV tags are loaded).

See an example of another opportunity here.

ORGANIZERS: Opportunities List Information

This page lists all of the opportunities that you are managing and is the primary place for administering all of your competitions. Opportunities can be in one of five possible states:

Note: You cannot undo a status change or roll back a status change. For example, once the call for submissions is published, it cannot be set to the status of Not Published.

Listing non-NME Opportunities

This page contains the opportunities that you listed on New Music Engine. These opportunities are not hosted by NME, but are simply listed for the convenience of members

Note: You cannot undo a status change or roll back a status change. For example, once listing is submitted, it cannot be set back to "Open for Edits"

ORGANIZERS: All Submissions Spreadsheet

Use this page to manage submissions for . On this spreadsheet, you can review submission information, media files, accept and reject submissions, and email individual artists or groups of artists.

Table Color Legend

Actions Menu and Sorting

To sort columns, click the column header.

To perform an action on a submission or a group of submissions, select the submissions by checking the checkbox aligned with the submission and choose the action from the "Actions Menu."

View Submissions by Adjudication Round

To view submissions assigned to a specific judging round, simply click the judging round name in the "Judging Round(s) Alignment" column. This will return only the submissions in the adjudication round. Use "View All Submissions" in the View menu to return.

ORGANIZERS: Judging Round Manager

This page lists all of the opportunities that you are managing and is the primary place for administering all of your competitions.

Opportunities can be in one of five possible states:

Note: You cannot undo a status change or roll back a status change. For example, once the judging round is active, it cannot be set back to "Open for Edits".

ORGANIZERS: RubricBuilder Guide

A judging rubric is a great way to help judges think about elements to consider when reviewing submisssions. As a generic example, you may want judges to consider and provide a score for the level of creativity of a submission. Additionally, you may want to gather general comments about submissions from the judges or have them give an overall score for the submitted creative work. With the RubricBuilder, you can easily create a system to collect this type of data and much more.

Below is are examples of rubric elements. They are presented here in the way judges see them on the screen. Elements in brackets are hints and explanations for you and will not be displayed to the judges.

ORGANIZERS: Judging Task Distribution

Basic Distribution: With this assignment, every judge will receive every piece, which must be judged, in their task list.

Complete Distribution: With this assignment, every judge will receive every piece in their task list. Redundancy effects the number of submissions that each judge will score.

Even Distribution: With this assignment, submissions are distributed evenly to judges. Judges will not review every submission, but a random selection of submissions. For example, if your judging round has three judges and 60 submissions with no score redundancy (see below), then each judge will be assigned 20 submissions to judge.

Score Redundancy: Choose the number of judging scores each submission will need to be considered "judged".

Examples:


Scenario 1:
Distribution Method: Basic Distribution
Score Redundancy: n/a
# of Judges: 3
# of Submissions: 60

In Scenario 1, each judge will be presented with all 60 submissions and each judge must adjudicate each submission. This is the same as using Complete Distibution (see scenario 2, below) where the redundancy equals the number of assigned judges.


Scenario 2:
Distribution Method: Complete Distribution
Score Redundancy: 2
# of Judges: 3
# of Submissions: 60

In Scenario 2, each judge will be presented with the entire list of submissions (Complete Distribution); however, due to the score redundancy of 2, they will not judge every piece. Once a submission is judged twice, it will be considered complete and be removed from the list of tasks. In other words, the task list is dynamic -- submissions are removed as judging occurs.


Scenario 3:
Distribution Method: Even Distribution
Score Redundancy: 1
# of Judges: 3
# of Submissions: 60

In Scenario 3, each judge will receive 20 submissions in their task list. The task list for the round is not dynamic, therefore each judge will have to complete their assigned task list. Judging will not be complete until each judge completes their individual task list.


Scenario 4:
Distribution Method: Even Distribution
Score Redundancy: 2
# of Judges: 3
# of Submissions: 60

In Scenario 4, each judge will receive 40 submissions in their task list: (Submissions x Score Redundancy) ÷ Number of Judges. Each judge will have to complete their task list as the task list is not dynamic. Judging will not be complete until each judge completes their individual task list.

ORGANIZERS: Judging Round Information

This page simply lists the settings for this judging round.

ORGANIZERS: Judging Tasks Manager

This page lists all of the judging tasks for this judging round.