Page History
...
| Feature | Notes / Tickets | Priority | Volunteer(s) | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
 Single Search / Browse System (SOLR) |
| High | Kim Shepherd for LuceneTim Donohue | ||||||||||||||||
| Service Based API / Hibernate |
| Medium/High | Kevin Van de Velde (Atmire) | ||||||||||||||||
| DSpace needs local object identifiers | UUIDs are provided as part of the Service Based API refactor (see above) | Medium | Mark H. Wood | ||||||||||||||||
| Enhance DSpace testing framework (for integration testing) |
| Medium | |||||||||||||||||
| AWS S3 Bitstream Storage | A refactor of the Bitstream Storage Manager to allow different implementations for file/bitstream storage. The primary motivation is leverage a cloud service, such as Amazon S3, which offers easy management, infinite scalability, and low pricing. Other storage implementations could be built off of this work. This follows the DSpace 2.0 goal of having a Pluggable Assetstore.
| Peter Dietz | |||||||||||||||||
| Make configurable which PI to show in JSPUI item view |
| Low | Pascal-Nicolas Becker | ||||||||||||||||
| Framework to better support metadata import from external sources |
| @mire | |||||||||||||||||
|
| Netherlands Cancer Institute | |||||||||||||||||
| Import of ScienceDirect metadata including embargo and linking to or embedding of the final version |
| Letitia Mukherjee | |||||||||||||||||
|
| ||||||||||||||||||
| Reloadable / Dynamic Configurations |
(Would also need a resolution to
| ||||||||||||||||||
| Metadata registry via REST API |
| Terrence W Brady | |||||||||||||||||
| REST API extensions to support interactive reports |
| Terrence W Brady | |||||||||||||||||
| CSV export of search results in XMLUI |
| ||||||||||||||||||
| Indexing of right-to-left text in PDFs |
| ||||||||||||||||||
| Default search to boolean AND |
| Andrea Schweer | |||||||||||||||||
| OAI deletion mode correction |
| ||||||||||||||||||
| REST API needs versioning |
| Peter Dietz | |||||||||||||||||
| Move LNI into a separate project | As LNI is not in wide use anymore, and it was disabled by default in 5.0, it probably would be best to migrate it to a separate GitHub Project. Anyone who wishes to still use LNI can still install it separately. But, it would no longer be provided out-of-the-box.
| Robin Taylor | |||||||||||||||||
| Changes to REST API | TODO: any changes go here
|
...
Instead of a single "Release Coordinator", the DSpace 6.0 release will be managed by a "Release Team".
Release Team Leader
...
Release Team Members
...
| Date | Milestone | What it means |
|---|---|---|
| November 12 | Deadline for feature pull requests | If you wish to contribute features to DSpace 6.0, you must submit a pull request by this date. |
| November - January | Review, merger and conflict resolution between pull requests | The entire hour's meeting will be used to discuss proposed features submitted by the deadline. |
FebruaryMarch, 2016 | Feature freeze | DSpace 6.0 is considered feature-complete on this date. Only bugfixes will be pulled between this date and final release. |
| February March 31st (TBAestimated) | Release Candidate 1 tagged | A DSpace 6.0 Release Candidate will be available for wider testing. |
TBA | Testathon | Intensive public testing of the 6.0 Release Candidate is invited. The Release Team will focus on getting problems resolved. |
| TBA | Release Candidate 2 tagged | An updated DSpace 6.0 Release Candidate will be available for wider testing. |
| March/April | DSpace 6.0 is publicly released | DSpace 6.0 is released for download and general use. |
...
Overview
Content Tools