Dieneke S
Community Producer - Request a series program slot
Similar as above but slightly more complex. With a step (Seasons) between project and
program - Staff doing steps or with help
Invite producer to fill out a form with a Project and a Season with requested time slots
Mass create placeholder seasons in a status of "Renew offered"
Send email notifications to producers to renew via a link
Once approved create around 13 Programs placeholder records (with default values)
Approval process - View landing page for Programs/Projects who are in pending status - Update with approved status, completing fields in same records
Approval process - Request a slot - Provide Information in advance
Similar as above but slightly more complex. With a step (Seasons) between project and
program - Staff doing steps or with help
Invite producer to fill out a form with a Project and a Season with requested time slots
Mass create placeholder seasons in a status of "Renew offered"
Send email notifications to producers to renew via a link
Once approved create around 13 Programs placeholder records (with default values)
Approval process - View landing page for Programs/Projects who are in pending status - Update with approved status, completing fields in same records
Approval process - Request a slot - Provide Information in advance
Dieneke S
First meeting DEV planned with david this friday. Lets go over the proposal today for prep.
Dieneke S
My initial thoughts on timing suggest we could do 11:30 CT/10:30 PT on Fridays. I can be more available starting Friday, April 12. (message david)
Dieneke S
Christopher, I’m thinking of our discussion which was fairly recent, this year.
The meeting included extending access to a ticket system I hadn’t seen before.
In the meeting we discussed our 2 use cases which share several steps.
The sheet captured the major business logic we need, for both single and series use cases. About a dozen items.
I’ve requested access to view the sheet linked here.
The meeting included extending access to a ticket system I hadn’t seen before.
In the meeting we discussed our 2 use cases which share several steps.
The sheet captured the major business logic we need, for both single and series use cases. About a dozen items.
I’ve requested access to view the sheet linked here.
Christopher B
dam_contact_type might be fine as a list, not sure.
dam_is_series seems redundant, unless it’s needed for a reason I’m not seeing. I think we hid some fields when it was false, in the previous build.
Runtime fields need to be simplified to reference a list of specified lengths in minutes, and no need for optional manual entry.
The items which reference a person will need to be sorted, and might be ignored for now.
I want to remove the contact info columns since we’re moving to a contact database and ref’ing ids.
We need a place to have a default program number and program number. This would eventually be generated from business logic, for new records.
Seasons need a renewal priority column, to allow for sorting based on the policies we have. Business logic might help update these as we process requests.
dam_is_series seems redundant, unless it’s needed for a reason I’m not seeing. I think we hid some fields when it was false, in the previous build.
Runtime fields need to be simplified to reference a list of specified lengths in minutes, and no need for optional manual entry.
The items which reference a person will need to be sorted, and might be ignored for now.
I want to remove the contact info columns since we’re moving to a contact database and ref’ing ids.
We need a place to have a default program number and program number. This would eventually be generated from business logic, for new records.
Seasons need a renewal priority column, to allow for sorting based on the policies we have. Business logic might help update these as we process requests.
Dieneke S
Hello Dieneke and Christopher!
It’s been a bit of an adventure over here. We’ve just signed on with a nonprofit specific financial services provider, so I’m expecting to be a bit busy onboarding with them for the next few weeks. After which, I can turn my full attention to completing the various program ingest and scheduling projects. Would you please illuminate on our remaining balance?
I’ve some sample data, attached. Our folks are working on resolving questions I have around workflow needs; mainly person records being associated with a procedural action, attached to the Project/Season/Program records.
The sample data may include items that do not yet exist, or may need to be matched to the proper name.
The exports taken recently used to create them included columns we don’t intend to use and some items are missing in one table while present in others.
Some concepts captured by Ron in the original schema need to be parsed by our folks before we try to implement them:
Requested By: Presumably the producer, but could this be someone else?
Responsible Staff: I’m unsure how this differs from Requested, but can imagine requested to be a client we’re producing for.
Approved By: I’ve some notes here suggesting that’s the person who processed the request, who completed the schedule reservation. Should be "Processed By" if the notes are accurate.
Promised By: Now I’m confused… would this be the staff producer? Would this be playback?
Some notes:
dam_contact_type might be fine as a list, not sure.
dam_is_series seems redundant, unless it’s needed for a reason I’m not seeing. I think we hid some fields when it was false, in the previous build.
Runtime fields need to be simplified to reference a list of specified lengths in minutes, and no need for optional manual entry.
The items which reference a person will need to be sorted, and might be ignored for now.
I want to remove the contact info columns since we’re moving to a contact database and ref’ing ids.
We need a place to have a default program number and program number. This would eventually be generated from business logic, for new records.
Seasons need a renewal priority column, to allow for sorting based on the policies we have. Business logic might help update these as we process requests.
It’s been a bit of an adventure over here. We’ve just signed on with a nonprofit specific financial services provider, so I’m expecting to be a bit busy onboarding with them for the next few weeks. After which, I can turn my full attention to completing the various program ingest and scheduling projects. Would you please illuminate on our remaining balance?
I’ve some sample data, attached. Our folks are working on resolving questions I have around workflow needs; mainly person records being associated with a procedural action, attached to the Project/Season/Program records.
The sample data may include items that do not yet exist, or may need to be matched to the proper name.
The exports taken recently used to create them included columns we don’t intend to use and some items are missing in one table while present in others.
Some concepts captured by Ron in the original schema need to be parsed by our folks before we try to implement them:
Requested By: Presumably the producer, but could this be someone else?
Responsible Staff: I’m unsure how this differs from Requested, but can imagine requested to be a client we’re producing for.
Approved By: I’ve some notes here suggesting that’s the person who processed the request, who completed the schedule reservation. Should be "Processed By" if the notes are accurate.
Promised By: Now I’m confused… would this be the staff producer? Would this be playback?
Some notes:
dam_contact_type might be fine as a list, not sure.
dam_is_series seems redundant, unless it’s needed for a reason I’m not seeing. I think we hid some fields when it was false, in the previous build.
Runtime fields need to be simplified to reference a list of specified lengths in minutes, and no need for optional manual entry.
The items which reference a person will need to be sorted, and might be ignored for now.
I want to remove the contact info columns since we’re moving to a contact database and ref’ing ids.
We need a place to have a default program number and program number. This would eventually be generated from business logic, for new records.
Seasons need a renewal priority column, to allow for sorting based on the policies we have. Business logic might help update these as we process requests.
Dieneke S
David Elkin-Bram
Tue, Nov 7, 2:56 PM (20 hours ago)
to Dieneke, Christopher
Hi… You’re absolutely correct. Things have been heating up for me a bit.
I’ve got some critical structural things to nail down in an adjacent project.
I have plans to ask the grantor for more time on this project, in a meeting next week.
We’re meeting this evening to discuss our hiring plans for the Director of Finance and an executive assistant who will mostly support the DoF position; which we didn’t previously plan for in the budget.
I’m now in charge of Payroll and the pay equity study's implementation; which both come before this work.
Some time will open up next week for me to look at the demo data a bit more. I looked today, and had to stop before I got very far.
Tue, Nov 7, 2:56 PM (20 hours ago)
to Dieneke, Christopher
Hi… You’re absolutely correct. Things have been heating up for me a bit.
I’ve got some critical structural things to nail down in an adjacent project.
I have plans to ask the grantor for more time on this project, in a meeting next week.
We’re meeting this evening to discuss our hiring plans for the Director of Finance and an executive assistant who will mostly support the DoF position; which we didn’t previously plan for in the budget.
I’m now in charge of Payroll and the pay equity study's implementation; which both come before this work.
Some time will open up next week for me to look at the demo data a bit more. I looked today, and had to stop before I got very far.
Dieneke S
Thanks for checking in. I was unsure about the state of schema and whether or not it is ready, particularly the table “dam_contacts” replacing dedicated fields and lists.
That said, I haven’t had time to look at those things. We’ve just been informed that our finance director has an offer that we cannot meet or beat, and they are leaving in 2 weeks. I’ll be taking over a portion of their work while we attempt to hire anew.
This project remains a very important part of a grant which is due end of December. I’ll be doing what I can to keep this moving forward.
I’ll make time to assess my question noted above about contacts, and get some feedback back to you.
I do recall the next item for us was that I would be adjusting the sample data CSV files to match the new column names. That will be next, but it’s uncertain that I will make much progress in the next 2 weeks.
Appreciate you both. Thanks!
Message above from David
That said, I haven’t had time to look at those things. We’ve just been informed that our finance director has an offer that we cannot meet or beat, and they are leaving in 2 weeks. I’ll be taking over a portion of their work while we attempt to hire anew.
This project remains a very important part of a grant which is due end of December. I’ll be doing what I can to keep this moving forward.
I’ll make time to assess my question noted above about contacts, and get some feedback back to you.
I do recall the next item for us was that I would be adjusting the sample data CSV files to match the new column names. That will be next, but it’s uncertain that I will make much progress in the next 2 weeks.
Appreciate you both. Thanks!
Message above from David
Dieneke S
Chris, do you have any more notes on last weeks meeting with david of metro east? Whats the plan of action, new meeting needs to planned soon?
Cristobal M
Took note of 2 thins only:
Add a list of modules that are not entities (easy way to create modules+entity)
Scroll bar on editing metadata when a lot of fields
Add a list of modules that are not entities (easy way to create modules+entity)
Scroll bar on editing metadata when a lot of fields
Cristobal M
So at the end everything was working ok, all the time were the modules not configured properly 😅
Dieneke S
the appointment with David is today, please see agenda on things to do. the dev meeting today is before the meeting with David.
Attachments
Dieneke S
Metro east prep for meeting next week: 1. Allow Editing boxes to be used as entity tabs
2. Make sure Browse Asset UI works well and has a category tree
3. Make sure we can filter drop down lists such as adding a query filter: type="staff" (I think this is an old feature we had already) 4.
Make sure Render masks can combine two fields such as First and Last and dave it to the "Name" field
