Technology Committee/2016-04-22
From PCSAR
(Difference between revisions)
| Line 45: | Line 45: | ||
* moving pcsar server to commercial host | * moving pcsar server to commercial host | ||
** not necessarily Canadian host | ** not necessarily Canadian host | ||
| + | ** consider whipport.com in Lethbridge | ||
| + | ** upgrade the distribution | ||
| + | ** better DNS | ||
| + | * email services | ||
| + | ** president@pcsar.ca | ||
| + | ** email portal webmail | ||
| + | ** email archive accessible to members | ||
| + | ** consider google for business | ||
* hand-off access to server (root) | * hand-off access to server (root) | ||
* orientation to RapidNotify | * orientation to RapidNotify | ||
| Line 50: | Line 58: | ||
* custom mapping | * custom mapping | ||
** standard search segments | ** standard search segments | ||
| + | ** can we use front end tools that don't require much training | ||
* GPS data integration | * GPS data integration | ||
** download data from members GPS's or PCSAR's GPS's | ** download data from members GPS's or PCSAR's GPS's | ||
| Line 68: | Line 77: | ||
* what offloads work from people that are busy | * what offloads work from people that are busy | ||
| + | actions: | ||
| + | * investigate simple creation search polygons (segment boundaries) | ||
| + | * what will it take to set up dedicated machine to collect GPS data | ||
Revision as of 03:02, 23 April 2016
Contents |
Booking
Meeting location, date, time and duration.
- 2016-04-22 19:00 by phone
Participants
List who should participate and indicate for each person whether they've been invited, have confirmed or declined, and attended.
Agenda
Purpose of meeting or detailed agenda.
- brainstorm tools for inventory
- ideas of what the committee should work on
- D4H bot password (done)
Handouts
Any related documents distributed before or during the meeting.
Minutes
Rough notes or formal minutes of the meeting.
mediawiki
- MonoDB
- semantic mediawiki
Equipment Committee
- Bill
D4H
- would have to expand who has access to system
- has good list of typical fields
- risk of severed relationship
- not integrated into wiki
- cross-links to wiki - not active, no field type for HTML or URL
- chance that we might not have D4H
trickle strategy
to do:
- verify that D4H equipment can be fully exported (or at least all that's important to us)
- request custom field type for clickable URLs
- Develop plan for provincial digital radio system
- investigate adding LASARA channel to PCSAR radios
- moving pcsar server to commercial host
- not necessarily Canadian host
- consider whipport.com in Lethbridge
- upgrade the distribution
- better DNS
- email services
- president@pcsar.ca
- email portal webmail
- email archive accessible to members
- consider google for business
- hand-off access to server (root)
- orientation to RapidNotify
- orientation to Phone.com
- custom mapping
- standard search segments
- can we use front end tools that don't require much training
- GPS data integration
- download data from members GPS's or PCSAR's GPS's
- load GPS with waypoints, route, base map, or segment area (geofence)
- examine whether cheaper phone configurations (627-2262)
- examine cost of sat phones and alternatives
- how to integrate member's inReach devices into search
- plan increase in number of team inReach devices
- automating inReach rate changes
- computer in MCP
- dedicated
- data connectivity at MCP
setting priorities
- what saves money
- what creates most impact
- what offloads work from people that are busy
actions:
- investigate simple creation search polygons (segment boundaries)
- what will it take to set up dedicated machine to collect GPS data
Suggestions
List suggestions for future actions that came up during this meeting.
| # | Suggestion | Referred to |
|---|---|---|
| 0001 | determine how much of D4H equipment data can be easily exported | technology |
| 0002 | request D4H custom field type for clickable URL | technology |
| 0003 | Show tech committee how to support RapidNotify | technology |
| 0004 | Show tech committee how to support Phone.com | technology |
| 0005 | provide technology committee root access to server | technology |
