RosterUpdate
RIXML 2.5 Element
An element that represents individual changes to publisher personnel rosters, enabling communication of additions, updates, or deletions of people and groups involved in research production
A roster update gives a publisher the ability to communicate changes to the groups of people playing various roles on its behalf in the investment research marketplace. The common case would be a financial services firm updating its roster of research analysts with aggregator partners.
Usage
Required child element of RosterUpdates with multiple instances allowed, each containing StatusInfo and choice of Organization, PersonGroup, PersonGroupMember, or Person elements
Business Context
Critical for maintaining current personnel information in research aggregation systems, particularly for tracking analyst coverage assignments and organizational changes at financial services firms
Where It Fits
Canonical Path
Definition
| Type | RosterUpdateType |
| Namespace | http://www.rixml.org/2017/9/RIXML |
| Min Occurs | 1 |
| Max Occurs | 1 |
Attributes
rosterUpdateIDstring |
This is to facilitate the unique identification of a particular individual roster update. Enables a consumer of this information to keep track of which updates have been applied to its database and which are duplicates. We recommend UUIDs to ensure uniqueness. optionalSince 2.5 |
Children
StatusInfo(complex)1..unbounded |
For statusType attribute, use: Published=Add, Revised=Update, Deleted=Delete. requiredSince 2.5 |
OrganizationOrganizationType1..1 |
requiredSince 2.5 |
PersonGroup(complex)1..1 |
requiredSince 2.5 |
PersonGroupMember(complex)1..1 |
requiredSince 2.5 |
PersonPersonType1..1 |
requiredSince 2.5 |
Example
<RosterUpdate>
<StatusInfo> ... </StatusInfo>
<Organization> ... </Organization>
<PersonGroup> ... </PersonGroup>
<PersonGroupMember> ... </PersonGroupMember>
<Person> ... </Person>
</RosterUpdate>Version History
Unchanged since introduction in RIXML 2.5
Business Rules
Universal Unique Identifiers (UUIDs) should be used for roster update identification to ensure uniqueness
Design Decisions
Unique identification for roster updates should preferably use UUIDs to ensure global uniqueness
Enables consumers to track which updates have been applied to their databases and identify duplicates
RIXML Research Data Dictionary v2.5.1, p.135
Semantic Relationships
Requires1 relationship
Roster updates must include status information to indicate whether the update is an add, update, or delete operation for tracking changes to research analyst rosters
RIXML Research Data Dictionary v2.5.1, p.135— RosterUpdate
Constrains1 relationship
The roster update identifier enables consumers to track which updates have been applied and identify duplicates, with UUIDs recommended for uniqueness
RIXML Research Data Dictionary v2.5.1, p.135— rosterUpdateID