Wouldn't it make sense for CCs to be able to delete videos that are no longer available and replace with a new one? It looks like they can only add a new video if there is no video already added.
I'll add this to the list of accesses we could possibly be giving in a second phase of the project.
Some feedback thus far. My original suggestion:
a) Revising public comments. Personally, this would mostly be noting that a performance is live rather than studio, noting where a subsequent studio recording was released, deleting relic comments. noting that a performance is mostly instrumental (when technically considered vocal by site rules), etc.
b) Flagging performances as instrumentals when incorrectly coded as vocal.
c) Adding missing cover art.
d) Indexing performances to additional releases when both are already on site, e.g. when a performance is first released as a single but the related album or a compilation is already on site.
e) The ability to read (but not necessarily write on) editor discussion forums. There have been several instances when an editor has sent me a link to some thread that I could not access.
Powers that were added thus far:
a) Add missing information to artists: Identify as person or member, visual, birth date, death date, home country, and free biography details.
b) View editor notes for all database objects. These notes contain research-related information by the editors.
c) View attachments for all database objects. For example, in the case of releases you will often find the back cover scan.
d) View and post in the editor boards.
So far, the only new database object related power exercised is adding missing artist images and bios. I don't see why adding is any riskier than revising. At first I didn't have access to the birth date, etc. fields, tho I think some but not all are available now for populating.
Access to editors' notes and attachments has been helpful in better documenting errors and avoiding unnecessary error reports.
Access to the editor boards does allow one to see the proverbial sausage being made, rather than waiting for a status on suggestions, etc. posted on the public boards.
Not being able to revise/add performance comments remains an irritant. Live vs. studio and mostly instrumental are important notes for me, so I assume they would be to others. Nevertheless, such suggestions are not error report worthy.
Correcting vocal vs. instrumentals results in a relatively high number of error reports, which I'm sure irritates the editors. Ditto for missing cover art.
Multi-indexing also remains something of interest to me, yet I acknowledge that subjective discretion and different editor preferences play a strong role here. I have some ideas for this area and may post a related site suggestion.
In short, adding missing artist images/bios and avoiding some error reports are the only things that is relieving some editor burdens, and these are rather few.
I definitely agree with VV at least on the issue of changing performances to instrumentals. I am sure that there remain a lot of this type of error on SHS because distinguishing instrumentals and vocals was not something that we systematically did for the first several years of the database's life. Moreover, it is very easy just to miss checking the instrumental box when new performances are added. Speaking for myself, I am an editor who gets exasperated having to deal with error reports that merely state a particular performance is an instrumental.
That looks like it's just something someone typed into the generic "Comments" field, which isn't available to us because it's already been populated.
That someone is me; since I didn't have access to the "Real Name" field, I put it there. Since I've added a comment, it is now locked to CCs, since we can't revise.
Dear Certified Contributors,
We have generated a few queries that give you a direct view at which entries you can update. They are available in the Explore section, under "Missing Information".
Hoping this is useful for you! Thanks in advance for any entry updated
Feel free to comment, or to reply with a simple "Read" to remove the reply request.
Last edit: 2018-01-30 19:37:44 UTC by Bastien