What happens if we need to merge Third Iron accounts?
Organisational changes such as mergers can result in there being multiple Third Iron accounts attached to a single organisation. To avoid confusion, complexity and rework a plan should be made to move to the most appropriate Third Iron account to support the new service arrangements.
Third Iron cannot merge accounts and the process is more around dealing with the consequences of deactivating an account. Third Iron have worked to reduce the impact of such changes on end users.
You should select the account with the largest existing user base to minimise the number of people who may be inconvenienced.
The account name can be tweaked if required to reflect the new status - this often involves simplification of any temporary arrangement such as (Your Hospital NHS Trust - South sites) (Your Hospital NHS Trust - North sites) to (Your Hospital NHS Trust)
For LibKey Nomad
- If the deactivating Trust had used a site-wide install of LibKey Nomad (using Microsoft Group Policy), they will want to ensure the library ID is replace by the other before deactivation
- Individual installs of LibKey Nomad will be prompted to select the revised Library account name via the usual selection process
For LibKey Links
- ie in the Hub and EBSCOHost - the continuing account with LibKeyID/API key will be linked as part of any merger process (by the Service Desk team) and users will not notice a change
- The merged HLM will supply the data so ensuring the validity of collection data on the Hub remains critical
- Integrations such as PubMed and Google Scholar will continue to use the selected account
- In the event a change has not been made correctly the user will be presented a custome screen confirming that the subscription has expired and inviting them to select the current account via the Find your library search
For Browzine
- Presents an experience that is optimized for the end-user. Briefly says the library is not subscribed and then lands on the WAYF "choose library" screen, where the user can quickly filter for the correct Trust.
For INCDocs
- Users do not see these screens and therefore only minimal development has been completed for this eventuality. An error message is returned and library teams should check if they are using the correct account at this point. The old account is deleted and will no longer receive INCDocs requests or be able to request.