Difference between revisions of "ChoralWiki:Add score activities"

From ChoralWiki
Jump to navigation Jump to search
(Added remark about new editions to be added on top with respect to the others)
m (add copyright and also new section, checking if published →‎Exception management)
 
Line 46: Line 46:
  
 
III. Erroneously linked external files. Sometimes users do not correctly copy-and-paste the relevant links for externally hosted files when they fill the "add work" form, therefore the links inside the wiki code automatically produced do not link to the real file or website page. In this case, you need to visit the external website and look for a reasonable page to be linked from ChoralWiki. As a general rule, "shallow linking" is preferred with respect to "deep linking", i.e., the link from ChoralWiki should open a web page on the external website that allows the user to browse the website itself, rather than directly opening the target file(s).
 
III. Erroneously linked external files. Sometimes users do not correctly copy-and-paste the relevant links for externally hosted files when they fill the "add work" form, therefore the links inside the wiki code automatically produced do not link to the real file or website page. In this case, you need to visit the external website and look for a reasonable page to be linked from ChoralWiki. As a general rule, "shallow linking" is preferred with respect to "deep linking", i.e., the link from ChoralWiki should open a web page on the external website that allows the user to browse the website itself, rather than directly opening the target file(s).
 +
 +
IV. Copyright questions. Please e-mail copyright{{@}}cpdl.org.
 +
 +
===Checking if editions have been published===
 +
Volunteers typically start by having another volunteer identify and forward one or more editions to add.
 +
 +
Once you are ready to be added to the feed of submissions, you will need to check for yourself whether an edition has been added. The simplest way to do this is to put the CPDL edition number in the search box and check the results of the search.
 +
 +
Addscore volunteers update [[Help:Why_hasn%27t_my_edition_been_added_yet%3F|this Help page]] indicating the status of the current backlog. If a score is missing on CPDL but the date of submission predates the date indicated, it likely means that a volunteer evaluated the edition and there was a reason it was not added, such as:
 +
 +
* duplicate form filled out for an edition covered by an earlier CPDL #;
 +
* the contributor has been contacted with a question, such as if the score cannot be found;

Latest revision as of 10:25, 10 February 2012

This page contains a description of the so-called "Add score" activities, to be performed to add new scores to ChoralWiki, especially by volunteers or other users helping out when the publication process was not completed by the user who originally submitted the work.

CPDL users performing these activities are expected to be familiar with the CPDL submission process. Please find details in the Add music help and in the Score submission guide (available in multiple languages). Users performing these activities should also receive via e-mail the wiki code automatically produced by the system whenever a new work is submitted. CPDL Administrators will provide it, either by manually forwarding existing emails, or by adding the user's email to the existing distribution list of the wiki code.

Basic activities

These activities are those allowing a new work to be published on ChoralWiki "as is", without refining any details (see "Refinement activities" next) and assuming that the wiki code automatically produced does not require any corrections (see "Exception management" next).

All instructions to perform these activities are provided in the Score submission guide (available in multiple languages). A staged approach is generally best in order to learn the process:

  • first, a new edition of a work published already, so that it is not necessary to create either the composer page nor the work page, as they both exist already; then
  • second, a new work of an existing composer, so that a new work page needs to be created, but the composer page already exists; then
  • third, a new work for a new composer, so that both the composer page and the work page have to be created.

Some tips:

1. Check whether the composer page exists already. Please consider possible alternative spellings of the name. ChoralWiki generally follows Wikipedia's spelling;

2. Check whether a work page exists for this piece by this composer. If it exists, it may be convenient to right-click on the link for that piece to open the work page in a new tab, checking to make sure that this same editor does not already have an edition listed there under a separate CPDL# (sometimes users submit the form twice, even consecutively, and add their own under one number and then we have to figure out that the second number is a duplicate). If it's not a duplicate, then add just the snippet describing the work, rather than all of the text to create a whole new page for that particular work. New editions should be added on top with respect to the others;

3. Use the Preview feature to see what changes will look like before saving them. However, when looking at one's update in preview mode, don't forget to save the changes, which are lost if you close the browser window or click on a link that takes you to another page. If clicking on links within your preview, it's important to click in the way that opens it in a new browser tab, rather than changing the current browser window (control-left click works on Firefox under Windows, and there may be different single click combinations that work in different environments; certainly, left-clicking should be avoided; we will refer to this as Special-Click hereafter).

Refinement activities

a. Update the date inside {{NewWork|YYYY-MM-DD}} to the date that you yourself are actually adding it to CPDL's listings. The date the contributor submitted it is already covered in the Editor field.

b. If the CPDL number information is formatted as '''CPDL #XXXXX:''', change it to {{CPDLno|XXXXXX}} (withough the quotes). Recent wiki code is already produced with the new format.

c. If the links for the files are on an external site rather than hosted locally on CPDL, then the {{pdf}} needs to be changed to {{extpdf}}, {{mid}} similarly to {{extmid}} to indicate that it's external -- that puts a little offsite globe next to the graphic image indicating PDF or Midi as the file type.

d. In Preview mode, make sure nothing broke due to weird line breaks in your cut-and-paste. Links generally show as blue or purple, otherwise red links indicate a non-existing link within the wiki.

e. In Preview mode, Special-Click to make sure the links to the PDF and other formats are actual files and work properly. Sometimes people leave [[mid]] without actually specifying a location for the midi file. So if a PDF, midi, source and/or mp3 link is indicated, they should all click to something real rather than being non-clickable or giving a "404 not found" error. Externally hosted files should be "shallow linked" and not "deep linked", i.e., the link from ChoralWiki should open a web page on the external website that allows users to browse the website itself, rather than directly opening the target file(s). See next about fixing exceptions of this type.

Other possible refinements: add texts/translations; check/add incorrect/missing composer nationality, era, composition genre, voicing, birth/death dates, etc.; create redirects and aliases for optional composer spellings. See details on the Volunteers page.

To do: additional templates that cannot be added automatically? Other?

Exception management

I. Missing files. Sometimes users fill the "add work" form, but they forget to actually upload the files associated to it (pdf, midi, source, mp3). In order to check whether files exist somewhere, go to the Log page, select the "upload log" option and enter the username of the user who submitted the form. This will list all files submitted by the user, in reverse chronological order. If you cannot locate any file that appears reasonably related with the work submitted, there is no other alternative than contacting the user and ask clarification. This is the text of a possible request, which may be sent to the user via email and/or through the user's discussion page:

Thank you for offering this work to CPDL. Unfortunately, you don't seem to have uploaded the appropriate file(s) to the CPDL server. To do this, log in and click on the "Upload file" link on the left of any CPDL page. Please then inform via email the "addscore team" (addscore@cpdl.org) that you have done so. Alternatively, if you're having problems uploading the file(s), you can include them in an email to the team, and a team member will upload them for you. Please do not run the add works form again. Many thanks.


II. Erroneously linked local files. Sometimes users correctly upload the required files, however they do not correctly copy-and-paste the relevant links when they fill the "add work" form, therefore the links inside the wiki code automatically produced do not link to the real file. In this case, you might be able to locate the actual files as described above (go to the Log page, select the "upload log" option and enter the username of the user who submitted the form. This will list all files submitted by the user, in reverse chronological order), and then you can correct the relevant links. You can use the {{filepath:xxxxxx}} syntax to simply enter the filename and let the wiki software do the rest, without specifying the whole "http://www.cpdl.org/wiki/..." path.

III. Erroneously linked external files. Sometimes users do not correctly copy-and-paste the relevant links for externally hosted files when they fill the "add work" form, therefore the links inside the wiki code automatically produced do not link to the real file or website page. In this case, you need to visit the external website and look for a reasonable page to be linked from ChoralWiki. As a general rule, "shallow linking" is preferred with respect to "deep linking", i.e., the link from ChoralWiki should open a web page on the external website that allows the user to browse the website itself, rather than directly opening the target file(s).

IV. Copyright questions. Please e-mail copyright At sign.png cpdl.org.

Checking if editions have been published

Volunteers typically start by having another volunteer identify and forward one or more editions to add.

Once you are ready to be added to the feed of submissions, you will need to check for yourself whether an edition has been added. The simplest way to do this is to put the CPDL edition number in the search box and check the results of the search.

Addscore volunteers update this Help page indicating the status of the current backlog. If a score is missing on CPDL but the date of submission predates the date indicated, it likely means that a volunteer evaluated the edition and there was a reason it was not added, such as:

  • duplicate form filled out for an edition covered by an earlier CPDL #;
  • the contributor has been contacted with a question, such as if the score cannot be found;