Same goes for an empty term

The statute reference right now is only plain text. It is meant to be a human readable description of a place in the municpal code.

We would also like to link directly to the relevant section on the municipal code website. We probably need a seperate field for the Statute URL.

It would be more convenient to have an edit button on the /committees/view screen.

Changing committee type in a data entry error situation requires some cleanup work in the database.

Changing the type in the situation of a change in charter has different things that should be done with the existing terms.

Because of these two cases, it's probably best, for now, if we limit the changing of committee type to Administrators only. I'm more comfortable deferring writing code to handle all the possible eventualities. I think we can expect the Admin to know what cleanup they want to do for each situtation.

I got hasty and took shortcuts while building the application. Not all the text is inside the language file, and cannot be translated.

Sometime, I need to spend some time moving all the rest of the text into the .po file

Currently, only P2Y is an option for selection

If a seat is currently appointed, there should still be an option to reappoint the current member for that seat.

Any time reappoint is available, clicking reappoint should take you to a new page to confirm the reappointment, rather than automatically performing the action.

If a reappointment has already been configured for the next term, the confirmation page should inform the user of this condition (same route as reappointment confirmation page). If the user is an admin, there should be a link to edit the seat details from this message page. If the user is a staff account, inform them that changes to this configuration must be requested from an administrator.

It would be nice if seats or terms could declare other people as alternates or proxies.

BZA has alternates. Council has one alternate for one council appointee.
Mayor has one (or more) alternates for multiple appointees.

If the seat is open, there is no fixed term length.
Also, language files should be updated so that "termLength" is displayed as "Term Length"

Sample open seat page showing term length:
http://rogue.bloomington.in.gov/boards-staging/seats/view?seat_id=65

Currently the title of resign says "Add an appointee to ...". This should be updated to reflect the action of resign / ending membership.

For example:
http://rogue.bloomington.in.gov/boards/members/resign?member_id=1

When viewing the details of a seat, the Type should be capitalized ('Termed' or 'Open').

For the Requirements field, the data entered should be displayed with line breaks that were entered in the text input. Currently all lines run together:
http://rogue.bloomington.in.gov/boards-staging/seats/view?seat_id=16

application needs to have feeds capable of being read by CKAN for

• current vacancies and
• full commission memberships
• actions/votes

We want to support markdown for all of the description fields that users type.

Drupal is going to be reaching out to this application to display any and all information related to boards and commissions.

We need to create feeds for the information that Drupal desires.

We need to separate out member info and description when listing these things in drupal

Stuff like:

Arts Commission has appointments with term limits: only 2 consecutive
terms.

While this seemed like a good idea at the start, in practice it gets out of control, and doesn't offer much. It turns out to be insanely hard to try and codify all the detailed, special rules for seats.

Since we are already linking each committee to the establishment definition in the municipal code, I think we can rely on that to describe requirements for membership in commissions.

We should just delete the requirements feature from the system. The system will be simpler and better for it.

The seats number shown in the list is not matching what's displayed when you view the committee.

See the MPO Citizens Advisory Committee, for example.

Fatal error: Cannot use object of type Zend\Db\ResultSet\ResultSet as array in /srv/sites/committee_manager/blocks/html/people/committees.inc on line 24
on this page:
https://apps.bloomington.in.gov/committee_manager/people/view?person_id=25

At a minimum the date fields should show a placeholder of the format expected.

I like the option of using . Firefox support isn't there yet, but it looks like there is momentum in that direction:
https://bugzilla.mozilla.org/show_bug.cgi?id=825294

If the date input type falls back to a standard input with placeholder text, that should be viable and adapt well to browser updates.

This reference gives support for using 3 separate text fields:
https://designnotes.blog.gov.uk/2013/12/05/asking-for-a-date-of-birth/

The last option would be to use a javascript polyfill to get calendar functionality.

I know that this discussion has come up on other projects, so hopefully this is a chance to document the decisions we make, or updates to best practices.

Currently, when a board member's term expires they will no longer be returned in results. Ideally, if no one else has been assigned to that position, the original person would be shown in the "Carryover" period.

We need to discuss a more fitting name for this project

Committee name and Seat name should link to the corresponding view of that item.

(http://rogue.bloomington.in.gov/boards-staging/committees/vacancies)

After creating a new seat, the seat details page has an error because no terms have been associated with the seat yet.

After creating an empty seat, the following message is shown on a seat detail page (example: http://rogue.bloomington.in.gov/boards-staging/seats/view?seat_id=14)

Notice: Indirect modification of overloaded property Blossom\Classes\Block::$terms has no effect in /srv/sites/boards-staging/blocks/html/terms/list.inc on line 20

Ability to track board/commission activity and votes needs to be a setting that can be enabled/disabled for individual boards/commissions and enabled/disabled for the entire system.

It should be possible to export a CSV file containing:

• current vacancies and
• full commission memberships

The output for the full commission memberships should include:
Board Name,Seat Name / Type,Appointed By,Person,Current Term Dates

This functionality should be available to everyone.
This functionality may satisfy issue #5

We have several people in seats that want Dr. or Mrs. in front of their name.

We should add a seperate field for honorific, otherwise, it's getting added into the firstname field, which makes it harder to search for people.

When editing a seat, it is possible to create previous terms, but there is no way to associate who served those terms. This should be an admin only function for editing historical data.

We're wanting to put more and more formatted information into these fields. We need to extend the fields and make them parsed as markdown.

Seated committees are how committees work right now. In order to have membership, you have to create a seat with which to associate member terms.

We want to allow for open committees as well.
Open committees will not require seats to be created. Members can just serve terms on the committee without the extra seat requirements.

When you're logged in and looking at the members of a board, when a vacancy is displayed, add a link to add a person to it.

I realize this will bring up the problem of whether or not this person exists yet. Can we use some of the same UI techniques for entering a case in uReport when given the choice of adding a new person or choosing an existing one?

Some commissions just have general membership. Anyone who wants to can be a member, and just show up to meetings.

Currently, when editing a seat, the Cancel button will go back to the (deprecated) seat list.

Instead, it should return to the seat details view.

For example, editing:
http://rogue.bloomington.in.gov/boards-staging/seats/update?seat_id=16

Cancel goes:
http://rogue.bloomington.in.gov/boards-staging/committees/seats?committee_id=9

but should go:
http://rogue.bloomington.in.gov/boards-staging/seats/view?seat_id=16

We do not have exact dates for hardly any of these. It is sufficient to know the year the committee was created.

We should change the date formed to be year only.

I cannot remember why we ever put the synopsis field in. It would have the same information as the description. We should just drop this field.

We need a few standard reports for board membership... sex, race, duplicate people, people serving on multiple boards, and board vacancies.

Instead of the word Race, we want to use Ethnicity

We're using font awesome for both apps. Let's keep things as consistent as we can by using the same add, edit, delete, search icons. This should be a default for any application we develop - to try to use the same skinning rules and graphics whenever possible.

Once a new term is added, take the user back to the members tab. I'm training people to add terms off that tab, but after successfully adding a term, it takes you to the seats tab

YUI has been end of lifed. We should switch over to jQuery

When doing an "Add Term" we should be helpful to the city employee doing the data entry. We should autopopulate the person for the new term with the previous person who was filling that seat.

Currently, adding a new seat will redirect back to the seat list. The default action should be to show the details for the newly created seat.

Currently the Cancel button is very close to the save button and is easy to accidentally hit and lose changes.

Additionally, the "rollback / reload" like icon is not the best choice for the action.

Ex-Officio seats are not showing up as vacant, even with no current member assigned. For example:
http://rogue.bloomington.in.gov/boards-staging/committees/members?committee_id=9

Recently, the ability to add a new term (term management) became unavailable:
http://rogue.bloomington.in.gov/boards-staging/seats/view?seat_id=24

People table needs...

a field for personal URL (homepage, blog, facebook or twitter)

Also for race we should use these census categories and descriptions. Users may select more than one category. These are not mutually exclusive.

White – A person having origins in any of the original peoples of Europe, the Middle East, or North Africa.

Black or African American – A person having origins in any of the Black racial groups of Africa.

American Indian or Alaska Native – A person having origins in any of the original peoples of North and South America (including Central America) and who maintains tribal affiliation or community attachment.

Asian – A person having origins in any of the original peoples of the Far East, Southeast Asia, or the Indian subcontinent including, for example, Cambodia, China, India, Japan, Korea, Malaysia, Pakistan, the Philippine Islands, Thailand, and Vietnam.

Native Hawaiian or Other Pacific Islander – A person having origins in any of the original peoples of Hawaii, Guam, Samoa, or other Pacific Islands.

Hispanic or Latino Origin - People who classify themselves as “Mexican, Mexican Am., Chicano” or ”Puerto Rican” or “Cuban” – as well as “another Hispanic, Latino, or Spanish origin." People who identify their origin as Hispanic, Latino, or Spanish may be of any race.