One tap mobile +16468769923,,831622397# US (New York) +16699006833,,831622397# US (San Jose)
Dial by your location +1 646 876 9923 US (New York) +1 669 900 6833 US (San Jose) Meeting ID: 831 622 397 Find your local number: https://cornell.zoom.us/u/apAE4wSY5
progress on saving a snapshot of voyager data in postgres that can still be used for reporting after the migration to FOLIO
dealing with the MARC has proved most difficult
geting postgres to match byte for byte voyager was a trick, but managed to do it
data type in postgres is BITA byte array
tables have moved to postgres
MARC segments have been concatenated in postgres tables (views in voyager become tables in postgres)
oraclepg to do this
the marc is byte for byte the same as what was in voyager
can we read it from a microsoft access report that uses some VBA that reads blobs? so far we haven't been able to do that. everything looks good on the surface. postgres odbc drive has option to read byte array as large object but checking the box hasn't helped. Access doesn't import the table, it creates a link. So something on the postgres side has to be providing access a way to support large objects. There's a large object ll module for postgres but AWS won't support it for RDS. Can we load it on an AWS box ourselves? Yes, now have PG with LL module, hosting the byte array marc tables as well as other tables and they all look good but microsoft access reports are still unable to read that marc. Created consistent system of records. When we read the table out, the marc is an OLE object but still can't read, just get empty result set. Suggests the VBA package that is reading through the oracle ODBC driver is doing something specific to Oracle to do that, going to get in touch with the person that wrote the package.