11. Data Types

Nexus supports the migration of four primary data types:
  1. Email
  2. Calendar
  3. Contacts
  4. Tasks

With each primary data type it is anticipated that some elements may not migrate from the source system to Nexus. The data may not map appropriately into Exchange or the migration tool in use may not have the ability to migrate that data element. It is the responsibility of the unit to determine the limitations of the migration process/tools and take appropriate decisions as the the value of any data lost during the process and to inform end users of any data-loss during the migration process.

For some systems a migration of existing mailbox permissions/sharing rights may be possible, but this will be a product of the source system, migration tool in use and the creation of an appropriate mapping between source and target accounts.

There are two other data types which may also be migrated to Nexus, most likely outside of the mailbox migration process. These are:
  1. Address list (Global Contacts) meta-data
  2. Groups/Distribution lists
Address list (Global Contacts) meta-data: Liaison with IT Services registration or the Nexus team may be necessary if this meta-data needs to be amended before or during the migration. Such meta-data includes:
  • Display Name (Display names on project accounts must make sense in a whole-University context, i.e. not "Reception" or "Accounts")
  • Street Address (overwritten if user moves department)
  • City (overwritten if user moves department)
  • Province (overwritten if user moves department)
  • PostCode (overwritten if user moves department)
  • Business Phone Number
  • Pager Number
  • Fax Number
  • Mobile Number
  • Job Title
  • Office
  • Manager
  • Assistant Name
  • Assistant Telephone Number
  • WebPage
Many of the fields above are not routinely used, but they may be, depending on the needs of the migrating unit and if a system is to be put in place with the aim of keeping such information up to date in an automated or semi-automated manner. All other data in the GAL is reserved for update only by Nexus/Registration automated processes.

Groups/Distribution lists: Groups should be evaluated to determine if they are solely required in a mailing list capacity or if they are also used for authorization decisions. The Nexus service is anticipating the existence of a central GroupStore service (beyond the remit of the Nexus Team) to deliver user-customizable groups to Nexus, as well as other central services. In the meantime groups/distribution lists should be migrated into Nexus only if they are used for authorization. Other groups, used only as email lists, should be migrated to the IT Services Mailing List service. Group maintenance can be devolved to owners of such groups under some circumatances (e.g. through Microsoft Outlook). Units should be aware that they may be required to migrate their groups from Nexus to the GroupStore service as soon as it becomes available and some degree of reconfiguration may be required for their users at this point (re-granting calendar access for example).

Up: Contents Previous: 10. Mailboxes over 3GB Next: 12. IT Services Resources