2025-04-07 Resource Access Meeting Notes

🗣️ Discussion Points:

1. Bugfest Environment Issues (00:07:23 - 00:08:00):

   • Context: The Bugfest environment had significant usability issues last week due to its recent setup. This caused delays and hindered testing activities.
   • Details: Participants discussed the challenges faced with the Bugfest environment, noting that it was essentially unusable. The conversation highlighted the importance of setting up capability sets correctly to ensure smooth testing. Capability sets are configurations that define what actions users can perform within the system, and improper setup can create barriers to effective testing.
   • Impact: The issues with the Bugfest environment led to a lack of testing progress, emphasizing the need for better preparation and setup before testing phases.

2. FeeFines Settings and Tests (00:24:34 - 01:05:43):

   • Context: FeeFines settings and tests were a major topic of discussion, with participants sharing updates and challenges.
   • Details: Susan mentioned creating a new role for FeeFines Settings that can perform all necessary actions. Laurence is waiting for JIRA:BF-1189 and JIRA:BF-1190, which are related to Floating collections and Retrieval SP tests. Laurence is currently working on Refund tests while waiting for these JIRAs to be resolved. There was also a discussion about the process of declaring lost Claimed returned fees, which first get canceled and then re-billed, causing confusion.
   • Impact: The creation of new roles and the ongoing work on JIRAs and tests are crucial for improving the FeeFines system. The discussion highlighted the complexity and the need for clear processes to avoid confusion.

3. Excel Copy-Paste Issue (00:14:18 - 00:20:03):

   • Context: Participants discussed issues with copying and pasting data from Excel into Folio, where extra characters were being added.
   • Details: The issue involves Excel adding characters (like carriage returns) when data is copied and pasted into Folio. Various workarounds were suggested, such as copying from the top of the cell instead of the whole cell, using Control Shift V to strip formatting, and testing in different apps like Inventory and Users. It was noted that this behavior is app-specific, with Inventory showing the issue but Users not.
   • Impact: Understanding and addressing these copy-paste issues is important for ensuring data integrity and usability within Folio. The discussion provided valuable insights into potential solutions and highlighted the need for consistent behavior across different apps.

4. Title Level Requests (00:33:49 - 00:36:07):

   • Context: Issues with searching for HR ID in the Requests app were discussed.
   • Details: Participants noted that searching for HR ID in the Requests app was slow, sometimes showing only three dots and not progressing. Refreshing the page was suggested as a workaround. The conversation also touched on the workflow for creating title-level requests and the challenges faced in this process.
   • Impact: The slow search functionality and the need for workarounds indicate areas for improvement in the Requests app. Ensuring efficient and reliable search capabilities is essential for user productivity.

5. FeeFines Testing Challenges (01:02:34 - 01:05:43):

   • Context: The complexity and challenges of FeeFines testing were discussed in detail.
   • Details: Participants shared their experiences with setting up FeeFines tests, noting the complexity and the need for automation. Laurence mentioned the difficulty of creating tests that involve multiple steps and dependencies. The conversation also highlighted the potential for automating these tests to simplify the process and reduce manual effort.
   • Impact: The discussion underscored the need for better tools and processes to manage FeeFines testing. Automating tests could significantly improve efficiency and accuracy, reducing the burden on testers.

6. Bursar Transfer System (01:13:13 - 01:14:30):

   • Context: Thomas shared details about a new bursar transfer system for Cornell.
   • Details: The new system, written in Python, can run as an AWS Lambda function and handle credits and charges. It is designed to automate the bursar transfer process, reducing manual effort and improving accuracy. The system can run daily jobs to export credits and charges, save data to an AWS bucket, and send notifications via email or Slack.
   • Impact: The new bursar transfer system has the potential to streamline financial processes at Cornell, making them more efficient and reliable. The automation capabilities could save time and reduce errors, benefiting both staff and students.

📌 Action Items:

• Laurence to continue working on Refund tests while waiting for JIRA:BF-1189 and JIRA:BF-1190.
• Susan to refine the new role for FeeFines Settings.
• Thomas to finalize and implement the new bursar transfer system for Cornell.

📊 Data & Insights:

• The Bugfest environment's usability issues and the impact on testing.
• The complexity of FeeFines tests and the need for automation.
• The new bursar transfer system's potential to streamline processes at Cornell.

🔄 Follow-Up:

• No specific follow-up meetings or checkpoints were noted.

🐝 JIRAs:

• JIRA:BF-1189 (Type: Unknown)
• JIRA:BF-1190 (Type: Unknown)