Uses of Package
org.dspace.core

Packages that use org.dspace.core
Package
Description
Access status allows the users to view the bitstreams availability before browsing into the item itself.
 
Provides classes and methods for administrative functions that fall outside the regular use of other subsystems.
 
 
 
 
 
The DSpace Batch Metadata Editor, which uses a CSV file to export/import item metadata.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Tools for exporting and importing DSpace objects (Community, Collection, Item, etc.) wrapped in various kinds of packaging.
Feature for conveying a request that materials forbidden to the requester by resource policy be made available by other means.
 
 
 
 
 
Defines usage event instrumentation points and provides implementations for testing.
 
 
 
 
Miscellaneous utility classes.
 
 
 
End-user authentication manager, interface and implementations.
 
 
 
 
Represents permissions for access to DSpace content.
 
 
 
Provides classes and methods for browsing Items in DSpace by whatever is specified in the configuration.
Provides content fixity checking (using checksums) for bitstreams stored in DSpace software.
 
Database access for the Checksum Checker tool, which looks for unexpected changes in Bitstream content.
 
Provides an API for reading and manipulating content in the DSpace system.
 
Provides an API and implementations of metadata crosswalks, which are directional mappings from one schema to another, performed in the context of Item ingestion or dissemination.
 
 
 
 
 
Provides an API and implementations of content packages, used in the context of ingest (SIP), or dissemination (DIP)
 
 
 
 
Provides some basic functionality required throughout the DSpace system.
 
 
 
 
In DSpace, "curation" refers to the application of one or more "tasks" to one or more model objects.
 
 
 
 
 
 
 
 
Embargo allows the deposit of Items whose content should not be made visible until later.
 
Provides classes representing e-people and groups of e-people.
 
 
 
Actions which alter DSpace model objects can queue Events, which are presented to Consumers by a Dispatcher.
 
 
Provides classes and methods to interface with the CNRI Handle System.
 
 
 
 
 
 
 
 
 
Providers of durable unique identifiers (Handles, DOIs, etc.).
 
 
Make requests to the DOI registration agencies and analyze the responses.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Interface to the Lucene search engine, and the 'harvest' API for retrieving items modified within a given date range.
 
Facilities for detecting and storing both model and usage events, and for querying the store.
 
 
 
 
 
 
 
Mostly classes for dealing with detection of spiders, and command line tools.
Provides an API for storing, retrieving and deleting streams of bits in a transactionally safe fashion.
 
 
 
 
 
 
 
 
 
 
 
 
 
Capture of "usage events".
Generally useful classes, not particularly tied to any other package.
 
 
 
 
 
DSpace has a simple workflow system, which models the workflows as named steps: SUBMIT, arbitrary named steps that you define, and ARCHIVE.
An Item submission begins as a WorkspaceItem in some user's workspace.
 
 
A workflow consists of a sequence of steps.
An Action changes the state of an object in a workflow.
 
 
The state of an item in a workflow is persisted in a number of objects.