You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the Uploader completes putting the TAR file together, packaging the metadata, and calls the Ingest API.
It then pops up the Status Tool with the Data Asset ID and provides the message. Two things are an issue:
the message is confusing.
the interconnection can timeout. Both confuse the person doing the upload.
Here's the proposed solution
Open up a new tab that has an informative message, but not a communication link, just a message
Message elements - or something similar
"You completed the submission of instrument data to the MyEMSL data repository'
"The upload was 'XXX' big and should take approximately "mmmm' minutes to be placed in the archive
"Here is a link to verify that your update has been completed" URL of the Status Tool with the data asset ID
If the link doesn't provide results after - {mmmm-to-upload)*2, then please notify the Operations & Support group via this link - - URL for Service ticket.
This gets rid of the communication link
It keeps them from re-uploading data once they get the message.
It allows the Ops team to be aware of any upload issues quickly
The text was updated successfully, but these errors were encountered:
@kauberry I like where this is going so far. It was much clearer in the version i deployed for datahub. My only issue with the current wording is it is MyEMSL specific and should be a tad more generic ideally, at least until we can get a new set of UI tools in order. Much appreciated!
Right now the Uploader completes putting the TAR file together, packaging the metadata, and calls the Ingest API.
It then pops up the Status Tool with the Data Asset ID and provides the message. Two things are an issue:
Here's the proposed solution
This gets rid of the communication link
It keeps them from re-uploading data once they get the message.
It allows the Ops team to be aware of any upload issues quickly
The text was updated successfully, but these errors were encountered: