MetroEast

No prob! Im canceling this week schedule meeting.

I'm still behind a bit here. Not sure we have anything to review or discuss. I've at least managed not to have a conflicting overlap.

I'm going to focus on getting out the door and being on site for further minor chaos today.

all right sounds good!

Thsi entire month has been consumed with our leadership review process and cleaning our largest office/moving folks into other rooms. I haven't had much space to work on the form config. I hope to see more time in Early august, we want to pilot our quarterly renewals. That's an early August item, so I'm thinking we're timing this okay. I cannot make the Thursday meeting, tomorrow, but I'd like to keep the 31st and following available for follow-up.

Ok David, let's talk on the 31st.

I think I have something we can work on. We were discussing a first record save triggered script that would use the choices made in fields to simplify some data entry like creating a season for a project if they select series for the type. This was discussed last meeting as a way to save steps when creating the parents for the program records. I'm also interested in the best method to handle sorting a numeric list of values for a list selector. I tried changing it to numeric at the list, but encountered odd behavior and an error during reindexing. Probably missed a step.

I've been thinking about the workflow for new folks as well as returning folks, and I have an idea that needs vetting and develpoment.
Someone new to the system: We invite them by email to fill out a person record, and once successfully filled out they are then invited to fill out a Project record.
Someone who has a person record: Could when logged in, fill out a new project record. When saved, we evaluate the "type" and decide if we then invite them to fill out a Season record, or simply notify the playback staff email that a new single program project record has been entered for review.
Someone who has a project that is a series, could be invited to fill out a new season when it's time to start seasonal renewals. When they save that new record, we would notify playback staff that a new season record has been entered for review.
Once reviewed by staff... single program projects after staff save the project record with "accepted" status, the script would instance the single program record. Season records would be similar, when staff save the season record as "accepted" status the script would instance the episode/programs.
I think this meets the needs of inheriting data, but I'm not sure. I've done some form work to reflect this idea.

I believe this is pretty close to where we've been headed with the logic and scripting. Main difference is the 3 invitations to create a record. First a Person/People, then a Project, and then Season if the pick series project type. I'd like to start work on the invitation to make a person record and maybe a way to set a Project field picking from the list of People based on who is logged in or which user created the person record.

Once this 3 part logic is in place, it should be trivial to add options for staff to set the record state to "needs more info" where we'd want to notify the account associated with the record to login and update the record. Might have logic on save that if the state was "needs more info" then the new state is "ready for review"

Hello David, I just figure it out about the Title field mask not working for Programs, the problem was the field for Projects it was named "dam_project_id", and the mask is referncing to data.data_project.title, so to make it work and keep naming conventions I added new field: "dam_project" this matches the table name so is better to keep track of what they mean.. In the screen shot still the wrong field present, but I'm removing it rigth now.

Idea 1:
copy users into people db
use people database for data entries
they can use my account
first page is project page

Idea 2:
Do not use people db (less maintenance)
need to elaborate more next meeting.

Thanks for the notes. I'll try the field mask things soon. I want to get clarity on the people flexibility vs. assuming the user logged in for that.
I think I should push until next week. Today is getting full of chaos per usual, but this week has been extraordinary for it so far.

I think Davinf wants Idea 2. Have all user lookups be from the User Database. Then we hide the people database and dont use it.

I'll confirm. I have Qs out to staff for reflection on this. Thanks to Ron's work, we have People idea in several places. Most of it is about who approved (playback staff) and who submitted (producer) .. there's also some ideas around promising delivery, which may be the only odd bit I can see those others would work based on who is currently logged in.

I had plans to confirm this week, but my contact/person of interest has been very busy this week. I need to skip the meet for today, but should have useful info by next Thursday.

Sounds good, have a great weekend!

Our playback person is deep into quarterly scheduling, and wont be available for a bit. I'm about to begin the rebuild of our main studio's control room, for 2 weeks. I think the next Thursday I have open is right after that, on the 11th.

Hello, lets talk on the 11th!