Editing New Stuff (section)

== Other Features ==

=== Planned ===

* More built-in metadata for scientific data applications.
** URIs for documents.
** Need some advice from the experts on this one. ie. The guys who've already been doing this stuff.
* the ability to search subobjects and related items, eg. search eprints by document format (already done)
* Elimination of need for generate_static (this is mostly done)
* Improved generate_views to produce variations of a view (by first author, by year etc.)
* Action icons for delete/deposit/edit etc on "Manage Items" and "Review". This is done, but the icons could be nicer :-)
* EPrints Toolkit - a service-level API that is available through scripting and REST interfaces. This is done, but still requires security and may gain some features before 3.1
* Export and RSS feeds for view pages.
* add_field and remove_field bin scripts.
* ZIP , wget and .tar.gz feature for file upload.
* Custom templates for searches, views and abstract pages for basic collection styling.

=== Proposed ===

* Process Workflow: as well as the deposit workflow, a process workflow will manage the various sequences of actions that an eprint can undergo from creation to final deposit (and beyond). This may include collaborative authoring, problem management, refereeing, copyright clearance, security clearance, IPR checking, metadata quality checks, e-journal and conference workflows. (EPrints currently allows, but does not manage, process workflows.)
* Plugin "masking" - to allow an installed plugin to subclass an existing plugin but to be called '''instead''' of it. This would be very useful for the DC plugin.
* AJAX autocompletion on search fields.

=== Proposed as Extension ===

* Virtual Collections: an individual eprint may be represent a collection of other eprint items; mainly used for image collections, workshop proceedings or learning objects composed of teaching assets. This may be achievable just with a new default type.
* Calendar view: calendar screen to track all embargo and license expirations, plus other planned events and timeouts.
* Increased support for "eprints application profile" Dublin Core recommendations.
* Web Services interface: currently in beta, awaiting debugging of the .NET SOAP interface.
* Better Semantic Web support (see Harry Mason's PhD work)
* Integration with Google Scholar or Web of Science (for citation capture and analysis.
** Gather citation data (score) from somewhere
** Provide view
** Provide search/order facility on this.
* Map widgets for input/output of location metadata
* Interoperable Statistics: statistics on the download use of individual eprints, eprint collections (per user, per research group, per community) or whole repository. (This is already provided as a separate IRStats package.)
* Validation Workflow Component (needs some bugs ironing out)
* Extra metadata fields

[[Category:Releases]]