Learn how your DSpace repository submissions can be easier for you and your content contributors. By modifying your submission configuration you can use these not-so-obvious hints to improve the quality of information in your repository as well as minimizing the time it takes to complete a submission. Topics: Collection templates: pre-filling certain metadata fields on a per collection basis. Reviewer only fields: option to qualify fields in input forms to have them only visible for reviewers in the workflow Type based submission: inclusion of certain metadata fields in the form, based on a selected submission type Modifying your lists of dropdown values (the lists that are included at the bottom of input-forms.xml) Working with hierarchical controlled vocabularies (the XML based subject categories) Enabling LC Name authority control for author values Collection based Input forms: duplicating an input-forms configuration & showing the match between an input-forms config and a collection Simple embargo & private item state

1. Secrets of the Submission Form
Bram Luyten
www.atmire.com

2. WHAT FOLLOWS IS NOT ACTUALLY A SECRET
Most of this is in the docs
http://www.flickr.com/photos/28958738@N06/8455870586/

3. OUTLINE
Collection Templates
Field visibility setting
Publication type based fields
Dropdown options
Hierarchical taxonomies
External Authority Integration
Collection based forms
Embargo settings

4. COLLECTION ITEM TEMPLATES
Definition of pre-filled metadata fields in the
submission form
Collection based

5. COLLECTION ITEM TEMPLATES

6. FIELD VISIBILITY SETTING
Show fields only during submit or workflow
Use case examples
Fields that should only be accessible to
reviewers
Fields that should only be accessible to
submitters
https://wiki.duraspace.org/display/DSDOC4x/Submission+User
+Interface#SubmissionUserInterface-FormsandPages

7. FIELD VISIBILITY SETTING
Accepted values are “submit” and “workflow”

8. PUBLICATION TYPE BASED FIELDS
Show fields only for specific types of content
Use case example
Specific contributor fields that only apply
to ETDs
https://wiki.duraspace.org/display/DSDOC4x/Submission+User+Interface

9. PUBLICATION TYPE BASED FIELDS
Type binding in input-forms.xml
https://wiki.duraspace.org/display/DSDOC4x/Submission+User+Interface

10. DROPDOWN OPTIONS
Modify the standard lists of DSpace dropdown
options
Use case examples
We’re not tracking particular identifiers
Certain content types are not allowed
https://wiki.duraspace.org/display/DSDOC4x/Authority+Control+of+Metadata+Values

11. DROPDOWN OPTIONS
Any “pair” that is useless in the context of your
repository can be safely deleted.

12. HIERARCHICAL TAXONOMIES
Add your own hierarchical taxonomies
https://wiki.duraspace.org/display/DSDOC4x/Authority+Control+of+Metadata+Values

13. HIERARCHICAL TAXONOMIES
Swedish Research Subject Categories default

14. HIERARCHICAL TAXONOMIES
Compiling your own taxonomies in XML
dspace/config/controlled-vocabularies/srsc.xml

15. HIERARCHICAL TAXONOMIES
Linking your taxonomy to a field in input-forms

16. EXTERNAL AUTHORITY INTEGRATION
DSpace can perform live lookup in the Library
of Congress Names service (OCLC)
https://wiki.duraspace.org/display/DSDOC4x/Authority+Control+of+Metadata+Values

17. REPRESENTATION IN METADATA
Together with this external authority key, also a
confidence value is being stored

18. DOES THIS REALLY WORK?

19. COLLECTION BASED FORMS
Every collection can have a different configuration
Use case examples
Content-type based collections
User-persona based collections
https://wiki.duraspace.org/display/DSDOC4x/Submission+User+Interface

20. FORM MAP AND FORM NAME
By default, all collections use the same form

21. FORM DEFINITIONS
By default, all collections use the same form

22. SIMPLE EMBARGO SETTINGS - ITEM
https://wiki.duraspace.org/display/DSDOC4x/Embargo

23. SIMPLE EMBARGO SETTINGS - FILE
https://wiki.duraspace.org/display/DSDOC4x/Embargo

24. ADVANCED EMBARGO SETTINGS

25. PRIVATE ITEM STATUS
Discovery is aware of the item policies.
The old browse and search are not.
As an intermediate step, the private item
status was introduced to keep items out of
search, browse and discovery indexes.

26. Questions?
www.atmire.com