Warning: This page has not been updated in over over a year and may be outdated or deprecated.
indexing:marc:export_notes
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
indexing:marc:export_notes [2016/01/20 14:30] – [Koha] demiankatz | indexing:marc:export_notes [2023/11/28 19:14] (current) – demiankatz | ||
---|---|---|---|
Line 5: | Line 5: | ||
If you have experience working with a particular system, please consider taking a moment to add notes that might help others get started more quickly. | If you have experience working with a particular system, please consider taking a moment to add notes that might help others get started more quickly. | ||
- | + | * [[indexing:marc:export_notes:aleph|Ex Libris Aleph]] | |
- | + | | |
- | ===== ExLibris Voyager ===== | + | |
- | Voyager includes a marcexport program designed for exporting MARC data. Details of its use can be found in the "Bulk Export of MARC Records" | + | * [[indexing:marc: |
- | + | | |
- | Additionally, | + | |
- | + | ||
- | You may also want to take a look at the [[administration:automation# | + | |
- | + | ||
- | ==== Loading MFHDs with Bibs ==== | + | |
- | + | ||
- | Voyager offers the option of exporting holdings information along with bibliographic information. This can be useful for setting up location-based faceting, but it requires some extra configuration to achieve. | + | |
- | + | ||
- | + | ||
- | After adding the appropriate flag to your marcexport call to include the MFHDs, you need to do a few things on the VuFind side: | + | |
- | + | ||
- | 1. Tell [[indexing:solrmarc|SolrMarc]] to combine the bibs and MFHDs by adding these lines to your import.properties file (found in the import subdirectory of either your VuFind home or [[configuration:local_settings_directory|local settings directory]], | + | |
- | + | ||
- | < | + | |
- | marc.combine_records = 852 | + | |
- | marc.combine_records.left_field = 001 | + | |
- | marc.combine_records.right_field = 004 | + | |
- | </ | + | |
- | + | ||
- | More details on the exact meanings of the various marc.combine_records settings can be found in the [[https:// | + | |
- | + | ||
- | // NOTE: SolrMarc expects holdings records to immediately follow matching bibliographic records. If you have holdings records shared by multiple bibliographic records (a rare situation caused when items are bound together but cataloged separately) you may have some problems during import. // | + | |
- | + | ||
- | 2. Tell [[indexing:solrmarc|SolrMarc]] to index your locations to an appropriate field and map Voyager' | + | |
- | + | ||
- | < | + | |
- | collection = 852b, locations.properties(locations) | + | |
- | </ | + | |
- | + | ||
- | // Note: " | + | |
- | + | ||
- | 3. Create the translation map file referenced in step 2 -- this goes in the translation_maps subdirectory of your import directory and will need to be customized to your institution' | + | |
- | + | ||
- | < | + | |
- | locations.MAIN = Main Stacks | + | |
- | locations.MICRO = Micro Collection | + | |
- | locations.MUSIC = Music CDs | + | |
- | </ | + | |
- | ===== ExLibris Aleph ===== | + | |
- | + | ||
- | **Data Preparation** | + | |
- | * choose data to export via p-ret-01 | + | |
- | * if you don’t export everything, you need to run p-ret-10 afterwards (for example if you don’t want to export records which items are lost/ | + | |
- | + | ||
- | \\ | + | |
- | **Exporting Data** | + | |
- | * export data via p-print-03 | + | |
- | * since Aleph v20 you can export directly to MARC binary mode (XML; necessary for UTF8) | + | |
- | * in earlier versions you need a tool to convert the data (for example: yaz for SLES 11 http:// | + | |
- | \\ | + | |
- | * export options (were recommended to me): | + | |
- | * Fix-Routine: | + | |
- | + | ||
- | MABUS fix_doc_mab | + | |
- | MABUS fix_doc_convit | + | |
- | MABUS fix_doc_convit | + | |
- | + | ||
- | It is probable that the MABUS routine in tab_fix is superflous for MARC-Libraries (this is an example for those who work with MAB-Format). | + | |
- | + | ||
- | * Expand-Routine: | + | |
- | + | ||
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | + | ||
- | If you use MARC-format, | + | |
- | + | ||
- | | + | |
- | | + | |
- | + | ||
- | + | ||
- | + | ||
- | * If you use ADAM (catalogue enrichment), | + | |
- | \\ | + | |
- | + | ||
- | * Character Conversion: none \\ | + | |
- | \\ | + | |
- | + | ||
- | **Further Information I received: | + | |
- | * Some libraries use the PST, AVA, OWN, DEL, and STA fields for the export | + | |
- | * To update the index you can use the field z07p to determine the items to export and insert into the index (for example new items) | + | |
- | \\ | + | |
- | **Documentation** | + | |
- | + | ||
- | * Expand-Routines: | + | |
- | http:// | + | |
- | \\ | + | |
- | * RESTful API: | + | |
- | http:// | + | |
- | + | ||
- | \\ | + | |
- | \\ | + | |
- | Notes from Václav Rosecký: | + | |
- | + | ||
- | For export process we use procedure print-03. If you need incremental | + | |
- | update, you must combine print-03 with ret-01. Procedure ret-01 | + | |
- | returns modified system numbers and you can use this list as the input | + | |
- | for print-03. Export format is ISO 2709 MARC and you should not need | + | |
- | any additional data processing in SolrMarc if you have one | + | |
- | bibliographic base. If you have two or more bibliographic bases, you | + | |
- | must modify index scripts in vufind to change record ID (we have two | + | |
- | bibliographic bases, so our id in vufind is base + sysno separated by | + | |
- | ' | + | |
- | + | ||
- | + | ||
- | ===== Innovative Millennium | + | |
- | + | ||
- | Before exporting your records, review your export tables to make sure that you are exporting all of the fields that you want and none of the fields that you don’t want. In particular, make sure that item and order record information containing potentially confidential data is not exported. Manual page 101563 has information about how to view export tables; to change your export tables, you must submit a service request. | + | |
- | + | ||
- | If you want to export 970 fields containing table of contents information from a third-party vendor such as Backstage Library Works, you must get your vendor to contact Innovative and give permission before Innovative will change your export table to include 970 fields. | + | |
- | + | ||
- | Data Exchange (see manual page 106000) is the easiest way to export the records used for the initial load. Although the file of records that is created will have an .out extension, it is really in .mrc format; it is safe to simply change the extension. | + | |
- | + | ||
- | A script for daily exports of new items is available on the IUG Clearinghouse under the title “Create List of New Items automated.” | + | |
- | + | ||
- | ==== Related Tools ==== | + | |
- | + | ||
- | * [[http:// | + | |
- | + | ||
- | ===== NewGenLib ===== | + | |
- | + | ||
- | See [[http:// | + | |
- | + | ||
- | ===== SirsiDynix Horizon ===== | + | |
- | // Note: These comments were written in reference to VuFind 1.0RC1 and Horizon 7.3.4 but should apply to other versions of both packages as well. // | + | |
- | + | ||
- | Horizon provides two methods for exporting MARC records: either from the Horizon client itself or using a command line utility. | + | |
- | + | ||
- | To create an export target that doesn' | + | |
- | + | ||
- | Now that an export target has been created, the actual MARC records can be exported using either the Horizon client or from the command line as mentioned earlier. | + | |
- | + | ||
- | Exporting MARC records from the command line requires a utility called MarcOut.exe, | + | |
- | + | ||
- | marcout / | + | |
- | + | ||
- | When checking item status, VuFind queries your Horizon database' | + | |
- | + | ||
- | ===== SirsiDynix Symphony ===== | + | |
- | + | ||
- | Notes currently unavailable -- please help us fill in the documentation! | + | |
- | + | ||
- | ===== Koha ===== | + | |
- | Koha has a cgi-bin/ | + | |
- | + | ||
- | To run that manually, you will need to set the path for PERL5LIB (or whatever your perl lib variable is), and set the variable that points to the Koha configuration file. They will look something like: | + | |
- | < | + | |
- | export PERL5LIB=/ | + | |
- | export KOHA_CONF=/ | + | |
- | </ | + | |
- | To do the export, you will want to do something like this (the paths may differ) | + | |
- | < | + | |
- | / | + | |
- | </ | + | |
- | Once you have exported the koha records, you will need to import the records into VuFind. | + | |
- | + | ||
- | Copy your marc_local.properties from vufind/ | + | |
- | make the changes to this file that you need to | + | |
- | < | + | |
- | #collection = "" | + | |
- | institution = "My University" | + | |
- | #building = " | + | |
- | id = 999c, first | + | |
- | </ | + | |
- | Koha needs to use the id = 999c for Vufind to properly tie the two together. | + | |
- | + | ||
- | Now you are ready to [[indexing: | + | |
- | + | ||
- | See the [[indexing:koha|How to index Koha with VuFind]] page for a full end-to-end example. | + | |
---- struct data ---- | ---- struct data ---- | ||
+ | properties.Page Owner : | ||
---- | ---- | ||
indexing/marc/export_notes.1453300231.txt.gz · Last modified: 2016/01/20 14:30 by demiankatz