DSpace 1.8 Documentation Page of 1 643 DSpace 1.8 Documentation URL: Date: Author: The DSpace Developer Team 24 February 2012 https://wiki.duraspace.org/display/DSDOC18 DSpace 1.8 Documentation Page of 2 643 Table of Contents 1 Preface _____________________________________________________________________________ 15 1.1 Release Notes ____________________________________________________________________ 15 2 Introduction __________________________________________________________________________ 17 3 Functional Overview ___________________________________________________________________ 19 3.1 Data Model ______________________________________________________________________ 19 3.2 Plugin Manager ___________________________________________________________________ 21 3.3 Metadata ________________________________________________________________________ 21 3.4 Packager Plugins _________________________________________________________________ 22 3.5 Crosswalk Plugins _________________________________________________________________ 23 3.6 E-People and Groups ______________________________________________________________ 23 3.6.1 E-Person __________________________________________________________________ 23 3.6.2 Groups ____________________________________________________________________ 24 3.7 Authentication ____________________________________________________________________ 24 3.8 Authorization _____________________________________________________________________ 24 3.9 Ingest Process and Workflow ________________________________________________________ 26 3.9.1 Workflow Steps _____________________________________________________________ 27 3.10 Supervision and Collaboration _______________________________________________________ 28 3.11 Handles _________________________________________________________________________ 28 3.12 Bitstream 'Persistent' Identifiers ______________________________________________________ 29 3.13 Storage Resource Broker (SRB) Support _______________________________________________ 30 3.14 Search and Browse ________________________________________________________________ 30 3.15 HTML Support ____________________________________________________________________ 31 3.16 OAI Support ______________________________________________________________________ 32 3.17 SWORD Support __________________________________________________________________ 32 3.18 OpenURL Support _________________________________________________________________ 32 3.19 Creative Commons Support _________________________________________________________ 33 3.20 Subscriptions _____________________________________________________________________ 33 3.21 Import and Export _________________________________________________________________ 33 3.22 Registration ______________________________________________________________________ 33 3.23 Statistics ________________________________________________________________________ 34 3.23.1 System Statistics ____________________________________________________________ 34 3.23.2 Item, Collection and Community Usage Statistics ___________________________________ 34 3.24 Checksum Checker ________________________________________________________________ 35 3.25 Usage Instrumentation _____________________________________________________________ 35 3.26 Choice Management and Authority Control _____________________________________________ 35 3.26.1 Introduction and Motivation ____________________________________________________ 36 DSpace 1.8 Documentation Page of 3 643 4 Installation ___________________________________________________________________________ 38 4.1 For the Impatient __________________________________________________________________ 38 4.2 Prerequisite Software ______________________________________________________________ 59 4.2.1 UNIX-like OS or Microsoft Windows _____________________________________________ 38 4.2.2 Oracle Java JDK 6 (standard SDK is fine, you don't need J2EE) _______________________ 39 4.2.3 Apache Maven 2.2.x or higher (Java build tool) _____________________________________ 39 4.2.4 Apache Ant 1.8 or later (Java build tool) __________________________________________ 40 4.2.5 Relational Database: (PostgreSQL or Oracle). _____________________________________ 40 4.2.6 Servlet Engine: (Apache Tomcat 5.5 or 6, Jetty, Caucho Resin or equivalent). ____________ 41 4.2.7 Perl (only required for [dspace]/bin/dspace-info.pl) __________________________________ 42 4.3 Installation Instructions _____________________________________________________________ 42 4.3.1 Overview of Install Options ____________________________________________________ 42 4.3.2 Overview of DSpace Directories ________________________________________________ 44 4.3.3 Installation _________________________________________________________________ 45 4.4 Advanced Installation ______________________________________________________________ 49 4.4.1 'cron' Jobs _________________________________________________________________ 49 4.4.2 Multilingual Installation ________________________________________________________ 50 4.4.3 DSpace over HTTPS _________________________________________________________ 50 4.4.4 The Handle Server ___________________________________________________________ 55 4.4.5 Google and HTML sitemaps ___________________________________________________ 56 4.4.6 DSpace Statistics ____________________________________________________________ 57 4.4.7 Manually Installing/Updating GeoLite Database File _________________________________ 58 4.5 Windows Installation _______________________________________________________________ 59 4.5.1 Installation Steps ____________________________________________________________ 59 4.6 Checking Your Installation ___________________________________________________________ 61 4.7 Known Bugs _____________________________________________________________________ 61 4.8 Common Problems ________________________________________________________________ 62 4.8.1 Common Installation Issues ____________________________________________________ 62 4.8.2 General DSpace Issues _______________________________________________________ 64 DSpace 1.8 Documentation Page of 4 643 5 Upgrading a DSpace Installation __________________________________________________________ 66 5.1 Upgrading From 1.8 to 1.8.x _________________________________________________________ 66 5.1.1 Backup your DSpace _________________________________________________________ 67 5.1.2 Upgrade Steps ______________________________________________________________ 68 5.2 Upgrading From 1.7.x to 1.8.x ________________________________________________________ 69 5.2.1 Backup your DSpace _________________________________________________________ 71 5.2.2 Upgrade Steps ______________________________________________________________ 72 5.3 Upgrading From 1.7 to 1.7.x _________________________________________________________ 76 5.3.1 Upgrade Steps ______________________________________________________________ 77 5.4 Upgrading From 1.6.x to 1.7.x ________________________________________________________ 78 5.4.1 Upgrade Steps ______________________________________________________________ 78 5.5 Upgrading From 1.6 to 1.6.x _________________________________________________________ 88 5.5.1 Upgrade Steps ______________________________________________________________ 89 5.6 Upgrading From 1.5.x to 1.6.x ________________________________________________________ 90 5.6.1 Upgrade Steps ______________________________________________________________ 91 5.7 Upgrading From 1.5 or 1.5.1 to 1.5.2 _________________________________________________ 104 5.7.1 Upgrade Steps _____________________________________________________________ 104 5.8 Upgrading From 1.4.2 to 1.5 ________________________________________________________ 113 5.8.1 Upgrade Steps _____________________________________________________________ 113 5.9 Upgrading From 1.4.1 to 1.4.2 ______________________________________________________ 118 5.9.1 Upgrade Steps _____________________________________________________________ 118 5.10 Upgrading From 1.4 to 1.4.x ________________________________________________________ 118 5.10.1 Upgrade Steps _____________________________________________________________ 118 5.11 Upgrading From 1.3.2 to 1.4.x _______________________________________________________ 120 5.11.1 Upgrade Steps _____________________________________________________________ 120 5.12 Upgrading From 1.3.1 to 1.3.2 ______________________________________________________ 123 5.12.1 Upgrade Steps _____________________________________________________________ 123 5.13 Upgrading From 1.2.x to 1.3.x _______________________________________________________ 124 5.13.1 Upgrade Steps _____________________________________________________________ 124 5.14 Upgrading From 1.2.1 to 1.2.2 ______________________________________________________ 125 5.14.1 Upgrade Steps _____________________________________________________________ 126 5.15 Upgrading From 1.2 to 1.2.1 ________________________________________________________ 127 5.15.1 Upgrade Steps _____________________________________________________________ 127 5.16 Upgrading From 1.1.x to 1.2 ________________________________________________________ 129 5.16.1 Upgrade Steps _____________________________________________________________ 129 5.17 Upgrading From 1.1 to 1.1.1 ________________________________________________________ 132 5.17.1 Upgrade Steps _____________________________________________________________ 133 5.18 Upgrading From 1.0.1 to 1.1 ________________________________________________________ 133 5.18.1 Upgrade Steps _____________________________________________________________ 133 6 Configuration ________________________________________________________________________ 137 6.1 General Configuration _____________________________________________________________ 137 6.1.1 Input Conventions __________________________________________________________ 137 6.1.2 Update Reminder ___________________________________________________________ 138 DSpace 1.8 Documentation Page of 5 643 6.2 The dspace.cfg Configuration Properties File ___________________________________________ 139 6.2.1 The dspace.cfg file __________________________________________________________ 139 6.2.2 Main DSpace Configurations __________________________________________________ 150 6.2.3 DSpace Database Configuration _______________________________________________ 151 6.2.4 DSpace Email Settings ______________________________________________________ 153 6.2.5 File Storage _______________________________________________________________ 156 6.2.6 SRB (Storage Resource Brokerage) File Storage __________________________________ 157 6.2.7 Logging Configuration _______________________________________________________ 160 6.2.8 Configuring Lucene Search Indexes ____________________________________________ 161 6.2.9 Handle Server Configuration __________________________________________________ 164 6.2.10 Delegation Administration : Authorization System Configuration _______________________ 165 6.2.11 Restricted Item Visibility Settings _______________________________________________ 169 6.2.12 Proxy Settings _____________________________________________________________ 170 6.2.13 Configuring Media Filters _____________________________________________________ 171 6.2.14 Crosswalk and Packager Plugin Settings ________________________________________ 173 6.2.15 Event System Configuration ___________________________________________________ 177 6.2.16 Embargo __________________________________________________________________ 180 6.2.17 Checksum Checker Settings __________________________________________________ 185 6.2.18 Item Export and Download Settings _____________________________________________ 186 6.2.19 Subscription Emails _________________________________________________________ 187 6.2.20 Hiding Metadata ____________________________________________________________ 187 6.2.21 Settings for the Submission Process ____________________________________________ 188 6.2.22 Configuring Creative Commons License _________________________________________ 188 6.2.23 WEB User Interface Configurations _____________________________________________ 190 6.2.24 Browse Index Configuration ___________________________________________________ 194 6.2.25 Author (Multiple metadata value) Display ________________________________________ 198 6.2.26 Links to Other Browse Contexts ________________________________________________ 199 6.2.27 Recent Submissions ________________________________________________________ 200 6.2.28 Submission License Substitution Variables _______________________________________ 201 6.2.29 Syndication Feed (RSS) Settings _______________________________________________ 201 6.2.30 OpenSearch Support ________________________________________________________ 205 6.2.31 Content Inline Disposition Threshold ____________________________________________ 207 6.2.32 Multi-file HTML Document/Site Settings _________________________________________ 208 6.2.33 Sitemap Settings ___________________________________________________________ 208 6.2.34 Authority Control Settings ____________________________________________________ 209 6.2.35 JSPUI Upload File Settings ___________________________________________________ 210 6.2.36 JSP Web Interface (JSPUI) Settings ____________________________________________ 211 6.2.37 JSPUI Configuring Multilingual Support __________________________________________ 215 6.2.38 JSPUI Item Mapper _________________________________________________________ 217 6.2.39 Display of Group Membership _________________________________________________ 217 6.2.40 JSPUI / XMLUI SFX Server ___________________________________________________ 217 6.2.41 JSPUI Item Recommendation Setting ___________________________________________ 219 6.2.42 Controlled Vocabulary Settings ________________________________________________ 219 DSpace 1.8 Documentation Page of 6 643 6.2.43 XMLUI Specific Configuration _________________________________________________ 221 6.2.44 DSpace SOLR Statistics Configuration __________________________________________ 225 6.3 Optional or Advanced Configuration Settings ___________________________________________ 226 6.3.1 The Metadata Format and Bitstream Format Registries _____________________________ 227 6.3.2 XPDF Filter ________________________________________________________________ 228 6.3.3 Creating a new Media/Format Filter _____________________________________________ 231 6.3.4 Configuring Usage Instrumentation Plugins _______________________________________ 233 6.4 Authentication Plugins _____________________________________________________________ 234 6.4.1 Stackable Authentication Method(s) ____________________________________________ 234 6.5 Batch Metadata Editing Configuration _________________________________________________ 256 6.6 Configurable Workflow ____________________________________________________________ 257 6.6.1 Introduction _______________________________________________________________ 257 6.6.2 Instructions for Enabling Configurable Reviewer Workflow in XMLUI ___________________ 258 6.6.3 Data Migration (Backwards compatibility) ________________________________________ 259 6.6.4 Configuration ______________________________________________________________ 260 6.6.5 Authorizations _____________________________________________________________ 266 6.6.6 Database _________________________________________________________________ 266 6.6.7 Additional workflow steps/actions and features ____________________________________ 268 6.6.8 Known Issues ______________________________________________________________ 269 6.7 Discovery _______________________________________________________________________ 270 6.7.1 What is DSpace Discovery ____________________________________________________ 270 6.7.2 Discovery Features _________________________________________________________ 271 6.7.3 DSpace 1.8 Improvements ____________________________________________________ 271 6.7.4 Enabling Discovery _________________________________________________________ 272 6.7.5 Configuration files __________________________________________________________ 273 6.7.6 General Discovery settings (config/modules/discovery.cfg) ___________________________ 274 6.7.7 Modifying the Discovery User Interface (config/spring/spring-dspace-addon-discovery-configuration-services.xml) ______________________ 274 6.7.8 Routine Discovery SOLR Index Maintenance _____________________________________ 281 6.7.9 Advanced SOLR Configuration ________________________________________________ 281 6.8 DSpace Service Manager __________________________________________________________ 282 6.8.1 Introduction _______________________________________________________________ 282 6.8.2 Configuration ______________________________________________________________ 282 6.8.3 Architectural Overview _______________________________________________________ 285 6.8.4 Tutorials __________________________________________________________________ 285 DSpace 1.8 Documentation Page of 7 643 6.9 DSpace Statistics ________________________________________________________________ 285 6.9.1 What is exactly being logged ? ________________________________________________ 285 6.9.2 Web user interface for DSpace statistics _________________________________________ 286 6.9.3 Usage Event Logging and Usage Statistics Gathering ______________________________ 287 6.9.4 Configuration settings for Statistics _____________________________________________ 287 6.9.5 Older setting that are not related to the new 1.6 Statistics ____________________________ 290 6.9.6 Statistics Administration ______________________________________________________ 291 6.9.7 Statistics differences between DSpace 1.7.x and 1.8.0 ______________________________ 291 6.9.8 Statistics differences between DSpace 1.6.x and 1.7.0 ______________________________ 292 6.9.9 Web UI Statistics Modification (XMLUI Only) ______________________________________ 292 6.9.10 Custom Reporting - Querying SOLR Directly ______________________________________ 293 6.10 Embargo _______________________________________________________________________ 294 6.10.1 What is an embargo? ________________________________________________________ 294 6.11 Google Scholar Metadata Mappings __________________________________________________ 298 6.12 OAI ___________________________________________________________________________ 299 6.12.1 OAI Interfaces _____________________________________________________________ 299 6.13 SWORDv1 Client _________________________________________________________________ 306 6.13.1 Enabling the SWORD Client __________________________________________________ 306 6.13.2 Configuring the SWORD Client ________________________________________________ 307 6.14 SWORDv1 Server ________________________________________________________________ 308 6.14.1 Enabling SWORD Server _____________________________________________________ 308 6.14.2 Configuring SWORD Server __________________________________________________ 308 6.15 SWORDv2 Server ________________________________________________________________ 313 6.15.1 Enabling SWORD v2 Server __________________________________________________ 314 6.15.2 Configuring SWORD v2 Server ________________________________________________ 314 7 JSPUI Configuration and Customization ___________________________________________________ 322 7.1 Configuration ____________________________________________________________________ 322 7.2 Customizing the JSP pages ________________________________________________________ 322 DSpace 1.8 Documentation Page of 8 643 8 XMLUI Configuration and Customization __________________________________________________ 324 8.1 Overview of XMLUI / Manakin _______________________________________________________ 324 8.1.1 Understanding the Flow of an XMLUI Request ____________________________________ 325 8.2 Manakin Configuration Property Keys _________________________________________________ 327 8.3 Configuring Themes and Aspects ____________________________________________________ 330 8.3.1 Aspects __________________________________________________________________ 330 8.3.2 Themes __________________________________________________________________ 332 8.4 Multilingual Support _______________________________________________________________ 332 8.5 Creating a New Theme ____________________________________________________________ 333 8.6 Customizing the News Document ____________________________________________________ 334 8.7 Adding Static Content _____________________________________________________________ 335 8.8 Harvesting Items from XMLUI via OAI-ORE or OAI-PMH __________________________________ 336 8.8.1 Automatic Harvesting (Scheduler) ______________________________________________ 338 8.9 Additional XMLUI Learning Resources ________________________________________________ 338 8.10 Mirage Configuration and Customization ______________________________________________ 338 8.10.1 Introduction _______________________________________________________________ 339 8.10.2 Configuration Parameters ____________________________________________________ 339 8.10.3 Technical Features __________________________________________________________ 340 8.10.4 Troubleshooting ____________________________________________________________ 341 8.11 XMLUI Base Theme Templates (dri2xhtml) ____________________________________________ 342 8.11.1 dri2xhtml __________________________________________________________________ 342 8.11.2 dri2xhtml-alt _______________________________________________________________ 343 9 Advanced Customisation _______________________________________________________________ 346 9.1 Maven WAR Overlays _____________________________________________________________ 346 9.2 DSpace Source Release ___________________________________________________________ 346 10 System Administration _________________________________________________________________ 347 10.1 AIP Backup and Restore ___________________________________________________________ 347 10.1.1 Background & Overview ______________________________________________________ 347 10.1.2 Makeup and Definition of AIPs _________________________________________________ 351 10.1.3 Running the Code __________________________________________________________ 352 10.1.4 Additional Packager Options __________________________________________________ 363 10.1.5 Configuration in 'dspace.cfg' __________________________________________________ 368 10.1.6 Common Issues or Error Messages _____________________________________________ 371 10.1.7 DSpace AIP Format _________________________________________________________ 372 10.2 Batch Metadata Editing ____________________________________________________________ 390 10.2.1 Batch Metadata Editing Tool __________________________________________________ 390 DSpace 1.8 Documentation Page of 9 643 10.3 Curation System _________________________________________________________________ 394 10.3.1 Changes in 1.8 _____________________________________________________________ 395 10.3.2 Tasks ____________________________________________________________________ 395 10.3.3 Activation _________________________________________________________________ 395 10.3.4 Writing your own tasks _______________________________________________________ 396 10.3.5 Task Invocation ____________________________________________________________ 397 10.3.6 Asynchronous (Deferred) Operation ____________________________________________ 400 10.3.7 Task Output and Reporting ___________________________________________________ 401 10.3.8 Task Properties ____________________________________________________________ 402 10.3.9 Task Annotations ___________________________________________________________ 404 10.3.10Scripted Tasks _____________________________________________________________ 404 10.3.11Starter Tasks ______________________________________________________________ 406 10.4 Importing and Exporting Content via Packages _________________________________________ 411 10.4.1 Package Importer and Exporter ________________________________________________ 411 10.5 Importing and Exporting Items via Simple Archive Format _________________________________ 417 10.5.1 Item Importer and Exporter ___________________________________________________ 417 10.6 Importing Community and Collection Hierarchy _________________________________________ 423 10.6.1 Community and Collection Structure Importer _____________________________________ 423 10.7 Managing Community Hierarchy _____________________________________________________ 425 10.7.1 Sub-Community Management _________________________________________________ 425 10.8 Managing Embargoed Content ______________________________________________________ 427 10.8.1 Embargo Lifter _____________________________________________________________ 427 10.9 Managing Usage Statistics _________________________________________________________ 427 10.9.1 DSpace Log Converter _______________________________________________________ 428 10.9.2 Filtering and Pruning Spiders __________________________________________________ 429 10.9.3 Routine SOLR Index Maintenance ______________________________________________ 430 10.10Moving Items ___________________________________________________________________ 430 10.10.1Moving Items via Web UI ____________________________________________________ 430 10.10.2Moving Items via the Batch Metadata Editor ______________________________________ 431 10.11Performance Tuning DSpace _______________________________________________________ 431 10.11.1Give Tomcat (DSpace UIs) More Memory _______________________________________ 431 10.11.2Give the Command Line Tools More Memory _____________________________________ 433 10.11.3Give PostgreSQL Database More Memory _______________________________________ 434 10.11.4SOLR Statistics Performance Tuning ___________________________________________ 434 10.12Registering (not Importing) Bitstreams via Simple Archive Format __________________________ 434 10.12.1Overview _________________________________________________________________ 435 10.13ReIndexing Content (for Browse or Search) ___________________________________________ 437 10.13.1Overview _________________________________________________________________ 437 10.13.2Creating the Browse & Search Indexes _________________________________________ 437 10.13.3Running the Indexing Programs _______________________________________________ 438 10.13.4Indexing Customization ______________________________________________________ 439 10.14Testing Database Connection ______________________________________________________ 440 10.14.1Test Database _____________________________________________________________ 440 DSpace 1.8 Documentation Page of 10 643 Test Database ____________________________________________________________ 440 10.15Transferring or Copying Content Between Repositories __________________________________ 441 10.15.1Transferring Content via Export and Import ______________________________________ 441 10.15.2Transferring Items using Simple Archive Format __________________________________ 441 10.15.3Transferring Items using OAI-ORE/OAI-PMH Harvester ____________________________ 442 10.15.4Copying Items using the SWORD Client _________________________________________ 442 10.16Transforming DSpace Content (MediaFilters) __________________________________________ 442 10.16.1MediaFilters: Transforming DSpace Content _____________________________________ 442 10.17Updating Items via Simple Archive Format ____________________________________________ 445 10.17.1Item Update Tool ___________________________________________________________ 445 10.18Validating CheckSums of Bitstreams _________________________________________________ 448 10.18.1Checksum Checker _________________________________________________________ 448 11 Directories and Files __________________________________________________________________ 453 11.1 Overview _______________________________________________________________________ 453 11.2 Source Directory Layout ___________________________________________________________ 453 11.3 Installed Directory Layout __________________________________________________________ 455 11.4 Contents of JSPUI Web Application __________________________________________________ 455 11.5 Contents of XMLUI Web Application (aka Manakin) ______________________________________ 455 11.6 Log Files _______________________________________________________________________ 456 11.6.1 log4j.properties File. _________________________________________________________ 458 DSpace 1.8 Documentation Page of 11 643 12 Architecture _________________________________________________________________________ 459 12.1 Overview _______________________________________________________________________ 459 12.1.1 DSpace System Architecture __________________________________________________ 459 12.2 Application Layer _________________________________________________________________ 461 12.2.1 Web User Interface _________________________________________________________ 461 12.2.2 OAI-PMH Data Provider ______________________________________________________ 471 12.2.3 DSpace Command Launcher __________________________________________________ 475 12.3 Business Logic Layer _____________________________________________________________ 476 12.3.1 Core Classes ______________________________________________________________ 476 12.3.2 Content Management API ____________________________________________________ 479 12.3.3 Plugin Manager ____________________________________________________________ 484 12.3.4 Workflow System ___________________________________________________________ 494 12.3.5 Administration Toolkit ________________________________________________________ 495 12.3.6 E-person/Group Manager ____________________________________________________ 495 12.3.7 Authorization ______________________________________________________________ 496 12.3.8 Handle Manager/Handle Plugin ________________________________________________ 497 12.3.9 Search ___________________________________________________________________ 498 12.3.10Browse API _______________________________________________________________ 500 12.3.11Checksum checker _________________________________________________________ 503 12.3.12OpenSearch Support ________________________________________________________ 503 12.3.13Embargo Support __________________________________________________________ 505 12.4 DSpace Services Framework _______________________________________________________ 507 12.4.1 Architectural Overview _______________________________________________________ 507 12.4.2 Basic Usage _______________________________________________________________ 509 12.4.3 Providers and Plugins _______________________________________________________ 510 12.4.4 Core Services ______________________________________________________________ 511 12.4.5 Examples _________________________________________________________________ 512 12.4.6 Tutorials __________________________________________________________________ 513 12.5 Storage Layer ___________________________________________________________________ 513 12.5.1 RDBMS / Database Structure _________________________________________________ 513 12.5.2 Bitstream Store ____________________________________________________________ 516 DSpace 1.8 Documentation Page of 12 643 13 Submission User Interface _____________________________________________________________ 522 13.1 Understanding the Submission Configuration File _______________________________________ 522 13.1.1 The Structure of item-submission.xml ___________________________________________ 522 13.1.2 Defining Steps ( ) within the item-submission.xml ____________________________ 523 13.2 Reordering/Removing Submission Steps ______________________________________________ 525 13.3 Assigning a custom Submission Process to a Collection __________________________________ 526 13.3.1 Getting A Collection's Handle _________________________________________________ 529 13.4 Custom Metadata-entry Pages for Submission __________________________________________ 527 13.4.1 Introduction _______________________________________________________________ 527 13.4.2 Describing Custom Metadata Forms ____________________________________________ 528 13.4.3 The Structure of input-forms.xml _______________________________________________ 528 13.4.4 Deploying Your Custom Forms ________________________________________________ 533 13.5 Configuring the File Upload step _____________________________________________________ 533 13.6 Creating new Submission Steps _____________________________________________________ 533 13.6.1 Creating a Non-Interactive Step ________________________________________________ 534 14 DRI Schema Reference ________________________________________________________________ 536 14.1 Introduction _____________________________________________________________________ 536 14.1.1 The Purpose of DRI _________________________________________________________ 536 14.1.2 The Development of DRI _____________________________________________________ 536 14.2 DRI in Manakin __________________________________________________________________ 537 14.2.1 Themes __________________________________________________________________ 537 14.2.2 Aspect Chains _____________________________________________________________ 538 14.3 Common Design Patterns __________________________________________________________ 538 14.3.1 Localization and Internationalization ____________________________________________ 538 14.3.2 Standard attribute triplet ______________________________________________________ 539 14.3.3 Structure-oriented markup ____________________________________________________ 539 14.4 Schema Overview ________________________________________________________________ 540 14.5 Merging of DRI Documents _________________________________________________________ 541 14.6 Version Changes _________________________________________________________________ 542 14.6.1 Changes from 1.0 to 1.1 ______________________________________________________ 542 DSpace 1.8 Documentation Page of 13 643 14.7 Element Reference _______________________________________________________________ 543 14.7.1 BODY ____________________________________________________________________ 547 14.7.2 cell ______________________________________________________________________ 548 14.7.3 div _______________________________________________________________________ 549 14.7.4 DOCUMENT ______________________________________________________________ 551 14.7.5 field ______________________________________________________________________ 551 14.7.6 figure ____________________________________________________________________ 553 14.7.7 head _____________________________________________________________________ 554 14.7.8 help _____________________________________________________________________ 555 14.7.9 hi _______________________________________________________________________ 556 14.7.10instance __________________________________________________________________ 557 14.7.11item _____________________________________________________________________ 557 14.7.12label _____________________________________________________________________ 558 14.7.13list ______________________________________________________________________ 560 14.7.14META ___________________________________________________________________ 561 14.7.15metadata _________________________________________________________________ 562 14.7.16OPTIONS ________________________________________________________________ 563 14.7.17p _______________________________________________________________________ 564 14.7.18pageMeta ________________________________________________________________ 565 14.7.19params __________________________________________________________________ 567 14.7.20reference _________________________________________________________________ 568 14.7.21referenceSet ______________________________________________________________ 569 14.7.22repository _________________________________________________________________ 570 14.7.23repositoryMeta _____________________________________________________________ 570 14.7.24row ______________________________________________________________________ 571 14.7.25table _____________________________________________________________________ 572 14.7.26trail ______________________________________________________________________ 574 14.7.27userMeta _________________________________________________________________ 574 14.7.28value ____________________________________________________________________ 576 14.7.29xref _____________________________________________________________________ 577 15 Appendices _________________________________________________________________________ 579 15.1 Appendix A _____________________________________________________________________ 579 15.1.1 Default Dublin Core Metadata Registry __________________________________________ 579 15.1.2 Default Bitstream Format Registry ______________________________________________ 581 DSpace 1.8 Documentation Page of 14 643 16 History _____________________________________________________________________________ 584 16.1 Changes in DSpace 1.8.2 __________________________________________________________ 584 16.1.1 General Improvements _______________________________________________________ 637 16.1.2 Bug Fixes _________________________________________________________________ 623 16.2 Changes in DSpace 1.8.1 __________________________________________________________ 585 16.3 Changes in DSpace 1.8.0 __________________________________________________________ 586 16.3.1 New Features ______________________________________________________________ 621 16.4 Changes in DSpace 1.7.2 __________________________________________________________ 594 16.5 Changes in DSpace 1.7.1 __________________________________________________________ 595 16.6 Changes in DSpace 1.7.0 __________________________________________________________ 597 16.7 Changes in DSpace 1.6.2 __________________________________________________________ 607 16.8 Changes in DSpace 1.6.1 __________________________________________________________ 608 16.9 Changes in DSpace 1.6.0 __________________________________________________________ 611 16.10Changes in DSpace 1.5.2 _________________________________________________________ 621 16.11Changes in DSpace 1.5.1 _________________________________________________________ 628 16.11.1General Improvements and Bug Fixes __________________________________________ 628 16.12Changes in DSpace 1.5 ___________________________________________________________ 630 16.12.1Bug fixes and smaller patches ________________________________________________ 631 16.13Changes in DSpace 1.4.1 _________________________________________________________ 632 16.13.1Bug fixes _________________________________________________________________ 642 16.14Changes in DSpace 1.4 ___________________________________________________________ 633 16.15Changes in DSpace 1.3.2 _________________________________________________________ 635 16.16Changes in DSpace 1.3.1 _________________________________________________________ 635 16.17Changes in DSpace 1.3 ___________________________________________________________ 635 16.18Changes in DSpace 1.2.2 _________________________________________________________ 636 16.18.1Changes in JSPs ___________________________________________________________ 637 16.19Changes in DSpace 1.2.1 _________________________________________________________ 637 16.19.1Changed JSPs ____________________________________________________________ 638 16.20Changes in DSpace 1.2 ___________________________________________________________ 639 16.20.1General Improvments _______________________________________________________ 639 16.20.2Administration _____________________________________________________________ 639 16.20.3Import/Export/OAI __________________________________________________________ 639 16.20.4Miscellaneous _____________________________________________________________ 639 16.20.5JSP file changes between 1.1 and 1.2 __________________________________________ 640 16.21Changes in DSpace 1.1.1 _________________________________________________________ 642 16.21.1Improvements _____________________________________________________________ 642 16.22Changes in DSpace 1.1 ___________________________________________________________ 643 DSpace 1.8 Documentation Page of 15 643 1 Preface Online Version of Documentation also available This documentation was produced with software. A PDF version was generated directlyConfluence from Confluence. An online, updated version of this 1.8.0 Documentation is also available at: https://wiki.duraspace.org/display/DSDOC18 1.1 Release Notes Welcome to Release 1.8.0. The developers have volunteered many hours to fix, re-write and contribute new software code for this release. Documentation has also been updated. The following is a list of the new features included for release 1.8.0 (not an exhaustive list): Improvements to the (sections of dspace.cfg haveupgrade and configuration process (see page 69) been split into separate configuration files). .More Curation Tools/Plugins (see page 394) .Configurable Workflow (see page 257) .SWORD Client (see page 306) .SWORDv2 Server Module (see page 313) RSS feeds now support richer features, such as iTunes podcast and publishing to iTunesU (see new )."webui.feed.podcast.*" settings (see page 201) Enhancements to .Discovery (see page 270) Rewrite of for the XMLUI.Creative Commons licensing (see page 188) .Reordering of bitstreams .Enable virus checking during submission (see page 407) .Ability to Withdraw/Reinstate/Delete Items in Bulk, via Batch Metadata Editing (see page 394) A full list of all changes / bug fixes in 1.8.0 is available in the section.History (see page 584) http://www.atlassian.com/software/confluence/ https://wiki.duraspace.org/display/DSDOC18 https://jira.duraspace.org/browse/DS-749 DSpace 1.8 Documentation Page of 16 643 The following people have contributed directly to this release of DSpace: Alex Lemann, Álvaro López, Andrea Schweer, Ben Bosman, Bill Hays, Bram De Schouwer, Bram Luyten, Brian Freels-Stendel, Claudia Jürgen, David Chandek-Stark, Denys Slipetskyy, Fabio Bolognesi, Gareth Waller, Hardik Mishra, Hardy Pottinger, Ivan Masár, James Russell, Janne Pietarila, Jason Stirnaman, Joonas Kesäniemi, Jordan Pišanc, Jose Blanco, Juan García, Kevin Van de Velde, Kim Shepherd, Konstantinos V. Paraskevopoulos 1, Lighton Phiri, Mark Diggory, Mark H. Wood, Nicholas Riley, Onivaldo Rosa Junior, Peter Dietz, Richard Rodgers, Robin Taylor, Ronee Francis, Samuel Ottenhoff, Scott Phillips, Stuart Lewis, Stuart Yeates, Terry Burton, Tim Donohue, Timo Aalto, Vladislav Zhivkov, Wendy Bossons. Many of them could not do this work without the support (release time and financial) of their associated institutions. We offer thanks to those institutions for supporting their staff to take time to contribute to the DSpace project. A big thank you also goes out to the (DCAT), who helped the developers toDSpace Community Advisory Team prioritize and plan out several of the new features that made it into this release. The current DCAT members include: Amy Lana, Augustine Gitonga, Bram Luyten, Ciarán Walsh, Claire Bundy, Dibyendra Hyoju, Elena Feinstein, Elin Stangeland, Imma Subirats, Iryna Kuchma, Jennifer Laherty, Jim Ottaviani, Leonie Hayes, Maureen Walsh, Michael Guthrie, Sarah Shreeves, Sue Kunda, and Valorie Hollister. We apologize to any contributor accidentally left off this list. DSpace has such a large, active development community that we sometimes lose track of all our contributors. Our ongoing list of all known people/institutions that have contributed to DSpace software can be found on our . AcknowledgementsDSpace Contributors page to those left off will be made in future releases. All you have to do is report an issue, fix a bug,Want to see your name appear in our list of contributors? improve our documentation or help us determine the necessary requirements for a new feature! Visit our Issue to report a bug, or join to take part in development work. If you'd like to helpTracker dspace-devel mailing list improve our current documentation, please get in touch with one of our with your ideas. You don'tCommitters even need to be a developer! Repository managers can also get involved by volunteering to join the DSpace and helping our developers to plan new features.Community Advisory Team The Documentation Gardener for this release was Jeffrey Trimble with input from everyone.  All typos are his fault. Robin Taylor was the Release Coordinator of this release with immeasurable help from the DSpace Technical Lead Tim Donohue. Additional thanks to Tim Donohue from DuraSpace for keeping all of us focused on the work at hand, and calming us when we got excited and for the general support for the DSpace project. https://wiki.duraspace.org/display/cmtygp/DSpace+Community+Advisory+Team https://wiki.duraspace.org/display/DSPACE/DSpaceContributors https://jira.duraspace.org/browse/DS https://jira.duraspace.org/browse/DS https://lists.sourceforge.net/lists/listinfo/dspace-devel https://wiki.duraspace.org/display/DSPACE/DSpaceContributors#DSpaceContributors-Committers https://wiki.duraspace.org/display/cmtygp/DSpace+Community+Advisory+Team https://wiki.duraspace.org/display/cmtygp/DSpace+Community+Advisory+Team DSpace 1.8 Documentation Page of 17 643 2 Introduction DSpace is an open source software platform that enables organisations to: capture and describe digital material using a submission workflow module, or a variety of programmatic ingest options distribute an organisation's digital assets over the web through a search and retrieval system preserve digital assets over the long term This system documentation includes a , which is a goodfunctional overview of the system (see page 19) introduction to the capabilities of the system, and should be readable by non-technical folk. Everyone should read this section first because it introduces some terminology used throughout the rest of the documentation. For people actually running a DSpace service, there is an , and sections on installation guide (see page 38) and the .configuration (see page 137) directory structure (see page 453) Finally, for those interested in the details of how DSpace works, and those potentially interested in modifying the code for their own purposes, there is a detailed .architecture and design section (see page 459) Other good sources of information are: The DSpace Public API Javadocs. Build these with the command mvn javadoc:javadoc The contains stacks of useful information about the DSpace platform and the work peopleDSpace Wiki are doing with it. You are strongly encouraged to visit this site and add information about your own work. Useful Wiki areas are: (Web sites, mailing lists etc.)A list of DSpace resources Technical FAQ A list of projects using DSpace Guidelines for contributing back to DSpace has announcements and contains useful information about bringing up an instance ofwww.dspace.org DSpace at your organization. The . Join DSpace-General to ask questions or join discussions about non-technicalDSpace General List aspects of building and running a DSpace service. It is open to all DSpace users. Ask questions, share news, and spark discussion about DSpace with people managing other DSpace sites. Watch DSpace-General for news of software releases, user conferences, and announcements from the DSpace Federation. The . DSpace developers help answer installation and technology questions, shareDSpace Technical List information and help each other solve technical problems through the DSpace-Tech mailing list. Post questions or contribute your expertise to other developers working with the system. http://wiki.dspace.org/ https://wiki.duraspace.org/display/DSPACE/DSpaceResources https://wiki.duraspace.org/display/DSPACE/TechnicalFaq http://www.dspace.org/whos-using-dspace/Repository-List.html https://wiki.duraspace.org/display/DSPACE/Code+Contribution+Guidelines http://www.dspace.org/ https://lists.sourceforge.net/lists/listinfo/dspace-general https://lists.sourceforge.net/lists/listinfo/dspace-tech DSpace 1.8 Documentation Page of 18 643 The . Join Discussions among DSpace Developers. The DSpace-Devel listservDSpace Development List is for DSpace developers working on the DSpace platform to share ideas and discuss code changes to the open source platform. Join other developers to shape the evolution of the DSpace software. The DSpace community depends on its members to frame functional requirements and high-level architecture, and to facilitate programming, testing, documentation and to the project. https://lists.sourceforge.net/lists/listinfo/dspace-devel DSpace 1.8 Documentation Page of 19 643 3 Functional Overview The following sections describe the various functional aspects of the DSpace system. 3.1 Data Model Data Model Diagram The way data is organized in DSpace is intended to reflect the structure of the organization using the DSpace system. Each DSpace site is divided into , which can be further divided into communities sub-communities reflecting the typical university structure of college, department, research center, or laboratory. DSpace 1.8 Documentation Page of 20 643 Communities contain , which are groupings of related content. A collection may appear in more thancollections one community. Each collection is composed of , which are the basic archival elements of the archive. Each item is owneditems by one collection. Additionally, an item may appear in additional collections; however every item has one and only one owning collection. Items are further subdivided into named of . Bitstreams are, as the name suggests, streamsbundles bitstreams of bits, usually ordinary computer files. Bitstreams that are somehow closely related, for example HTML files and images that compose a single HTML document, are organized into bundles. In practice, most items tend to have these named bundles: – the bundle with the original, deposited bitstreamsORIGINAL – thumbnails of any image bitstreamsTHUMBNAILS – extracted full-text from bitstreams in ORIGINAL, for indexingTEXT – contains the deposit license that the submitter granted the host organization; in other words,LICENSE specifies the rights that the hosting organization have – contains the distribution license, if any (a license) associated with theCC_LICENSE Creative Commons item. This license specifies what end users downloading the content can do with the content Each bitstream is associated with one . Because preservation services may be an importantBitstream Format aspect of the DSpace service, it is important to capture the specific formats of files that users submit. In DSpace, a bitstream format is a unique and consistent way to refer to a particular file format. An integral part of a bitstream format is an either implicit or explicit notion of how material in that format can be interpreted. For example, the interpretation for bitstreams encoded in the JPEG standard for still image compression is defined explicitly in the Standard ISO/IEC 10918-1. The interpretation of bitstreams in Microsoft Word 2000 format is defined implicitly, through reference to the Microsoft Word 2000 application. Bitstream formats can be more specific than MIME types or file suffixes. For example, and span multiple versions ofapplication/ms-word .doc the Microsoft Word application, each of which produces bitstreams with presumably different characteristics. Each bitstream format additionally has a , indicating how well the hosting institution is likely to besupport level able to preserve content in the format in the future. There are three possible support levels that bitstream formats may be assigned by the hosting institution. The host institution should determine the exact meaning of each support level, after careful consideration of costs and requirements. MIT Libraries' interpretation is shown below: Supported The format is recognized, and the hosting institution is confident it can make bitstreams of this format usable in the future, using whatever combination of techniques (such as migration, emulation, etc.) is appropriate given the context of need. Known The format is recognized, and the hosting institution will promise to preserve the bitstream as-is, and allow it to be retrieved. The hosting institution will attempt to obtain enough information to enable the format to be upgraded to the 'supported' level. http://www.creativecommons.org DSpace 1.8 Documentation Page of 21 643 Unsupported The format is unrecognized, but the hosting institution will undertake to preserve the bitstream as-is and allow it to be retrieved. Each item has one qualified Dublin Core metadata record. Other metadata might be stored in an item as a serialized bitstream, but we store Dublin Core for every item for interoperability and ease of discovery. The Dublin Core may be entered by end-users as they submit content, or it might be derived from other metadata as part of an ingest process. Items can be removed from DSpace in one of two ways: They may be 'withdrawn', which means they remain in the archive but are completely hidden from view. In this case, if an end-user attempts to access the withdrawn item, they are presented with a 'tombstone,' that indicates the item has been removed. For whatever reason, an item may also be 'expunged' if necessary, in which case all traces of it are removed from the archive. Object Example Community Laboratory of Computer Science; Oceanographic Research Center Collection LCS Technical Reports; ORC Statistical Data Sets Item A technical report; a data set with accompanying description; a video recording of a lecture Bundle A group of HTML and image bitstreams making up an HTML document Bitstream A single HTML file; a single image file; a source code file Bitstream Format Microsoft Word version 6.0; JPEG encoded image format 3.2 Plugin Manager The PluginManager is a very simple component container. It creates and organizes components (plugins), and helps select a plugin in the cases where there are many possible choices. It also gives some limited control over the lifecycle of a plugin. A plugin is defined by a Java interface. The consumer of a plugin asks for its plugin by interface. A Plugin is an instance of any class that implements the plugin interface. It is interchangeable with other implementations, so that any of them may be "plugged in". The mediafilter is a simple example of a plugin implementation. Refer to the Business Logic Layer (see page for more details on Plugins.476) 3.3 Metadata Broadly speaking, DSpace holds three sorts of metadata about archived content: DSpace 1.8 Documentation Page of 22 643 : DSpace can support multiple flat metadata schemas for describing an item. ADescriptive Metadata qualified Dublin Core metadata schema loosely based on the set of elementsLibrary Application Profile and qualifiers is provided by default. The comesset of elements and qualifiers used by MIT Libraries 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. and have some simple descriptive metadata (a name, and some descriptiveCommunities collections prose), held in the DBMS. : This includes preservation metadata, provenance and authorization policyAdministrative Metadata data. Most of this is held within DSpace's relational 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. : This includes information about how to present an item, or bitstreams within anStructural Metadata 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 . This is currently used by the HTML support to indicate which bitstream in the bundle is the firstbitstream HTML file to send to a browser. In addition to some basic technical metadata, a bitstream also has 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. 3.4 Packager Plugins are software modules that translate between DSpace Item objects and a self-contained externalPackagers representation, or "package". A interprets, or , the package and creates an Item. A Package Ingester ingests writes out the contents of an Item in the package format.Package Disseminator A package is typically an archive file such as a Zip or "tar" file, including a document which containsmanifest metadata and a description of the package contents. The is a typical packaging standard.IMS Content Package 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 (see page ), so it is easy to add new packagers specific to the needs of your site. You do not have to supply both an21) ingester and disseminator for each format; it is perfectly acceptable to just implement one of them. Most packager plugins call upon to translate the metadata between DSpace'sCrosswalk Plugins (see page 23) object model and the package format. http://www.dublincore.org/documents/library-application-profile/ http://dspace.org/technology/metadata.html http://www.imsglobal.org/content/packaging/ DSpace 1.8 Documentation Page of 23 643 More information about calling Packagers to ingest or disseminate content can be found in the Package Importer section of the System Administration documentation.and Exporter (see page ) 3.5 Crosswalk Plugins are software modules that translate between DSpace object metadata and a specific externalCrosswalks representation. An interprets the external format and crosswalks it to DSpace's internal dataIngestion Crosswalk structure, while a does the opposite.Dissemination Crosswalk 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. Crosswalk plugins are named plugins (see ), so it is easy to add newPlugin Manager (see page 21) 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. 3.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. 3.6.1 E-Person DSpace holds 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 DSpace 1.8 Documentation Page of 24 643 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, if LDAP authentication is used for this E-Person. 3.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 being identified as anwithout 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 corresponding privileges. Administrators can also use groups as "roles" to manage the granting of privileges more efficiently. 3.7 Authentication is when an application session positively identifies itself as belonging to an E-Person and/orAuthentication Group. In DSpace 1.4 and later, it is implemented by a mechanism called : the DSpaceStackable Authentication configuration declares a "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. 3.8 Authorization DSpace 1.8 Documentation Page of 25 643 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 built-in 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: 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 get the same default read policy.not 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 Bitstream READ view bitstream WRITE modify bitstream Note that there is no 'DELETE' action. In order to 'delete' an object (e.g. an item) from the archive, one must have REMOVE permission on all objects (in this case, collection) that contain it. The 'orphaned' item is automatically deleted. DSpace 1.8 Documentation Page of 26 643 Policies can apply to individual e-people or groups of e-people. 3.9 Ingest Process and Workflow Rather than being a single subsystem, ingesting is a process that spans several. Below is a simple illustration of the current ingesting process in DSpace. DSpace Ingest Process The batch item importer is an application, which turns an external SIP (an XML metadata document with some content files) into an "in progress submission" object. The Web submission UI is similarly used by an end-user to assemble an "in progress submission" object. Depending on the policy of the collection to which the submission in targeted, a workflow process may be started. This typically allows one or more human reviewers or 'gatekeepers' to check over the submission and ensure it is suitable for inclusion in the collection. When the Batch Ingester or Web Submit UI completes the InProgressSubmission object, and invokes the next stage of ingest (be that workflow or item installation), a provenance message is added to the Dublin Core which includes the filenames and checksums of the content of the submission. Likewise, each time a workflow changes state (e.g. a reviewer accepts the submission), a similar provenance statement is added. This allows us to track how the item has changed since a user submitted it. Once any workflow process is successfully and positively completed, the InProgressSubmission object is consumed by an "item installer", that converts the InProgressSubmission into a fully blown archived item in DSpace. The item installer: Assigns an accession date Adds a "date.available" value to the Dublin Core metadata record of the item Adds an issue date if none already present DSpace 1.8 Documentation Page of 27 643 Adds a provenance message (including bitstream checksums) Assigns a Handle persistent identifier Adds the item to the target collection, and adds appropriate authorization policies Adds the new item to the search and browse index 3.9.1 Workflow Steps A collection's workflow can have up to three steps. Each collection may have an associated e-person group for performing each step; if no group is associated with a certain step, that step is skipped. If a collection has no e-person groups associated with any step, submissions to that collection are installed straight into the main archive. In other words, the sequence is this: The collection receives a submission. If the collection has a group assigned for workflow step 1, that step is invoked, and the group is notified. Otherwise, workflow step 1 is skipped. Likewise, workflow steps 2 and 3 are performed if and only if the collection has a group assigned to those steps. When a step is invoked, the submission is put into the 'task pool' of the step's associated group. One member of that group takes the task from the pool, and it is then removed from the task pool, to avoid the situation where several people in the group may be performing the same task without realizing it. The member of the group who has taken the task from the pool may then perform one of three actions: Workflow Step Possible actions 1 Can accept submission for inclusion, or reject submission. 2 Can edit metadata provided by the user with the submission, but cannot change the submitted files. Can accept submission for inclusion, or reject submission. 3 Can edit metadata provided by the user with the submission, but cannot change the submitted files. Must then commit to archive; may not reject submission. DSpace 1.8 Documentation Page of 28 643 Submission Workflow in DSpace If a submission is rejected, the reason (entered by the workflow participant) is e-mailed to the submitter, and it is returned to the submitter's 'My DSpace' page. The submitter can then make any necessary modifications and re-submit, whereupon the process starts again. If a submission is 'accepted', it is passed to the next step in the workflow. If there are no more workflow steps with associated groups, the submission is installed in the main archive. One last possibility is that a workflow can be 'aborted' by a DSpace site administrator. This is accomplished using the administration UI. The reason for this apparently arbitrary design is that is was the simplest case that covered the needs of the early adopter communities at MIT. The functionality of the workflow system will no doubt be extended in the future. 3.10 Supervision and Collaboration In order to facilitate, as a primary objective, the opportunity for thesis authors to be supervised in the preparation of their e-theses, a supervision order system exists to bind groups of other users (thesis supervisors) to an item in someone's pre-submission workspace. The bound group can have system policies associated with it that allow different levels of interaction with the student's item; a small set of default policy groups are provided: Full editorial control View item contents No policies Once the default set has been applied, a system administrator may modify them as they would any other policy set in DSpace This functionality could also be used in situations where researchers wish to collaborate on a particular submission, although there is no particular collaborative workspace functionality. 3.11 Handles Researchers require a stable point of reference for their works. The simple evolution from sharing of citations to emailing of URLs broke when Web users learned that sites can disappear or be reconfigured without notice, and that their bookmark files containing critical links to research results couldn't be trusted in the long term. To help solve this problem, a core DSpace feature is the creation of a persistent identifier for every item, collection and community stored in DSpace. To persist identifiers, DSpace requires a storage- and location- independent mechanism for creating and maintaining identifiers. DSpace uses the for creating theseCNRI Handle System identifiers. The rest of this section assumes a basic familiarity with the Handle system. http://www.handle.net/ DSpace 1.8 Documentation Page of 29 643 DSpace uses Handles primarily as a means of assigning globally unique identifiers to objects. Each site running DSpace needs to obtain a unique Handle 'prefix' from CNRI, so we know that if we create identifiers with that prefix, they won't clash with identifiers created elsewhere. Presently, Handles are assigned to communities, collections, and items. Bundles and bitstreams are not assigned Handles, since over time, the way in which an item is encoded as bits may change, in order to allow access with future technologies and devices. Older versions may be moved to off-line storage as a new standard becomes de facto. Since it's usually the that is being preserved, rather than the particular bititem encoding, it only makes sense to persistently identify and allow access to the item, and allow users to access the appropriate bit encoding from there. Of course, it may be that a particular bit encoding of a file is explicitly being preserved; in this case, the bitstream could be the only one in the item, and the item's Handle would then essentially refer just to that bitstream. The same bitstream can also be included in other items, and thus would be citable as part of a greater item, or individually. The Handle system also features a global resolution infrastructure; that is, an end-user can enter a Handle into any service (e.g. Web page) that can resolve Handles, and the end-user will be directed to the object (in the case of DSpace, community, collection or item) identified by that Handle. In order to take advantage of this feature of the Handle system, a DSpace site must also run a 'Handle server' that can accept and resolve incoming resolution requests. All the code for this is included in the DSpace source code bundle. Handles can be written in two forms: hdl:1721.123/4567 http://hdl.handle.net/1721.123/4567 The above represent the same Handle. The first is possibly more convenient to use only as an identifier; however, by using the second form, any Web browser becomes capable of resolving Handles. An end-user need only access this form of the Handle as they would any other URL. It is possible to enable some browsers to resolve the first form of Handle as if they were standard URLs using , butCNRI's Handle Resolver plug-in since the first form can always be simply derived from the second, DSpace displays Handles in the second form, so that it is more useful for end-users. It is important to note that DSpace uses the CNRI Handle infrastructure only at the 'site' level. For example, in the above example, the DSpace site has been assigned the prefix '1721.123'. It is still the responsibility of the DSpace site to maintain the association between a full Handle (including the '4567' local part) and the community, collection or item in question. 3.12 Bitstream 'Persistent' Identifiers http://www.handle.net/resolver/index.html DSpace 1.8 Documentation Page of 30 643 Similar to handles for DSpace items, bitstreams also have 'Persistent' identifiers. They are more volatile than Handles, since if the content is moved to a different server or organization, they will no longer work (hence the quotes around 'persistent'). However, they are more easily persisted than the simple URLs based on database primary key previously used. This means that external systems can more reliably refer to specific bitstreams stored in a DSpace instance. Each bitstream has a sequence ID, unique within an item. This sequence ID is used to create a persistent ID, of the form: dspace url/bitstream/handle/sequence ID/filename For example: https://dspace.myu.edu/bitstream/123.456/789/24/foo.html The above refers to the bitstream with sequence ID 24 in the item with the Handle . The hdl:123.456/789 foo.html is really just there as a hint to browsers: Although DSpace will provide the appropriate MIME type, some browsers only function correctly if the file has an expected extension. 3.13 Storage Resource Broker (SRB) Support DSpace offers two means for storing bitstreams. The first is in the file system on the server. The second is using . Both are achieved using a simple, lightweight API.SRB (Storage Resource Broker) SRB is purely an option but may be used in lieu of the server's file system or in addition to the file system. Without going into a full description, SRB is a very robust, sophisticated storage manager that offers essentially unlimited storage and straightforward means to replicate (in simple terms, backup) the content on other local or remote storage resources. 3.14 Search and Browse DSpace allows end-users to discover content in a number of ways, including: Via external reference, such as a Handle Searching for one or more keywords in metadata or extracted full-text http://www.sdsc.edu/srb DSpace 1.8 Documentation Page of 31 643 Browsing though title, author, date or subject indices, with optional image thumbnails Search is an essential component of discovery in DSpace. Users' expectations from a search engine are quite high, so a goal for DSpace is to supply as many search features as possible. DSpace's indexing and search module has a very simple API which allows for indexing new content, regenerating the index, and performing searches on the entire corpus, a community, or collection. Behind the API is the Java freeware search engine . Lucene gives us fielded searching, stop word removal, stemming, andLucene the ability to incrementally add new indexed content without regenerating the entire index. The specific Lucene search indexes are configurable enabling institutions to customize which DSpace metadata fields are indexed. Another important mechanism for discovery in DSpace is the browse. This is the process whereby the user views a particular index, such as the title index, and navigates around it in search of interesting items. The browse subsystem provides a simple API for achieving this by allowing a caller to specify an index, and a subsection of that index. The browse subsystem then discloses the portion of the index of interest. Indices that may be browsed are item title, item issue date, item author, and subject terms. Additionally, the browse can be limited to items within a particular collection or community. 3.15 HTML Support For the most part, at present DSpace simply supports uploading and downloading of bitstreams as-is. This is fine for the majority of commonly-used file formats – for example PDFs, Microsoft Word documents, spreadsheets and so forth. HTML documents (Web sites and Web pages) are far more complicated, and this has important ramifications when it comes to digital preservation: Web pages tend to consist of several files – one or more HTML files that contain references to each other, and stylesheets and image files that are referenced by the HTML files. Web pages also link to or include content from other sites, often imperceptibly to the end-user. Thus, in a few year's time, when someone views the preserved Web site, they will probably find that many links are now broken or refer to other sites than are now out of context.In fact, it may be unclear to an end-user when they are viewing content stored in DSpace and when they are seeing content included from another site, or have navigated to a page that is not stored in DSpace. This problem can manifest when a submitter uploads some HTML content. For example, the HTML document may include an image from an external Web site, or even their local hard drive. When the submitter views the HTML in DSpace, their browser is able to use the reference in the HTML to retrieve the appropriate image, and so to the submitter, the whole HTML document appears to have been deposited correctly. However, later on, when another user tries to view that HTML, their browser might not be able to retrieve the included image since it may have been removed from the external server. Hence the HTML will seem broken. Often Web pages are produced dynamically by software running on the Web server, and represent the state of a changing database underneath it. Dealing with these issues is the topic of much active research. Currently, DSpace bites off a small, tractable chunk of this problem. DSpace can store and provide on-line browsing capability for HTML documents. In practical terms, this means:self-contained, non-dynamic http://jakarta.apache.org/lucene/ DSpace 1.8 Documentation Page of 32 643 No dynamic content (CGI scripts and so forth) All links to preserved content must be , that do not refer to 'parents' above the 'root' of therelative links HTML document/site: is OKdiagram.gif is OKimage/foo.gif is only OK in a file that is at least a directory deep in the HTML document/site../index.html hierarchy is not OK (the link will break)/stylesheet.css is not OK (the link will continue to link to the external sitehttp://somedomain.com/content.html which may change or disappear) Any 'absolute links' (e.g. ) are stored 'as is', and will continue to linkhttp://somedomain.com/content.html to the external content (as opposed to relative links, which will link to the copy of the content stored in DSpace.) Thus, over time, the content referred to by the absolute link may change or disappear. 3.16 OAI Support The has developed a . This allows sites toOpen Archives Initiative protocol for metadata harvesting programmatically retrieve or 'harvest' the metadata from several sources, and offer services using that metadata, such as indexing or linking services. Such a service could allow users to access information from a large number of sites from one place. DSpace exposes the Dublin Core metadata for items that are publicly (anonymously) accessible. Additionally, the collection structure is also exposed via the OAI protocol's 'sets' mechanism. OCLC's open source OAICat framework is used to provide this functionality. You can also configure the OAI service to make use of any crosswalk plugin to offer additional metadata formats, such as MODS. DSpace's OAI service does support the exposing of deletion information for withdrawn items, but not for items that are 'expunged' (see above). DSpace also supports OAI-PMH resumption tokens. 3.17 SWORD Support SWORD (Simple Web-service Offering Repository Deposit) is a protocol that allows the remote deposit of items into repositories. SWORD was further developed in SWORD version 2 to add the ability to retrieve, update, or delete deposits. DSpace supports the SWORD protocol via the 'sword' web application and SWord v2 via the swordv2 web application. The specification and further information can be found at .http://swordapp.org 3.18 OpenURL Support http://somedomain.com/content.html http://somedomain.com/content.html http://www.openarchives.org/ http://www.openarchives.org/OAI/openarchivesprotocol.html http://www.oclc.org/research/software/oai/cat.shtm http://swordapp.org DSpace 1.8 Documentation Page of 33 643 DSpace supports the from , in a rather simple fashion. If your institution has an SFXOpenURL protocol SFX server, DSpace will display an OpenURL link on every item page, automatically using the Dublin Core metadata. Additionally, DSpace can respond to incoming OpenURLs. Presently it simply passes the information in the OpenURL to the search subsystem. A list of results is then displayed, which usually gives the relevant item (if it is in DSpace) at the top of the list. 3.19 Creative Commons Support DSpace provides support for Creative Commons licenses to be attached to items in the repository. They represent an alternative to traditional copyright. To learn more about Creative Commons, visit .their website Support for license selection is controlled by a site-wide configuration option, and since license selection involves interaction with the Creative Commons website, additional parameters may be configured to work with a proxy server. If the option is enabled, users may select a Creative Commons license during the submission process, or elect to skip Creative Commons licensing. If a selection is made, metadata and (optionally) a copy of the license text is stored along with the item in the repository. There is also an indication - text and a Creative Commons icon - in the item display page of the web user interface when an item is licensed under Creative Commons. For specifics of how to configure and use Creative Commons licenses, see the configuration section. 3.20 Subscriptions As noted above, end-users (e-people) may 'subscribe' to collections in order to be alerted when new items appear in those collections. Each day, end-users who are subscribed to one or more collections will receive an e-mail giving brief details of all new items that appeared in any of those collections the previous day. If no new items appeared in any of the subscribed collections, no e-mail is sent. Users can unsubscribe themselves at any time. RSS feeds of new items are also available for collections and communities. 3.21 Import and Export DSpace includes batch tools to import and export items in a simple directory structure, where the Dublin Core metadata is stored in an XML file. This may be used as the basis for moving content between DSpace and other systems. For more information see .Item Importer and Exporter (see page ) DSpace also includes various package importer and exporter tools, which support many common content packaging formats like METS. For more information see .Package Importer and Exporter (see page ) 3.22 Registration http://www.sfxit.com/OpenURL/ http://www.sfxit.com/ http://creativecommons.org DSpace 1.8 Documentation Page of 34 643 Registration is an alternate means of incorporating items, their metadata, and their bitstreams into DSpace by taking advantage of the bitstreams already being in accessible computer storage. An example might be that there is a repository for existing digital assets. Rather than using the normal interactive ingest process or the batch import to furnish DSpace the metadata and to upload bitstreams, registration provides DSpace the metadata and the location of the bitstreams. DSpace uses a variation of the import tool to accomplish registration. 3.23 Statistics DSpace offers system statistics for administrator usage, as well as usage statistics on the level of items, communities and collections. 3.23.1 System Statistics Various statistical reports about the contents and use of your system can be automatically generated by the system. These are generated by analyzing DSpace's log files. Statistics can be broken down monthly. The report includes following sections A customizable general overview of activities in the archive, by default including: Number of items archived Number of bitstream views Number of item page views Number of collection page views Number of community page views Number of user logins Number of searches performed Number of license rejections Number of OAI Requests Customizable summary of archive contents Broken-down list of item viewings A full break-down of all performed actions User logins Most popular searches Log Level Information Processing information!stats_genrl_overview.png! The results of statistical analysis can be presented on a by-month and an in-total report, and are available via the user interface. The reports can also either be made public or restricted to administrator access only. 3.23.2 Item, Collection and Community Usage Statistics DSpace 1.8 Documentation Page of 35 643 Usage statistics can be retrieved from individual item, collection and community pages. These Usage Statistics pages show: Total page visits (all time) Total Visits per Month File Downloads (all time)* Top Country Views (all time) Top City Views (all time) *File Downloads information is only displayed for item-level statistics. Note that downloads from separate bitstreams are also recorded and represented separately. DSpace is able to capture and store File Download information, even when the bitstream was downloaded from a direct link on an external website. 3.24 Checksum Checker The purpose of the checker is to verify that the content in a DSpace repository has not become corrupted or been tampered with. The functionality can be invoked on an ad-hoc basis from the command line, or configured via cron or similar. Options exist to support large repositories that cannot be entirely checked in one run of the tool. The tool is extensible to new reporting and checking priority approaches. 3.25 Usage Instrumentation DSpace can report usage events, such as bitstream downloads, to a pluggable event processor. This can be used for developing customized usage statistics, for example. Sample event processor plugins writes event records to a file as tab-separated values or XML. 3.26 Choice Management and Authority Control DSpace 1.8 Documentation Page of 36 643 1. 2. 3. This is a configurable framework that lets you define plug-in classes to control the choice of values for a given DSpace metadata fields. It also lets you configure fields to include "authority" values along with the textual metadata value. The choice-control system includes a user interface in both the Configurable Submission UI and the Admin UI (edit Item pages) that assists the user in choosing metadata values. 3.26.1 Introduction and Motivation Definitions Choice Management This is a mechanism that generates a list of choices for a value to be entered in a given metadata field. Depending on your implementation, the exact choice list might be determined by a proposed value or query, or it could be a fixed list that is the same for every query. It may also be closed (limited to choices produced internally) or open, allowing the user-supplied query to be included as a choice. Authority Control This works in addition to choice management to supply an authority key along with the chosen value, which is also assigned to the Item's metadata field entry. Any authority-controlled field is also inherently choice-controlled. About Authority Control The advantages we seek from an authority controlled metadata field are: , by comparing authorityThere is a simple and positive way to test whether two values are identical keys. Comparing plain text values can give false positive results e.g. when two different people have a name that is written the same. It can also give false negative results when the same name is written different ways, e.g. "J. Smith" vs. "John Smith". The submission and admin UIs may call on the authority toHelp in entering correct metadata values. check a proposed value and list possible matches to help the user select one. By sharing a name authority with another application, your DSpace canImproved interoperability. interoperate more cleanly with other applications. For example, a DSpace institutional repository sharing a naming authority with the campus social network would let the social network construct a list of all DSpace Items matching the shared author identifier, rather than by error-prone name matching. When the name authority is shared with a campus directory, DSpace can look up the email address of an author to send automatic email about works of theirs submitted by a third party. That author does not have to be an EPerson. DSpace 1.8 Documentation Page of 37 643 4. 1. 2. Authority keys are normally invisible in the public web UIs. They are only seen by administrators editing metadata. The value of an authority key is not expected to be meaningful to an end-user or site visitor. Authority control is different from the controlled vocabulary of keywords already implemented in the submission UI: The source of authority control is typically an external database orAuthorities are external to DSpace. network resource. Plug-in architecture makes it easy to integrate new authorities without modifying any core code. This authority proposal impacts all phases of metadata management. The keyword vocabularies are only for the submission UI. Authority control is asserted everywhere metadata values are changed, including unattended/batch submission, LNI and SWORD package submission, and the administrative UI. Some Terminology Authority An authority is a source of fixed values for a given domain, each unique value identified by a key. . For example, the OCLC LC Name Authority Service. Authority Record The information associated with one of the values in an authority; may include alternate spellings and equivalent forms of the value, etc. Authority Key An opaque, hopefully persistent, identifier corresponding to exactly one record in the authority. DSpace 1.8 Documentation Page of 38 643 4 Installation 4.1 For the Impatient Since some users might want to get their test version up and running as fast as possible, offered below is an outline of getting DSpace to run quickly in a Unix-based environment using the DSpace sourceunsupported release. Only experienced unix admins should even attempt the following without going to the detailed Installation Instructions (see page 42) useradd -m dspace gunzip -c dspace-1.x-src-release.tar.gz | tar -xf - createuser -U postgres -d -A -P dspace createdb -U dspace -E UNICODE dspace cd [dspace-source]/dspace/config vi dspace.cfg mkdir [dspace] chown dspace [dspace] su - dspace cd [dspace-source]/dspace mvn package cd [dspace-source]/dspace/target/dspace--build.dir ant fresh_install cp -r [dspace]/webapps/* [tomcat]/webapps /etc/init.d/tomcat start [dspace]/bin/dspace create-administrator 4.2 Prerequisite Software The list below describes the third-party components and tools you'll need to run a DSpace server. These are just guidelines. Since DSpace is built on open source, standards-based tools, there are numerous other possibilities and setups. Also, please note that the configuration and installation guidelines relating to a particular tool below are here for convenience. You should refer to the documentation for each individual component for complete and up-to-date details. Many of the tools are updated on a frequent basis, and the guidelines below may become out of date. 4.2.1 UNIX-like OS or Microsoft Windows DSpace 1.8 Documentation Page of 39 643 UNIX-like OS (Linux, HP/UX, Mac OSX, etc.) : Many distributions of Linux/Unix come with some of the dependencies below pre-installed or easily installed via updates, you should consult your particular distributions documentation or local system administrators to determine what is already available. Microsoft Windows: After verifying all prerequisites below, see the Windows Installation (see page 59) section for Windows tailored instructions 4.2.2 Oracle Java JDK 6 (standard SDK is fine, you don't need J2EE) Please note, at this time,DSpace requires Oracle Java 6 (standard SDK is fine, you don't need J2EE). DSpace does not function properly with Java JDK 7 (see warning below). Oracle's Java can be downloaded from the following location: . Again, you can just download the Javahttp://www.oracle.com/technetwork/java/javase/downloads/index.html SE JDK version. Java 7 is currently unsupported DSpace does not currently support Java 7, as there is a known issue with Java 7 and Lucene/SOLR (which DSpace uses for search & browse functionality). For more details, see this article on the Apache site: "WARNING: Index corruption and crashes in Apache Lucene Core / Apache Solr with as well as this Java bug report: Java 7" 7073868 Other flavors of Java may cause issues Only Oracle's Java has been tested with each release and is known to work correctly. Other flavors of Java may pose problems. 4.2.3 Apache Maven 2.2.x or higher (Java build tool) DSpace 1.7.x requires usage of Maven 2.2.x DSpace 1.7.x required usage of Maven 2.2.x, as it did not build properly when using Maven 2.0.x or Maven 3.x. This was a known issue (see ). However, DSpace 1.8.x resolved this issue so thatDS-788 DSpace now builds properly with Maven 2.2.x or above. http://www.oracle.com/technetwork/java/javase/downloads/index.html http://lucene.apache.org/java/docs/index.html#28+July+2011+-+WARNING%3A+Index+corruption+and+crashes+in+Apache+Lucene+Core+%2F+Apache+Solr+with+Java+7 http://lucene.apache.org/java/docs/index.html#28+July+2011+-+WARNING%3A+Index+corruption+and+crashes+in+Apache+Lucene+Core+%2F+Apache+Solr+with+Java+7 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7073868 https://jira.duraspace.org/browse/DS-788 DSpace 1.8 Documentation Page of 40 643 Maven is necessary in the first stage of the build process to assemble the installation package for your DSpace instance. It gives you the flexibility to customize DSpace using the existing Maven projects found in the directory or by adding in your own Maven project to build the installation[dspace-source]/dspace/modules package for DSpace, and apply any custom interface "overlay" changes. Maven can be downloaded from the following location: http://maven.apache.org/download.html Configuring a Proxy You can configure a proxy to use for some or all of your HTTP requests in Maven 2.0. The username and password are only required if your proxy requires basic authentication (note that later releases may support storing your passwords in a secured keystore‚ in the mean time, please ensure your file (usually settings.xml ) is secured with permissions appropriate for your operating system).${user.home}/.m2/settings.xml Example: . . true http proxy.somewhere.com 8080 proxyuser somepassword www.google.com|*.somewhere.com . . 4.2.4 Apache Ant 1.8 or later (Java build tool) Apache Ant is still required for the second stage of the build process. It is used once the installation package has been constructed in and still uses some of the familiar[dspace-source]/dspace/target/dspace--build.dir ant build targets found in the 1.4.x build process. Ant can be downloaded from the following location: http://ant.apache.org 4.2.5 Relational Database: (PostgreSQL or Oracle). http://maven.apache.org/download.html http://ant.apache.org/ DSpace 1.8 Documentation Page of 41 643 PostgreSQL can be downloaded from the following location: PostgreSQL 8.2 to 8.4 . It is highly recommended that you try to work with Postgres 8.4 or greater,http://www.postgresql.org/ however, 8.2 or greater should still work. Unicode (specifically UTF-8) support must be enabled. This is enabled by default in 8.0+. Once installed, you need to enable TCP/IP connections (DSpace uses JDBC). In : uncomment the line starting: . Then tighten up security apostgresql.conf listen_addresses = 'localhost' bit by editing and adding