SUNScholar/Submissions/Steps

Go to the source folder by typing as follows:

cd /home/dspace/dspace-1.7.2-src-release/dspace/config

Edit the item-submission.xml file as follows:

nano /home/dspace/dspace-1.7.2-src-release/dspace/config/item-submission.xml

<!-- This XML configuration file allows you to configure the ordering     -->
<!-- and number of the steps that occur in the Item Submission Process.   -->

Submission maps (submission2collection map)

Information from the file for setting up submission maps.

<!-- The process-map maps collection handles to a particular Item         -->
<!-- Submission Process.  This requires that a collection's name be       -->
<!-- unique, even within a community. DSpace does however insure that each-->
<!-- collection's handle is unique.  Process-map provides the means to    -->
<!-- associate a unique collection name with an Item Submission process.  -->
<!-- The process-map also provides the special handle "default" (which is -->
<!-- never a collection), here mapped to "traditional". Any collection    -->
<!-- which does not appear in this map will be associated with the mapping-->
<!-- for handle "default".

For example:

<submission-map>
 <name-map collection-handle="123456789/1" submission-name="full" />
</submission-map>

Submission definitions (submission steps)

This is where you define what steps are completed per submission per collection.

Information from the file for submission definitions (workflows). Tip: Copy an existing definition to create a new one with a new process of name.

 <!-- The submission-definitions map lays out the detailed definition of   -->
 <!-- all the Item Submission Processes (and the ordering of their steps). -->
 <!-- Each separate "submission-process" has a unique name as an attribute,-->
 <!-- which matches one of the names in the process-map. One named         -->
 <!-- "submit-process" has the name "traditional"; as this name suggests,  -->
 <!-- it is the default item submission process, which gets used when      -->
 <!-- the specified collection has no correspondingly named submit-process.-->
 <!--                                                                      -->
 <!-- Each submit-process contains an ordered set of steps; each step      -->
 <!-- defines one "step" occurring during the process of submitting an     -->
 <!-- item.  A step can either be reference by 'id' (in which case it must -->
 <!-- be defined in <step-definitions> above), or defined completely here. -->

For example, the "full" workflow.

<submission-definitions>
 <submission-process name="full">
        <step>
          ...
        </step>
 </submission-process>
</submission-definitions>

Now you can customize the number of steps for the "full" workflow by editing the steps in the new submission process of name full.

Note: There must be a minimum of one step and a maximum of six steps.

Shared submission definitions (shared submission steps)

Information from the file for "shared" step definitions for submission processes.

 <!-- The 'step-definitions' allows you to define steps which you may wish -->
 <!-- to "share" amongst multiple submission-item definitions.  In order to-->
 <!-- share the same step definition, you can refer to it by its unique id -->
 <!-- defined in this section.  EVERY 'step' in this section MUST have a   -->
 <!-- unique identifier in the 'id' attribute!                             -->

---

NANO Editor Help

CTL+O	= Save the file and then press Enter
CTL+X	= Exit "nano"
CTL+K	= Delete line
CTL+U	= Undelete line
CTL+W	= Search for %%string%%
CTL+\	= Search for %%string%% and replace with $$string$$
CTL+C	= Show line numbers

More info = http://en.wikipedia.org/wiki/Nano_(text_editor)

---

Back to Submissions