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

[Joan Kranich]

Hi,

The patron edit screen looks good.  I like that the options for Save and Save & 
Clone are on the right where staff currently click and also because most staff 
using a mouse use it on the right side.  I'm assuming that if you do not want 
to Save then staff would just click the next function such as Holds.

Thanks.
Joan

Joan Kranich
C/W MARS Member Services
jkran...@cwmars.org
508-755-3323 ext. 21


-Original Message-
From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Kathy 
Lussier
Sent: Tuesday, July 28, 2015 9:40 AM
To: open-ils-general@list.georgialibraries.org
Subject: Re: [OPEN-ILS-GENERAL] Feedback requested on patron editor in web 
client

Hi all,

Thanks to everyone on the feedback you provided for the patron editor. 
I've created a mock-up based on the feedback - 
http://www.screencast.com/t/4lcqzkcxedgN.

The idea is that all of the elements above the Patron Edit heading in this 
interface would remain fixed to the top of the interface. This mock-up displays 
the edit view of the registration/edit form. The tabs that bring you to the 
different areas of the patron record (check out, items out, holds, etc.) would 
be fixed as well, which fits in with the easy access we have to those buttons 
in the existing client.

Although people didn't think it was necessary to keep the display options 
accessible at all times, I put those in the fixed area primarily because it 
made the best use of the space available.

Let me know if you have any feedback on this mock-up!

Kathy

On 07/10/2015 02:21 PM, Jason Etheridge wrote:
> For what it's worth, I've seen mobile web pages that use floating top 
> and bottom bars to good effect.
>

--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

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

[McCanna, Terran]

I like it! 


Terran McCanna 
PINES Program Manager 
Georgia Public Library Service 
1800 Century Place, Suite 150 
Atlanta, GA 30345 
404-235-7138 
tmcca...@georgialibraries.org 
- Original Message -
From: "Kathy Lussier" 
To: open-ils-general@list.georgialibraries.org
Sent: Tuesday, July 28, 2015 9:39:41 AM
Subject: Re: [OPEN-ILS-GENERAL] Feedback requested on patron editor in web 
client

Hi all,

Thanks to everyone on the feedback you provided for the patron editor. 
I've created a mock-up based on the feedback - 
http://www.screencast.com/t/4lcqzkcxedgN.

The idea is that all of the elements above the Patron Edit heading in 
this interface would remain fixed to the top of the interface. This 
mock-up displays the edit view of the registration/edit form. The tabs 
that bring you to the different areas of the patron record (check out, 
items out, holds, etc.) would be fixed as well, which fits in with the 
easy access we have to those buttons in the existing client.

Although people didn't think it was necessary to keep the display 
options accessible at all times, I put those in the fixed area primarily 
because it made the best use of the space available.

Let me know if you have any feedback on this mock-up!

Kathy

On 07/10/2015 02:21 PM, Jason Etheridge wrote:
> For what it's worth, I've seen mobile web pages that use floating top
> and bottom bars to good effect.
>

-- 
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

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

[Jennifer Pringle (Project Sitka)]

Hi Kathy,

We think this looks great and are glad to see the display options  
accessible.  We have multiple libraries that use that functionality on  
a regular basis.


Thanks!

Jennifer





Quoting Kathy Lussier :


Hi all,

Thanks to everyone on the feedback you provided for the patron  
editor. I've created a mock-up based on the feedback -  
http://www.screencast.com/t/4lcqzkcxedgN.


The idea is that all of the elements above the Patron Edit heading  
in this interface would remain fixed to the top of the interface.  
This mock-up displays the edit view of the registration/edit form.  
The tabs that bring you to the different areas of the patron record  
(check out, items out, holds, etc.) would be fixed as well, which  
fits in with the easy access we have to those buttons in the  
existing client.


Although people didn't think it was necessary to keep the display  
options accessible at all times, I put those in the fixed area  
primarily because it made the best use of the space available.


Let me know if you have any feedback on this mock-up!

Kathy

On 07/10/2015 02:21 PM, Jason Etheridge wrote:

For what it's worth, I've seen mobile web pages that use floating top
and bottom bars to good effect.



--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier



--
Jennifer Pringle
Co-op Support
BC Libraries Cooperative
Tel: 1-888-848-9250
Email:jprin...@sitka.bclibraries.ca
Website: http://bc.libraries.coop

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

[Geoffrey Brown]

That looks good - very helpful.

Thanks,
Geoff Brown


-Original Message-
From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Kathy 
Lussier
Sent: Tuesday, July 28, 2015 9:40 AM
To: open-ils-general@list.georgialibraries.org
Subject: Re: [OPEN-ILS-GENERAL] Feedback requested on patron editor in web 
client

Hi all,

Thanks to everyone on the feedback you provided for the patron editor. 
I've created a mock-up based on the feedback - 
http://www.screencast.com/t/4lcqzkcxedgN.

The idea is that all of the elements above the Patron Edit heading in this 
interface would remain fixed to the top of the interface. This mock-up displays 
the edit view of the registration/edit form. The tabs that bring you to the 
different areas of the patron record (check out, items out, holds, etc.) would 
be fixed as well, which fits in with the easy access we have to those buttons 
in the existing client.

Although people didn't think it was necessary to keep the display options 
accessible at all times, I put those in the fixed area primarily because it 
made the best use of the space available.

Let me know if you have any feedback on this mock-up!

Kathy

On 07/10/2015 02:21 PM, Jason Etheridge wrote:
> For what it's worth, I've seen mobile web pages that use floating top 
> and bottom bars to good effect.
>

--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

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

[Kathy Lussier]

Hi all,

Thanks to everyone on the feedback you provided for the patron editor. 
I've created a mock-up based on the feedback - 
http://www.screencast.com/t/4lcqzkcxedgN.


The idea is that all of the elements above the Patron Edit heading in 
this interface would remain fixed to the top of the interface. This 
mock-up displays the edit view of the registration/edit form. The tabs 
that bring you to the different areas of the patron record (check out, 
items out, holds, etc.) would be fixed as well, which fits in with the 
easy access we have to those buttons in the existing client.


Although people didn't think it was necessary to keep the display 
options accessible at all times, I put those in the fixed area primarily 
because it made the best use of the space available.


Let me know if you have any feedback on this mock-up!

Kathy

On 07/10/2015 02:21 PM, Jason Etheridge wrote:

For what it's worth, I've seen mobile web pages that use floating top
and bottom bars to good effect.



--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

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

[Jason Etheridge]

For what it's worth, I've seen mobile web pages that use floating top
and bottom bars to good effect.

-- 
Jason Etheridge
| Community and Migration Manager
| Equinox Software, Inc. / The Open Source Experts
| phone: 1-877-OPEN-ILS (673-6457)
| email: ja...@esilibrary.com
| web: http://www.esilibrary.com

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

[Joan Kranich]

Hi,

My thought too was a Save at the top and bottom however the changes we make 
most frequently are located in the middle of the screen.  I think the floating 
box is fine with an average resolution as shown in the screencast.  It is 
unlikely in our network that staff would be using patron edit on a phone.  I 
know tho that we try to ensure functionality across screen size and resolution.

I am inquiring with front line circulation staff about the use of the options 
to view required, suggested or all fields.  I do not see those options used 
regularly and if they displayed at the top of the patron registration/edit form 
it would be fine.  I'll let you know if circulation staff object.

Joan

Joan Kranich
C/W MARS Member Services
jkran...@cwmars.org
508-755-3323 ext. 21


-Original Message-
From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Kathy 
Lussier
Sent: Thursday, July 9, 2015 4:01 PM
To: 'Evergreen Discussion Group'
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
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

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

[Jason Stephenson]

Quoting Lindsay Stratton :

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.


/Me should read better.

You are correct that it affects both edit and registration, but
other responses in this thread implied that some do not know that
the settings exist.  I thought I'd point that out.

If you'd like separate settings for edit vs. registration, I
suggest opening a bug on Launchpad. It may never actually happen
unless someone funds the development, but at least there will
be a record that someone wants that feature beyond a message in
a mailing list archive.

Launchpad is the formal way to make feature requests known to the
developers and the rest of the community.

Cheers,
Jason
--
Jason Stephenson
Assistant Director for Technology Services
Merrimack Valley Library Consortium
4 High ST, Suite 175
North Andover, MA 01845
Phone: 978-557-5891
Email: jstephen...@mvlc.org

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

[Jason Stephenson]

Quoting Lindsay Stratton :


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.


That exists already. They are organizational unit settings.

--
Jason Stephenson
Assistant Director for Technology Services
Merrimack Valley Library Consortium
4 High ST, Suite 175
North Andover, MA 01845
Phone: 978-557-5891
Email: jstephen...@mvlc.org

Re: [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" 
> To: "Evergreen Discussion Group" 
> 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 

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

[Ruth Frasur]

Just a few notes

1.  I do like the floating save/close&save block.  It does, however, even
now behave funny when the staff client is re-sized.  From what I see in the
web client, it looks like, when the staff client is resized and acting
responsively, the block floats UNDER the fields as opposed to it floating
OVER the fields (and other links like "replace barcode" and "set username"
or whatever they're called - I'm not looking at it this moment).  The
existing behavior can amount to a jumble of links/buttons.  The "under
float" seems like it would alleviate some of this.

2.  We NEVER use the "suggested fields" or "show only required fields."  Of
course, that's our library.  I can't speak to the entire Evergreen Indiana
consortium, but I do imagine that our behavior is common in this regard.

3.  I don't know the technicalities of Angular JS, so I can't really speak
to whether it'd be good to have a sticky top bar from a coding standpoint.
>From a user standpoint, it would.  Personally, I'd like to see that sticky
top bar with the save, and then a save at the end of the form as well.


On Thu, Jul 9, 2015 at 4:00 PM, Kathy Lussier  wrote:

> 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
> kluss...@masslnc.org
> Twitter: http://www.twitter.com/kmlussier
>
>


-- 
Ruth Frasur
Director of the Historic(ally Awesome) Hagerstown - Jefferson Township
Library
10 W. College Street in Hagerstown, Indiana (47346)
p (765) 489-5632; f (765) 489-5808

Our Kickin' Website   Our Rockin' Facebook
Page   and Stuff I've Read

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

[Jessica Venturo]

Hi Kathy,

1) I train people NOT to click the show only suggested field or required
field buttons. Clicking them eliminates some pretty essential fields, in my
opinion. (Daytime phone number, for example).

2) I like the idea of having the button at the top and bottom of the form.
Is there any possibility of adding a "Back to Top" and/or "Scroll to
Bottom" link in the section headers (the green bars that label "User
Settings," "Address," and Statistical Categories") for those who may find
themselves in the middle of the form?

Jessica

On Thu, Jul 9, 2015 at 4:38 PM, Kathy Lussier  wrote:

> Sorry folks! I made the screencast public so that you all can actually
> view it.
>
> Kathy
>
>
> On 07/09/2015 04:26 PM, McCanna, Terran wrote:
>
>> Hi Kathy,
>>
>> I'm unable to open your Google link (permission error), but I got a peek
>> at Bill's work a month or so ago and it looked great and it responded very
>> quickly. I know he's made some changes since I saw it last, though, so my
>> comments are based on memory.
>>
>> 1) In my experience, very few people ever use the view required,
>> suggested or all fields links, and for those people that do, I think having
>> those options at the top would be appropriate.
>>
>> 2) I don't mind the floating Save and Save/Clone buttons except when they
>> overlap other page elements. I also wouldn't mind having them at the bottom
>> of the form - I understand the point about keeping scrolling to a minimum,
>> but I also like the idea of encouraging staff to review the entire form for
>> errors/incomplete information each time it is updated. I wouldn't want the
>> buttons at the top unless they stuck on screen when the screen was scrolled
>> down. This would be a different approach from any of the other screens, but
>> the floating box is already a different approach than the other screens.
>>
>> Also - what about the alerts that appear under the Save button if there
>> are matching patron names/addresses? Those tend to overlap on a small
>> resolution monitor in the current client too (not sure if Bill was able to
>> find a better way to display those already).
>>
>>
>> Terran McCanna
>> PINES Program Manager
>> Georgia Public Library Service
>> 1800 Century Place, Suite 150
>> Atlanta, GA 30345
>> 404-235-7138
>> tmcca...@georgialibraries.org
>> - Original Message -
>> From: "Kathy Lussier" 
>> To: "Evergreen Discussion Group" <
>> open-ils-general@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 

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

[McCanna, Terran]

Thanks Kathy!

The only thing I would add to my earlier comments is that if the floating box 
stays, it should float on top of everything else, and not run behind.


Terran McCanna 
PINES Program Manager 
Georgia Public Library Service 
1800 Century Place, Suite 150 
Atlanta, GA 30345 
404-235-7138 
tmcca...@georgialibraries.org 
- Original Message -
From: "Kathy Lussier" 
To: open-ils-general@list.georgialibraries.org
Sent: Thursday, July 9, 2015 4:38:43 PM
Subject: Re: [OPEN-ILS-GENERAL] Feedback requested on patron editor in web 
client

Sorry folks! I made the screencast public so that you all can actually 
view it.

Kathy

On 07/09/2015 04:26 PM, McCanna, Terran wrote:
> Hi Kathy,
>
> I'm unable to open your Google link (permission error), but I got a peek at 
> Bill's work a month or so ago and it looked great and it responded very 
> quickly. I know he's made some changes since I saw it last, though, so my 
> comments are based on memory.
>
> 1) In my experience, very few people ever use the view required, suggested or 
> all fields links, and for those people that do, I think having those options 
> at the top would be appropriate.
>
> 2) I don't mind the floating Save and Save/Clone buttons except when they 
> overlap other page elements. I also wouldn't mind having them at the bottom 
> of the form - I understand the point about keeping scrolling to a minimum, 
> but I also like the idea of encouraging staff to review the entire form for 
> errors/incomplete information each time it is updated. I wouldn't want the 
> buttons at the top unless they stuck on screen when the screen was scrolled 
> down. This would be a different approach from any of the other screens, but 
> the floating box is already a different approach than the other screens.
>
> Also - what about the alerts that appear under the Save button if there are 
> matching patron names/addresses? Those tend to overlap on a small resolution 
> monitor in the current client too (not sure if Bill was able to find a better 
> way to display those already).
>
>
> Terran McCanna
> PINES Program Manager
> Georgia Public Library Service
> 1800 Century Place, Suite 150
> Atlanta, GA 30345
> 404-235-7138
> tmcca...@georgialibraries.org
> ----- Original Message -
> From: "Kathy Lussier" 
> To: "Evergreen Discussion Group" 
> 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 differe

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

[Kathy Lussier]

Thanks Terran!



On 07/09/2015 04:26 PM, McCanna, Terran wrote:

Hi Kathy,

I'm unable to open your Google link (permission error), but I got a peek at 
Bill's work a month or so ago and it looked great and it responded very 
quickly. I know he's made some changes since I saw it last, though, so my 
comments are based on memory.

1) In my experience, very few people ever use the view required, suggested or 
all fields links, and for those people that do, I think having those options at 
the top would be appropriate.

Good to know.



2) I don't mind the floating Save and Save/Clone buttons except when they 
overlap other page elements. I also wouldn't mind having them at the bottom of 
the form - I understand the point about keeping scrolling to a minimum, but I 
also like the idea of encouraging staff to review the entire form for 
errors/incomplete information each time it is updated. I wouldn't want the 
buttons at the top unless they stuck on screen when the screen was scrolled 
down. This would be a different approach from any of the other screens, but the 
floating box is already a different approach than the other screens.


FWIW, I think the only form we have in the web client so far that we 
could use as an example for an approach is the place holds form, which 
really is a form for the catalog, but is also used in the client. My 
first step was to see if there were precedents we should be following. 
:) But I could be overlooking something.





Also - what about the alerts that appear under the Save button if there are 
matching patron names/addresses? Those tend to overlap on a small resolution 
monitor in the current client too (not sure if Bill was able to find a better 
way to display those already).
We haven't gotten to that phase of the project yet, but I'll keep it in 
mind for when it comes up.


Thanks!
Kathy




Terran McCanna
PINES Program Manager
Georgia Public Library Service
1800 Century Place, Suite 150
Atlanta, GA 30345
404-235-7138
tmcca...@georgialibraries.org
- Original Message -
From: "Kathy Lussier" 
To: "Evergreen Discussion Group" 
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_i

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

[Benjamin Kalish]

- Yes, I think these buttons should have fixed position so that they don't
scroll with the form.
- I would much rather have these buttons in a horizontal bar at the top or
the bottom of the edit screen then in the box on the right.
- Whatever geometry is used, the box should have an opaque background. (In
the screencast it was transparent, which is what made it hard to read when
it overlapped other content.)

Benjamin Kalish
Forbes Library / 413-587-1012 / bkal...@forbeslibrary.org

Currently reading: *Babel-17* by Samuel R. Delany
Just Finished: *Frederica  *by Georgette Heyer

On Thu, Jul 9, 2015 at 4:00 PM, Kathy Lussier  wrote:

> 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
> kluss...@masslnc.org
> Twitter: http://www.twitter.com/kmlussier
>
>

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

[Geoff Sams]

For NTLC, I can pretty much say the same thing.  

1) Most of us don't use the view options, and those that do will be fine with 
it being at the top of the page.  

2) Most of our workflows end at the very bottom of the form anyway, and so the 
save options at the bottom would be perfectly fine.

+1 to this suggestion.

Thanks,
Geoff Sams
Library Manager
Roanoke Public Library

-Original Message-
From: Open-ils-general 
[mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of 
McCanna, Terran
Sent: Thursday, July 09, 2015 3:27 PM
To: Evergreen Discussion Group
Subject: Re: [OPEN-ILS-GENERAL] Feedback requested on patron editor in web 
client

Hi Kathy, 

I'm unable to open your Google link (permission error), but I got a peek at 
Bill's work a month or so ago and it looked great and it responded very 
quickly. I know he's made some changes since I saw it last, though, so my 
comments are based on memory.

1) In my experience, very few people ever use the view required, suggested or 
all fields links, and for those people that do, I think having those options at 
the top would be appropriate.

2) I don't mind the floating Save and Save/Clone buttons except when they 
overlap other page elements. I also wouldn't mind having them at the bottom of 
the form - I understand the point about keeping scrolling to a minimum, but I 
also like the idea of encouraging staff to review the entire form for 
errors/incomplete information each time it is updated. I wouldn't want the 
buttons at the top unless they stuck on screen when the screen was scrolled 
down. This would be a different approach from any of the other screens, but the 
floating box is already a different approach than the other screens. 

Also - what about the alerts that appear under the Save button if there are 
matching patron names/addresses? Those tend to overlap on a small resolution 
monitor in the current client too (not sure if Bill was able to find a better 
way to display those already). 


Terran McCanna
PINES Program Manager
Georgia Public Library Service
1800 Century Place, Suite 150
Atlanta, GA 30345
404-235-7138
tmcca...@georgialibraries.org
- Original Message -
From: "Kathy Lussier" 
To: "Evergreen Discussion Group" 
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

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

[Kathy Lussier]

Sorry folks! I made the screencast public so that you all can actually 
view it.


Kathy

On 07/09/2015 04:26 PM, McCanna, Terran wrote:

Hi Kathy,

I'm unable to open your Google link (permission error), but I got a peek at 
Bill's work a month or so ago and it looked great and it responded very 
quickly. I know he's made some changes since I saw it last, though, so my 
comments are based on memory.

1) In my experience, very few people ever use the view required, suggested or 
all fields links, and for those people that do, I think having those options at 
the top would be appropriate.

2) I don't mind the floating Save and Save/Clone buttons except when they 
overlap other page elements. I also wouldn't mind having them at the bottom of 
the form - I understand the point about keeping scrolling to a minimum, but I 
also like the idea of encouraging staff to review the entire form for 
errors/incomplete information each time it is updated. I wouldn't want the 
buttons at the top unless they stuck on screen when the screen was scrolled 
down. This would be a different approach from any of the other screens, but the 
floating box is already a different approach than the other screens.

Also - what about the alerts that appear under the Save button if there are 
matching patron names/addresses? Those tend to overlap on a small resolution 
monitor in the current client too (not sure if Bill was able to find a better 
way to display those already).


Terran McCanna
PINES Program Manager
Georgia Public Library Service
1800 Century Place, Suite 150
Atlanta, GA 30345
404-235-7138
tmcca...@georgialibraries.org
- Original Message -
From: "Kathy Lussier" 
To: "Evergreen Discussion Group" 
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 yo

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

[McCanna, Terran]

Hi Kathy, 

I'm unable to open your Google link (permission error), but I got a peek at 
Bill's work a month or so ago and it looked great and it responded very 
quickly. I know he's made some changes since I saw it last, though, so my 
comments are based on memory.

1) In my experience, very few people ever use the view required, suggested or 
all fields links, and for those people that do, I think having those options at 
the top would be appropriate.

2) I don't mind the floating Save and Save/Clone buttons except when they 
overlap other page elements. I also wouldn't mind having them at the bottom of 
the form - I understand the point about keeping scrolling to a minimum, but I 
also like the idea of encouraging staff to review the entire form for 
errors/incomplete information each time it is updated. I wouldn't want the 
buttons at the top unless they stuck on screen when the screen was scrolled 
down. This would be a different approach from any of the other screens, but the 
floating box is already a different approach than the other screens. 

Also - what about the alerts that appear under the Save button if there are 
matching patron names/addresses? Those tend to overlap on a small resolution 
monitor in the current client too (not sure if Bill was able to find a better 
way to display those already). 


Terran McCanna 
PINES Program Manager 
Georgia Public Library Service 
1800 Century Place, Suite 150 
Atlanta, GA 30345 
404-235-7138 
tmcca...@georgialibraries.org 
- Original Message -
From: "Kathy Lussier" 
To: "Evergreen Discussion Group" 
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 
optio

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

[Kathy Lussier]

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
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier