Information Management Committee - Revision history

Anna Vesala at 06:28, 6 January 2014

2014-01-06T06:28:33Z

← Older revision		Revision as of 06:28, 6 January 2014
Line 1:		Line 1:
	Note: [http://en.wikipedia.org/wiki/Wikipedia:SPLIT Split] Information about social media used by EBC to [[IMC_Social_Media_Integration]]. This page should only describe the commitee work.		Note: [http://en.wikipedia.org/wiki/Wikipedia:SPLIT Split] Information about social media used by EBC to [[IMC_Social_Media_Integration]]. This page should only describe the commitee work.
	Information about the 2010 version of the Committee can be found [2010-~~11 Information Management Committee~~ here].		Information about the 2010 version of the Committee can be found [http://edmontonbikes.ca/w/2010-11_Information_Management_Committee here].

	'''DRAFT'''		'''DRAFT'''

Anna Vesala at 06:20, 6 January 2014

2014-01-06T06:20:39Z

← Older revision		Revision as of 06:20, 6 January 2014
Line 1:		Line 1:
	Note: [http://en.wikipedia.org/wiki/Wikipedia:SPLIT Split] Information about social media used by EBC to [[IMC_Social_Media_Integration]]. This page should only describe the commitee work.		Note: [http://en.wikipedia.org/wiki/Wikipedia:SPLIT Split] Information about social media used by EBC to [[IMC_Social_Media_Integration]]. This page should only describe the commitee work.
	Information about the 2010 version of the Committee can be found [~~http://edmontonbikes.ca/w/2010_Committees#Information_Management~~ here].		Information about the 2010 version of the Committee can be found [2010-11 Information Management Committee here].

	'''DRAFT'''		'''DRAFT'''
Line 108:		Line 108:
	* When was this TOR approved by the board?		* When was this TOR approved by the board?

	~~=== Meetings ===~~		=== Meeting Minutes ===
	==== Meeting Minutes ====		*
	* [[Committee Name Minutes November 2011]]
	* [[Committee Name Minutes December 2011]]
	* ~~[[Committee Name Minutes January 2012]]~~

Cwc at 04:31, 19 September 2012

2012-09-19T04:31:48Z

← Older revision		Revision as of 04:31, 19 September 2012
Line 84:		Line 84:
	==== Specific Annual Objectives ====		==== Specific Annual Objectives ====
	The above list may be too long and general. Things to be accomplished by the AGM should be listed here		The above list may be too long and general. Things to be accomplished by the AGM should be listed here
	===== Document the establishment of ~~Bikeworks~~ north =====		===== Document the establishment of BikeWorks north =====
	By August 31, 2012, the IMC will have added information about setting up the second location to:		By August 31, 2012, the IMC will have added information about setting up the second location to:
	http://www.bikecollectives.org/wiki/index.php?title=Bike_Collective_Starter_Kit		http://www.bikecollectives.org/wiki/index.php?title=Bike_Collective_Starter_Kit

Adam.burgess: /* Financial */

2012-06-11T16:52:48Z

Financial

← Older revision		Revision as of 16:52, 11 June 2012
Line 67:		Line 67:
	*Note: Microfiche conversion is not expected to be a budget item in the near future. The mere act of paginating and removing external dependencies from the information is important.		*Note: Microfiche conversion is not expected to be a budget item in the near future. The mere act of paginating and removing external dependencies from the information is important.

	'''-This stuff is already part of our operational budget. The committee as such should require no financial resources.'''		'''--This stuff is already part of our operational budget. The committee as such should require no financial resources.'''

	===== Staff =====		===== Staff =====

Adam.burgess: /* Staff */

2012-06-11T16:52:28Z

Staff

← Older revision		Revision as of 16:52, 11 June 2012
Line 78:		Line 78:
	* security analysis		* security analysis

	'''That would be great, but this is all operational, so they'd be working for staff, not for a committee of the board.'''		'''--That would be great, but this is all operational, so they'd be working for staff, not for a committee of the board.'''

	Support from the Treasurer and Secretary in ensuring digital copies of documents are properly archived, and that significant paper documents are digitized and/or copied to microfiche (where it is likely to be useful and reasonable).		Support from the Treasurer and Secretary in ensuring digital copies of documents are properly archived, and that significant paper documents are digitized and/or copied to microfiche (where it is likely to be useful and reasonable).

Adam.burgess: /* Staff */

2012-06-11T16:52:09Z

Staff

← Older revision		Revision as of 16:52, 11 June 2012
Line 81:		Line 81:

	Support from the Treasurer and Secretary in ensuring digital copies of documents are properly archived, and that significant paper documents are digitized and/or copied to microfiche (where it is likely to be useful and reasonable).		Support from the Treasurer and Secretary in ensuring digital copies of documents are properly archived, and that significant paper documents are digitized and/or copied to microfiche (where it is likely to be useful and reasonable).

	~~'''Yes, possibly.'''~~

	==== Specific Annual Objectives ====		==== Specific Annual Objectives ====

Adam.burgess: /* Staff */

2012-06-11T16:51:25Z

Staff

← Older revision		Revision as of 16:51, 11 June 2012
Line 77:		Line 77:
	* statistics		* statistics
	* security analysis		* security analysis

			'''That would be great, but this is all operational, so they'd be working for staff, not for a committee of the board.'''

	Support from the Treasurer and Secretary in ensuring digital copies of documents are properly archived, and that significant paper documents are digitized and/or copied to microfiche (where it is likely to be useful and reasonable).		Support from the Treasurer and Secretary in ensuring digital copies of documents are properly archived, and that significant paper documents are digitized and/or copied to microfiche (where it is likely to be useful and reasonable).

			'''Yes, possibly.'''

	==== Specific Annual Objectives ====		==== Specific Annual Objectives ====

Adam.burgess: /* Financial */

2012-06-11T16:49:46Z

Financial

← Older revision		Revision as of 16:49, 11 June 2012
Line 66:		Line 66:
	*Office supplies		*Office supplies
	*Note: Microfiche conversion is not expected to be a budget item in the near future. The mere act of paginating and removing external dependencies from the information is important.		*Note: Microfiche conversion is not expected to be a budget item in the near future. The mere act of paginating and removing external dependencies from the information is important.

			'''-This stuff is already part of our operational budget. The committee as such should require no financial resources.'''

	===== Staff =====		===== Staff =====

Adam.burgess: /* Level of Authority */

2012-06-11T16:48:26Z

Level of Authority

← Older revision		Revision as of 16:48, 11 June 2012
Line 44:		Line 44:

	===== Level of Authority =====		===== Level of Authority =====
	Much of this committee's work is very public-facing, and may be the first interaction people have with EBC. Any major, public-facing changes, therefore (such as a website redesign) should be passed before the board for review, though decisions can be made by the committee without a board vote once a reasonable amount of time has been given for review (unless the board indicates otherwise during this review period).		Much of this committee's work is very public-facing, and may be the first interaction people have with EBC. Any major, public-facing changes, therefore (such as a website redesign) should be passed before the board for review, though decisions can be made by the committee without a board vote once a reasonable amount of time has been given for review (unless the board indicates otherwise during this review period). '''--something like a website redesign would be an ED responsibility.'''
	Decisions involving a significant new financial cost or liability to EBC must first be recommended to the board for approval.		Decisions involving a significant new financial cost or liability to EBC must first be recommended to the board for approval.
	Decisions involving significant privacy or security concerns must also first be recommended to the board for approval.		Decisions involving significant privacy or security concerns must also first be recommended to the board for approval.
			'''--The committee's work should be to propose new policy and solutions for it's implementation. There's no need for it to be making independent decisions.'''

	===== Reporting Relationship =====		===== Reporting Relationship =====

Adam.burgess: /* Key Duties and Responsibilities */

2012-06-11T16:42:16Z

Key Duties and Responsibilities

← Older revision		Revision as of 16:42, 11 June 2012
Line 23:		Line 23:

	==== Key Duties and Responsibilities ====		==== Key Duties and Responsibilities ====
	#Selection and maintenance of computer equipment used by EBC. -staff responsibility		#Selection and maintenance of computer equipment used by EBC. '''-staff responsibility'''
	#Selection and maintenance of paper/microfiche handing equipment. -staff responsibility		#Selection and maintenance of paper/microfiche handing equipment. '''-staff responsibility'''
	#Selection and maintenance of software used by EBC. -staff responsibility		#Selection and maintenance of software used by EBC. '''-staff responsibility'''
	#Document any web services used by EBC, including any Terms Of Service or Privacy Policies that apply (review annually). -possible volunteer project, ~~maybe~~ not a board project?		#Document any web services used by EBC, including any Terms Of Service or Privacy Policies that apply (review annually). '''-possible volunteer project, not a board project'''
	#Developing a security policy for access to sensitive documents, taking into account Board turn-over. -yes, this is policy:)		#Developing a security policy for access to sensitive documents, taking into account Board turn-over. '''-yes, this is policy:)'''
	#Develop a data archival and destruction policy. Automate as much as is practical. -yes, this is policy:)		#Develop a data archival and destruction policy. Automate as much as is practical. '''-yes, this is policy:)'''
	#Improve organizational transparency with open data initiatives (http://sunlightfoundation.com/policy/documents/ten-open-data-principles/) -possible volunteer project~~, maybe not a board project? (Could~~ be policy work as long as it doesn't commit us to standards beyond our current resources.)		#Improve organizational transparency with open data initiatives (http://sunlightfoundation.com/policy/documents/ten-open-data-principles/) '''-possible volunteer project; could be policy work as long as it doesn't commit us to standards beyond our current resources'''
	#Collaborate with other organizations facing similar challenges to those above. (For example, the EFF has an almost dead program to [http://www.tosback.org/timeline.php track TOS and Privacy Policy changes]) Bike Calgary has expressed interest in collaborating with us in the past. bikeroot.ca has apparently developed some kind of shop management system we may want to investigate. -this is a potential implication of working on ''any'' problem.		#Collaborate with other organizations facing similar challenges to those above. (For example, the EFF has an almost dead program to [http://www.tosback.org/timeline.php track TOS and Privacy Policy changes]) Bike Calgary has expressed interest in collaborating with us in the past. bikeroot.ca has apparently developed some kind of shop management system we may want to investigate. '''-this is a potential implication of working on ''any'' problem.'''
	#Work with other committees to help them with any data storage needs -		#Work with other committees to help them with any data storage needs '''-needn't be explicit here'''
	#Maintaining websites (stolenbikes, brb, cycleedmonton, edmontonbikes, ghostbikes.org, bikecollectives.org). -staff responsibility		#Maintaining websites (stolenbikes, brb, cycleedmonton, edmontonbikes, ghostbikes.org, bikecollectives.org). '''-staff responsibility'''
	#Find or develop a program to send event notices to Website, (Google) Calender, Facebook, and Twitter all at the same time (Use RSS feed?). -volunteer project in cooperation with staff, not board		#Find or develop a program to send event notices to Website, (Google) Calender, Facebook, and Twitter all at the same time (Use RSS feed?). '''-volunteer project in cooperation with staff, not board'''
	#Document how we went about opening the second location so that others can benefit from our experience. -a volunteer project		#Document how we went about opening the second location so that others can benefit from our experience. '''-a volunteer project'''
	#Migrating primary EBC website to new platform (Wordpress) -staff responsibility (volunteer help may be welcome, I'~~m sure~~)		#Migrating primary EBC website to new platform (Wordpress) '''-staff responsibility (volunteer help may be welcome, I don't know)'''
	#Maintain phone and network equipment -staff responsibility (volunteer help may be welcome~~, I~~'~~m sure)~~		#Maintain phone and network equipment '''-staff responsibility (volunteer help may be welcome)'''
	#Monitoring and archiving media -staff responsibility (volunteer help may be welcome~~, I~~'~~m sure)~~		#Monitoring and archiving media '''-staff responsibility (volunteer help may be welcome)'''
	#Maintain EBC Library/bookshelves -volunteer (this may be Micah's pet project)		#Maintain EBC Library/bookshelves '''-volunteer (this may be Micah's pet project)'''
	#Some data entry, collection of photos for EBC use. -volunteer in cooperation with staff		#Some data entry, collection of photos for EBC use. '''-volunteer in cooperation with staff'''
	#Audit IPv6 compliance. -fine as a pet project, below board level		#Audit IPv6 compliance. '''-fine as a pet project, below board level'''
	#Audit bandwidth usage as needed. -fine as a pet project, below board level		#Audit bandwidth usage as needed. '''-fine as a pet project, below board level'''

	===== Level of Authority =====		===== Level of Authority =====