Content Comparison

Sure, here is the revised summary with last names removed:

🗣️ Discussion Points:

1. Announcements and Updates (11:00 - 11:06)

   • LDP Light Update:
     • New Developers and PO: The meeting began with an update on the LDP Light project, highlighting the addition of new developers, Catherine and a new Product Owner, Patrick. This indicates a strengthening of the team and potentially faster progress on the project.
     • New Slack Channel: A new Slack channel has been created for better communication and collaboration among team members. This channel is linked in the agenda, providing easy access for those interested.
     • Vision and Mission: The new vision and mission for LDP Light were discussed, emphasizing the project's goals and future direction. This is crucial for aligning the team and stakeholders with the project's objectives.
   • WolfCon Proposals:
     • Call for Proposals: The call for proposals for WolfCon, scheduled to be held in Kansas City, was announced. Participants were encouraged to submit their session proposals by April 11th.
     • Registration: Registration for WolfCon is open, allowing attendees to secure their spots early.
     • Hotel Room Costs: There was a brief discussion on the high cost of hotel rooms for WolfCon, which might be a concern for some attendees.

2. Workshop Topics (11:07 - 11:09)

   • Pre-WolfCon Workshops:
     • Full Day and Half-Day Workshops: The idea of conducting full-day and half-day workshops before WolfCon was proposed. These workshops are intended to be more interactive and in-depth, allowing participants to work closely on specific topics.
     • Suggested Topics: Topics like AI and Eureka permissions and roles were suggested for these workshops. These areas are seen as valuable for deeper exploration and practical application.

3. Request Features and Upgrades (11:10 - 11:12)

   • Ramsons Features:
     • Dedicated Meetings: There was interest in having dedicated meetings to discuss Ramsons features and upgrade experiences. This would provide a focused platform for sharing insights and addressing concerns related to Ramsons upgrades.
     • Upgrade Experiences: The discussion included the idea of having sessions both before and after upgrades to cover the changes and gather feedback on the upgrade process.

4. Request Management (11:13 - 11:17)

   • JIRA:UXPROD-897:
     • Resetting In-Process Requests: The feature request to reset in-process requests to open not yet filled was discussed. It was considered an edge case with existing workarounds, leading to the suggestion for closure.
   • JIRA:UXPROD-4470:
     • UAT Retrieval Service Point: A link to the UAT retrieval service point was shared, providing access to relevant information and updates.

5. Reports and CSV Exports (11:18 - 11:24)

   • Request Pick List:
     • Existing Functionality: The discussion highlighted that the existing functionality for exporting CSVs is sufficient for generating request pick lists. This led to the suggestion for closure of the feature request.
   • Hold Shelf Inventory List:
     • Similar Functionality: It was noted that similar functionality already exists for generating hold shelf inventory lists, leading to the suggestion for closure.

6. Purging Closed Requests (11:25 - 11:30)

   • Performance Issues:
     • Anonymization vs. Purging: The debate centered around whether to anonymize or purge closed requests. Performance issues related to the number of requests were highlighted, but the consensus was that purging is not the solution. This led to the suggestion for closure.

7. Tracking Request Changes (11:31 - 11:35)

   • Request History:
     • Importance of Tracking: The importance of tracking changes to requests was discussed. This feature is seen as valuable for understanding the lifecycle of requests and was suggested for further refinement.

8. Tenant Level Settings (11:36 - 11:38)

   • Request Types:
     • Existing CERC Rules: The discussion concluded that existing CERC rules are sufficient for managing request types at the tenant level. This led to the suggestion for closure of the feature request.

9. Rush Recalls (11:39 - 11:41)

   • Override Minimum Loan Period:
     • Reserves: The need for rush recalls, particularly for reserves, was discussed. While the ability to manually reorder the request queue exists, the feature to override the minimum loan period was suggested for further refinement but deemed low priority.

10. Check-In Modals (11:42 - 11:49)

    • In-Transit Requests:
      • Differentiation Needed: The need for different check-in modals for requests versus home location transits was discussed. This feature is seen as necessary for better workflow management and was suggested for further refinement.

11. Customization of Check-In Modals (11:50 - 11:57)

    • Requester Name:
      • Privacy Concerns: The debate on the need for customization of check-in modals to include requester names highlighted privacy concerns. The consensus was that broad customization is unnecessary, leading to the suggestion for closure.

✅ Decisions Made:

• Closure of JIRA:UXPROD-897: Due to edge case nature and existing workarounds.
• Closure of Request Pick List and Hold Shelf Inventory List: Existing functionality deemed sufficient.
• Closure of Purging Closed Requests: Performance issues should be addressed separately.
• Further Refinement for Tracking Request Changes: Importance acknowledged, needs more detail.
• Closure of Tenant Level Settings for Request Types: Existing CERC rules sufficient.
• Further Refinement for Rush Recalls: Low priority but acknowledged.
• Further Refinement for In-Transit Requests: Need for differentiation acknowledged.
• Closure of Customization of Check-In Modals: Broad customization deemed unnecessary.

📌 Action Items:

• Track and Display Request Changes: Further refinement needed.
• In-Transit Requests: Further refinement needed to differentiate requests from home location transits.
• Rush Recalls: Further refinement needed, but low priority.

📊 Data & Insights:

• Performance Issues: Highlighted by the number of requests affecting system performance.
• Existing Functionalities: Many proposed features already have existing workarounds or functionalities.

🔄 Follow-Up:

• Future Meetings: Dedicated sessions for Ramsons features and upgrades.
• Workshop Topics: Continued discussion on pre-WolfCon workshop topics.

🐝 JIRAs:

• JIRA:UXPROD-897: Feature request.
• JIRA:UXPROD-4470: UAT retrieval service point.

💻 Related Projects:

• LDP Light: New vision and mission discussed.
• WolfCon: Conference proposals and logistics.