At our university we hold person information in various systems, and would like to consolidate person identities together with their affiliations (such as staff member, student, contractor) into a FIM repository. A person might have multiple affiliations at a time (and in rare cases multiple affiliations of the same type). Possibly somebody can provide any guidance on what would be the best representation in Metaverse. My current thinking is to have a Person object and related objects representing the Affiliation. During import is it possible to use a rules extension creating multiple objects of different object type with the Management Agent for Joins / Projections?

The short answer is no - there is no way to have references or lookups from one metaverse object to another (outside of standard primary key based lookups like manager) and there is no way to create an affiliation between one metaverse and another object. What you are asking for would require a connectorspace object to have multiple metaverse connectors which also is not possible. You either need to flatten the affiliations into attributes on the record or, more likely, model the affiliations as groups/roles in the metaverse. Modeled as Groups a single affiliation could have multlpe "members".Brad Turner, ILM MVP - Ensynch, Inc - www.identitychaos.com [If a post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of that post. By marking a post as Answered or Helpful, you help others find the answer faster.]