solution for plagiarism of data

[merera lemessa]

i am graduated student in ethiopian and iam developing web based final project allocation and management for graduated students of my college and how can i avoid duplicated titles while students submit titles for their final project

[gits]

this depends on how you want that to work. if one topic should only be submitted once then you might avoid entries in your database when its present already and give the submitter a hint/message to choose another title (topic) instead. If the topics are in a list where they can choose from - just remove already submitted entries from that list and let only choose those that are still 'free' to be chosen for example.

[rollerbladegirl]

I can see how that might get stressful for students if they have to rename or change things to make them look like you dictate. You could append the entry of duplicated titles with something like "duplicate title." That way you do not force the student to interrupt their thoughts by a requirement that they rename or change something, and they (and others) see clearly that their chosen title is a duplicate and not a forgery of originality. They could change the title later if you give them that option, and go on inputting their current information.

[gits]

the OP didn't give enough information about the use case - so each advice is guesswork so far. If there is a list - then its easy. If the submissions are proposals - then a student should even be able to find a clear title that is not a duplicate of another unless it is in fact a duplicate. That is not interrupting any thoughts - it is more guiding the thoughts. I did work long enough with students at the university and they are grown up adults so there is no need to be a babysitter or build babysitting software. If there is a rule/guideline - this can be (and should be) enforced like it is in real life projects.