Page History

...

The service is broken down into two phases. In the first phase, the imported publications' metadata are converted to an intermediate format while in the second phase, the intermediate format is converted to DSpace metadata schema

Explanation of beans:

<bean id="org.dspace.submit.lookup.SubmissionLookupService" />

...

This is the top level bean that describes the service of theSubmissionLookup. It accepts two properties:

...

The transformation engine for the first phase of the service (from external service to intermediate format)

 It accepts three properties:

...

Some loaders have more properties:

CSV and TSV (which is actually a CSV loader if you look carefully the class value of the bean) loaders have some more properties:

...

pubmedOnlineDataLoader, crossRefOnlineDataLoader and arXivOnlineDataLoader also support another property:

a) searchProvider searchProvider: if is set to true, the dataloader supports free search by title, author or year. If at least one of these data loaders is declared as a search provider, the accordion tab "Free search" is appeared. Otherwise, it stays hidden.

...

All of them have the property "fieldKeys" which is a list of keys where the step will be applied.

In the case you need to create your own filters and modifiers follow the instructions below:
  
To create a new filter, you need to extend the following BTE abstact class:

...

<bean id="customfilter"   class="org.mypackage.MyFilter" />

<bean id="phase1LinearWorkflow" class="gr.ekt.bte.core.LinearWorkflow">
    <property name="process">
    <list>
		 ... <stuff_already_here> <old filters and modifiers>...
         <ref bean="customfilter" />
    </list>
    </property>
</bean>

<bean id="phase2TransformationEngine" />

The transformation engine for the second phase of the service (from the intermediate format to DSpace metadata schema)

Normally, you do not need to touch any of these three properties. You can edit the reference beans instead.

<bean id="phase2linearWorkflow" />

 This bean specifies the processing steps to be applied to the records metadata before they proceed to the output generator of the transformation engine. Currenty, two steps are supported, but you can add yours as well.

<bean id="fieldMergeModifier" />
<bean id="valueConcatenationModifier" />

 These beans are the processing steps that are supported by the 2nd phase of transformation engine. The first mergest he values of multiple keys to a new key. The second one concatenates the values of a specific key to a unique value.

<bean id="org.dspace.submit.lookup.DSpaceWorkspaceItemOutputGenerator" />

This bean declares the output generator to be used which is, in this case, a DSpaceWorkspaceItem generator. It accepts two properties:

 a) outputMap: A map from the intermediate keys to the DSpace metadata schema fields.

b) extraMetadataToKeep: A list of DSpace metadata schema fields to keep in the output

...