This is an old revision of the document!
CeRTNA Standard XML - Common
XML structures can be challenging to document in a manner that is simple and easy to read or understand. This said, this document is intended to outline the characteristics of the most frequently used XML nodes and properties in the CeRTNA Standard XML structures.
The CeRTNA Standard XML consists of 3 major structures, a REQUEST_GROUP, a RESPONSE_GROUP, and a PRIA_DOCUMENT structure. The PRIA_DOCUMENT structure is 'included' (common) across both the REQUEST_GROUP and the RESPONSE_GROUP structures.
The REQUEST_GROUP, with its embedded PRIA_DOCUMENT nodes represents what is delivered by the Submitter and the RESPONSE_GROUP, with its embedded PRIA_DOCUMENT nodes represents what is returned by the County Recorder.
The PRIA_DOCUMENT nodes contained in the RESPONSE_GROUP returned by the County Recorder will contain either recording information or reject information, depending on the action taken by the County Recorder.
Additional information associated with CeRTNA recommendations and/or best practices for CeRTNA System Integrators can be found in the CeRTNA System Integrators Guide.
The following tables provide information describing, historically, the most commonly used nodes and properties:
The Req column will use one of the following codes.
- R = Required
- O = Optional
- P = Required if Parent node is present.
REQUEST_GROUP Structure
| Node | Parent/Properties | Req | Description |
|---|---|---|---|
| REQUEST_GROUP | - | R | - |
| - | PRIAVersionIdentifier | O | The PRIA schema version that CeRTNA XML structures are currently based on. (Currently 2.4.2) |
| REQUESTING_PARTY | REQUEST_GROUP | R | This node contains information that identifies the Submitter organization. (Not the Agent) |
| - | _Name | R | Submitter name. |
| - | _StreetAddress | R | Address line 1. |
| - | _StreetAddress2 | O | Address line 2. |
| - | _City | R | City. |
| - | _State | R | State. |
| - | _PostalCode | R | Zip code. |
| - | _Identifier | R | This is the most important property of the REQUESTING_PARTY node. This attribute contains the id of the requesting party as assigned by the CeRTNA application when the Submitter account is established. The list of CeRTNA submitters is constantly changing. Contact the CeRTNA organization for a current list of Submitter _Identifier values. |
| SUBMITTING_PARTY | REQUEST_GROUP | R | This node contains information that identifies the organization (Typically an Agent) who submitted this transaction. |
| - | _Name | R | The name of the organization that does the actual electronic submission of the transaction. For Direct ERDS or Direct G2G submitters, this value will typically be the same as the _Name attribute of the REQUESTING_PARTY. Transactions submitted by Agent submitters will have the name of the Agent submitting agency here, for example AGENT - SIMPLIFILE. If this is a G2G SecureFTP transaction the name will be G2G Submitting Agent. |
| - | LoginAccountIdentifier | R | For Agents this will be the login userid of one of their authorized users. For G2G SecureFTP transactions, this will be g2gsubmitting user. For Direct entry, this will be the user who is submitting the transaction. |
| REQUEST | REQUEST_GROUP | R | This node serves as a wrapper for the PRIA_REQUEST node. |
| - | RequestDateTime | O | For Direct submitters, the CeRTNA ERDS and G2G processes fill this value in and it represents the date/time that the XML transaction was created. For ERDS or G2G Agents/Agencies that create their own XML files this field/property may or may not be present. |
| KEY | REQUEST | O | This node is used to specify optional Name/Value pairs. Currently the only valid Name/Value pair is to support a transaction level comment. |
| - | _Name | P | Name of the data element. The only item in use at this time is Comment (Required if the KEY element is used.). |
| - | _Value | P | The value of the named data item. (Required if the KEY element is used.) |
| PRIA_REQUEST | REQUEST | R | This node is used to specify optional Name/Value pairs. Currently the only valid Name/Value pair is to support a transaction level comment. |
| - | _RelatedDocumentsIndicator | R | This is used to convey Dependent versus Independent documents in a transaction. If this value should is set to True it indicates that all the documents in the transaction must be recorded as a whole, otherwise they must all be rejected as a whole. If the value is False, then each document in the transaction can be recorded or rejected independent of each other. |
| PACKAGE | PRIA_REQUEST | R | This node is the wrapper for all of the PRIA_DOCUMENT nodes. There is only 1 occurrence of a package node in a CeRTNA XML payload. |
| - | CountyFIPSCode | R | County 3-digit FIPS code. Represent as a 3 character string. Example: Kern County FIPS = “029”. |
| - | StateFIPSCode | R | State 2-digit FIPS code. Represent as a 2 character string. Example: California FIPS = “06”. |
| - | SecurityType | R | Security type for the payload. Due to changes in DOJ regulations, all transactions should set SecurityType=“1”. |
| - | Priority | R | Supports a counties ability to offer special recording priority such as 8:00 AM recordings or 1:00 PM recordings. The values will be one of the following: “Standard” = Real-time recording. (When received). “1” = (Configured in the portal, typically means 8:00 AM). “2” = (Configured in the portal, Not used so far.) |
| RECORDING_TRANSACTION_IDENTIFIER | PRIA_REQUEST | R | The properties in this node are used by Submitters to represent their internal order number. Order numbers must be unique by Submitter. This node is also referred to as a Primary Reference number and/or Customer Reference number. |
| - | _Value | R | The is the primary unique number. The CeRTNA database stores this in the PRIMARY_REFERENCE field |