[UX-219] UX: Mockups for Adding Service Point Assignment to Location Record and Marking One Primary Created: 27/Sep/18  Updated: 02/Oct/18  Resolved: 02/Oct/18

Status: Closed
Project: User Experience Design
Components: None
Affects versions: None
Fix versions: None

Type: Story Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Kimie Kester
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File screenshot-1.png    
Issue links:
Blocks
blocks UIORG-110 Settings for Location: primary servic... Closed
blocks UIORG-115 Move SP to Location Relationship Esta... Closed
Sprint:

 Description   
  • We now want to support selection of a service point on the location record (see UIORG-115 Closed )
  • So we need a mockup for that AND the mockup for making one of the assigned service points "primary" is going to have to change accordingly (see UIORG-110 Closed for original mockups)
  • We might just want to combine these stories, but we can do that after the mockups come back
  • Kimie, UIORG-115 Closed contains some UX details that are flexible. If you want things to work differently, please just mock it up and I'll adjust the story accordinly.


 Comments   
Comment by Kimie Kester [ 27/Sep/18 ]

Hi Cate Boerema, So for this one part related to Settings > Organization > Service points, is it possible that a user could get to the service point View or Edit mode screens and see either of these scenarios:

  • Under Assigned locations, it says, No locations found
  • Under Assigned locations, you could have some locations, but they are read only on both View and Edit modes and one of them will say "primary" in parens

Take a look at these to see what I mean:
https://drive.google.com/open?id=1eNfARcbiDeL-PaY8IPJZu-HRl9Dp9mm8
Thanks!

Comment by Kimie Kester [ 27/Sep/18 ]

Here are 3 more screens to review under FOLIO UX Designs > Settings > Locations:

Comment by Cate Boerema (Inactive) [ 28/Sep/18 ]

Hi Former user. That was fast! I like your mockups for Settings > Organization > Service points. Just keep in mind that more than one of the locations can have the service point as primary. Maybe you could tweak your mockup to show two locations with "(primary)"?

For Settings > Organization > Locations, the mockups also look great. Just a few questions/comments:

  1. I think the label should be "Service point(s) *". The reason I say that is that, in most cases, there will probably be just one service point per location. Also, I think we need to show the asterisk to indicate it's a required field. Your mockup is missing asterisks on other required fields (just look at the working software to see which ones are required)
  2. There is no service point lookup - the list won't be that long
  3. We need some ability to indicate which service point is primary (radio buttons?)
  4. Why do we use trash cans in some places and Xes in others?
  5. I think this pattern of selecting from a menu and clicking add is okay, but given there is usually only one service point, I wonder if it would make more sense to do something like what we do for repeatable fields in Inventory. I guess I don't really understand when we use one pattern vs the other

Thanks so much for the speedy turnaround on this!!

Comment by Kimie Kester [ 28/Sep/18 ]

Hi Cate Boerema. Here are updated mocks ups for:

Settings > Organization > Service points
https://drive.google.com/open?id=1eNfARcbiDeL-PaY8IPJZu-HRl9Dp9mm8

Settings > Organization > Locations
3-Settings-Organizations-Locations-Detail.png
4-Settings-Organizations-Locations-Edit.png
5-Settings-Organizations-Locations-View-Mode.png

  1. I added the asterisks on the Edit mode but I think normally on View mode we don't show them
  2. Removed link to Service point look-up
  3. I added an ability to select Primary. If they can select multiples, that is why I used checkboxes. Let me know if they can only select one and I will change to radios
  4. I think some areas like Permissions use a component that started out with an X. Then later a trash can was introduced for clarity. I think the components that use X's were left as is for now until there is time to go back and update them.
  5. Thanks for pointing out the pattern in Inventory. I think that is a fine one to use. The other pattern that is seen in Permissions was created awhile ago. I think it could be revisited to see if it can follow the new pattern although it may have special issues.
Comment by Emma Boettcher [ 28/Sep/18 ]

Former user, re: 3, the system shouldn't allow you to select multiple service points as primary for location (though a service point can be the primary service point for multiple locations, like you have in the mockups on Google Drive). Each location has one and only one primary service point (like in UX-203 Closed ).

Comment by Cate Boerema (Inactive) [ 28/Sep/18 ]

Looks great to me, aside from Emma's point. Thanks!

Comment by Kimie Kester [ 28/Sep/18 ]

Thanks Emma Boettcher and Cate Boerema. So if you go to:

3-Settings-Organizations-Locations-Detail.png
The mockup shows Baker Circ Desk 1 as primary

Then if you go Edit the screen and change primary to Baker Circ Desk 4
4-Settings-Organizations-Locations-Edit.png

When you come back to View mode, Baker Circ Desk 4 would be first in the list and be designated as primary
5-Settings-Organizations-Locations-View-Mode.png

Is that correct?

Comment by Cate Boerema (Inactive) [ 01/Oct/18 ]

This looks good to me, Former user. Emma Boettcher, if this looks good to you, can you please close this story? Thanks!

Comment by Cate Boerema (Inactive) [ 01/Oct/18 ]

Former user. Question: how should the edit/create page look when there is just one service point displaying (by far the majority of cases).

  • It should not be possible to delete the last service point. Should the trash can icon be invisible or inactive when there is only one service point menu?
  • If there is only one service point, it needs to be primary. Should the radio button display, but inactive in this case?

Also, how important do you think it is that the primary service point display at the top as shown in your mockups? I feel like this is more of a nice-to-have than a must-have.

Once we have all these questions answered, I'm thinking we can probably merge our two stories, Emma Boettcher ( UIORG-115 Closed and UIORG-110 Closed )

Comment by Kimie Kester [ 01/Oct/18 ]

Hi Cate Boerema. Here's what I am thinking regarding your questions:

  • It should not be possible to delete the last service point. Should the trash can icon be invisible or inactive when there is only one service point menu
    [Kimie: Invisible]
  • If there is only one service point, it needs to be primary. Should the radio button display, but inactive in this case?
    [Kimie: I would think it would display and be active, similar to a Primary address on the user record]
  • Also, how important do you think it is that the primary service point display at the top as shown in your mockups? I feel like this is more of a nice-to-have than a must-have.
    [Kimie: Yes, it is a nice-to-have. Currently on the user record if you add an address and then select the new address as primary, when the screen is saved and user returns, that new address will be at the top of the list and shown as primary]
Comment by Cate Boerema (Inactive) [ 02/Oct/18 ]

Thanks Kimie!

Generated at Fri Feb 09 00:13:24 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.