edbirmingham/network

Facilitates beneficial connections in a network of people.

network's Issues

Upgrade to newest MEAN/Node versions

Import match data

This issue requires access to a spreadsheet with private information so it can only be completed by a committer. The data will require significant parsing so it is easier to look at the data than to describe well enough to for someone to implement this.

Fields:

• Member
• Action (Offering, Request, Declaration, BOTN)
• Match With?
• Status
• Connect With?
• Notes/Progress
• Next Steps
• Owner(s)

See the story of release 0.1.0 for context.

Import participant communication consent

When the participants were imported, the ability to specify consent to be communicated with was not implemented. The information from the google docs needs to be added to the Network Database.

Match network actions

Network actions ( #26 ) that were recorded need to be matched with people. This may happen immediately or at some later point in time. An initial version of this may be very simple but this is where the magic will happen as we create various ways of making the matches happen.

Setup hosting on Heroku

Setup an account with edbirmingham for the application to be hosted with a mongodb database. Get the application deployed and working. Once this is done then #15 to Heroku can be setup.

See the story of release 0.1.0 for context.

High level application UI design

Design the high level navigation and the Birmingham Education Foundation branding of the Network.

See the story of release 0.1.0 for context.

Add Educator Roundtable event type

Add Education Roundtable to the static list of event types. Issue #57 will add dynamic event type registration.

Add participant communication consent

In order to respect participants privacy, as a participant I want to be able to inform Ed that I don't want to be communicated with concerning the network.

Make participant quick search unambiguous

In order to differentiate participants with the same name, as a volunteer or administrator I want to see the participant's phone number and email address when selecting them from a quick search typeahead box.

Developer Notes:

• These should be able to be found with git grep typeahead.

Add photographs to the member signup page

See discussion in #21 concerning photographs.

Understanding:

• Participant comes to member sign up table
• Volunteer registers new member using interface
• Takes picture/picture is logged in their membership record
• Volunteers/Connectors are able to use picture to remember what member looks like during Network Night and when following up with member

Benefits

• Makes it easier to identify people in the interface. (Or does it? They have name tags.)
• Puts a picture with matches and nodes automatically for the Hot List

Concerns

• Might be off-putting to some people.
• Privacy issues.
• Camera API for the browser their tablet uses.
• This could slow membership registration down some--explaining the picture taking process, members asking why their picture is taken, etc.
• Unless privacy was checked off during registration, this becomes a huge concern. This does make me think that we need to add a privacy question on the registration....something to this effect: "We take pictures to capture the story unfolding during Network Night. Do you give us permission to take photos of you/around you?"

Member administration

Functionality:

• List members in alphabetical order by name with pagination.
• Create a member.
• Edit a member.
• Delete a member.
  See: #18, #20

See the story of release 0.1.0 for context.

Security

Make sure that security is in place for all server routes. Users must be logged in for everything but logging in.

Setup continuous deployment.

When pull requests are merged into master and the tests pass then they should be automatically deployed to the site. Initially this will be Heroku.

Document the purpose of the project

This project is to facilitate the Birmingham Education Foundation's Raise Up Network. We need to document this at the beginning of the README so people will know what the project is all about.

http://edbirmingham.org
https://www.youtube.com/watch?v=OI0qip6XlZc
http://edbirmingham.org/asset-mapping/

Setup creation of an automated development environment.

If the app is going to be frontend and api combined then Vagrant may work. If they are separate services then something Docker based would probably be good.

Import Member Data

Import data for members is in the following csv format.

,Name,Phone,Email,Mailing Address,Who are you? ,Affiliation?,T-Shirt Size,What are you good at? What do you have a talent/passion for? ,Neighborhood/Community Network # 1,Place of Worship,Extracurricular Group # 1,Other Network # 1,Neighborhood/Community Network # 2,Neighborhood/Community Network # 3,Extracurricular Group # 2,Extracurricular Group # 3,Other Network # 2,Other Network # 3
7/25/2015 10:59:32,Anthony Crumley,999-490-9432,[email protected],50 18th Street N,Community Partner,BCRI,L,"History, Art, Education",,,,,,,,,,
7/25/2015 11:29:03,Martha Lake,999-287-6916,[email protected],"19 Grove Road Town, AL 35346",Community Partner,Birmingham Bank,L,Finance,Town,"First Baptist Church Town, AL",,,,,,,,
7/25/2015 11:08:56,Sangra Mars Jones,999-596-2798,[email protected],"56 Ave Z Birmingham, AL 35284",Parent,Ramsay HS,2XL,"Cooking, programs",,St. John Christian Center,,,,,,,,
7/25/2015 11:12:58,Daniel Rehner,999-910-3732,[email protected],"33 4th S Birmingham, AL 33285",Resident,ACE,M,Engaging Community,,St. Francis Assisi,Frisbee,,,,,,,

See the story of release 0.1.0 for context.

Record attendance

We need to be able to record every time a person attends. This will give the attendance at each network night event as well as the number of events a person has attended.

Details:

• Everyone who participates in ANY Birmingham Education Foundation event is a "Participant"
• Some "Participants" register as a "member" of the Ed Network
• Some "Participants" attend multiple events, and do not register as "members" of the Ed Network

Issue:

• The database needs to be able to sign in new "Participants"
• The database needs to efficiently check in Ed Network "Members"
• The database needs to efficiently check in return "Participants" (non-members)
• The database needs to records the number of events that all "Participants" (members and non) have attended

See the form screenshot in #21, particularly the "Number of students with you?" question.

Import additional participant data

Once Marshall has provided a comprehensive participant spreadsheet, import the additional participants.

Create initial code base.

Generate an initial project that we will begin with.

Setup code style analyzer

Setup something like https://houndci.com/ and https://codeclimate.com/oss to do static code analysis and comment on pull requests.

Add photographs to the sign in page

See discussion in #21 concerning photographs.

Understanding:

• Participant comes to sign in table
• Person signs in using interface
• Takes picture/picture is logged in their sign in file
• Volunteers/Connectors are able to use picture to remember what participant looks like during Network Night and when following up with participant

Benefits

• Makes it easier to identify people in the interface. (Or does it? They have name tags.)
• Puts a picture with matches and nodes automatically for the Hot List

Concerns

• Might be off-putting to some people.
• Privacy issues.
• Camera API for the browser their tablet uses.
• This could slow sign in down significantly--explaining the picture taking process, participants asking why their picture is taken, etc.
• Unless privacy was checked off during sign in, this becomes a huge concern. This does make me think that we need to add a privacy question on the sign in....something to this effect: "We take pictures to capture the story unfolding during Network Night. Do you give us permission to take photos of you/around you?"

Setup continuous integration.

Setup a service like Jenkins that will run the test suite every time a commit is made to the repository.

Add contributing information

The contributing section of the readme is empty. Instructions need to be given so people know what to do beyond the setup instructions.

Sign In Participants

As a volunteer, I want to sign in new participants so that they are known in the network and can be interacted with.

See the story of release 0.1.0 for context.

Acceptance Criterion 1:

Given that the participant is attending their first Ed event
And they were not previously entered into Network by a connector
When they arrive at an Ed event
Then ensure that they were not previously entered into Network
And record their name
And record their phone number
And record their email address
And record their identity (student, parent, educator, resident or community partner
And record their affiliation (i.e. UAB, Carver High School, Literacy Council)
And submit the participants information
And Network is ready for the next participant

Acceptance Criterion 2:

Given that the participant was previously entered by a connector
When they arrive at an Ed event
Then find them in the Network
And mark them as attended
And inform them that they are in Network
And inform them that next time they can just go through the record attendance line ( #35 )
And Network is ready for the next participant

Acceptance Criterion 3:

Given that the participant is attending their first Ed event
And they were not previously entered into Network by a connector
And they are able to enter themselves into the Network
When they arrive at an Ed event
And a volunteer determines they are able to enter themselves into the Network
Then the volunteer ensures that they were not previously entered into Network
And the volunteer gives a tablet to the participant
And they enter their name
And they enter their phone number
And they enter their email address
And they enter their identity (student, parent, educator, resident or community partner
And they enter their affiliation (i.e. UAB, Carver High School, Literacy Council)
And they submit the information
And Network is ready for the next participant
And the participant gives the tablet back to the volunteer

Notes

• The comments related to photographs are not part of this issue. New issues were created to implement that separately. See issues #29 and #30.
• See the google form screenshot below as an example.
• The "Number of students with you?" question is really part of recording attendance which is in issue #35 and should not be implemented in this issue.

Create separate volunteer application

The volunteers need a separate application that does not require a login and will only allow participant signup/checkin/update and member registration. It will only work on the day of the event and should have an event specific password.

Record network actions

During a network event, actions occur which need to be recorded. These actions are requests, offers, declarations and Business of the Network (BOTN). Requests are made by network participants for resources or opportunities that they need. Offers are made by network participants of resources or opportunities they are willing to provide. Declarations are made by participants to inform of resources or opportunities that exist in the community. Business of the Network is a conversation that results in a set of ideas and next steps. These actions need to be recorded with the type, person, description and matches.

See the story of release 0.1.0 for context.

Setup code review bot like Hound.

Setup a super simple development environment like Cloud9.

This is intended to make it easy for beginner developers and those who don't have powerful machines to be able to participate.

Follow-up on network actions

Follow-up on network actions is very important. If there is no follow-up then the network will have little to no effect. Currently follow-up is a manual process. Automating and managing the process with CRM like functionality would be very helpful. Basic functionality would be to email each person who made a request or offer along with the matches. This email should contain a description of the request or offer and contact information for everyone involved. The ability to print the same information at the network event and hand it to the people before they leave would be good as well. Especially since some people don't have email addresses.

Give success feedback on participation create

When participations are being created, the form refreshes on success so that another participation can be created but no success message is displayed. A success message should be displayed like on the Action create page.

Network Member Registration

During a network night, some participants will become network members. A volunteer will enter people into the system as members. Members are participants with extra information and a membership indicator.

See the story of release 0.1.0 for context.

Focus on Find participant field

After a participation is successfully created, the focus should be on the Find participant field like on the Action create where focus is set to the actor field. This will allow more efficient signin of participants.

Import participant data

Add Administrator permission

On the user edit/create screen there needs to be a checkbox to determine if the user is an administrator. This administrator selection then needs to be persisted for the user. This permission will be used to authorize user access to administrative functionality.

Match board view

A screen for viewing the match board. This will be used to see the matches for an event to be able to follow-up with the people who were matched to provide them with contact information and encourage them to follow through with their commitment. This will primarily be done by the connectors.

This will need the ability to assign a connector to the action and specify a status of the action.

See the story of release 0.1.0 for context.

Merge duplicate participants

In order to have more useful and accurate data, as a Network Database administration I want to be able to merge participants without loosing related information such as actions, matches and event participation.

Add location administration

Add functionality for listing, creating, editing and deleting network event locations. Authorization to perform this functionality needs to be controlled by the administrator permission #12.

See the story of release 0.1.0 for context.

Remove Articles Functionality

The MEAN.JS generator added example functionality and it needs to be removed. It is CRUD functionality for Articles.

Create contributor guidelines.

Create a contributor document. This can be based on contributor documents from other good open source projects.

Returning participant checkin

As a volunteer, I want to record people's participation in events so that network activity can be measured and used to better understand the effectiveness of the network.

Acceptance Criterion 1:

Given that the participant has attended a previous network event
And has been entered into the network database
When they return to another network event
Then ensure that a duplicate participant is not created
And record an attendance for the participant including the location and date/time

Implementation Notes:

• Ensure that the Participant Sign-in form ( #21 ) does not create duplicates.
• See the story of release 0.1.0 for context.

Participant Administration

Functionality:

• List participants in alphabetical order by name with pagination.
• Create a participant.
• Edit a participant.
• Delete a participant.
• See #21 .

See the story of release 0.1.0 for context.

Add user administration

Add functionality for listing, creating, editing and deleting users. Authorization to perform this functionality needs to be controlled by the administrator permission #12.

See the story of release 0.1.0 for context.

View participants at an event

There needs to be a Participations list view that shows all the participants at an event. It would be nested under the NetworkEvent like the Participations create view.

Improve error message display on forms

Currently the messages are displayed as...

<div data-ng-show="error" class="text-danger">
    <strong data-ng-bind="error"></strong>
</div>

They would look a lot better and be more obvious if they were displayed something like...

<alert data-ng-show="error" data-ng-bind="error" type="error"></alert>

Remove Signup functionality

Users will not be able to sign themselves up for Network initially. The initial usage will be closely controlled by the EdBirmingham. We just want to remove access to the signup, not all the signup functionality. It will probably be used in the future.

• Remove the link to the signup page.

See the story of release 0.1.0 for context.

Gather all participant data

Gather all previous participant information into one spreadsheet so it can be added to the Network Database. Put the spreadsheet in an Ed google doc.

Ed Network T-Shirt Collection Tracking

Participant joins the Network. Participant name and t-shirt size go into a repository.

As participant joins the network they can receive t-shirts in two ways:

1. Participant receives simultaneous to joining
2. Participant picks up t-shirt at an event (Network Night/CDC/in school presentation) AFTER having joined the Network

As soon as participant has received t-shirt, they will be logged in this repository.

Program management

Currently they are static, they need to be dynamically creatable.

Coding Conventions

Determine coding conventions we will follow and reference them in the documentation. See also #3

Change Raise Up name

When creating and editing an event type, there is an option for the "Raise Up Network". This should instead say "Raise Up Initiative"