Back in the day when our contract with our former ILS vendor limited us to < 500K titles it became necessary to put several non-circulating titles into a separate MySQL db named Louisa.
Louisa has x 2 db tables:
mysql> describe titles;
+------------+-------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+------------+-------------+------+-----+---------+----------------+
| mrc | mediumtext | YES | | NULL | |
| tcn | varchar(20) | YES | | NULL | |
| ckey | int(11) | YES | | NULL | |
| createDate | date | YES | | NULL | |
| titleID | int(11) | NO | PRI | NULL | auto_increment |
+------------+-------------+------+-----+---------+----------------+
...
After these titles and items are in FOLIO their MARCs will need to be re-written with FOLIO 999s and added to the records db table so before loading them into FOLIO they should be added to the folio:marcRecords and itemData MySQL tables table (see Parse) from whence bibLoad.pl should be able to do what needs to be done. So, the trick is going to be to write a Louisa2?an /opt/folio/parse/Louisa2folio.pl script to get that job done. Note that Louisa's MARCs do not have 999s - since that is the case, rather than copying data from Louisa:items to folio:itemData it would probably be better to have bibLoad.pl look at Louisa:items where it would other wise parse the 999.
So, all that Louisa2folio needs to do is map three fields from Louisa:titles to folio:marcRecords:
Louisa:titles | folio:marcRecords |
---|---|
mrc | marc |
ckey | catalogKey |
createDate (yyyy-mm-dd) | catalogedDate (yyyymmdd) |
I'm adding a field to Louisa:titles to indicate that the data has been copied to folio:marcRecords : Louisa:titles.copied (Y or NULL)
Once those 240,??? Louisa titles are loaded into the marcRecords table then I can see about tweaking the bibLoad.pl script to load them into FOLIO...