Last modified: 2011-08-30 22:18:11 UTC
Steps to reproduce: 1) Upload a file (say taken from a digital camera) with bad file name (e.g.P7260266) 3) Go to the Describe page and notice that title has been set to the file name (P7260266) There is no indication that title has been directly taken from file name (bad file name) and user has to change that.
I agree that bad filenames like these should be spotted and warned, but should that be core MW or an extension? Certainly this is something for the UploadWizard, though.
It should be a feature of core MW, but we are the only project so far that needs it. Anyway, to my knowledge, the only way to really know whether a filename is acceptable or not is to actually try to publish a file with that name. (There are many different reasons why the server might reject it, and any number of extensions can use certain hooks. We can't simulate it on the client effectively.) This is obviously unacceptable for us, especially since we are working on files that aren't published yet. So we will need to write another API method, or, rewrite the appropriate extensions, to do this properly. The main extensions I'm aware of are TitleBlacklist and TitleWhitelist.
Unassigning default assignments. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/54734
This is resolved with the title blacklist API implementation.