Staff Slips (UXPROD-19)

[UXPROD-4179] Add "service point for the effective location" as staff slip token Created: 04/Apr/23  Updated: 30/Nov/23  Resolved: 10/Aug/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Poppy (R2 2023)
Parent: Staff Slips

Type: New Feature Priority: P3
Reporter: Brad Berkotte Assignee: Ravi Gupta
Resolution: Done Votes: 0
Labels: LC-priority3, loc, nla, staff_slips, staff_slips_tokens
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-4465 Pick slip token enhancements (staff s... Draft
is defined by CIRC-1785 Update staff slips to have the primar... Closed
Release: Poppy (R2 2023)
Epic Link: Staff Slips
Analysis Estimate: Large < 10 days
Front End Estimate: Large < 10 days
Front-End Confidence factor: 90%
Back End Estimate: Large < 10 days
Back-End Confidence factor: 90%
Development Team: NLA
PO Rank: 0
Rank: Cornell (Full Sum 2021): R3

 Description   

Current situation or problem: Currently the service point for the items effective location is not a token that can be added via staff slips.

In scope

  • Adding a token to the staff slip
  • Showing live data on a staff slip produced in the Requests app (pick slip)
  • Showing live data on a staff slip produced in the Check in app (hold, delivery request and transfer slips)

Proposed solution/stories

Each items effective location has an attached service location within the tenant the effective location in which the item sits should also return the relevant service point.

https://folio-org.atlassian.net/browse/UXPROD-533

https://folio-org.atlassian.net/browse/UXPROD-3813

https://folio-org.atlassian.net/browse/UXPROD-4189

 

Links to additional info

... / circulation/requests/(uuid)

→ (request) / item / location / (code)

→ locations / (code) → locations primaryServicePoint (uuid)
(e.g.  (okapi) /locations/?query=code=="(item location code)" )

→ servicepoints (primaryServicePoint uuid) → servicepoints name OR discoveryDisplayName

 

Questions



 Comments   
Comment by julie.bickle [ 13/Apr/23 ]

What if there are several service points assigned to a location?
For the token Departments (https://folio-org.atlassian.net/browse/UIREQ-814), we went with separating each entry (i.e. service point) by a semi-colon and a space.
Example: On the piece of paper, I see “Library Technical Services; IT Operations”

Comment by Brad Berkotte [ 20/Apr/23 ]

julie.bickle 

Sorry for taking a while to get back to you on this.

 

We would be using effecting location to determine service point, which as it is for an item I believe would make it singular if I am correct in my thinking? Happy to look into that more if there are any known examples where this would be the case, as it is for the overarching FOLIO project it would need to be addressed and cater for those examples.

 

As I am looking at the NLA prod environment for the majority of my data examples, we have been quite specific with assigning locations related to service points too, as our legacy system had some quirky but somewhat useful things that have helped the library set up our inventory somewhat differently I presume to other libraries.

Comment by Thomas Trutt [ 20/Apr/23 ]

Brad Berkotte julie.bickle is correct you can have multiple service points assigned to a location (effective location). julie.bickle you could handle it as you purposed or just pull the primary service point.

Comment by Brad Berkotte [ 21/Apr/23 ]

Thomas Trutt Thank you that is great to know, probably just the way we have it set out at current to why that was my thought process, very important we make it useable for all. 

I will chat to the Dev we have working on this in our space and go with the primary service point as the first instance and the semi colon and space as the second, see what path he is more comfortable with and will update the ticket accordingly.

 

Thank you both for bringing this to my attention julie.bickle 

Comment by julie.bickle [ 08/May/23 ]

Sorry for my late response; I agree with you Tom, I think pulling in the primary service point is a good compromise.

Comment by Khalilah Gambrell [ 09/May/23 ]

Hey Brad Berkotte, julie.bickle, and Terence Ingram will this work be included in the Poppy release? Dev freeze currently set for June 2.

Comment by Brad Berkotte [ 09/May/23 ]

Hi Khalilah Gambrell, yes we intend to have this ticket and UXPROD-4180 Closed ready to be included in the poppy release, I shall inform our dev at NLA about the development freeze date.

Comment by Brad Berkotte [ 10/Aug/23 ]

Testing and development complete

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