DSpace1.5.2深度解析与应用指南

需积分: 10 58 浏览量更新于2024-08-01 收藏 1.08MB PDF 举报

"DSpace1.5.2 使用手册提供了对 DSpace 系统的全面介绍，涵盖了功能概述、数据模型、插件管理、元数据、包打包插件、交叉引用插件、用户与组管理、认证、授权、 ingest 进程与工作流、监督与协作、Handles、持久标识符、SRB 支持、搜索浏览、HTML 支持、OAIS 支持、OpenURL 支持、Creative Commons 支持、订阅、导入导出、注册、统计、校验和检查器以及使用指标等核心功能的详细解释。" DSpace 是一个开源的数字存储库平台，它允许机构存储、管理和提供访问其学术内容。DSpace 1.5.2 手册是理解这个系统的关键资源，提供了丰富的信息来帮助用户理解和操作该系统。 1. 功能性概述：DSpace 提供了一个完整的框架，用于管理和展示各种数字对象，包括科研论文、报告、数据集等。它支持多种工作流程和权限管理机制，以适应不同机构的需求。 2. 数据模型：DSpace 的数据模型是其核心部分，定义了如何组织和关联存储在系统中的各种信息。这包括元数据记录、包打包和交叉引用插件等。 3. 插件管理：DSpace 具有一个插件管理系统，允许用户扩展其功能，如添加新的数据格式支持、元数据标准或自定义工作流程。 4. 元数据：DSpace 支持多种元数据标准，如 Dublin Core 和 Qualified Dublin Core，用于描述和检索存储的内容。 5. 用户与组管理：E-People 和 E-Groups 功能允许管理员创建和管理用户账户，设置权限，并将用户分组以实现协作和权限分配。 6. 认证与授权：DSpace 提供了多种认证机制（如本地账户、 Shibboleth 等），并有精细的权限控制，确保只有授权用户才能访问特定内容。 7. Ingest 进程与工作流：DSpace 包含一系列预定义的工作流步骤，用于内容提交、审核和发布。 8. OAIS 支持：DSpace 遵循开放存档信息系统 (OAIS) 标准，符合长期保存和可发现性的需求。 9. OpenURL 支持和 Creative Commons 支持：这两项特性分别使得用户可以轻松地从其他资源链接到 DSpace 内容，并允许内容作者选择 Creative Commons 许可。 10. 统计和校验和检查器：DSpace 可以收集使用统计数据，同时通过校验和检查确保数据的完整性。 DSpace 1.5.2 的这些特性使得它成为学术机构理想的数字存储库解决方案，无论是用于学术出版、数据存档还是知识共享。手册中的详细内容为管理员、开发人员和用户提供了全面的操作指南和参考信息，帮助他们充分利用这一强大的工具。

DSpace System Documentation:

Functional Overview

pre-configured with the DSpace source code. However, you can configure multiple schemas and select metadata

fields from a mix of configured schemas to describe your items.

Other descriptive metadata about items (e.g. metadata described in a hierarchical schema) may be held in serialized

bitstreams. Communities and collections have some simple descriptive metadata (a name, and some descriptive

prose), held in the DBMS.

Administrative Metadata

This includes preservation metadata, provenance and authorization policy data. Most of this is held within

DSpace's relation DBMS schema. Provenance metadata (prose) is stored in Dublin Core records. Additionally,

some other administrative metadata (for example, bitstream byte sizes and MIME types) is replicated in Dublin

Core records so that it is easily accessible outside of DSpace.

Structural Metadata

This includes information about how to present an item, or bitstreams within an item, to an end-user, and the

relationships between constituent parts of the item. As an example, consider a thesis consisting of a number of

TIFF images, each depicting a single page of the thesis. Structural metadata would include the fact that each image

is a single page, and the ordering of the TIFF images/pages. Structural metadata in DSpace is currently fairly

basic; within an item, bitstreams can be arranged into separate bundles as described above. A bundle may also

optionally have a primary bitstream. This is currently used by the HTML support to indicate which bitstream in

the bundle is the first HTML file to send to a browser.

In addition to some basic technical metadata, bitstreams also have a 'sequence ID' that uniquely identifies it within

an item. This is used to produce a 'persistent' bitstream identifier for each bitstream.

Additional structural metadata can be stored in serialized bitstreams, but DSpace does not currently understand

this natively.

2.4. Packager Plugins

Packagers are software modules that translate between DSpace Item objects and a self-contained external

representation, or "package". A Package Ingester interprets, or ingests, the package and creates an Item. A Package

Disseminator writes out the contents of an Item in the package format.

A package is typically an archive file such as a Zip or "tar" file, including a manifest document which contains metadata

and a description of the package contents. The IMS Content Package [http://www.imsglobal.org/content/packaging/] is

a typical packaging standard. A package might also be a single document or media file that contains its own metadata,

such as a PDF document with embedded descriptive metadata.

Package ingesters and package disseminators are each a type of named plugin (see Plugin Manager), so it is easy to

add new packagers specific to the needs of your site. You do not have to supply both an ingester and disseminator for

each format; it is perfectly acceptable to just implement one of them.

Most packager plugins call upon Crosswalk plugins to translate the metadata between DSpace's object model and the

package format.

2.5. Crosswalk Plugins

Crosswalks are software modules that translate between DSpace object metadata and a specific external representation.

An Ingestion Crosswalk interprets the external format and crosswalks it to DSpace's internal data structure, while a

Dissemination Crosswalk does the opposite.

For example, a MODS ingestion crosswalk translates descriptive metadata from the MODS format to the metadata

fields on a DSpace Item. A MODS dissemination crosswalk generates a MODS document from the metadata on a

DSpace Item.

DSpace System Documentation:

Functional Overview

Crosswalk plugins are named plugins see Plugin Manager), so it is easy to add new crosswalks. You do not have to

supply both an ingester and disseminator for each format; it is perfectly acceptable to just implement one of them.

There is also a special pair of crosswalk plugins which use XSL stylesheets to translate the external metadata to or from

an internal DSpace format. You can add and modify XSLT crosswalks simply by editing the DSpace configuration

and the stylesheets, which are stored in files in the DSpace installation directory.

The Packager plugins and OAH-PMH server make use of crosswalk plugins.

2.6. E-People and Groups

Although many of DSpace's functions such as document discovery and retrieval can be used anonymously, some

features (and perhaps some documents) are only available to certain "privileged" users. E-People and Groups are the

way DSpace identifies application users for the purpose of granting privileges. This identity is bound to a session of a

DSpace application such as the Web UI or one of the command-line batch programs. Both E-People and Groups are

granted privileges by the authorization system described below.

2.6.1. E-Person

DSpace hold the following information about each e-person:

• E-mail address

• First and last names

• Whether the user is able to log in to the system via the Web UI, and whether they must use an X509 certificate

to do so;

• A password (encrypted), if appropriate

• A list of collections for which the e-person wishes to be notified of new items

• Whether the e-person 'self-registered' with the system; that is, whether the system created the e-person record

automatically as a result of the end-user independently registering with the system, as opposed to the e-person record

being generated from the institution's personnel database, for example.

• The network ID for the corresponding LDAP record

2.6.2. Groups

Groups are another kind of entity that can be granted permissions in the authorization system. A group is usually an

explicit list of E-People; anyone identified as one of those E-People also gains the privileges granted to the group.

However, an application session can be assigned membership in a group without being identified as an E-Person. For

example, some sites use this feature to identify users of a local network so they can read restricted materials not open

to the whole world. Sessions originating from the local network are given membership in the "LocalUsers" group and

gain the corresonding privileges.

Administrators can also use groups as "roles" to manage the granting of privileges more efficiently.

2.7. Authentication

Authentication is when an application session positively identifies itself as belonging to an E-Person and/or Group. In

DSpace 1.4, it is implemented by a mechanism called Stackable Authentication: the DSpace configuration declares a

DSpace System Documentation:

Functional Overview

"stack" of authentication methods. An application (like the Web UI) calls on the Authentication Manager, which tries

each of these methods in turn to identify the E-Person to which the session belongs, as well as any extra Groups. The

E-Person authentication methods are tried in turn until one succeeds. Every authenticator in the stack is given a chance

to assign extra Groups. This mechanism offers the following advantages:

• Separates authentication from the Web user interface so the same authentication methods are used for other

applications such as non-interactive Web Services

• Improved modularity: The authentication methods are all independent of each other. Custom authentication methods

can be "stacked" on top of the default DSpace username/password method.

• Cleaner support for "implicit" authentication where username is found in the environment of a Web request, e.g.

in an X.509 client certificate.

2.8. Authorization

DSpace's authorization system is based on associating actions with objects and the lists of EPeople who can perform

them. The associations are called Resource Policies, and the lists of EPeople are called Groups. There are two special

groups: 'Administrators', who can do anything in a site, and 'Anonymous', which is a list that contains all users.

Assigning a policy for an action on an object to anonymous means giving everyone permission to do that action. (For

example, most objects in DSpace sites have a policy of 'anonymous' READ.) Permissions must be explicit - lack of an

explicit permission results in the default policy of 'deny'. Permissions also do not 'commute'; for example, if an e-person

has READ permission on an item, they might not necessarily have READ permission on the bundles and bitstreams in

that item. Currently Collections, Communities and Items are discoverable in the browse and search systems regardless

of READ authorization.

The following actions are possible:

Community

ADD/REMOVE add or remove collections or sub-communities

Collection

ADD/REMOVE add or remove items (ADD = permission to submit items)

DEFAULT_ITEM_READ inherited as READ by all submitted items

DEFAULT_BITSTREAM_READ inherited as READ by Bitstreams of all submitted items.

Note: only affects Bitstreams of an item at the time it is

initially submitted. If a Bitstream is added later, it does

_not_ get the same default read policy.

COLLECTION_ADMIN collection admins can edit items in a collection, withdraw

items, map other items into this collection.

Item

ADD/REMOVE add or remove bundles

READ can view item (item metadata is always viewable)

WRITE can modify item

Bundle

ADD/REMOVE add or remove bitstreams to a bundle

剩余263页未读，继续阅读

kongjing0815

粉丝: 73
资源: 2

DSpace1.5.2深度解析与应用指南

Dspace Dspace_System_Desk_Tutorial帮助手册_V4.7（中英文互译）

Dspace 1.6.1 Manual(English)

dSPACE学习详解

dspace7参考手册

dspace简单使用入门

dspace和dSPACE的区别

dspace的modeldesk 的使用操作流程

dSPACE的microlabbox如何使用

from dspace.com import Enums

dspace config

最新资源