03-18-2025: Working Group on Remote Storage

Date

Jan 14, 2025

Agenda

• Housekeeping (5-min.)

Homework and Pre-Reads

• None!

Useful Resources

Recording

https://recordings.openlibraryfoundation.org/folio/implementation-group/2025-01-14T10:55/

Attendees

• @Thomas Trutt@David Jones @Pennington Jr, Buddy @David Bottorff @Hinman, Wes @Justin Barnett @Darsi Rueda @Wilhelmina Randtke @Katie Motush @Wayne Schneider Ken Rettinger Lev Rickards Mary Anderson @Dale Arntson

🗣️ Discussion Points:

1. Status Codes Documentation (11:02:58 - 11:06:36)

   • Overview: Thomas initiated the discussion on documenting status codes, identifying which ones are functioning and which are not.

   • Details:

     • Buddy mentioned that items in white on the spreadsheet were not having issues, indicating that these status codes were functioning correctly.

     • David clarified the use of status codes for different transaction responses from EMS, explaining that the codes are dependent on the original message type, such as inventory add, inventory delete, status check, or pick request.

     • Debate: The group discussed the differences between web services and TCP/IP protocols. David and wrandtke provided insights on the advantages and limitations of each. Web services require payment for setup and changes, and documentation is not readily available, whereas TCP/IP is standardized and accessible despite being labeled as a trade secret.

2. Permissions Bug (11:19:36 - 11:23:27)

   • Overview: Wayne raised the issue of a permissions bug (JIRA:MODRS-178) that was closed without being fixed.

   • Details:

     • The bug was related to the permission to mark items missing, which was not documented properly. Instead of fixing the bug by adding the necessary permissions to the right module descriptor, a workaround was identified, but it was not documented.

     • Wayne suggested reopening the bug to fix it correctly, ensuring that the permissions are properly assigned and documented.

     • Debate: The group discussed the deliberate behavior of Folio in marking items missing upon receiving a 002 status code from EMS. This behavior was specified by someone and might break existing implementations if changed. Wayne mentioned that GVSU was involved in testing this behavior, and Katie from GVSU confirmed that staging director marking items missing has caused issues for them.

3. Handling 002 Status Code (11:35:08 - 11:39:59)

   • Overview: The group debated the appropriate behavior for handling the 002 status code from EMS.

   • Details:

     • David explained the issue of Folio attempting to mark items as missing, causing a loop if the item status cannot be changed. This happens when Folio receives a 002 status code indicating that the item has been delivered out of the bin, but Folio cannot change the status to missing due to business logic restrictions.

     • Debate: The group discussed the need for configurable behavior to handle different status codes. David suggested adding a logging feature to the UI to see errors and understand what went wrong. Wayne emphasized the importance of acknowledging the message from EMS to avoid loops. Buddy raised the question of whether marking the item as missing triggers a change in the request status, and David confirmed that it does not.

4. Heartbeat Messages (11:54:16 - 11:58:03)

   • Overview: The necessity and handling of heartbeat messages between EMS and Folio were discussed.

   • Details:

     • David explained that EMS does not care if it does not receive a heartbeat message from Edge-damatic. The heartbeat message is used to determine if the interface is still up, but EMS does not consider it an error if it does not receive a response.

     • Debate: The group agreed that Edge-damatic should always respond to heartbeat messages to avoid issues. Thomas suggested that Edge-damatic should respond with a 000 status code to indicate that everything is normal.

✅ Decisions Made:

• Reopen Permissions Bug: The group decided to request the reopening of JIRA:MODRS-178 to fix the permissions issue correctly.

• Configurable Behavior for Status Codes: It was agreed that Folio should have configurable settings to handle different status codes, particularly the 002 status code.

• Logging Errors in UI: The group decided that logging errors in the Folio UI would be beneficial for troubleshooting and workflow management.

📌 Action Items:

• Reopen JIRA:MODRS-178: Wayne to request reopening and fixing the permissions bug.

• Develop Configurable Settings: David to work on creating configurable settings for handling status codes in Folio.

• Implement Error Logging: Thomas to explore the implementation of error logging in the Folio UI.

📊 Data & Insights:

• Permissions Bug: The bug related to marking items missing was closed without proper documentation, leading to issues in implementation.

• Status Codes: Different transaction responses from EMS require specific handling, and configurable settings can help manage these effectively.

• Heartbeat Messages: Ensuring Edge-damatic responds to heartbeat messages can prevent communication issues between EMS and Folio.