Page History

...

1. The traditional way is to use the "collection-handle" attribute to map a submission form to it's Collection. Its collection-handle attribute is the Handle of the collection. Its submission-name attribute is the submission definition name, which must match the name attribute of a submission-process element (in the submission-definitions section of item-submission.xml.

   1. For example, the following fragment shows how the collection with handle "12345.6789/42" is assigned the "custom" submission process:

      Code Block
      language html/xml
      <submission-map> <name-map collection-handle="12345.6789/42" submission-name="custom" /> ... </submission-map> <submission-definitions> <submission-process name="custom"> ... </submission-definitions>

      
      

2. As of 7.6,  another Another option is to use the "collection-entity-type" attribute to map all Collections which use that Entity Type (requires Configurable Entities) to a specific submission definition name (via the submission-name attribute, similar to above).

   1. For example, the following fragment shows how to map all Collections which use the out-of-the-box Entity Types to a submission definition of the same name:

      Code Block
      language xml
      <submission-map>     ...     <name-map collection-entity-type="Publication" submission-name="Publication"/>     <name-map collection-entity-type="Person" submission-name="Person"/>     <name-map collection-entity-type="Project" submission-name="Project"/>     <name-map collection-entity-type="OrgUnit" submission-name="OrgUnit"/>     <name-map collection-entity-type="Journal" submission-name="Journal"/>     <name-map collection-entity-type="JournalVolume" submission-name="JournalVolume"/>     <name-map collection-entity-type="JournalIssue" submission-name="JournalIssue"/> ... <submission-map>

      
      

   2. WARNING: If you create a new Collection using a specific Entity Type, you must currently restart your servlet container (e.g. Tomcat) for the submission form configuration to take effect for the new Collection.  This is the result of a known bug where the Submission forms are cached until the servlet container is restarted.  See this issue ticket: https://github.com/DSpace/DSpace/issues/7985
3. Finally, it is also possible to use the "community-handle" attribute to map a submission process to all descendant collections that do not have a direct mapping assigned by collection handle or by entity type (also via the submission-name attribute).
   1. For example, the following fragment shows how the descendant collections of the community with handle "12345.6789/38" are assigned the "custom2" submission process:

      Code Block
      language xml
      <submission-map> <name-map community-handle="12345.6789/38" submission-name="custom2" /> ... </submission-map> <submission-definitions> <submission-process name="custom2"> ... </submission-definitions>

   2. If a collection has multiple parent communities with a defined mapping, the collection will use the submission process mapped for the closest community.

...