anchor.diff:                         {default_update/2, update}]}
          ]).
   
  +%% We don't have a class for 'organizations' on the client yet, but eventually we may want
  +%% to send a json_class Chef::ApiOrganization or the like.
  +%% Then we would amend DEFAULT_FIELD_VALUES and VALIDATION_CONSTRAINTS to include:
  +%% {<<"json_class">>, <<"Chef::Organization">>},
  +%% {<<"chef_type">>, <<"organization">>},
  +-define(DEFAULT_FIELD_VALUES, [ ]).
  +-define(NAME_FIELD, <<"name">>).
  +-define(FULL_NAME_FIELD, <<"full_name">>).
  +
  +-define(VALIDATION_CONSTRAINTS,
  +        {[ {?NAME_FIELD, {string_match, regex_for(org_name)}},
  +           {?FULL_NAME_FIELD,  {string_match, regex_for(org_full_name) }}
  +         ]}).
  +
  +-define(VALID_KEYS, [?NAME_FIELD, ?FULL_NAME_FIELD]).
  +
  +
  +
   authz_id(#oc_chef_organization{authz_id = AuthzId}) ->
       AuthzId.
   
  
positive.code: ejson_for_indexing(#oc_chef_organization{}, _EjsonTerm) ->
     erlang:error(not_indexed).
  
  update_from_ejson(#oc_chef_organization{} = _Organization, _OrganizationData) ->
      erlang:error(not_implemented).
  
  set_created(#oc_chef_organization{} = Organization, ActorId) ->
      Now = chef_object_base:sql_date(now),
  
negative.code:          name/1,
           id/1,
           org_id/1,
           type_name/1,
           assemble_organization_ejson/1,
           parse_binary_json/1
          ]).
  
  -mixin([
  