Page History

...

BTE configuration file is located in path: [dspace]/config/spring/api/bte.xml and it's a Spring XML configuration file that consists of beans. (If these terms are unknown to you, please refer to Spring Dependency Injection web site for more information)  

Explanation of beans:

 

beam   id= "gr.ekt.bte.core.TransformationEngine"

This bean is instantiated when the import takes place. It deploys a new  BTE transformation engine that will do the transformation from one format to the other. It needs one input argument, the workflow (the processing step mentioned before) that will run when transformation takes place. Normally, you don't need to modify this bean.

 

bean   id= "org.dspace.app.itemimport.DataLoaderService"

Within this bean we declare all the possible data loaders that we need to support. Keep in mind that for each data loader we specify a key that can be used as the value of option "-i" in the import script that we mentioned earlier. Here is the point where you would add a new custom DataLoader in case the default ones doesn't match your needs.

 Moreover, this bean holds the "outputMap" which is a Map between the internal keys that BTE uses to hold metadata and the DSpace metadata fields. (See later on, how data loaders specify the keys that BTE uses to hold the metadata)

 

bean   id= "linearWorkflow"

This bean describes the processing steps. Currently there are no processing steps meaning that all records loaded by the data loader will pass to the output generator, unfiltered and unmodified. ( See next section "Case studies" for info about how to add a filter or a modifier )

...

bean   id= "gr.ekt.bteio.loaders.EndnoteDataLoader"

bean   id= "gr.ekt.bteio.loaders.OAIPMHDataLoader"

Each one of them the 5 first data loaders (which are actually "file" data loaders) has the following properties:

...

c) quoteChar: this property specifies the the quote char of the csv and the default value is "

For the OAIPMHDataLoader, the properties that are supported are:

a) fieldMap: the same as above, the mapping between the keys that hold the metadata in the input and the ones that we want to have internal in the BTE.

b) serverAddress: the base address of the OAI server. Base address can be specified also in the "-s" option of the command prompt. If is specified in both places, the one in command prompt is preferred.

c) prefix: the metadata prefix to be used in the OAI requests

So, in case you need to pass through the system more metadata fields than the ones that are specified by default, you need to change the data loaders configuration and the output map

...