Add "service point for the effective location" as staff slip token

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

Priority

Fix versions

Development Team

NLA

Assignee

Solution Architect

Parent Field Value

None

Parent Status

None

Checklist

hide

TestRail: Results

Activity

Show:

Brad Berkotte August 10, 2023 at 3:21 AM

Testing and development complete

Brad Berkotte May 9, 2023 at 11:44 PM

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

Khalilah Gambrell May 9, 2023 at 11:06 PM

Hey , , and will this work be included in the Poppy release? Dev freeze currently set for June 2.

julie.bickle May 8, 2023 at 8:56 AM

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

Brad Berkotte April 21, 2023 at 1:08 AM

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  

Done

Details

Reporter

PO Rank

0

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%

Release

Poppy (R2 2023)

Rank: Cornell (Full Sum 2021)

R3

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created April 4, 2023 at 10:54 PM
Updated September 17, 2024 at 1:05 PM
Resolved August 10, 2023 at 3:21 AM
TestRail: Cases
TestRail: Runs