Description of the data model conversion process

This page describes the forced data conversion steps that will take place to convert registry data objects from the current data model to the new data model.

During the conversion, a log file is created for each registrar which describes the conversion of data objects sponsored by the registrar. When the conversion has been performed, the log file will be published on the registrar web under daily dumps as a service to the registrar.


CONTENTS:

  1. Object transformation and update work flow
  2. Logging and log file

Object transformation and update work flow

The object transformation and update starts with delegation objects, then organization, person and name server objects are transformed.

The term ‘orgname’ below corresponds to the  EPP contact ‘org’ element. The term ‘adminc’ refers to the legal contact data.

1a) Delegation objects held by private persons

If a delegation has got no adminc (held by a private person), any relation to techc persons are removed if there exists at least one techc role.

For the delegation object:

  • Delete relation to techc (person) if there exists a techc (role).

1b) Delegation objects held by organizations

If a delegation has got more that one adminc, the adminc handles are sorted and the first handle/adminc is used for further processing.

For the registrant organization object:

  • Set ‘orgname’ to the value of ‘name’ if ‘orgname’ is empty.
  • Delete fax number.
  • Copy ‘name’ from adminc to ‘name’ in registrant.
  • Copy all adminc ’email’ to ‘xemail’ in registrant if they do not already exists.
  • Copy ‘phone’ from adminc to ‘phone’ in registrant if it is empty.
  • Copy ‘mobile phone’ from adminc to ‘mobile phone’ in registrant if it is empty.

For the delegation object:

  • Delete relations to adminc.
  • Delete relation to techc (person) if there exists a techc (role).

When we have many delegations with different adminc objects related to the same registrant, as long as the adminc data is the same(*), we reuse the registrant object. Otherwise we need to create a new registrant object for each adminc that differs. In the latter case we use the new feature where multiple organization contacts with the same identity can be created within a registrar workspace.

*) The adminc data is the same when all values of name, email, xemail, phone and mobile phone are the same.

2) Organization objects

Only handle organization objects that has not been processed in 1)

For the organization objects:

  • Set ‘orgname’ to the value of ‘name’ if ‘orgname’ is empty.
  • Delete fax number.

3) Person objects

For each person object of type person:

  • Delete fax number.
  • Delete organization references.

4) Role objects

For each person object of type role:

  • Delete fax number.
  • Delete organization references.
  • Delete person references.

4) Name server objects

For each name server object:

  • Delete person references.

Logging and log file

All changes to objects are logged to a log file, one file per registrar, with description of what is changed and where the data came from. When the conversion is performed, the log file for each registrar will be published as a daily dump status file on the registrar web.

Some examples from such a log file are shown below.

Example from step 1):

Updating delegation objects ...
Updating delegation AAG129D ...
Convert registrant object AMHA7O
Updating AMHA7O with orgname: ANDERS M HANSEN AS
Deleting fax from AMHA7O
Updating AMHA7O with name: Arild Bottolfsen from AB8162P
Removing adminc AB8162P from AAG129D
Updating delegation AQU893D ...
Convert registrant object BA2900O
Updating BA2900O with orgname: BEDRE PARTNER AS
Updating BA2900O with name: Sverre Gardtun from SG3139P
Updating BA2900O with xemail: sverre.gardtunm@bedrepartner.org from SG3139P
Updating BA2900O with phone: +47.95199000 from SG3139P
Removing adminc SG3139P from AQU893D

Example from step 2):

Updating organization objects ...
Updating AA10962O with orgname: ATEA AS
Updating AA7871O with orgname: ACTIVE 24 ASA
Deleting fax from AA7871O
Updating BA3964O with orgname: Byavisa AS
Deleting fax from BA3964O

Example from step 3):

Updating person objects ...
Deleting org reference ER395O from ER4861P
Deleting org reference WC199O from AP2654P
Deleting fax from HG1075P
Deleting org reference ONA318O from OLT37P
Deleting fax from FP636P
Deleting org reference CA1530O from FP636P

Example from step 4):

Updating person objects ...
Deleting person reference JAN252P from ESBH65R
Deleting person reference FE801P from ESBH65R
Deleting fax from UH1479R
Deleting org reference UA1488O from UH1479R
Deleting person reference ST3230P from UH1479R
Deleting fax from DH4474R
Deleting org reference DA2354O from DH4474R
Deleting person reference SS8836P from DH4474R

Example from step 5):

Updating nameserver objects ...
Removing person JN1312P from NSGR137H
Removing person DA542P from DNSU28H
Removing person AH4026P from NSIN110H
Removing person BFAS2P from NSSC45H
Removing person RL2640P from NSNL6H
Removing person WH271P from NSNE193H
Removing person HWWA3P from AUTH64H
Removing person JH5982P from NSEU592H
Last updated 4 December 2017