DSpace

The automapper plugin allows to define a "logical rule"
(java class) for the automatic mapping
of an item to a different collection than that where it
was submitted.
The plugin consists of two classes:
- AutomapperManager that is responsible of managing any
"logical rule" defined in the DSpace configuration;
- AutoMapper, the abstract class that any "logical
rule" needs to implement.
A new table must be created in the db, sql is provided
in etc/automapper.sql file.

With the plugin we provide a generic sample
implementation of this logical rule:
"an item must be mapped in the collection (within a
defined community), whose name is equal to the value
of a configured metadata".
This plugin allows the automatic creation of different
"views" to browse the archive: items can be viewed
from different collections and communities (eg. both
from a department community and a subject tree).
Moreover, this allows an item to be automatically
included in more than one OAI-PMH set and to be notified
from different collections. More information: slides
19-21 at http://dsug2006.uib.no/archive/meschini.ppt.

This "logical rule" is named MetaDataMapper and can be
configured in dspace.cfg using the parameters below:
automapper.metadata.root.<index> = ID of the community
where the collection must be searched
automapper.metadata.separator.<index> = the string that
will be used to indicate a subCommunity
automapper.metadata.type.<index> = the metadata that
will be used (multi metadata can be specified with a
comma separated list, eg. schema.element.qualifier,
schema2.element2.qualifier2)
<index> is an incremental integer (1+), multi metadata
mapper can be configured!

Example (from Earth-prints.org repository,
www.earth-prints.org)
automapper.metadata.root.1 = 102
automapper.metadata.separator.1 = ::
automapper.metadata.type.1 = dc.subject.INGV
where
item - hdl: 2122/783
and
dc.subject.INGV = 04. Solid Earth::04.06.
Seismology::04.06.05. Historical seismology
the item will be mapped in:
Subject Classification (Community ID: 102)
- 01. Atmosphere
- 02. Cryosphere
- 03. Hydrosphere
- 04. Solid Earth (Community match! first part of
metadata value)
-- 04.01. Earth Interior
-- 04.02. Exploration geophysics
-- 04.03. Geodesy
-- 04.04. Geology
-- 04.05. Geomagnetism
-- 04.06. Seismology (Community match! second part of
metadata value)
--- 04.06.01. Earthquake faults: properties and evolution
--- 04.06.02. Earthquake interactions and probability
--- 04.06.03. Earthquake source and dynamics
--- 04.06.04. Ground motion
--- 04.06.05. Historical seismology (Collection match!
final part of metadata the item will be mapped in this
collection)

Other "logical rules" can be implemented fastly writing
an implementation of AutoMapper abstract class: only the
getMappingCollection(Context context, Item item) method
must be implemented.
The functionality can be activated by cmd line (main of
AutomapperManager,
eg dsrun org.dspace.app.automapper.AutomapperManager
--help) or used in "real time" (new submissions, edit
item).
In this last case, some small modifications are
required to the Browse class (automapper-browse-patch
is the
patch for dspace 1.4 version)
Best regards,
Andrea Bollini