-
Notifications
You must be signed in to change notification settings - Fork 492
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #8271 from IQSS/8096-8205-ingest-messaging
improve messaging for ingest failures, file upload #8096
- Loading branch information
Showing
12 changed files
with
144 additions
and
31 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
Ingest and file upload messaging improvements | ||
|
||
On the pages for adding files on create or edit | ||
|
||
- Explain that all types are supported, link to tabular ingest guides | ||
- Show max files per upload #7227 | ||
- Show global tabular ingest limit | ||
- Show per format tabular ingest limits | ||
- Move messaging from blue info block to regular text. | ||
|
||
Failed ingest messaging | ||
|
||
- Calm blue message that files are available in original format only | ||
- Click for a popup about ingest and specifics of why ingest failed | ||
|
||
Email notification for ingest success | ||
|
||
- Link to tabular ingest guides | ||
- Don't show the files that were just ingested | ||
|
||
Email notification for ingest failure | ||
|
||
- Link to tabular ingest guides | ||
- Say "incomplete" instead of "error" | ||
|
||
Email notification for mix of ingest success and failure | ||
|
||
- Looks just like the email for failure, no mention of files that had success | ||
|
||
In-app notification for ingest success | ||
|
||
- Reworded and links to guides | ||
|
||
In-app notification for ingest failure | ||
|
||
- Reworded and links to guides |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.