Locations and Service Points (UXPROD-771)

[UXPROD-269] CRUD service points Created: 27/Feb/18  Updated: 16/Sep/20  Resolved: 04/May/18

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q2 2018
Parent: Locations and Service Points

Type: New Feature Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Cate Boerema (Inactive)
Resolution: Done Votes: 0
Labels: locations, resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks UXPROD-72 Regular opening hours for service points Closed
blocks UXPROD-851 Exceptional opening hours for service... Closed
blocks UXPROD-4 Assign Patron default service point f... Closed
blocks UXPROD-260 Indicate service point for session Closed
blocks UXPROD-270 Associate service points with locations Closed
blocks UXPROD-37 Limit/scope for permission assignments Closed
Epic Link: Locations and Service Points
Analysis Estimate: Large < 10 days
Analysis Estimator: Cate Boerema (Inactive)
Front End Estimate: XL < 15 days
Front End Estimator: Jakub Skoczen
Back End Estimate: XL < 15 days
Back End Estimator: Jakub Skoczen
Estimation Notes and Assumptions: New endpoint for processing centers, potentially new endpoint for the relationship/association. An an indicator on the loan for processing center used so it can go in the Loan actions table
Development Team: Prokopovych
Rank: BNCF (MVP Feb 2020): R1
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: GBV (MVP Sum 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

Ability to CRUD a list of service points for the tenant. I think we can probably use the UX pattern we've used for Loan policies. There will be a name and some metadata (description etc). Service points are a conceptual center of Operations. These may NOT have loan rules directly applied to it.

These service points will be used in a variety of ways:

  • You will be able to set up a workstation (e.g. a circ desk) so that it is associated with a "service point" ( UXPROD-260 Closed ) CB: Actually going to do this differently, see notes below
  • You are then able to limit users' permissions to specific service points. So users may have different permissions depending on the workstation they are working from. ( UXPROD-37 Closed ) CB: After further discussion, the RA SIG doesn't think this is a top priority. See notes below.
  • We may want to associate users with a service point ( UXPROD-4 Closed )
  • There may be different versions of the institutional calendar for the various service points ( UXPROD-72 Closed )
  • We need a way to associate service points with locations so you know which circ desk, for example, covers
  • Circ desks need to be associated with physical locations in such a way that, when an item is checked in, the system knows whether it is “home” or if it needs to go in transit back to the physical location it calls home. ( UXPROD-270 Closed )
  • Etc...

April 5, 2018

There were some questions about where service points should "live" architecturally. I have some information that might help inform that decision. Tagging Jakub Skoczen, Marc Johnson, Kurt Nordstrom here. Please tag others if I missed anyone.

There is no need to filter by service points in the FOLIO UI, but we will want to be able to generate lots of reports with service point data. For example, items loaned at a service point, holds at a service point that have expired, which locations are associated with service points etc.

Some service points will not be circulation-related (e.g. binderies) so if there is a scenario in which a folio tenant doesn't have circulation enabled (not sure this makes sense in reality), we want service points to still be available functionality.

I also have more information about how service points are associated with transactions. We will not be attempting to tie workstations to service points as initially discussed. Instead, we need a way to to set the allowed service points for a FOLIO operator (staff user) as well as a default for that user. Then, when that user logs in, the service point is automatically set to their default. They can then change to another as long as it’s in their list of allowed service points.

There was also some further discussion as to whether we need to support limiting the scope of a FOLIO operator's permission by service point. Apparently this is something systems offer, but it didn't seem like a top priority to the RA SIG and we need to have more conversations with other SIGs about permission scope limits and what is really needed. We might end up doing permission scope limiting by locations instead (or some component of a location like libraries).


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