Changes between Version 214 and Version 215 of CoPCallAgenda


Ignore:
Timestamp:
03/13/17 16:17:28 (5 years ago)
Author:
Lois Haggard
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CoPCallAgenda

    v214 v215  
    1 == Monday, April 17, 2017 .  3:00 to 5:00 EDT (1:00 -3:00 PM MDT) (NM Hosting Dial-in: +1 ()  - Meeting ID: ) ==
     1== Monday, April 17, 2017 - 3:00 to 5:00 EDT (1:00 to 3:00 PM MDT) (NM Hosting Dial-in: +1 224-501-3412  - Meeting ID: 227-883-765) ==
    22
    33
     
    88'''ALL COP MEMBERS:  PLEASE BE PREPARED TO DISCUSS YOUR TICKETS'''.[[BR]]
    99 
    10  * When you submit a ticket, leave the Milestone=Unassigned and Version=Unknown and the ticket will come up on ticket report number 1 [http://www.ibisph.org/trac/report/1 "New Tickets for CoP Review"]
     10 * When you submit a ticket, leave the Milestone=Unassigned and Version=Unknown and the ticket will come up on ticket report number 1 [http://trac.ibisph.org/trac/report/1 "New Tickets for CoP Review"]
    1111
    12  * If you have new or open tickets please review them and be prepared to discuss them on the CoP call. You can run the [http://www.ibisph.org/trac/report/1 {1} New Tickets for CoP Review] report to see current tickets.  The purposes of discussing tickets are to a) communicate an idea to the community, and b) to identify and track IBIS-PH software issues. (Note that once a ticket has been marked to be worked then that ticket is only discussed on the CoP call for the purpose of moving the effort forward.)
     12 * If you have new or open tickets please review them and be prepared to discuss them on the CoP call. You can run the [http://trac.ibisph.org/trac/report/1 {1} New Tickets for CoP Review] report to see current tickets.  The purposes of discussing tickets are to a) communicate an idea to the community, and b) to identify and track IBIS-PH software issues. (Note that once a ticket has been marked to be worked then that ticket is only discussed on the CoP call for the purpose of moving the effort forward.)
    1313
    1414New Agenda Items:
    15151. Review agenda and add items...
    16 1. Base-map - Thunderforest API key issue (Paul)
     161. Training - IBIS Admin Version 3.0 (will proceed when Admin 3.0 development has been completed)
     171. The next two highest-prioritized training topics:
     18 * Using dynamic grouping variables in queries (grouping continuous variables in IBIS-Q, so you don't need to hard-code them in your SAS dataset)
     19 * Wiki formatting - when, where and how it's used in IBIS-View
     20
     21
     22Continued Agenda Items:
    17231. Training - JSON and Map layers (Chris and Paul)
    1824 * Modifying a map definition - choropleth colors, adding labels, adding a layer
    1925 * Setting up a new map - creating and using geojson files
    20 
    21 Continued Agenda Items:
    22261. [wiki:supportSchedule Adopter support status and priorities] (Paul/adopters).
    23 1. Version 3.0 Status (Garth).
    24 1. Review open tickets (Host).
     271. [wiki:developmentSchedule Version 3.0 Status] (Garth).
     281. [http://trac.ibisph.org/trac/report/1 Review open tickets] (Host).
    2529
    2630If Time/Interest, Future Agenda Items: