logo Calflora Group Options  HELP
Updated March 25, 2020
With the Group Options application you can edit various datasets that support your group's use of Weed Manager. Each dataset is available in a tab within this application.

Members with the Data Czar role are able to use all of the tabs in this application. Other members may be able to use some of the tabs, depending on the group's policies; see Roles and Data Access below.

  • Crew
  • Roles
  • Activities
  • Billing Codes
  • Chemicals
  • Searches
  • Column Sets
  • Export
  • Policies
  • Roles and Data Access


  • CREW
    The crew table supports the Work Session Entry (WSE) application; all crew entries appear in a dropdown in WSE. Each crew record has a name and a role. The value of name can be a person's name, or an abstract noun such as Restoration Staff. It also might be a collective noun, such as the name of a contractor.

    The value of role is from the role table, and represents the typical role for that crew entry.

    ROLES
    This tab is available to members with the Data Czar role.

    The role table supports the WSE application; all role entries appear in a dropdown in WSE. Each role record has the name of the role and an hourly rate. For instance, if the name of the role is Volunteer, the hourly rate would be $0.00.

    ACTIVITIES
    The activity table supports the WSE application; a work session record can be assigned to an activity. All activity entries appear in a dropdown in WSE.

    BILLING CODES
    The billing code table supports the WSE application; a work session record can be assigned to a billing code. All billing code entries appear in a dropdown in WSE.

    CHEMICALS
    This table shows the chemicals used by the orgranization, if any. Chemicals are selected from a master list.
    SEARCHES
    This table shows all saved searches which are associated with the group. A search is from either the Observation Search application or the Group Observations application.
    COLUMN SETS
    A column set is view of the observation and treatment data that the group collects. A column set can be defined in the Group Observations application. Once defined, members of your group can use it again in the Group Observations application.

    If you need to export observation and treatment data collected in Weed Manager to a local database, you can define a column set that lines up with the columns of your local database table, and then use Group Observations / Export.

    EXPORT
    This tab is available to members with the Data Czar role.

    Use this tab when you want to export your group's data from Calfora and load it into another copy of the MySQL database.

    Check the tables you are interested in, and press . For each table you checked, the definition of the table will be extracted into a .sql file, and the data for your group will be extracted into a .dat file. All of the extracted files will be archived into a .zip file, which is then downloaded to your desktop.

    As an example, suppose you checked the Crew table. Then the .zip file will contain an orgcrew.sql file that looks like this:

    CREATE TABLE `orgcrew` (
      `rid` int(11) NOT NULL AUTO_INCREMENT,
      `gid` int(11) NOT NULL,
      `name` varchar(48) NOT NULL,
      `wrole` varchar(36) NOT NULL,
      PRIMARY KEY (`rid`),
      KEY `orgcrew_gid` (`gid`)
    ) ENGINE=MyISAM DEFAULT CHARSET=latin1;
    
    and an orgcrew.dat file that looks something like this:
    213|52|Ralph Gibsion|Full-time staff
    214|52|Chris Wheelery|Part-time staff
    215|52|Letitia Slighcarp|Seasonal staff
    216|52|Janella Brisket|Seasonal staff
    217|52|AAAAA Landscaping|Contractor
    

    To use these files with a local copy of MySQL, you would define the table, and then load the data into the table as follows:

    $ mysql -p LocalDataBaseName < orgcrew.sql
    
    $ mysql -p LocalDataBaseName
    
       mysql> load data local infile 'orgcrew.dat' into table orgcrew fields terminated by '|';
    


    If you check a table, but your group does not have any data in that table, it will not be incuded in the .zip file. If you ask for the Activities + Billing Codes table, it will be called orgsds in the .zip file.


    POLICIES
    This tab is available to members with the Data Czar role.

    There are three policies:

      1. Use the reference polygon for historical records on Observer Pro

      2. Share private weed data with CalWeedMapper

      3. Limit access for regular members


    Roles and Data Access
    The owner of a group uses the Group Members application to add or remove members from the group, and to give certain members special roles within the group. By default the role of each member is regular member. There are several special roles, shown here ordered by capabilities (most to least):

    Data Czar
    A data czar can edit any resource associated with the group, including observations. A data czar can also use the Manage Groups application to edit the group record, and add new members or change member roles.

    Project Czar
    A project czar has the same capabilities as a team leader, but with this additional capability: they can edit any observation that is associated with certain projects in the group. The assignment of project czar to particular projects happens in the Project Setup application. To make a member into project czar for a particular project, use the Manage Groups application to give them the project czar role, and then use Project Setup to assign them to projects.

    Team Leader
    A team leader can use the Group Options application to edit group resources, such as saved searches. A Team Leader can also use the Project Setup application to edit existing projects, but cannot add new projects.

    Regular Member
    A regular member can add observations to the group, view others' observations, and use all group resources.

    Nominal Member
    A nominal member can contribute observations to the group, but cannot see unpublihsed or private observations contributed by others to the group.

    This table shows role capabilities in various applications.
    Application View Edit Add
    Group Members Regular member. Data Czar or Owner. Data Czar or Owner.
    Plant Observation Entry A regular member can view any other member's record, published or not. A Data Czar can edit any record. A Project Czar can edit any record in a project to which they are assigned. Any member.
    Group Observations Regular member. Data Czar (using Batch Edit).
    Project Setup Regular member. Team Leader. Data Czar.
    Work Session Entry Regular member. Team Leader. Team Leader.
    Group Options Regular member 1
    Team Leader2
    (See below.) (See below.)

    Policy #3 on the POLICIES tab limits what regular members are able to do. If policy #3 is in effect, a regular member cannot use the Group Options application.

    The table below explains how roles affect what members are able to do on various tabs of the Group Options application.

    Tab View Edit Add
    CREW Regular member 1
    Team Leader 2
    Data Czar. Data Czar.
    ROLES Data Czar. Data Czar. Data Czar.
    ACTIVITIES Regular member 1
    Team Leader 2
    Data Czar. Data Czar.
    BILLING CODES Regular member 1
    Team Leader 2
    Data Czar. Data Czar.
    CHEMICALS Regular member 1
    Team Leader 2
    Data Czar. Data Czar.
    SEARCHES Regular member 1
    Team Leader 2
    Team Leader. Team Leader.
    COLUMN SETS Regular member 1
    Team Leader 2
    Data Czar. Data Czar.
    EXPORT Data Czar.
    POLICIES Data Czar. Data Czar.
    1 if policy #3 is not in effect.
    2 if policy #3 is in effect.
    RELEASE NOTES:

    • November, 2017:   v. 0.60: Includes support for the Team Leader role and policy #3, which limits access for regular members who are not Team Leaders or Data Czars.

    • September, 2017:   v. 0.57: Includes the POLICIES tab.

    • July, 2017:   v. 0.55: Includes the EXPORT tab.