Chris Maurer - 11-May-2007 11:59 This is a Resources thing and not an OSP thing.

Jim Eng - 11-May-2007 12:20 This duplicates at least one earlier ticket identifying the same issue in earlier versions of Sakai. The decision has been "won't fix" because the complexities are too great. Maybe we can find a better answer now, based on careful analysis of user intentions. We have a browser-side script that provides a seed value for a possible display name. In most browsers, the script then puts the cursor in the display name input element and selects the seed value, making it easy for the user to reject the proposed seed value. A seed value is supplied based on the file that has been selected for upload, but the script only runs if there's not already a value in the display name field. If there's already a value in the display name field, can we tell anything about the user's intentions? In the scenario described here, the user intention seems obvious. The user would like to have the display name correspond to the file they are uploading. But can we be sure that's what is happening in all cases or even most cases? Suppose a user types in a display name and then selects a file. Should we wipe out what the user has typed in and replace it with the seed value? Is that very likely? There may be some additional possibilities. Suppose the user selects "~/folder1/file1" and the seed value "file1" is placed in the display-name field. Suppose the user then browses again and selects "~/folder1/file2". We would put "file2" in the display name field and put a link next to that field labeled "Keep 'file1' as display name". And we could also put the cursor in the field and select the text to make it easy for the user to supply a different display name. That seems like it may be adding complexity to the interface. I think this is a real problem, and I'm hoping Harriet might have a suggestion.

Harriet Truscott - 18-May-2007 03:55 Discussion in the resources group meeting suggested the following major scenarios: User uploads file, alters display name to reflect the use of that file, realises that the file was the wrong one, picks the correct file. User wishes display name to remain. User uploads file, leaves seed display name, realises that the file is the wrong one, picks the correct file. User wishes display name to be updated with name of correct file. Ideally, the interface would know whether the display name had been altered from the seed value. If it had been altered by the user, changing the file would not alter the display name. If it had not been altered, changing the file would alter the seed value.

Peter A. Knoop - 30-Sep-2008 06:37 Jim, has there been any progress on addressing this bug, or is it indeed too complex, as you cite above, and should be closed as Won't Fix?