Skip to content

Content and Actions Model

Jump to bottom
Dazza Greenwood edited this page Jun 20, 2017 · 29 revisions

Content Model for Core Use Actions and Functions

**Note: Mentions of "list" could be displayed as "table" or in other display visual design.

  • Probably best to mock out default file list (or table) view plage then the pages for view of individual docs (PDF) and last the page for individual attestations and claims (will be content from JSON objects). After all this is stable the profile page is nice to have but not needed.
  • Tricky UX challenges to focus on is the "sign" action (we must be sure the user is shown a notice that they are now signing a legal doc and to be sure they have reviewed the terms and want to sign it). This happens after they select the doc to be signed and when they are viewing the doc itself and can take the action to sign that doc. Sign mode is different from "view" mode for a doc. In sign mode the user can take an action (like click green "sign" button) to legally sign with digital signature.
  • Also tricky (less) is to type the emails of others to sign and send to them. Nice to have but not requires is to indicate the sequence they need to sign if that matters.
  • Also tricky is how best to display that attestations or claims have been verified. Need to be able to click back to the entity that verified the claim (eg the employer that verified claims or the Credit Union that verified deposits in checking account). User can have more than one verified claim for employment (eg for last employment in past and other claim for current employment)
  • For file list, we need columns that can be "sorted" for "file name" "verified" "document" "attestation" "date uploaded" "date signed" (maybe filters too)

Use Case

See: https://github.com/mitmedialab/CoreID/blob/master/CreditUnionUseCase.md

Key Pages

File List

This would be the default page for app

Let's try including the following for a start, to see how it all works at the point in time a user has some content in their app:

For PDF documents, list:

  • Mortgage Application (signed)
  • Promissory Note (unsigned)
  • Membership Agreement (signed)

For Attestations and Claims, list:

  • Verification of Employment
  • Verification of Deposits
  • FICO Score
  • Home Address
  • Ship-To Address
  • Primary Email
  • Mobile Phone
  • Blockchain Digital Signature Key

In the Context of a Table View

While there are many other ways to display a batch of files than in a table view, here is an example of the type of information we'd expect to see:

Here is an example for Ship-To Address

File Name: Ship-To Address Document: No Attestation: Yes Date Added: March 7, 2016 Date signed: March 19, 2016 Verified: Self-Asserted

Here is an example for Home Address

File Name: Home Address Document: No Attestation: Yes Date Added: February 2, 2016 Date signed: February 10, 2016 Verified: Yes

File Name: Promissory Note Document: Yes Attestation: No Date Added: April 22, 2017 Date signed: Unsigned Verified: No

Note that "ship-to" address is self-asserted and "home address" is a "verified claim". In this demo, the home address is verified by the CU as the mailing address of a depository account holder in compliance with KYC rules.

Individual (not list) Document View

Individual (not list) Attestations and Claims List View

  • When a use clicks a attestation or claim file name from the list of files the next page they see is this page.

Profile

User Profile info page (lowest priority)

Files

Documents List View Page

  • Lists current PDF documents (would be other doc types in future)
  • Any requests for signatures on files should be conspicuous and the user should be able to say "don't show notice or alert to sign this again" sort of thing but the file should still carry the "state" of "signature requested".

View Individual Doc Page

Attestations and Claims

Would be list of files like this:

  • Verification of Employment
  • Verification of Deposits
  • Verification of Insurance
  • FICO Score
  • Home Address
  • Ship-To Address
  • Primary Email
  • Mobile Phone
  • Blockchain Digital Signature Key

When user inspects any one of these pages they will see content as described here for each item listed above and other: https://github.com/alexfigtree/CoreID/wiki/Potential-Claims-and-Attribut

View Individual Attestation or Claim Page

Actions

Upload a File

  • This should be a file chooser.

Sign a File

  • The user can 1 select a file to sign from the file list (and also perhaps from the file view directly if we wish) and 2 take an action to "sign the file".
  • The above action should display the file to use for the to inspect and provide a "sign" action if/when they are ready to execute their digital signature on that file.
  • The result of the signature function changes the "state" of the file in the file list from unsigned to signed by the user.

Share File

  • This requires selection of a file and use takes action to share file.
  • When above happens the user should be presented a type-in filed to identify the other user with whom to share the file. This would presumably email or otherwise transmit the file.

Make Request Signature on File

  • This requires selection of a file and use takes action to sign file.
  • When above happens the user should be presented a input field to identify the other user to whom a request for signature is to be transmitted. This will be an email for our demo and could be a name.id, CU Member ID or public key or other identifier in future.

Receive Request for Signature on File

This is a "notice" action that requires only that the user has seen the information on screen that they have a received a request to sign a file.

  • This action is another way for a file to be added to the users file store (a PDF for example from external user)
  • The notice should include a method (like a thing to click) for the user to 1 see the file they are requested to sign (it should appear in a doc list too) and 2 be able to sign it if they so choose.
Clone this wiki locally