Proposals that have either been retired or decided to not move forward on. These may contain details that still may be of interest in future proposals
Open up rights to use a controlled vocabulary and link from an external source
Asynchronous Release: Asynchronous Release is change in the DSpace release process and version numbering process on modules within the DSpace trunk to allow more flexibility adding prebuilt Addon modules into DSpace.
Configurable submission is one of only a few mechanisms in DSpace to assist the process of managing the metadata or other characteristics of items being ingested. Another tool is the Item template, which notably also is only configurable by collection. You can think of both of them in terms of a more general capability: using contextual information to streamline or automate the ingest. We can call this capability 'context-driven ingest' or perhaps 'context-assisted ingest'. Maybe the best descri
Design Direction Proposal to work on the elimination of configuration files in favor of storing configuration in database wherever possible.
Use the "Other" field to specify which standards
Simplify/make local customizations more accessible through UI and expose RDF triples
summary page of the metadata projects/priorities identified by the October 2011 community survey on improving metadata support https://wiki.duraspace.org/download/attachments/30217377/Metadata+Support+Survey+Final.pdf?version=1&modificationDate=1328709175068 authored by the DSpace Community Advisory Team at the request of the DSpace Committers/Developers https://wiki.duraspace.org/display/DSPACE/DSpaceContributors
Improve the verification/safety measures when editing/removing metadata fileds
This page represented a proposed RoadMap to 2.0 from Tim Donohue. It still needs broader discussion/approval before adoption.
Using Quartz as a utility to manage asynchronous eventing in DSpace Services, we can setup a job scheduling environment in the DSpace web application that is consistent across platforms. Likewise, jobs can be managed such that they are persistent across tomcat sessions/restarts and give the Repo Admins the ability to manage the scheduling and de-scheduling of activities.
This is a page of possible technical refactoring proposals for moving the trunk forward towards greater modularity and plug-ability.
Currently instead of creating a customized metadata schema, some DSpace repository managers edit the default registry, effectively breaking compliance with the standard Dublin Core. This can create a problem for the portability of data to/from of your repository. It has been proposed that in the future that DSpace would include 3 different metadata schemas, to insure that the metadata will be easily portable to other systems
EPrints supports VOID and LoD, So should we?