DSpace uses a qualified Dublin Core metadata standard for describing items intellectually specifically, the Libraries Working Group Application Profile. Only three fields are required: title, language, and submission date, all other fields are optional. There are additional fields for document abstracts, keywords, technical metadata and rights metadata, among others. This metadata is displayed in the item record in DSpace, and is indexed for browsing and searching the system within a collection, across collections, or across Communities.
For the Dissemination Information Packages DIPs of the OAIS framework, the system currently exports metadata and digital material in a custom XML schema while we work with the METS [ 3 ] community to develop the necessary extension schemas for the technical and rights metadata about arbitrary digital formats. DSpace's current user interface is web-based. There are several interfaces: one for submitters and others involved in the submission process, one for end-users looking for information, and one for system administrators.
The end-user or public interface supports search and retrieval of items by browsing or searching the metadata all fields for now, and specific fields in the near future. Once an item is located in the system, retrieval is accomplished by clicking a link that causes the archived material to be downloaded to the user's web browser. DSpace is the first open source digital repository system to tackle the complex problem of how to accommodate the differing submission workflows needed for a multidisciplinary system.
In other words, different DSpace Communities, representing different schools, departments, research labs and centers, have very different ideas of how material should be submitted to DSpace, by whom, and with what restrictions.
Who is allowed to deposit items? What type of items will they deposit? Who else needs to review, enhance, or approve the submission? To what collections can they deposit material?
Who can see the items once deposited? All of these issues are addressed by the Community representatives, working together with the Libraries' DSpace user support staff, and are then modeled in a workflow for each collection to enforce their decisions. The system models "e-people" who have "roles" in the workflow of a particular Community in the context of a given collection.
Individuals from the Community are registered with DSpace, then assigned to appropriate roles. For example, a department may choose to have two collections: one for working papers and another for datasets. They may then decide that any member of the faculty can deposit items to either collection directly, and that any member of the general public can have access to these collections.
In this example the workflow is very simple, and the only "role" is that of submitter. In a more complex example, the same department may have a working paper collection that requires tight editorial control by the head of the department. In this case, they may choose to again designate all faculty as "submitters", but also designate a small group of people as "reviewers", an administrative staff person as a "metadata editor", and the head of the department as the final "coordinator".
An item deposited by a faculty member would then go through a process of review, cleanup and approval before finally being deposited to the relevant DSpace collection. Each person with a role to play in this process is notified of the new submission, and goes to a personal workspace in the system to perform their assigned task.
Items that do not make it through the process are not archived in the system. DSpace was developed to be open source, and in such a way that institutions and organizations with minimal resources could run it. The system is designed to run on the UNIX platform, and comprises other open source middleware and tools, and programs written by the DSpace team. All original code is in the Java programming language.
All leveraged components and libraries are also open source software. Libraries are bundled where possible exceptions are described in the installation instructions. It is our assumption that institutions that use DSpace will have resources to use the system, including adequate hardware that runs the UNIX operating system, and a UNIX systems administrator to install and configure the system [ 7 ]. Most institutions using DSpace will also want the services of a Java programmer who can localize and customize for them, or enhance it, although this is not absolutely necessary to run the system.
As DSpace continues to be improved by staff at HP, the MIT Libraries, and other institutions that adopt it during the coming year, MIT will take responsibility for evaluating and reincorporating these improvements into the main open source system available to the public.
Plans for building a more sustainable open source maintenance strategy through the DSpace Federation will be discussed later. Figure 2: DSpace technical architecture.
From architecture-based system design and block-diagram-based function prototyping to automatic production code generation and hardware-in-the-loop HIL tests, dSPACE products are successfully being used in the classroom and in research projects at internationally renowned universities.
To actively support high-end research at universities and the high-quality education of young talents, dSPACE exclusively offers its hardware and software products in special kits for universities at a very attractive price. Subscribe newsletter. DSpace is free open source software. That means that you can download, use, and modify DSpace for free. We have also tried to find good open-source tools to package with the DSpace application, all freely available under an open-source license although not all the same license as the one for DSpace itself , so that you get a complete system along with the part that we created.
Users are also allowed to modify DSpace to meet an organization's specific needs. The code for DSpace is kept within a source code control system from SourceForge.
This system allows code to be added or modified over time, while maintaining a track of all changes and a note of why the change was made and who made it. This assists with the development of the software and ensures the quality and traceability of the code. Any past version of DSpace can be downloaded from the system in an identical state as originally distributed.
Control of the source code repository is delegated to a small group of 'committers'. DSpace preserves and enables easy and open access to all types of digital content including text, images, moving images, mpegs and data sets. And with an ever-growing community of developers, committed to continuously expanding and improving the software, each DSpace installation benefits from the next.
0コメント