UX: User Page Layout with Many Fields

Description

Purpose: We are updating the user record with approximately 50 data elements. Some of these have already been implemented and can be seen in http://folio-demo-test.aws.indexdata.com/

Acceptance Criteria:

  • Review the current state of the user record (Create, Edit and View modes) in FOLIO (http://folio-demo-test.aws.indexdata.com/) and make suggested changes to user metadata layout so that the record feels organized and tidy

  • A couple of specific requests for attention:

    • The FOLIO ID for the user record appears editable in the create/edit modes when, in fact, it is read-only). NOTE: The SIG has also asked that we don't display this so prominently. Perhaps it is truncated and you hover over to see or copy the whole thing. Or maybe it's an icon you click to view/copy the ID.

    • The Open Date and Record Last Updated fields should be treated differently than the others. This is standard metadata that will display on many record types in FOLIO. It should not just be mixed in with the other metadata. There is another user story for consideration of these specific fields: UX-39

  • When making recommendations, please keep in mind that additional fields are going to be added to the record - ideally your mock-ups should include all the data elements in this document

  • Also, can we create designs that show what this page would look like with and without a profile picture displaying? Many orgs will not have profile pics available and we don't want the big grey box showing.

Scope- The scope of this story is _just _the user metadata, not the search and results panels, not other sections in the form such Fees and fines or Permissions. Section controls are out of scope etc. We really just want to focus on the user metadata display in create,edit and view modes. See attached screenshots for in-scope elements.

Additional info: Per Filip, Benny (FOLIO UX designer) is leaning towards a "16 column layout" for forms: https://dribbble.com/shots/3422987-Grid-Progression

Environment

None

Potential Workaround

None

Attachments

3

Checklist

hide

TestRail: Results

Activity

Show:

Cate Boerema October 24, 2017 at 3:33 PM

Got it. Thank you!!

Kimie Kester October 24, 2017 at 3:27 PM
Edited

I updated it a few days ago so I think it can be marked as DONE
https://drive.google.com/drive/folders/0B18Bhhmr94zaSWdHckJ2WDExUUE

Cate Boerema October 24, 2017 at 3:23 PM

Oops. I was just going to close this (in fact I did) when I realized you were still making that one tweak to the arrow direction for the user metadata section. So I reopened it and put in in progress.

Kimie Kester October 21, 2017 at 7:38 PM

Hi . It's not intentional. Just an oversight on my part. I will correct. Thanks!

Cate Boerema October 21, 2017 at 12:42 PM

Hi Kimie. I just noticed that the mechanism for expanding/collapsing the record last updated metadata is the same as the one used for the other sections but it seems to work in the opposite way (arrow down means section is open as opposed to closed). Was this intentional?

Done

Details

Assignee

Reporter

Priority

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created February 13, 2017 at 9:58 AM
Updated October 24, 2017 at 3:33 PM
Resolved October 24, 2017 at 3:33 PM
TestRail: Cases
TestRail: Runs