confused why some soundtrack additions were declined

Thank you Fran!  I didn't realize the people who wrote the lyrics vs. the music should not be distinguished.  I will refrain from doing so in the future.  I did on some other submissions today before I saw your response, but I think whoever approved them fixed that for me.

I have read the Soundtracks help article before, and looked through it again today, and I don't see where it says not to do this (although it certainly doesn't say TO do it), and I also don't see where it addresses how to deal with songs whose composers are unknown.  It addresses where performers are unknown, but not composers.  Perhaps that should be added to the help article.

If I'm understanding correctly, you're saying to simply omit the "written by" line if the composer is unknown, correct?  I will do so in the future.  I had included it before because the way I read the help I thought it was required.

Correct, you can add the information that you know and if you find out later more about it, you can always submit corrections and add the missing data to the contributions. 

I have more soundtrack additions/changes that were declined, and these are even more confusing, because I cannot find anything wrong with them.

FYI I figured out precisely how the lowercasing happened.  I incorrectly entered it this way:

"Song"

Written by: composer

Performed by: singer

The incorrect part is including the colon.  So on checking the updates, IMDb removed the colon and told me so, but for some reason also lowercased the first letter.  If the lowercase leads to a declined submission, the code should be changed to simply remove the colon and not lowercase the first letter.

Here is the message that gets printed when you do this:

• 'Written by:' has been replaced with 'written by' in accordance with IMDb rules.
• 'Performed by:' has been replaced with 'performed by' in accordance with IMDb rules.

@jbmorris​ Hi-

Thank you for posting the submission references! Further checking these other ones:

1. 250208-212256-797000: apart from the caps, some also had the (lyrics) and (music) as well which were mentioned by Fran above. However, it has been re-submitted on your behalf and approved, the corrections have already been applied. 
2. 250208-212459-225000 & 250208-195858-056000: for the corrections submission, this was a processing error. It has been re-submitted on your behalf and now approved.

The changes will be live on the site shortly.

Cheers!

Thank you Maya!  Right, that was submitted before the (lyrics) and (music) reply above, thus why it still had that.  Sorry about that, but I know not to do that in the future.  I had expected them to just remove those annotations before approving it.  Thank you for taking care of that and for resubmitting the other one as well!

@jbmorris​ Your welcome! No worries, glad we can help!

Maya - item #2 (250208-212459-225000) which you resubmitted yesterday came across as #250211-174227-277000 but for some reason it was just declined again.  Another processing error?  I don't quite understand why this would happen, and twice to the same update, when it's a very straightforward update of just noting that things were not listed in the credits.  This time it didn't even say why:

Reason Other

Your contribution has been declined.We did not capture a specific reason during processing.

@jbmorris​ Hi-

There were some issues with the submission yesterday after re-submitting, however, was now able to make the respective corrections for you.

Cheers!

Thank you, looks like my submission still shows Declined, but the edits are there since I think you're saying you just manually updated.  Thank you!  Was the problem with my submission (which you resubmitted) something on my end or on the other end?  Looking at it, I don't see any issues, although confusingly when you look at history on these things it omits the end of line characters, even though they correctly come across on the page itself.  Was the problem something to do with that?

@jbmorris​ Your welcome! No worries, the technical issue was on our end.