All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
...
For example, the following fragment shows how the collection with handle "12345.6789/42" is assigned the "custom" submission process:
Code Block | ||
---|---|---|
| ||
<submission-map> <name-map collection-handle="12345.6789/42" submission-name="custom" /> ... </submission-map> <submission-definitions> <submission-process name="custom"> ... </submission-definitions> |
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 | ||
---|---|---|
| ||
<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> |
It's a good idea to keep the definition of the default name-map, so there is always a default for collections which do not have a custom form set.
...
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).
...
title | For DSpace 7.6 release it requires Tomcat Restart for every new collection |
---|
...
.
...