OrdinanceStatusReason (JSON)

Reasons a status might exist.

URI:OrdinanceStatusReason

Values

http://familysearch.org/v1/BornInCovenant The "sealing to parent" ordinance is not needed when an individual is "born in the covenant".
http://familysearch.org/v1/CoupleRelationshipMissing The "sealing to spouse" ordinance requires a couple relationship between the couple.
http://familysearch.org/v1/DeathBeforeBirth The person's death date cannot be before his/her birthdate.
http://familysearch.org/v1/DiedBeforeAgeEight Baptism, Confirmation, Initiatory, Endowment, and Sealing to Spouse ordinances are not needed if a person died before the age of eight.
http://familysearch.org/v1/DeathDateReformatNeeded There's a death or burial date that cannot be standardized. Only applied when a person was born recently enough (110 years) that the death date should be findable and able to be standardized.
http://familysearch.org/v1/InvalidGivenNamePiece A person's given name(s) cannot contain one or more invalid words or be represented by a traditional prefix such as Mr., Miss, Mrs., etc.
http://familysearch.org/v1/InvalidName This person's name contains one or more invalid words.
http://familysearch.org/v1/InvalidNamePrefix This person's name contains an invalid name prefix.
http://familysearch.org/v1/InvalidNameSuffix This person's name contains an invalid name suffix.
http://familysearch.org/v1/InvalidSingleNamePiece A person's name cannot include descriptors such as Child, Baby, Son, Daughter, Sister, Brother, Aunt, Uncle, etc.
http://familysearch.org/v1/InvalidSpecialCharacterName A person's name cannot include invalid characters.
http://familysearch.org/v1/InvalidSurname A person's surname contains invalid words or characters. A person's surname cannot be a descriptor such as nephew, niece, spouse, twin, etc.
http://familysearch.org/v1/InvalidTitleGivenMissing A person has a title but no given name. A male person with a title and surname name must have a given name
http://familysearch.org/v1/MarriedTooYoung The person's marriage fact date occurs before the person is eight years old
http://familysearch.org/v1/Medieval A person who lived before A.D. 1500.
http://familysearch.org/v1/MissingStandardizedDate A person must have a standardized date reference.
http://familysearch.org/v1/MissingStandardizedPlace A person must have a standardized place reference.
http://familysearch.org/v1/MisterAsOnlySurname A person's surname cannot contain the word "Mister". If the person's surname is Mister, then it should be the only word in the last name.
http://familysearch.org/v1/NameContainsOnlyInitials A person cannot have a name that is only initials.
http://familysearch.org/v1/NameLangScriptMismatch One or more characters in the name do not match the designated language script of the name.
http://familysearch.org/v1/NameLangUndWithMultipleScripts The language script for the name is undefined and the name contains multiple scripts.
http://familysearch.org/v1/NameTooLong A person's full name (any name form) cannot be more than 255 characters.
http://familysearch.org/v1/NeedPermission This ordinance is for a person born too recently and the current user is not an immediate relative.
http://familysearch.org/v1/NoName A person's record needs a given name or surname.
http://familysearch.org/v1/NotAccountable A person has been declared not accountable.
http://familysearch.org/v1/NotAvailable A person's ordinance status is not available. Please contact FamilySearch Support if you are a direct descendant and need more information.
http://familysearch.org/v1/NotDeadAtLeastOneYear A person has not been deceased for one year.
http://familysearch.org/v1/NotMatchableUsingEvents A person must have enough event or relationship information, such as a birthdate and place, a death date and place, etc. A person's record must have enough date or place information for the system to be able to determine whether the ordinance is already done.
http://familysearch.org/v1/NotMatchableUsingRelationships A person must have has enough event or relationship information. A person's record must have enough relationship information for the system to be able to determine whether the ordinance is already done.
http://familysearch.org/v1/NotRelatedToMember A member must be related to a person to reserve ordinances for that person.
http://familysearch.org/v1/NotTempleOrdinance The ordinance must be a valid temple ordinance. The Family Tree cannot be used to reserve ordinances of this type.
http://familysearch.org/v1/OfficialCompletedOrdinanceForLiving This person is still listed as living.
http://familysearch.org/v1/OfficialCompletedOrdinance This is an official completed ordinance.
http://familysearch.org/v1/OneLatinLetterSurname Latin surnames cannot consist of only one letter.
http://familysearch.org/v1/OneNamePerScriptType ONE_NAME_PER_SCRIPT_TYPE maps to "one.name.per.script.type"
http://familysearch.org/v1/ParentRelationshipMissing A "sealing to parent" ordinance requires the person to have both child-to-father and child-to-mother relationships.
http://familysearch.org/v1/ParentsCoupleRelationshipMissing A "sealing to parent" ordinance requires the father and mother to have a couple relationship.
http://familysearch.org/v1/RepeatingSpecialCharacterName A person's name cannot contain repeated punctuation characters, such as .., --, etc.
http://familysearch.org/v1/Reserved The ordinance is reserved.
http://familysearch.org/v1/RestrictedDate A person who lived before 200 A.D.
http://familysearch.org/v1/SameSex A sealing to spouse must involve a husband and a wife. A sealing to parents must involve a father and a mother.
http://familysearch.org/v1/SealingToSelf A person cannot be sealed to themselves.
http://familysearch.org/v1/Stillborn A stillborn person does not need ordinances.
http://familysearch.org/v1/TooRecentlyDeceased The person has not been deceased long enough to qualify for temple ordinances.
http://familysearch.org/v1/UnknownGender A person must have a known gender, male or female.
http://familysearch.org/v1/UnsupportedTree The person is in a tree that does not allow ordinances to be performed.

Change Language

Feedback

Sending...

Feedback was sent.

Can't send feedback. Retry in 5 seconds.