When migrating from Voyager to Alma it may be helpful to review your Elinks data.

The following two queries, which can be run using Voyager's Prepackaged Access Reports produce detailed reports on Elinks stored in BIBs and in MFHDs. These reports can then be reviewed.

Elink_Bibs

SELECT ELINK_RECORD_TYPE.RECORD_TYPE,
       ELINK_INDEX.RECORD_ID AS BIB_ID,
       ELINK_INDEX.ELINK_ID,
       ELINK_INDEX.SEQNUM,
       ELINK_INDEX.LINK_TYPE,
       ELINK_INDEX.LINK,
       ELINK_INDEX.LINK_TEXT,
       ELINK_INDEX.LINK_TEXT_NORMAL,
       ELINK_INDEX.LINK_SUBTYPE,
       ELINK_INDEX.URL_HOST,
       ELINK_INDEX.URL_PORT,
       ELINK_RECORD_TYPE.RECORD_TYPE_ID,
       ELINK_INDEX.UPDATE_DATE,
       ELINK_INDEX.UPDATE_OPID
FROM ELINK_RECORD_TYPE
     INNER JOIN ELINK_INDEX
     ON ELINK_RECORD_TYPE.RECORD_TYPE_ID = ELINK_INDEX.RECORD_TYPE
WHERE (((ELINK_RECORD_TYPE.RECORD_TYPE_ID)="B"));

Elink_Mfhds

SELECT ELINK_RECORD_TYPE.RECORD_TYPE,
       ELINK_INDEX.RECORD_ID AS MFHD_ID,
       ELINK_INDEX.ELINK_ID,
       ELINK_INDEX.SEQNUM,
       ELINK_INDEX.LINK_TYPE,
       ELINK_INDEX.LINK,
       ELINK_INDEX.LINK_TEXT,
       ELINK_INDEX.LINK_TEXT_NORMAL,
       ELINK_INDEX.LINK_SUBTYPE,
       ELINK_INDEX.URL_HOST,
       ELINK_INDEX.URL_PORT,
       ELINK_RECORD_TYPE.RECORD_TYPE_ID,
       ELINK_INDEX.UPDATE_DATE,
       ELINK_INDEX.UPDATE_OPID
FROM ELINK_RECORD_TYPE
     INNER JOIN ELINK_INDEX
     ON ELINK_RECORD_TYPE.RECORD_TYPE_ID = ELINK_INDEX.RECORD_TYPE
WHERE (((ELINK_RECORD_TYPE.RECORD_TYPE_ID)="M"));

For other queries that may be useful, see my "Surviving Almanado: tips for a successful pre-implementation" presentation's Accompanying Materials.

Posted as is. If you need assistance in running custom SQL queries in Prepackaged Access Reports, consult the Voyager Customer Listserv.