person
Represents a special kind of content item used to store personal information about persons related to a publication (mostly contributors and editors of various kinds).
Syntax
<person id="text"? (source="text" sourceid="text")? dbid="text"? exported-dbid="text"? > <field>...</field>* </person>
Only one form of the field
element may be used:
Person field.
Examples
This example imports a publication user (a person with user name and password for accessing the publication).
<user source="ex" sourceid="21"> <field name="first-name">Marcus</field> <field name="last-name">Cicero</field> <field name="email-address">marcus@cicero.org</field> <field name="username">m.cicero</field> <field name="password">tullius</field> </user>
Attributes
id="
text"
(optional)-
A unique identifier for this
person
element. It is only valid and unique within the current syndication file and can be used to enable the establishment of relationships between elements in the file. Other elements in the file haveid-ref
attributes that can be used to referenceperson
elements. If aperson
element does not have anid
attribute then it must have either adbid
attribute or both asource
and asourceid
attribute. Aperson
element may have several or all of these attributes, in which case any of them can be used for establishing relationships.The
id
attribute is not imported along with persons. Unless adbid
attribute has been specified, all imported persons are assigned new internal IDs during import. source="
text"
(optional)-
The name of the system from which this person originates. Together with the
sourceid
attribute it forms a globally unique external identifier for the person that can be used for establishing relationships between elements in the syndication file. Other elements in the file havesource
andsourceid
attributes that can be used for this purpose. If this attribute is specified then asourceid
attribute must also be specified. If aperson
element does not have asource
andsourceid
attribute then it must have either adbid
attribute or anid
attribute. Aperson
element may have several or all of these attributes, in which case any of them can be used for establishing relationships.If supplied,
source
andsourceid
are imported and stored with persons. Ifsource
andsourceid
are supplied anddbid
is not supplied, then they are used to lookup an existing person. If a person with matchingsource
andsourceid
is found, then this person is updated; otherwise a new person is created.If supplied,
source
andsourceid
are imported and stored when creating new persons, but not when updating existing persons. sourceid="
text"
(optional)-
The id of this person in the system from which it originates. Together with the
source
attribute it forms a globally unique external identifier for theperson
that can be used for establishing relationships between elements in the syndication file. Other elements in the file havesource
andsourceid
attributes that can be used for this purpose. If this attribute is specified then asource
attribute must also be specified. If aperson
element does not have asource
andsourceid
attribute then it must have either adbid
attribute or anid
attribute. Aperson
element may have several or all of these attributes, in which case any of them can be used for establishing relationships.If
source
andsourceid
are supplied anddbid
is not supplied, then they are used to lookup an existing person. If a person with matchingsource
andsourceid
is found, then this person is updated; otherwise a new person is created.If supplied,
source
andsourceid
are imported and stored when creating new persons, but not when updating existing persons. dbid="
text"
(optional)-
The internal Content Engine ID of this person, which can be used when importing updated versions of existing content items. It can also be used for establishing relationships between elements in the syndication file. Other elements in the file have
dbid
attributes that can be used for this purpose. If aperson
element does not have adbid
attribute then it must have either asource
andsourceid
attribute or anid
attribute. Aperson
element may have several or all of these attributes, in which case any of them can be used for establishing relationships.You should only use the
dbid
attribute when importing updated versions of existing persons.This attribute is never present in syndication files that have been exported from a database. The ID is always written to the
exported-dbid
attribute in exported syndication files. exported-dbid="
text"
(optional)-
The internal Content Engine ID of this person, which can be used to identify the person in the database from which it was exported.
This attribute is generated during export from the , but ignored during import. It is provided mainly for information and debugging purposes.