This documentation relates to an old version of DSpace, version 5.x. Looking for another version? See all documentation.
Support for DSpace 5 ended on January 1, 2023. See Support for DSpace 5 and 6 is ending in 2023
The Item Mapper is a tool in the DSpace web user interface allowing repository managers to display the same item in multiple collections at once. Thanks to this feature, a repository manager is not forced to duplicate items to display them in different collections
Using the Item Mapper
In the XML User Interface, the item mapper can be accessed from the "Context" menu from a collection homepage.
In the JSP User Interface, the item mapper can be accessed from the "Admin Tools" menu on the right side of a collection homepage.
Item Mapper - JSPUI Interface
Item Mapper - XMLUI Interface
The item mapper offers an interface to search for items in the repository with the goal of mapping them to the collection from where you accessed the Item Mapper. While the JSPUI only offers a search for author names, the XMLUI Item Mapper offers a broader search.
The list of items mapped into the current collection can be consulted through the Item Mapper page. While JSPUI immediately shows the list of mapped items, the XMLUI requires you to click "Browse mapped items" in order to access the list.
The list of mapped items provides the functionality to remove the mapping for selected items.
Mapping collection vs Owning collection
The relation between an item and the collection in which it is mapped is different from the relation that this item has with the collection to which it was originally submitted. This second collection is referred to as the "owning" collection. When an item is deleted from the owning collection, it automatically disappears from the mapping collection. From within the mapping collection, the only thing that can be deleted is the mapping relation. Removing this mapping relation does not affect the presence of the item in the owning collection.
Mapping an item does not modify access rights
When an item gets mapped into a collection, it does not receive new access rights. It retains the authorizations that it inherited from the collection that "owns" it. Collection admins who do not have read access to an item will not be able to map them to other collections.