Differences

This shows you the differences between two versions of the page.

--- indexing:marc [2018/12/19 18:47] – demiankatz
+++ indexing:marc [2023/07/21 11:25] – Remove obsolete links/details. demiankatz
@@ Line 15: / Line 15: @@
 Keep these notes in mind to ensure that your records can be imported without any problems:
-  * Export your records in binary (ISO2709) MARC format, not human-readable ASCII.  If for some reason you cannot export the records in binary form, you can use a tool like yaz-marcdump from the [[http://www.indexdata.com/yaz|YAZ]] toolkit to convert one MARC format to another.
+  * Export your records in either binary (ISO2709) MARC format, or MARC-XML, not human-readable ASCII.  If for some reason you cannot export the records into binary or XML form, you can use a tool like yaz-marcdump from the [[http://www.indexdata.com/yaz|YAZ]] toolkit to convert one MARC format to another.
-  * Make sure your resulting file has a ".mrc" extension.  Most versions of [[indexing:solrmarc|SolrMarc]] require this extension, so it is a good practice to use it just to be on the safe side.
+  * Make sure your resulting file has a ".mrc" extension if in ISO2709 format, or a ".xml" extension if in MARCXML.  Most versions of [[indexing:solrmarc|SolrMarc]] require that you differentiate formats with these extensions, so it is a good practice to use them to be on the safe side.
   * Each exported record must contain a unique identifier so that VuFind can tell it apart from the others.  We recommend including your ILS's bibliographic record ID in the exported data for this purpose; you may need to add a special configuration option to your ILS's exporter to make this happen.  VuFind's importer expects to find the unique ID in the 001 field, but you can customize this by editing the marc.properties file (for more details, see [[indexing:solrmarc#customizing_import_mappings|Customizing Import Mappings]]).
 ==== 2. Configure the Importer ====
-The import tool relies on settings in import/import.properties.  If this is the first time you are indexing, make sure that file paths and URLs in this file are correct for your setup.  For more details on what everything means, see the [[http://code.google.com/p/solrmarc/wiki/ConfigProperties|SolrMarc documentation]].
+The import tool relies on settings in import/import.properties.  If this is the first time you are indexing, make sure that file paths and URLs in this file are correct for your setup.  For more details on what everything means, see the [[https://github.com/solrmarc/solrmarc/wiki/Command-line-options|SolrMarc documentation]].
 ==== 3. Import the Records ====
@@ Line 34: / Line 34: @@
 ./import-marc.sh your_records_file.mrc
 </code>
-Note: In versions of VuFind prior to 1.0RC2, import-marc.sh was named import.sh.
 === Windows Method ===
@@ Line 46: / Line 44: @@
 === Advanced Options ===
-// The following optional feature was introduced after the release of VuFind 1.0.1. //
 In both Linux and Windows, you can use the optional "-p" switch to override SolrMarc's default import.properties file with a different file.  For example:
@@ Line 56: / Line 52: @@
 This may be useful if you need to import different sets of records using different mappings.
+For more details, see [[indexing:marc:multiple_configs|Managing Multiple SolrMarc Configurations]].
 === Importing Authority Records ===
-Starting with VuFind 1.1, it is also possible to import authority records into VuFind's separate authority index (see the [[development:architecture:authority_control|Authority Control]] page for more details).  A special tool (import-marc-auth.sh under Linux, import-marc-auth.bat under Windows) is provided to help with this.  This works exactly like the standard import-marc script, except the SolrMarc settings are found in import/import_auth.properties, the default MARC mappings are found in import/marc_auth.properties, and you may provide a second parameter after the MARC filename to specify a set of additional MARC mappings to override the defaults in marc_auth.properties.
+It is also possible to import authority records into VuFind's separate authority index (see the [[development:architecture:authority_control|Authority Control]] page for more details).  A special tool (import-marc-auth.sh under Linux, import-marc-auth.bat under Windows) is provided to help with this.  This works exactly like the standard import-marc script, except the SolrMarc settings are found in import/import_auth.properties, the default MARC mappings are found in import/marc_auth.properties, and you may provide a second parameter after the MARC filename to specify a set of additional MARC mappings to override the defaults in marc_auth.properties.
 Important: The default properties assume a unique identifier in the 010 field. If your identifiers are in 001 (common for ILS exports), specify marc_auth_ils.properties as the second parameter of the script. If your identifiers are somewhere else, you may need to build your own custom properties.
 Authority data is currently used in two ways: it can be searched through the simple Authority module (found at http://your_server/vufind/Authority/Home), and it provides "see also" and "use instead" references within the index generated by the [[Alphabetical Heading Browse]] feature. Additionally, you can choose to activate the Authority Recommend module which will provide Search recommendations to users based on a search of the Authority Index for their current search terms. E.g., if users search for a known pseudonym, the Authority Recommend module will suggest that they search for the registered heading instead.
-== Troubleshooting Under Windows ==
-If you have trouble importing authority records under Windows, it may have to do with the classpath settings in some of the .bsh files found in the import/index_scripts subdirectory of your VuFind installation.  Try changing the addClassPath("../import"); lines to addClassPath("c:/vufind/import"); where "c:/vufind/import" is the path to the import subdirectory of your VuFind installation.  Note the use of forward slashes -- this is acceptable and simplifies escaping issues, even in the Windows environment.
 ==== 4. Restart VuFind ====
@@ Line 83: / Line 77: @@
 ===== Indexing Full Text =====
-Starting with VuFind 1.2, it is possible to harvest full text from URLs found in MARC records.  This requires that you first install [[indexing:full_text_tools|a full-text extraction tool]] and then uncomment the appropriate fulltext line in import/marc_local.properties.  Comments in the property file explain exactly how the functionality works.  Full text indexing is disabled by default.
+It is possible to harvest full text from URLs found in MARC records.  This requires that you first install [[indexing:full_text_tools|a full-text extraction tool]] and then uncomment the appropriate fulltext line in import/marc_local.properties.  Comments in the property file explain exactly how the functionality works.  Full text indexing is disabled by default.
 ===== Sources for Sample Records =====
@@ Line 89: / Line 83: @@
 This section is for listing sources of binary MARC records helpful for testing purposes if you want to try VuFind without using your own records:
-  * [[http://www.learner.org/resources/marc/download.html|Annenberg Media: MARC Records]]
   * [[http://www.archive.org/details/unc_catalog_marc|Internet Archive: MARC Records from UNC]] (you may find additional samples by browsing the Open Library Data collection)
+===== Related Video =====
+The [[videos:indexing_marc_records|Indexing MARC Records]] video provides an overview of some of the information found on this page.
 ---- struct data ----
+properties.Page Owner :
 ----