About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
indexing:eprints

Differences

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

Link to this comparison view

Next revision
Previous revision
importing_records:how_to_index_eprints_with_vufind [2012/05/08 12:36] – created demiankatzindexing:eprints [2023/11/28 20:08] (current) demiankatz
Line 1: Line 1:
-====== How to import EPrints with VuFind ======+====== How to import EPrints with VuFind® ======
  
 // Tips and configurations courtesy of Ranju Upadhyay, National University of Ireland Maynooth. // // Tips and configurations courtesy of Ranju Upadhyay, National University of Ireland Maynooth. //
  
-As our repo is EPrints, I have needed to do the configuration in VuFind for data harvest from EPrints It is not whole lot different than [[how to index dspace with vufind|DSpace]].+The [[https://www.eprints.org|EPrints]] repository is quite similar to [[indexing:dspace|DSpace]].
  
-On the EPrints side, the data is already exposed for harvesting in oai_dc, so there was no configuration needed there On VuFind, I did the following:+On the EPrints side, the data is already exposed for harvesting in oai_dc, so no additional configuration is required to obtain metadataYou can follow these steps to ingest EPrints data into VuFind®:
  
 ===== 1. Set up OAI Harvester ===== ===== 1. Set up OAI Harvester =====
  
-I created a section on oai.ini which looks something like this:+Create an oai.ini section similar to this example from National University of Ireland Maynooth:
  
 <code> <code>
Line 23: Line 23:
 </code> </code>
  
-The big thing that I discovered in this stage was that VuFind does not like full colon i.e. ":" so I had to use "-" as the delimeter between my namespace and eprints uuid i.e. nuimeprn- and not nuimeprn: +Because colons in identifiers can cause problems, it is helpful to remap the prefix to use "-" as the delimiter the my namespace and EPrints uuidi.e. nuimeprn- and not nuimeprn:
  
 ===== 2. Set up import properties ===== ===== 2. Set up import properties =====
  
-I then copied the dspace.properities file and renamed it to eprints.properties.In this file I made the following changes:+You can copy the dspace.properities file to eprints.properties, and make adjustments similar to:
  
 <code> <code>
Line 36: Line 36:
 ===== 3. Set up import XSLT ===== ===== 3. Set up import XSLT =====
  
-I then copied dspace.xsl and renamed it eprints.xsl.  Only change I made on this file is:+You can also copy dspace.xsl to eprints.xsl.  Two small changes should cover the differences between DSpace and EPrints. 
 + 
 +First, set the record type to eprints:
  
 <code> <code>
 <!-- RECORDTYPE --> <!-- RECORDTYPE -->
 <field name="recordtype">eprints</field> <field name="recordtype">eprints</field>
 +</code>
 +
 +Second, add support for URLs from the dc:relation field:
 +
 +<code>
 +         <xsl:for-each select="dc:relation">
 +            <field name="url">
 +                   <xsl:value-of select="normalize-space()"/>
 +            </field>
 +         </xsl:for-each>
 +</code>
 +
 +===== 4. Set Up Change Tracking (optional) =====
 +
 +If you need to track record change dates (see [[tracking_record_changes|Tracking Record Changes]] for details), you need to do a couple of extra things:
 +
 +  * Uncomment the injectDate line in the oai.ini file section above.
 +  * Add these lines to eprints.properties:
 +
 +<code>
 +change_tracking_core = "biblio"
 +change_tracking_date_tag_name = "datestamp"
 </code> </code>
 ---- struct data ---- ---- struct data ----
 +properties.Page Owner : 
 ---- ----
  
indexing/eprints.1336480588.txt.gz · Last modified: 2014/06/13 13:13 (external edit)