Secrets of the Submission Form
Bram Luyten

www.atmire.com
WHAT FOLLOWS IS NOT ACTUALLY A SECRET

Most of this is in the docs
http://www.flickr.com/photos/28958738@N06/8455870586/
OUTLINE
Collection Templates
Field visibility setting
Publication type based fields
Dropdown options
Hierarchical taxonomies
External Authority Integration
Collection based forms
Embargo settings
COLLECTION ITEM TEMPLATES

Definition of pre-filled metadata fields in the
submission form
Collection based
COLLECTION ITEM TEMPLATES
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
FIELD VISIBILITY SETTING

Accepted values are “submit” and “workflow”
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
PUBLICATION TYPE BASED FIELDS

Type binding in input-forms.xml

https://wiki.duraspace.org/display/DSDOC4x/Submission+User+Interface
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
DROPDOWN OPTIONS

Any “pair” that is useless in the context of your
repository can be safely deleted.
HIERARCHICAL TAXONOMIES

Add your own hierarchical taxonomies

https://wiki.duraspace.org/display/DSDOC4x/Authority+Control+of+Metadata+Values
HIERARCHICAL TAXONOMIES

Swedish Research Subject Categories default
HIERARCHICAL TAXONOMIES

Compiling your own taxonomies in XML

dspace/config/controlled-vocabularies/srsc.xml
HIERARCHICAL TAXONOMIES

Linking your taxonomy to a field in input-forms
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
REPRESENTATION IN METADATA

Together with this external authority key, also a
confidence value is being stored
DOES THIS REALLY WORK?
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
FORM MAP AND FORM NAME

By default, all collections use the same form
FORM DEFINITIONS

By default, all collections use the same form
SIMPLE EMBARGO SETTINGS - ITEM

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

https://wiki.duraspace.org/display/DSDOC4x/Embargo
ADVANCED EMBARGO SETTINGS
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.
Questions?

www.atmire.com

Secrets of the DSpace Submission Form

  • 1.
    Secrets of theSubmission Form Bram Luyten www.atmire.com
  • 2.
    WHAT FOLLOWS ISNOT ACTUALLY A SECRET Most of this is in the docs http://www.flickr.com/photos/28958738@N06/8455870586/
  • 3.
    OUTLINE Collection Templates Field visibilitysetting Publication type based fields Dropdown options Hierarchical taxonomies External Authority Integration Collection based forms Embargo settings
  • 4.
    COLLECTION ITEM TEMPLATES Definitionof pre-filled metadata fields in the submission form Collection based
  • 5.
  • 6.
    FIELD VISIBILITY SETTING Showfields 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 Acceptedvalues are “submit” and “workflow”
  • 8.
    PUBLICATION TYPE BASEDFIELDS 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 BASEDFIELDS Type binding in input-forms.xml https://wiki.duraspace.org/display/DSDOC4x/Submission+User+Interface
  • 10.
    DROPDOWN OPTIONS Modify thestandard 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 yourown hierarchical taxonomies https://wiki.duraspace.org/display/DSDOC4x/Authority+Control+of+Metadata+Values
  • 13.
    HIERARCHICAL TAXONOMIES Swedish ResearchSubject Categories default
  • 14.
    HIERARCHICAL TAXONOMIES Compiling yourown taxonomies in XML dspace/config/controlled-vocabularies/srsc.xml
  • 15.
    HIERARCHICAL TAXONOMIES Linking yourtaxonomy to a field in input-forms
  • 16.
    EXTERNAL AUTHORITY INTEGRATION DSpacecan 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 Togetherwith this external authority key, also a confidence value is being stored
  • 18.
  • 19.
    COLLECTION BASED FORMS Everycollection 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 ANDFORM 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.
  • 25.
    PRIVATE ITEM STATUS Discoveryis 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.