ldpmarc v1.2.0 released
4 views
Skip to first unread message
Nassib Nassar
Jun 22, 2021, 7:22:13 PM6/22/21
to librarydatapla...@googlegroups.com
ldpmarc v1.2.0 is released
https://github.com/library-data-platform/ldpmarc/releases/tag/v1.2.0
* The output table has been renamed to public.srs_marctab.
* Only "current" records are included in the output table. A record is defined as current if srs_records.state = ACTUAL and 999$i contains an identifier.
* The tag column has been renamed to field for consistency with SRS naming.
* The bib_id column has been removed.
* A new column matched_id has been added:
The matched_id is a "masking" ID presented in inventory which links back to the real ID; the real ID can change but matched_id persists. Multiple real IDs can be linked to the matched_id as each version of the SRS record gets a new ID.
* New columns instance_hrid and instance_id have been added.
* A bug has been fixed in CSV output which caused the process to terminate.
* Experimental support for incremental update has been added. It can be enabled using the -i command-line option. See the readme for details.
https://github.com/library-data-platform/ldpmarc/releases/tag/v1.2.0
* The output table has been renamed to public.srs_marctab.
* Only "current" records are included in the output table. A record is defined as current if srs_records.state = ACTUAL and 999$i contains an identifier.
* The tag column has been renamed to field for consistency with SRS naming.
* The bib_id column has been removed.
* A new column matched_id has been added:
The matched_id is a "masking" ID presented in inventory which links back to the real ID; the real ID can change but matched_id persists. Multiple real IDs can be linked to the matched_id as each version of the SRS record gets a new ID.
* New columns instance_hrid and instance_id have been added.
* A bug has been fixed in CSV output which caused the process to terminate.
* Experimental support for incremental update has been added. It can be enabled using the -i command-line option. See the readme for details.
Reply all
Reply to author
Forward
0 new messages