HAN

One of the principle problems with the data exchange between HAN and the EJL interface is how to determine when to change the data of an account and when to create a new account for a new period. Since there is no definite criterion to distinguish how to interpret the data, HAN has to decide itself what to do with the transmitted data. The criteria for the interpretation are the following four properties of an account: title, anchor, license period and URL.
Generally the following rules are applied:

1. If 3 of the 4 criteria (title, anchor, license period and URL) are unchanged -> update of the existing account
2. Change of URL -> update of the existing account
3. Only the license period is changed -> update of the existing account
4. Special case: change of anchor and URL -> update of the existing account

An exception to rule 4 is that for not defined license periods (i.e. empty license periods) and different anchor and different URL a new account will be created.

In all other cases that are not covered by this 4 rules a new account will be created.

This means that for a blocked e-journal no updates will be done. This includes the creation for accounts for new license periods or the deletion of exiting EJL accounts through the "clean" function (EJL cleanup).

The HAN administration can recognize if a HAN account is manually changed (change of root URL or adding further URLs) and informs in this case that without blocking the account for EJL updates these changes will be overwritten with the next update automatically. Only blocking the automatical update can protect such a modified account. When doing the EJL update this will be automatically detected if a script has been changed manually. In this case the existing script will backed up in the directory hh\han\hancfg\Backup and the account will be modified according to the transmitted data.

A new option is the import of accounts into groups but to use individual protocol IDs in the account itself. To activate this function, please set the entry InheritProtID=0 in the configuration file han.cfg in hh\han\bin in section [EZB Import].

Please be aware that the version number show in the HAN Administration's info dialog is not changed by this hotfix as this information is stored in the registry!