Community Company Search Contact

item-submission-XMLUI.xml from DSpace at Krugle

Show item-submission-XMLUI.xml syntax highlighted

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE item-submission SYSTEM "item-submission.dtd">

<!-- XML-UI Configurable Submission configuration file  -->

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

 <!-- 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".                                                -->
 <submission-map>
   <name-map collection-handle="default" submission-name="traditional" />
 </submission-map>


 
 <!-- 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!                             -->
 <!--                                                                      -->
 <!-- Each <step> REQUIRES the following attributes (@) and properties:    --> 
 <!-- @id       - The unique identifier for this step                      -->
 <!-- <processing-class> - The class which will process all information for-->
 <!--             this step. The class must extend the                     -->
 <!--             'org.dspace.submit.AbstractProcessingStep' class!        -->
 <!--             This property should reference the full path of the class-->
 <!--			  (e.g. org.dspace.submit.step.MyCustomStep)               -->
 <!--																	   -->
 <!-- The following properties are OPTIONAL for each <step>:			   -->
 <!-- <heading> -    References the message text (from the 				   -->
 <!--			     Messages.xml file) which will be used as this         -->
 <!--			     step's heading in the progress-bar.  If unspecified,  -->
 <!--			     the step does not show up in the Progress Bar.	       -->
 <!-- <xml-ui-class> - The class which acts as the XML-UI Transformer      -->
 <!--				 for this step.  This class must extend the            -->
 <!--				 'org.dspace.app.xmlui.submission.AbstractSubmissionStep'-->
 <!--				 class.  This class must generate the body of a valid  -->
 <!--                XML DRI document which can be transformed by Manakin. -->
 <!-- <workflow-editable> - whether or not this step will appear during the-->
 <!--				 "Edit Metadata" workflow approval process.  This field-->
 <!--				 defaults to TRUE (which means it can be edited during -->
 <!--				 the "Edit Metadata" workflow stage)				   -->
 <!--                                                                      -->
 <!--                                                                      -->
 <step-definitions>
     <!-- The "collection" step is a "special step" which is *REQUIRED* to be-->
     <!-- in this section!  In DSpace, all submitted items must be           -->
     <!-- immediately assigned to a collection. This step ensures that a     -->
     <!-- collection is always selected.  If a user is already submitting    -->
     <!-- from within a Collection (by clicking the "Submit to This          -->
     <!-- Collection" button) then this step will be automatically skipped.  -->
     <!-- In all other cases, this step ensures that the user *first* selects-->
     <!-- a collection!                                                      -->
     <!-- Since this is a "special step", it is *automatically* added at the -->
     <!-- beginning of each 'submission-process' (therefore it should not be -->
     <!-- referenced by any of the below 'submission-process' tags).  Also as-->
     <!-- a special step, it is currently NEVER editable in a workflow.      -->                              
     <step id="collection">
       <heading></heading> <!--can specify heading, if you want it to appear in Progress Bar-->
       <processing-class>org.dspace.submit.step.SelectCollectionStep</processing-class>
       <xml-ui-class>org.dspace.app.xmlui.aspect.submission.submit.SelectCollectionStep</xml-ui-class>
       <workflow-editable>false</workflow-editable>
     </step>
     
     <!-- The "complete" step is a "special step" which is *REQUIRED* to be  -->
     <!-- in this section!  In DSpace, when a submission is completed,       -->
     <!-- a workflow is automatically kicked off (if one exists)             -->
     <!-- This "complete" step performs all backend processing that occurs   -->
     <!-- immediately upon completing the submission.                        -->
     <!-- Since this is a "special step", it is *automatically* added at the -->
     <!-- end of each 'submission-process' (therefore it should not be       -->
     <!-- referenced by any of the below 'submission-process' tags).  Also as-->
     <!-- a special step, it is currently NEVER editable in a workflow.      -->                             
     <step id="complete">
       <heading>xmlui.Submission.general.progress.complete</heading>
       <processing-class>org.dspace.submit.step.CompleteStep</processing-class>
       <workflow-editable>false</workflow-editable>
     </step>
     
 </step-definitions>

 <!-- 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. -->
 <!--                                                                      -->
 <!-- If the step is not referred to by 'id', then the <step> REQUIRES the -->
 <!-- following properties are defined:                                    --> 
 <!-- <processing-class> - The class which will process all information for-->
 <!--             this step. The class must extend the                     -->
 <!--             'org.dspace.submit.AbstractProcessingStep' class!        -->
 <!--             This property should reference the full path of the class-->
 <!--			  (e.g. org.dspace.submit.step.MyCustomStep)               -->
 <!--                                                                      -->
 <!-- The following properties are OPTIONAL for each <step>:			   -->
 <!-- <heading> -    References the message text (from the 				   -->
 <!--			     Messages.xml file) which will be used as this         -->
 <!--			     step's heading in the progress-bar.  If unspecified,  -->
 <!--			     the Step does not show up in the Progress Bar.	       -->
 <!-- <xml-ui-class> - The class which acts as the XML-UI Transformer      -->
 <!--				 for this step.  This class must extend the            -->
 <!--				 'org.dspace.app.xmlui.submission.AbstractSubmissionStep'-->
 <!--				 class.  This class must generate the body of a valid  -->
 <!--                XML DRI document which can be transformed by Manakin. -->
 <!-- <workflow-editable> - whether or not this step will appear during the-->
 <!--				 "Edit Metadata" workflow approval process.  This field-->
 <!--				 defaults to TRUE (which means it can be edited during -->
 <!--				 the "Edit Metadata" workflow stage).  Set to either   -->
 <!--				 "true" or "false".				                       -->
 <!--                                                                      -->
 <submission-definitions>
   
   <!--This "traditional" process defines the DEFAULT item submission process-->
   <submission-process name="traditional">
        
     <!--Step 1 will be to gather initial information-->
	  <step>
	    <heading>xmlui.Submission.general.progress.initial-questions</heading>
	    <processing-class>org.dspace.submit.step.InitialQuestionsStep</processing-class>
	    <xml-ui-class>org.dspace.app.xmlui.aspect.submission.submit.InitialQuestionsStep</xml-ui-class>
	    <workflow-editable>true</workflow-editable>
	  </step>  
          
      <!--Step 2 will be to Describe the item.-->
      <step>
        <heading>xmlui.Submission.general.progress.describe</heading>
        <processing-class>org.dspace.submit.step.DescribeStep</processing-class>
        <xml-ui-class>org.dspace.app.xmlui.aspect.submission.submit.DescribeStep</xml-ui-class>
        <workflow-editable>true</workflow-editable>
      </step>
          
      <!--Step 3 will be to Upload the item-->
      <step>
        <heading>xmlui.Submission.general.progress.upload</heading>
        <processing-class>org.dspace.submit.step.UploadStep</processing-class>
        <xml-ui-class>org.dspace.app.xmlui.aspect.submission.submit.UploadStep</xml-ui-class>
        <workflow-editable>true</workflow-editable>
      </step>
     
 	  <!--Step 4 will be to Verify everything -->
 	  <step>
 	    <heading>xmlui.Submission.general.progress.review</heading>
        <processing-class>org.dspace.submit.step.VerifyStep</processing-class>
 	    <xml-ui-class>org.dspace.app.xmlui.aspect.submission.submit.ReviewStep</xml-ui-class>
        <workflow-editable>true</workflow-editable>
      </step>
     
      <!--Step 5 will be to Sign off on the License-->
      <step>
        <heading>xmlui.Submission.general.progress.license</heading>
        <processing-class>org.dspace.submit.step.LicenseStep</processing-class>
        <xml-ui-class>org.dspace.app.xmlui.aspect.submission.submit.LicenseStep</xml-ui-class>
        <workflow-editable>false</workflow-editable>
     </step>
     
   </submission-process>

 </submission-definitions>

</item-submission>

See more files for this project here

DSpace

Open Source Digital Asset Management system that enables services for access, provision, stewardship and re-use of digital assets with a focus on educational and research materials

Project homepage: http://sourceforge.net/projects/dspace
Programming language(s): Java,JSP,XML
License: other

  controlled-vocabularies/
    LICENCES
    nsi.xml
    srsc.xml
  crosswalks/
    QDC.properties
    mods-submission.xsl
    mods.properties
    sample-crosswalk-DIM2DC.xsl
  emails/
    change_password
    feedback
    internal_error
    register
    submit_archive
    submit_reject
    submit_task
    subscription
    suggest
  registries/
    bitstream-formats.xml
    dublin-core-types.xml
  dc2mods.cfg
  default.context.xml
  default.license
  dspace.cfg
  dstat.cfg
  dstat.map
  input-forms.dtd
  input-forms.xml
  item-submission-JSPUI.xml
  item-submission-XMLUI.xml
  item-submission.dtd
  log4j-console.properties
  log4j-handle-plugin.properties
  log4j.properties
  log4j.xml
  news-side.html
  news-top.html
  oaicat.properties
  xmlui.xconf