Page History

...

The handle is everything after "handle/" (in the above example it is "12345.6789/42"). It should look familiar to any DSpace administrator. That is what goes in the collection-handle attribute of your name-map element.

Assigning a default Submission Process per Entity Type 

Alternatively to a collection's Handle, Entities Types can be used as an attribute. With these configurations you will enable default submission forms per Entity type. You don't have to specify every collection's handle to use for a particular submission form if you intend to use entities.
In order to do it so, instead of collection-handle attribute you need to use collection-entity-type. The possible values for this attribute are the ones that you use or that you specified in relationship-types.xml file (please check the documentation for more information). In order the submission process to be assigned to an entity type, you need to previously have associated an Entity Type to a Collection (please check: Configurable Entities#3.ConfigureCollectionsforeachEntitytype). 

As an example, for every time you need to insert a new person in a Person's collection. You just need to specify the submission form to be used, like: submission-name="customPerson" in the example and also the entity type that is associated, like collection-entity-type="Person".

<submission-map>
    <name-map collection-entity-type="Person" submission-name="customPerson" />
    ...
</submission-map>

<submission-definitions>
    <submission-process name="customPerson">
    ...
</submission-definitions>

If a collection collection-handle="12345.6789/42" configuration will prevail over this configuration. Meaning that if a collection-entity-type is defined and a collection-handle is also defined and if a collection handle overlaps in both configurations, then, the submission to be considered it will be the one that is defined by collection-handle (it will prevail the one with more granularity).

Custom Metadata-entry Steps for Submission

...