[OPEN-ILS-GENERAL] Feedback requested on patron editor in web client

[Lindsay Stratton]

1) Show All/Suggested/Required/etc 
These only make sense if the settings controlling required and displayed fields behaved differently between Patron Registration and Patron Edit. There are fields in the edit form that do not make sense at the point of new record creation - active, barred, claims returned count, etc. - that serve only to make a long form longer. However, those fields are necessary to the patron edit form, which should display all by default. 

I would LOVE to see the ability to define required and displayed fields for patron registration on a field by field basis, and have that effect only patron registration. 

2) Floating Save/Clone box 
Our front line staff like the floating save box, particularly in Patron Edit - it makes it easier to save when editing something in the middle of the form. If, as someone else suggested, the floating box in the web client could have a solid background and float over the fields, that could resolve the overlap issue. 

I think the suggestion of a sticky save / options bar at the top also makes a lot more sense, and seems like it would be better in terms of responsive design and clarity. Also, that behavior is similar to other applications, like email. 

Lindsay Stratton 
Library Automation Services Manager 
Pioneer Library System 
2557 State Rte 21 
Canandaigua, NY 14424 
585-394-8260 x104 

> From: "Kathy Lussier" <klussier at masslnc.org>
> To: "Evergreen Discussion Group" <open-ils-general at list.georgialibraries.org>
> Sent: Thursday, July 9, 2015 4:00:44 PM
> Subject: [OPEN-ILS-GENERAL] Feedback requested on patron editor in web client

> Hi all,

> MassLNC has been working with Bill Erickson on a project to move the
> patron editor to AngularJS. As with the other pieces of the web client
> project, we are looking at maintaining feature parity with the old client.

> Bill has begun the work and has created a semi-functional wireframe to
> demonstrate the layout of the form. The wireframe brings up one area
> where an element that worked well in the xul client may not work so well
> in the web client.

> In the xul client, we have a floating box to the right of the form where
> the Save and Save & Clone buttons are available as well as the options
> to show required, suggested or all fields. The floating box follows you
> along as you scroll up and down the form so that the Save buttons are
> always in easy reach.

> The same thing happens in the new Angularized editor, but I'm not sure
> it works as well in the web client. I think it might be a good time to
> consider whether the way we handled this in the old client is the way we
> should handle it in the web client or if there are other ways we might
> be able to provide these options.

> I have a screencast showing the current version of the new patron
> editor.
> https://drive.google.com/file/d/0B74gDMUDwDXqM3NjbTZfRjY3RW8/view?usp=drivesdk

> At a typical screen resolution, the box with the save options travels
> with you without much trouble, although it does get a little awkward
> when you're scrolling over the separators with the green background. If
> you reduce the screen resolution, we do see a problem where the Save
> area overlaps with the input boxes. I don't know how much of a problem
> this will be since it seems to work fine at resolutions used by
> desktops, laptops, and tablets. However, it could be problematic at
> resolutions used on phones.

> I have a couple of questions:

> 1. Although I strongly believe the Save and the Save & Clone buttons
> should be in easy reach of the user at any location in the patron
> registration form, I'm not so sure that the options to view required,
> suggested or all fields needs to be there. What do you all think? Are
> those options that you are likely to click when you are at different
> places in the form? Or is it something you set as soon as you load the
> form? If it's the latter, I think the top of the patron registration
> form might be a nice location for them.

> 2. Is the floating box the best location for the Save and Save & Clone
> buttons or is there some other way we can keep these options in easy
> reach. When we first started working on this project, I looked at the
> mockup Julia Lima worked on for the Evergreen UI Style Guide project as
> a reference.
> http://media.tumblr.com/69beec7802a938b889bdfa80c7e0d54b/tumblr_inline_nkn0okinXl1t572gy.png

> She had placed the "Save" button along the top bar, but I could only see
> that working if the top navigation bar in the web client stuck to the
> top of the screen. We could certainly place the Save buttons at both the
> top and bottom of the screens, but the form is long enough that I could
> see cases where you would be in the middle of the form when you hit your
> save point.

> Any ideas on how we might be able to offer easy access to these Save
> options in a different way?

> Thanks in advance!
> Kathy

> Kathy Lussier
> Project Coordinator
> Massachusetts Library Network Cooperative
> (508) 343-0128
> klussier at masslnc.org
> Twitter: http://www.twitter.com/kmlussier
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20150710/438c0eb4/attachment.html>