Secrets of the DSpace Submission Form

Preview:

DESCRIPTION

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

Citation preview

www.atmire.com

Secrets of the Submission Form

Bram Luyten

WHAT FOLLOWS IS NOT ACTUALLY A SECRET

Most of this is in the docshttp://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.

www.atmire.com

Questions?

Recommended