Improve DSpace 7 drag and drop submission

[pilasou]

In MyDspace, a user can submit a new file using the drag and drop zone.

When doing so, he/she is prompt to select a collection :

Once done DSpace is displaying a notification on the top right on the screen.

However, if the user does not clic on the link in the notification to continue editing his/her submission, he/she ends up with an incomplete empty submission in MyDSpace without knowing it.

This feature has the potential to be the most attractive and simple way to submit in DSpace, however, it works differently than the other options to submit in DSpace (which follows an slightly different process: Add Item > Select Collection > Edit submission) and the notification is misleading for the user (green color and check icon make think that the submission has been done).

Describe the solution you'd like The drag and drop submission should align with the other submission process in DSpace.

The drag and drop option should follow a 3 step process:

1. Drag and Drop a file
2. Select collection
3. Edit submission (once the collection has been selected, the Edit Submission page of the collection selected automaticly appears so that the user can continue his/her submission process)

The notification asking for the user to clic to continue the process, is removed.

[alawvt]

I agree that the present notification is potentially misleading.

[tdonohue]

I agree this is a usability issue. I like the solution of sending people directly to the "Edit Submission" page after a successful drag & drop (which should allow us to remove the notification entirely).

Pulling this over to the 7.4 board. Flagging this as high priority as it seems like a common issue.

[nibou230]

Hello @tdonohue, we can drop the notification, but do we want to remove all related translations as well?

'mydspace.general.text-here',
'mydspace.upload.upload-successful'

They are not used anywhere else in the code.

[tdonohue]

@nibou230 : Yes, if i18n keys and translations are no longer used, they can be removed from en.json5 (at a minimum). Translators can then remove them from other language translation files the next time they update the translation.