2016 NOLA Fellowship project | A mobile-first website that acts as a digital one-pager for the workforce system in New Orleans, reducing drop-off by setting proper expectations and preparing job seekers for their first visit.
As a job seeker in an underserved population who has limited access to the internet register for career evaluation so that I may receive information that helps me prioritize my job search based on workforce development focused industries. CFA questions (1).xlsx
As a user, I would like to get information about any certification requirements and available training, so that I can be prepared to begin my career path.
As a user, I want to answer all questions in the questionnaire before being matched with potential career paths, so that I can be sure that I have all available options.
Instead of not asking questions, when we are stuck on something for more than 30 minutes or so, try to chat with each other, look at the internet, or we should try to ask other developers to attempt to solve issues instead of giving up or blindly experimenting.
Issues #31, #32, #33
What's there currently: Most of the work has been finished for this task. Currently, after submitting the job form, an email will be sent out to the proper clients. This is currently being achieved through AWS SES. It sends parameters from the submission into the function and displays parameters in the email as well as grabbing emails and names from these parameters. Due to some app restrictions, the emailer is split up into different parts in the app, with a chunk being in the app file and the other chunk in a separate file.
There is a pull request #53 for this.
What's left to be done: Email to opportunity centers have to be properly sent. As of now, there is no way to grab opportunity center emails from the job form after it has been submitted, so there is no way to email the proper opportunity center. As such, the email functions have to be accommodated to work with dynamic opportunity center emails. Ideally, they would be parameters. This relies on the manage page in issue #54.
Who did it: @tmloupe
The database does not correctly setup at the moment due to outdated seeds. The seed has to change so it lets the database work on a fresh creation of a database.
What's there currently: Currently the form structure is complete. It receives input from the user and sends them as parameters to the app to be processed. Additionally, with each submission, it sends it to a spreadsheet with all the parameters listed in order. There
What has to be done: Finish setting up the database for parameter entry for security reasons (No idea on the progress for this one, we had it working for a while but no definitive answer. There is a form_db branch with our work on this). Implementing dynamic opportunity center info grabbed from the manage page from issue #54 and sending it to be processed for emails as in issue #55.
Who worked on it originally: @jusantana
As a developer of this project, I would like to in-source the Job System form so that I may develop other user stories dependant on the output of this form.
Some requirements:
Ensure all fields needed are present
Validate input (needs conversation about what to validate)
Figure out storage solution
Match styling of site
As a registrant, I would like to have the Opportunity Center contact stay on screen after I submit so that I may take action without waiting for a reply or email.
As the clearinghouse for Job System registrants, I would like at least one method of contact information to be required, so that I may reach the registrant.
Create a template that that gives a more comprehensive picture of what help, concerns, and/or blockers we encounter to help enable greater communication within the team.
Issue #34.
What's there currently: The manage page itself is updated with HTML but has no connectivity to changing information on a spreadsheet. The issue is to input opportunity center information into the proper fields, updating the respective opportunity centers in the spreadsheet and updating them within the app. There is a pull request for this issue: #49.
What's left: Implementing connectivity between the manage page, the spreadsheet with opportunity centers, and the app as a whole. Currently there is no spreadsheet(?) as well to test changes. The manage page has to be able to change emails on the spreadsheet from the app as well as updating the app's internal opportunity center info.
Who did it originally: @maahern
As a prospective client of Opportunity Centers receive immediate contact via follow up from email notification by the agency recommended by job readiness and barrier/need criteria. OC Matrix with contacts (1).xlsx