18F / omb-eregs

A tool to find, read, and maintain White House Office of Management and Budget (OMB) policy requirements

Home Page:https://policy-beta.cio.gov/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

As a policy analyst or contractor, I need to know why my document failed to upload

austinhernandez opened this issue · comments

assumptions

  • A contractor or analyst tries to add a new document to the library, but it was REJECTED.

actions

  • Create wireframes high or low fidelity and/or a task flow for what happens in the case of the system letting me know that their document failed to upload.
  • Document necessary warning messages, error messages, and paths to success
  • Validate flow(s) with teams

Suggestions, things to consider, notes, etc.

  • Related to #849
  • Try to figure out how to incorporate the "status" of a policy (e.g. published, in review, unpublished etc.). This could be a button, dropdown or text, letting a user know if un-publish has been successful.

Text needs to be finalized by @thebestsophist at another time, but here is draft text to let users know the status of the document and what they can do.

Error modal. This document failed to import.

  • Text: This document failed to import.
  • Subtext: [Let the user know what are reasons for fail]
    • Your file is too big. Files can't exceed _xxx_MB, please select another document.
    • Your file has too many pages. File can't exceed more than xxx pages, please select another document.
    • [Bad document] Your file is corrupt or unreadable. Please select another document.

After a successful upload

Error modal. If a user tries to leave the page or save without a document title.

  • Text: You need to give your document a title before you save it.
  • Action: [Focus on the title field with an error message and state.]
    • Please add a title to save this document so you can find it later.

Updated microcopy!

Error modal. This document failed to import.

  • Text: Uh oh. The importing tool had problems with this document,
  • Subtext: [Let the user know what are reasons for fail]
    • The file was too big for the importer to handle. Currently, the importer can’t process files larger than [size]. If you need help getting this document into the library, contact support for help uploading this document while our engineers continue improving the importer.
    • This file is longer than the importer can currently handle. Currently, we can only handle documents up to [xxx] pages long. If you need help getting this document into the library, contact support for help while our engineers continue improving the importer.
    • This document seems to be corrupted or unreadable by the importer. You can try again if you think there was a hiccup in the upload process, otherwise you may want to try a different copy.

After a successful upload

Error modal. If a user tries to leave the page or save without a document title.

Text: Please give this document a title before save and closing.
Action: [Focus on the title field with an error message and state.]
This will help make it easier to find later.

Hey @thebestsophist

Looks like some of the copy is too long. This is what it looks like in the space (sorry for not including mocks earlier.

image

I tried changing the format so it would fit, but we might need a pairing sesh for this:
image

Also, not sure if the error for leaving a page without a document title needs to be a modal. I think it could just focus on the form field with error text. What do you think?
image

I can set up time for a content pair, but let me know how you'd like to do content in the future!

what about this copy for the 3 different states of error states?

image

Quick q: does "The file was unreadable" encompass the user uploading a non-PDF (like an image or a word doc)?

Good call, @rtwell.

Needs content approval from @thebestsophist