/
Vega - Ramsons: Available workflows by sprint

Vega - Ramsons: Available workflows by sprint

Owned by Stephanie Buck
Last updated: Mar 13, 2025 by Anne Ekblad
5 min read

 

Key
= work is complete and functioning

= work was complete and functioning, now has known issue

= work is not yet complete and functioning

Requesting and lending workflows

 

Last update: (3/13/2025 at 8:00 AM EST)

Workflow

Steps

Feature(s)

Target Sprint availability (dev environment - ECS Okapi)

DATED - Anne to update week of 3/10/2025

ECS Eureka bugfest

Known issues

Pre-validation Env

Known issues

Workflow

Steps

Feature(s)

Target Sprint availability (dev environment - ECS Okapi)

DATED - Anne to update week of 3/10/2025

ECS Eureka bugfest

Known issues

Pre-validation Env

Known issues

ECS Title level requests

  1. Create a title level request without using title or requester lookup links

  2. Create a title level request using title and requester lookup links

  3. Create a title level request with a Proxy

  4. View title level request details

  5. Edit a title level request

  6. Reorder a title level request queue

  7. Cancel a title level request

 

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

200
(Sept. 16-27, 2024)

  3. n/a

_7. MODTLR-164 (Sprint 212 - In refinement) - Impacts Secondary request cancellation for cancelled TLR Holds

  3. n/a

MODTLR-162 (In Sprint 212 - In refinement; Vega to ID if issue is due to configuration or code error)

MODTLR-163 (In Sprint 212 - In refinement; Vega to ID if issue is due to configuration or code error)

Note: There needs to be at least one Holdings record for an Instance in each tenant in which an Item might be located in order for materials to be requested.

  • Known to do: LOC to create these Holdings.

ECS Item level requests

  1. Create an item level request without using title or requester lookup links

  2. Create an item level request using requester lookup link

  3. View item level request details

  4. Edit an item level request

  5. Reorder an item level request queue

  6. Cancel an item level request

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

202
(Oct. 14-25, 2024)

 

MODTLR-163 (In Sprint 212 - In refinement; Vega to ID if issue is due to configuration or code error)

Note: There needs to be at least one Holdings record for an Instance in each tenant in which an Item might be located in order for materials to be requested.

  • Known to do: LOC to create these Holdings.

ECS Loans

  1. Check requested item out from Central tenant

  2. Check item in to Central tenant

    1. Ensure item is in transit to appropriate location in data tenant

  3. Ensure appropriate patron notice(s) sent for Loans

  4. Find above transactions in the Circ log & verify info in each column

  5. View Loan details

  6. View User details

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

202
(Oct. 14-25, 2024)

CIRC-2231 (Scheduled for T; workaround is to place request on items prior to checking them out to the patron)

 

Mediated requests

  1. Search for a mediated request

  2. Filter a mediated request

  3. Confirm item arrival

  4. Send item in transit

UXPROD-4657 (Closed)

202
(Oct. 14-25, 2024)

  4. -

#1. search is case sensitive currently MODREQMED-17 (Sprint 211 - Currently blocked by a ticket In code review)

#3. MODREQMED-93 (Sprint 212: In Review) unable to test steps 3 and 4 for TLR due to bug (Note: Only cross-tenant requesting is impacted. Can test oLOAN collection workflows)

#4 to be retested via entire workflow process

  3. -

  4. -

MODREQMED-93 (In review) - Issue seen in ECS Eureka BF, not yet confirmed in pre-val. (Note: Only cross-tenant requesting is impacted. Can test oLOAN collection workflows)

  1. Create a new mediated request

  2. Edit a mediated request

  3. Decline a mediated request

  4. Print slip for Mediated requests activity - Send item in transit

UXPROD-4657 (Closed)

203
(Oct. 28-Nov. 8, 2024)

  4. -

Note related to Shared instance requesting: There needs to be at least one Holdings record for an Instance in each tenant in which an Item might be located in order for materials to be requested.

  • Known to do: LOC to create these Holdings.

#4 Slip content to be tested

MODREQMED-95 (In Sprint 212 - In refinement; Vega to ID if issue is due to configuration or code error)

Note: There needs to be at least one Holdings record for an Instance in each tenant in which an Item might be located in order for materials to be requested.

  • Known to do: LOC to create these Holdings.

  1. Confirm a mediated request in Secure tenant

    1. Local request - available in development environment

    2. Shared instance

UXPROD-4657 (Closed)

20-
(Dec. 8-22, 2024)

  1. a.
    b.

 

  1. a.
    b.

Note: There needs to be at least one Holdings record for an Instance in each tenant in which an Item might be located in order for materials to be requested.

  • Known to do: LOC to create these Holdings.

  1. Mediated request statuses follow mediated request workflows

    1. Awaiting confirmation > Not yet filled

    2. Not yet filled > In transit for approval

    3. In transit for approval > Item arrived

    4. Item arrived > In transit to be checked out

    5. In transit to be checked out > Awaiting pickup/delivery

    6. Awaiting pickup/delivery > Closed - filled

UXPROD-4657 (Closed)

209

(Jan. 13-24, 2025)

Confirmed steps c, d, and e in ECS Eureka Bugfest - Can dev environment be updated?)

a.

b.

c.

d.

e. to be retested after d. complete

f.



a.

b.

c.

d. -

e. -

f. -

_d. MODREQMED-93 (Sprint 212: In Review) unable to test steps c-f for cross-tenant requests due to bug (Note: Only cross-tenant requesting is impacted. Can test oLOAN collection workflows)

a.

b.

c.

d. -

e. -

f. -

_d. MODREQMED-93 (Sprint 212: In Review) Issue seen in ECS Eureka BF, not yet confirmed in pre-val. (Note: Only cross-tenant requesting is impacted. Can test oLOAN collection workflows)

Private requests

  1. View a Secure request from the Secure tenant (Requests app.)

UXPROD-4119 (Closed)

206
(Dec. 8-22, 2024)

 

 

Private requests

  1. Edit a Secure request from the Secure tenant (Requests app.) - work complete

  2. Reorder a Secure request from the Central tenant (Requests app.) - work complete

  3. Cancel a Secure request from the Secure tenant (Requests app.) - work complete

  4. View a Secure request from the Central tenant (Requests app.) - work complete

  5. Check in item corresponding to Congressional requests with status of “Open - Not yet filled” from Central tenant (ensure routing to Authorized staff and rest of FOLIO Secure tenant workflow) (Check in app)

  6. Look at User loan details in Central tenant (Users app. - ensure User data is obfuscated) - work complete

  7. Look at User loan details in Secure tenant (Users app.) - work complete

UXPROD-4119 (Closed)

209

(Jan. 13-24, 2025)



  5. -

#5. needs testing

  5. -

 

Printing staff slips

  1. Generate and print the following with the information staff require to complete their workflows:

    1. Hold - from Central tenant

    2. Pick slip - from Central tenant using mod-tlr and data tenants using mod-circ

    3. Request delivery - Central tenant

    4. Search slip - Hold requests, Requests app, from Central tenant using mod-tlr

    5. Transit - from Central tenant

    6. Hold shelf expiration report - within data tenants related to non-congressional requests and loans

UXPROD-4985 (Closed)

206
(Dec. 8-22, 2024)

a.

b.

c.

d.

e.

f.

_a. MCBFF-75 (In Sprint 212)

_e. MCBFF-75 (In Sprint 212)

Note: Both a. and e. relate to missing CN tokens. Behavior noticed in both ECS Eureka BF and LOC pre-validation

 

a.

b.

c.

d.

e.

f.

a. and e. MCBFF-75 (In Sprint 212)

Note: Both a. and e. relate to missing CN tokens. Behavior noticed in both ECS Eureka BF and LOC pre-validation

 

 

 

Related content