| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| history:opw:ui_suggest:micaelaneus [2018/04/25 14:55] – ↷ Page moved from opw:ui_suggest:micaelaneus to history:opw:ui_suggest:micaelaneus dbwells | history:opw:ui_suggest:micaelaneus [2022/02/10 13:34] (current) – external edit 127.0.0.1 |
|---|
| The home page presents us with two unique opportunities: to “shortcut” the user to common functionalities and to seize the chance to “update” them about Evergreen or other relevant topics before they begin working. Currently, the home page takes advantage of only the first. I propose a few changes to the shortcuts (see annotations on the screenshot) and the addition of a dialog box that Evergreen could use to make announcements to users. | The home page presents us with two unique opportunities: to “shortcut” the user to common functionalities and to seize the chance to “update” them about Evergreen or other relevant topics before they begin working. Currently, the home page takes advantage of only the first. I propose a few changes to the shortcuts (see annotations on the screenshot) and the addition of a dialog box that Evergreen could use to make announcements to users. |
| |
| {{:opw:ui_suggest:opw_evergreen_proposal_08s.jpg|}} | {{history:opw:ui_suggest:opw_evergreen_proposal_08s.jpg|}} |
| | |
| === Part 2: Form Design === | === Part 2: Form Design === |
| Bucket View provides a good example of some of the table weaknesses. The headings are truncated and the heading hierarchy is muddled. | Bucket View provides a good example of some of the table weaknesses. The headings are truncated and the heading hierarchy is muddled. |
| |
| {{:opw:ui_suggest:opw_evergreen_proposal_01s.jpg|}} | {{history:opw:ui_suggest:opw_evergreen_proposal_01s.jpg|}} |
| {{:opw:ui_suggest:opw_evergreen_proposal_02s.jpg|}} | {{history:opw:ui_suggest:opw_evergreen_proposal_02s.jpg|}} |
| |
| == Input Forms: == | == Input Forms: == |
| Registration is a common and tedious task in today’s society. How could we expedite the process for librarians and patrons by redesigning the registration form? Using techniques like Address Autocomplete from the zip code and revealing information as needed (e.g., hide Parent/Guardian fields until Juvenile is checked) might reduce completion time significantly. | Registration is a common and tedious task in today’s society. How could we expedite the process for librarians and patrons by redesigning the registration form? Using techniques like Address Autocomplete from the zip code and revealing information as needed (e.g., hide Parent/Guardian fields until Juvenile is checked) might reduce completion time significantly. |
| |
| {{:opw:ui_suggest:opw_evergreen_proposal_05s.jpg|}} | {{history:opw:ui_suggest:opw_evergreen_proposal_05s.jpg|}} |
| |
| == Checkin/out: == | == Checkin/out: == |
| Another frequent activity is checking materials in and out of the system. Without a barcode scanner, I had limited power to explore these forms. Still, I see places where we could eliminate distracting inconsistencies between the forms and prioritize the information displayed that might make this process flow more smoothly. | Another frequent activity is checking materials in and out of the system. Without a barcode scanner, I had limited power to explore these forms. Still, I see places where we could eliminate distracting inconsistencies between the forms and prioritize the information displayed that might make this process flow more smoothly. |
| |
| {{:opw:ui_suggest:opw_evergreen_proposal_03s.jpg|}} | {{history:opw:ui_suggest:opw_evergreen_proposal_03s.jpg|}} |
| {{:opw:ui_suggest:opw_evergreen_proposal_04s.jpg|}} | {{history:opw:ui_suggest:opw_evergreen_proposal_04s.jpg|}} |
| |
| == Search: == | == Search: == |
| The most important-- and tricky!-- design elements would be the search forms. I barely want to comment on these forms until I could do more research and get feedback from librarians. Here, I present my first impressions. | The most important-- and tricky!-- design elements would be the search forms. I barely want to comment on these forms until I could do more research and get feedback from librarians. Here, I present my first impressions. |
| |
| {{:opw:ui_suggest:opw_evergreen_proposal_06s.jpg|}} | {{history:opw:ui_suggest:opw_evergreen_proposal_06s.jpg|}} |
| {{:opw:ui_suggest:opw_evergreen_proposal_07s.jpg|}} | {{history:opw:ui_suggest:opw_evergreen_proposal_07s.jpg|}} |
| |
| === Part 3: Language and Iconography === | === Part 3: Language and Iconography === |
| I propose taking a thoughtful look at how things are labelled within the staff client to ensure clarity and consistency across all views, along with the introduction of some iconography. Icons must be added carefully to ensure accessibility and avoid cluttering up the screen. To that end, I suggest [[http://alistapart.com/article/the-era-of-symbol-fonts|using a symbol or icon font]] judiciously to label basic activities such as registering a new patron. As a supporter of all things open source, I specifically want to investigate [[http://entypo.com|Entypo]] as a leading candidate for Evergreen’s icons. | I propose taking a thoughtful look at how things are labelled within the staff client to ensure clarity and consistency across all views, along with the introduction of some iconography. Icons must be added carefully to ensure accessibility and avoid cluttering up the screen. To that end, I suggest [[http://alistapart.com/article/the-era-of-symbol-fonts|using a symbol or icon font]] judiciously to label basic activities such as registering a new patron. As a supporter of all things open source, I specifically want to investigate [[http://entypo.com|Entypo]] as a leading candidate for Evergreen’s icons. |
| |
| {{:opw:ui_suggest:add_person.jpg|}} | {{history:opw:ui_suggest:add_person.jpg|}} |
| {{:opw:ui_suggest:book.jpg|}} | {{history:opw:ui_suggest:book.jpg|}} |
| {{:opw:ui_suggest:settings.jpg|}} | {{history:opw:ui_suggest:settings.jpg|}} |
| |
| === Part 4: The Style Guide === | === Part 4: The Style Guide === |
