All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
...
Info | ||
---|---|---|
| ||
<util:map id="org.dspace.importer.external.metadatamapping.MetadataFieldConfig" value-type="org.dspace.importer.external.metadatamapping.contributor.MetadataContributor"> <entry key-ref="dc.title" value-ref="titleContrib"/> <entry key-ref="dc.contributor.author" value-ref="authorContrib"/> </util:map> |
Note that the single field mappings used for the combined author mapping are not added to this list.
First read the base documentation on external importing This documentation explains the implementation of the importer framework using pubmed as an example.
The configuration done for pubmed specifically is located at pubmed-integration.xml in dspace/config/spring/api I will not go into detail to what exactly is configured for the pubmed integration as it is simply a usage of the classes explained here
Code Block | ||
---|---|---|
| ||
<!-- Find publications based on ID/DOI/Title/Author to pre-fill the submission
<step>
<heading>submit.progressbar.lookup</heading>
<processing-class>org.dspace.submit.step.XMLUIStartSubmissionLookupStep</processing-class>
<jspui-binding>org.dspace.app.webui.submit.step.JSPStartSubmissionLookupStep</jspui-binding>
<xmlui-binding>org.dspace.app.xmlui.aspect.submission.submit.StartSubmissionLookupStep</xmlui-binding>
<workflow-editable>true</workflow-editable>
</step>
--> |
To be able to do the lookup for our configured import-service, we need to be able to know what url to use to check for publications. This can be done by setting the publication.url property though maven using 2 different ways.
These classes are simply implementations based of the base classes defined in importer/external. They add characteristic behaviour for services/mapping for the pubmed specific data.