Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Yellow
Assigned To: Brandon Moore
Created By: Brandon Moore
Created Date/Time: 5/2/2022 9:32 am
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
Priority: 0
 
Time Id: 8966
Template/Type: Brandon Time
Title/Caption: Adilas Time
Start Date/Time: 5/23/2022 9:00 am
End Date/Time: 5/23/2022 10:00 am
Main Status: Active

Sorry, no photos available for this element of time.


Notes:

For the first part of the meeting, I was on with Wayne, Cory, and some outside clients on a Google meet meeting to go over an outside data analytics service that was being requested for one of our clients. It was mostly a brainstorming session about possible options and direction. We pitched a proposal for direct data access, showing real data, mirrored over to a new instance, but on an independent accessible database. One of the topics that came up was the data dictionary and the education on the database schema, rows, tables, columns, and relationships (what is what, inside the database). The term that was being flipped around between the parties was the data dictionary (written eduction on the database stuff).

I jumped on the GoToMeeting after we were done. Not much going on there this morning. I was doing emails and texting back and forth with Steve. He was on another meeting with Mike and the state of Mississippi. Steve had some questions about some timecard calculations and wanted to see if we were storing any of the calculated values. I told him that we do store calculated values for employee timeclocks and timecards but do not store calculated values on sub dates and times for elements of time. That may be something that we want to do in the future. It would help save time and speed things up. Steve was saying, when it's time, we'll go for the MVP (minimal viable product) type release. In the meantime, we'll just calculate things on the fly.