Project 2 - The Properties Files

I used several properties files with this project.

default.properties

#default properties
These variables are used by the ant build file, used to deploy my code from the Windows XP machine on which I wrote it to the Linux platform hosting the VuFind installation.
indexer.jar=crra_solr_indexer.jar
build.dir=${basedir}/build
config.dir=${basedir}/config
src.dir=${basedir}/src
dist.dir=${basedir}/dist
deploy.dir=Z:/Eclipse/CRRA_Indexer
The menu class (see previous post) imports these to learn:
solr.url=http://localhost:8983/solr/core1/   ... where the solr installation is
solr.ead=C:/Documents and Settings/slittle2/Desktop/Index Data/ead/xml/  ... where the EAD files are
solr.marc=C:/Documents and Settings/slittle2/Desktop/Index Data/crra.marc  ... where the MARC files are
crra.schema=./schema_map_DID ... which EAD-VuFind map to use
crra.presets=./schema_presets_NotreDame ... whether any preset field file is to be used

slittle.properties
Used on my local machine.
solr.url=http://localhost:8983/solr/core1/
solr.ead=C:/Documents and Settings/slittle2/Desktop/Index Data/ead/xml/
solr.marc=C:/Documents and Settings/slittle2/Desktop/Index Data/crra.marc
crra.schema=./config/schema_map_DID
crra.presets=./config/schema_presets_NotreDame 

solr.properties
 Used by the ant build file, copied from an earlier properties file (test.properties).
solr.url=@solr.url@
solr.ead=@solr.ead@
solr.marc=@solr.marc@
crra.schema=@crra.schema@
crra.presets=@crra.presets@

test.properties
 An earlier properties file, copied at build time into solr.properties for deployment to our VuFind installation.
solr.url=http://localhost:8080/solr/biblio/
solr.ead=/home/slittle2/EAD/ead/xml/
solr.marc=Not currently in use
crra.schema=/home/slittle2/Eclipse/CRRA_Indexer/schema_map_DID
crra.presets=/home/slittle2/Eclipse/CRRA_Indexer/schema_presets_NotreDame

schema_map_CRRA
An EAD-VuFind crosswalk. The first name in each line is the name of the VuFind field, while the rest of the names on the line are the element names within which data must be nested if it is to be sent to the given field.
id eadid
institution repository corpname
institution physloc
building physloc label
language langmaterial language
author author
author2 origination corpname
author2 controlaccess persname
author2 controlaccess corpname
title titlestmt titleproper
title_sub subtitle
physical physdesc extend
physical physdesc dimensions
physical physdesc genreform
physical physdesc physfacet
publisher publisher
publisher publicationstmt address addressline
description profiledesc
contents arrangement
contents c01
topic controlaccess subject
genre controlaccess genreform
geographic geogname 

schema_map_DID
Similar in concept to the previous file, this crosswalk demonstrates some advanced functionality--namely, that including "strictElementPaths" in the file will cause the program to require an *exact match* between the element names in this file and the "path" of the nested data in a given EAD file.

For example, without "strictElementPaths", "subject did" will cause <c01><did> to send data to the "subject" field. With it, <c01><did> will not, since <c01> is not mentioned in the schema file.
strictElementPaths dummy_value The dummy value is included to make this parse properly; with more time I would fix this into a more elegant system of preset values.
id ead archdesc did unitid
title ead archdesc did unittitle
publishDate ead archdesc did unitdate

schema_presets_NotreDame
Similarly to the crosswalk files, this file includes a list of fields, next to which is data that will be put in *every* record in the given field. This ensures some uniformity among the records sent to the index, and provides an opportunity to override data from the EAD files.
institution The University of Notre Dame
collection Hesburgh Libraries
building Hesburgh Library
recordtype ead