Difference between revisions of "SUNScholar/Submission System"

From Libopedia
Jump to navigation Jump to search
m
 
(51 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Introduction==
+
<center>
{{WARNING}}
+
'''[[SUNScholar/Operational_Guide|BACK TO OPERATIONAL GUIDE]]'''
 +
</center>
  
Items are submitted to collections using forms. Each collection can have its own customised submission forms and these forms can also have customised pages. Below is information about form pages and collection submissions.
+
===Introduction===
 +
Items are submitted to collections using workflow steps with forms. Each collection can have its own customised submission steps and forms.
  
==[[SUNScholar/Submissions/Steps|Submission Steps]]==
+
===<font color="red">Please note:</font>===
 +
Researchers may complain of a submission process that is onerous and takes too much time. A possible remedy is to create very simple submission forms per faculty/school/department for "quick" submissions.
 +
After submission, then let the faculty/subject librarians perform the submission workflow of reviewer, or metadata editor and then move or map the item into the correct collection.
  
==[[SUNScholar/Submissions/Forms|Submission Forms per Step]]==
+
===[[SUNScholar/Submissions/Steps|Step 1 - Define submission steps, where each step has a form]]===
  
==Notes==
+
===[[SUNScholar/Submissions/Forms|Step 2 - Define submission forms, as per the steps defined above and which may have custom input fields per form]]===
  
* The <code>&lt;required&gt;</code> element contains the textual hint displayed to the submitter about why the field is required. Leave it empty for optional fields.
+
===Step 3 - Activate new forms===
* The <code>&lt;vocabulary&gt;</code> element is optional.  It allows you to specify the controlled vocabulary that this field should select its values from.  This field also has an optional <code>closed</code> attribute.  If closed is set to true, a user can only select values from the controlled vocabulary.  By default, closed is set to false, which allows a user to also enter in free text if he/she chooses.  For example:<pre>&lt;vocabulary closed=”true”&gt;srsc&lt;/vocabulary&gt; </pre>
 
* The name of the controlled vocabulary must correspond to the name of the XML file (without “.xml”) which contains the vocabulary.  So, in the above example, <code>srsc</code> references the vocabulary specified in the file located at ''[dspace]''/config/controlled-vocabularies/srsc.xml
 
* Valid input types (for <code>&lt;input-type&gt;</code>) are:
 
** “date” 
 
** “name” (two text boxes, labeled last and first name)
 
** “onebox” (a one-line textbox)
 
** “twobox” (two textboxes on a single line)
 
** “dropdown” (for which you must specify a <code>value-pairs-name</code> attribute referring to the <code>&lt;value-pairs&gt;</code> list of allowed values.
 
** “qualdrop_value” (a textbox, which is preceded by a “qualifying” dropdown of values.  Requires a <code>value-pairs-name</code> attribute, similar to “dropdown”.  Also requires <code>&lt;repeatable&gt;</code> is set to “true”)
 
** “textarea” 
 
* Setting the <code>&lt;repeatable&gt;</code> element to “true” creates an “Add more” button, which allows you to add multiple values into that particular field.  Examples of this include the authors and keywords fields in the standard DSpace submission process.
 
 
 
==Activation of modified workflows==
 
 
{{REBUILD}}
 
{{REBUILD}}
  
==References==
+
===Tips===
*http://web.lib.sun.ac.za/dspace/docs/1.7.2/Submission%20User%20Interface.html
+
*http://www.slideshare.net/bramluyten/secrets-of-the-dspace-submission-form
* http://wiki.dspace.org/index.php/Alter_submission_input_forms
+
*https://wiki.duraspace.org/display/DSPACE/Alter+submission+input+forms
* http://di.tamu.edu/projects/xmlui/manakin/
+
*https://wiki.duraspace.org/display/DSPACE/Change+a+form+value
* http://cavlec.yarinareth.net/2008/01/07/the-dspace-batch-importer
+
*http://wiki.dspace.org/index.php/Alter_submission_input_forms
  
'''[[SUNScholar/Customisation|Back to Customisation]]'''
+
===References===
 +
*https://wiki.duraspace.org/display/DSDOC5x/Submission+User+Interface
 +
*https://wiki.duraspace.org/display/DSDOC4x/Submission+User+Interface
 +
*https://wiki.duraspace.org/display/DSDOC3x/Submission+User+Interface
 +
*http://dri.ie/vocabularies
 +
*http://thinkchecksubmit.org
 +
[[Category:Customisation]]

Latest revision as of 12:00, 28 May 2016

BACK TO OPERATIONAL GUIDE

Introduction

Items are submitted to collections using workflow steps with forms. Each collection can have its own customised submission steps and forms.

Please note:

Researchers may complain of a submission process that is onerous and takes too much time. A possible remedy is to create very simple submission forms per faculty/school/department for "quick" submissions. After submission, then let the faculty/subject librarians perform the submission workflow of reviewer, or metadata editor and then move or map the item into the correct collection.

Step 1 - Define submission steps, where each step has a form

Step 2 - Define submission forms, as per the steps defined above and which may have custom input fields per form

Step 3 - Activate new forms

Rebuild the DSpace webapps using the custom rebuild script.

Tips

References