= Support / Training =

[[Support/Handbook|Support Handbook]] / [[Arbitrations/Training/Lesson12|Precedent cases]] / [[Arbitrations/a20120126.1|Precedent case a20120126.1]]

== How to handle "add my full middle name to my account" cases that are similar to precedent case a20120126.1 "Please add my full middle name to my account" (WIP) ==

== Preconditions ==

The user has an account and the user has been assured at least once. If there is no assurance the user is able to change the name himself.

The middle name needs to be confirmed by at least 2 assurers, may it be previous or new assurances. The sum of all the assurance points given by all previous assurers, that can confirm the middle name, and the new asked assurers will give him, need to amount to at least 50 points, so the user can issue named certificates with the new name.<<BR>>
- case 1: assurer A and assurer B can give each 35 points => 35 + 35 > 50<<BR>>
- case 2: assurer A can give 20 points, assurers B, C and D each can give 10 points => 20 + 10 + 10 + 10 = 50

== Procedure steps ==

=== Initial mail to user ===
{{{
Dear <user>,

We've received your request to add a middle name to your account dated 
####-##-##.

I'll take this case as Support Engineer.

The process to add a middle name to an account is laid out in the 
precedent arbitration case a20120126.1 [1] and is documented in the 
support handbook [2]. 

Do you know if any of the assurers who already confirmed your identity 
is able to verify your middle name? If so, please name them with name 
and email address.

For this name change you have to have at least 50 assurance points from 
assurers who can confirm your middle name, previous and new assurances 
summed up. So if you do new assurances, take care they can give you enough 
assurance points or you have enough assurers. During the assurance please 
point out to the assurer that you need the middle name confirmed.

Once you received the new assurances in your account, send the names and 
primary email addresses of the assurers to support.

Like every normal arbitration case this also is opened by some formalities:

  1. Please reply to this email and confirm that you accept the
     Arbitration under the CAcert Community Agreement [3] and the
     Dispute Resolution Policy [4].
  2. The governing law will be that of NSW, Australia. It is possible
     to request a change of law, but it is unlikely to be helpful in
     this case.
  3. You need to notify me if you are seeking legal counsel (a lawyer).
     This is not recommended. Rather, if you feel the need for help, 
     I can ask an experienced Assurer to assist you.

Finally, please remember: this forum is about sorting out our common 
difficulties and improving our ability to secure ourselves. Unlike other 
forums, I ask you to maintain a positive and helpful spirit at all times!

The proceedings of the Arbitration have to be in English. If you have troubles 
expressing yourself in English, we can try to find a translator for you.

[1] http://wiki.cacert.org/Arbitrations/a20120126.1
[2] http://wiki.cacert.org/Support/Handbook/PrecedentCases/a20120126.1
[3] http://www.cacert.org/policy/CAcertCommunityAgreement.php
    CAcert Community Agreement
[4] http://www.cacert.org/policy/DisputeResolutionPolicy.php   
    Dispute Resolution Policy
-- 

Kind Regards
<SUPPORT TEAM MEMBER>
CAcert support

}}}

=== Mail to the Assurer to verify the middle name ===
{{{
Dear <assurer>,

you have been nominated by <user> that you are able to verify the middle name 
of <user>.

I took over this case as as Support Engineer.

The process to add a middle name to an account is laid out in the precedent 
arbitration case a20120126.1 [1] and documented in the support handbook [2].

You assured <user> according to our records on <yyyy-mm-dd> at <location/event>.

Please give me the following information:

1. The primary email address of <user> that is on the CAP form.

2. All names that you have recorded on the CAP form (all first names, all middle 
   names and all last names in all variants you found).

3. The amount of assurance points issued.

Sign your reply with the CARS statement. [3]

[1] http://wiki.cacert.org/Arbitrations/a20120126.1
[2] http://wiki.cacert.org/Support/Handbook/PrecedentCases/a20120126.1
[3] http://wiki.cacert.org/CARS
-- 

Kind Regards
<SUPPORT TEAM MEMBER>
CAcert support
}}}

=== Possible reply from the assurer ===

{{{
Dear support,

I assured <user> at <location> on <yyyy-mm-dd>.

I can confirm that I have the following information recorded on the CAP form:

Primary email address: <name@domain.tdl>

All names: <first names> <middle names> <last names> (variant 1)
           <first names> <middle names> <last names> (variant 2)
           ....

Assurance points issued: <number>

Sincerely
<assurer name> CARS
}}}

=== Execution mail to the user ===

{{{
Dear <user>,

I executed your request to add a middle name to your account dated ####-##-##.

As <number> assurer are able to verify your middle name and gave you enough 
assurance points, I entered/changed your middle name to <middle name> 
according to the process laid out in the precedent arbitration case 
a20120126.1. [1]  

[1] http://wiki.cacert.org/Arbitrations/a20120126.1

-- 

Kind Regards
<SUPPORT TEAM MEMBER>
CAcert support
}}}

=== Recording of change ===

Supports adds the ticket number and the execution date to precedent case.

=== Input and thoughts ===

Can this be also applied for the initial of a middle name?

 . u60 : once passed, again the name rules applies (reduction possible, add informations prevented)

=== Reference documents ===

[1] [[Arbitrations/a20120126.1|Precedent case a20120126.1]]

----
 . CategorySupport
 . CategorySupportPrecentCase