Page History
...
| Info |
|---|
DSpace 1.7.0 is a scheduled, "time-based" release. In order to decrease delays in releasing new features and increase transparency, the DSpace Developers have decided to schedule 1.7.0 in advance and base its features on what we are able to complete within that timeframe. So, 1.7.0 will be a departure from 1.6.0 in that it may include fewer new features overall, but will be completed in a much tighter timeframe. Scheduling releases will benefit us all as it should decrease the delays in releasing new features, and increase the transparency of the development process. The DSpace Developers feel that these benefits will far outweigh the cost of having fewer major features in a given DSpace release. We hope the DSpace Community will also realize the immediate benefits, which should allow them to receive new features more quickly, rather than potentially waiting years for the next major release of the software. |
Organizational
Release Coordination
- Release Coordinator: Peter Dietz, Ohio State University Libraries
- Release Coordinator: Tim Donohue, DuraSpace
Timeline and Proceeding
Release Timeline:
August 13, 2010 : Milestone 1 - "Feature Decision Day"- October 22, 2010 : Feature Freeze
- October 29, 2010 : Final Documentation "Due Date"
- November 5, 2010 : Release Candidate 1
- November 8-19, 2010 : 1.7 Testathon
- December 3, 2010 : Release Candidate 2
- December 6-15, 2010 : Final Testing / Bug Fixing
- December 17, 2010 : Final Release
Release Process needs to proceed according to the following Maven release process: Release Procedure
New features in DSpace 1.7
| Mirage, a clean and professional looking theme for XMLUI. |
| Discover, a faceted browsing and searching interface that gives a deeper and more intuitive look at repository contents. |
| Archival Information Package (AIP) Backup & Restore process. Allows for a backup of DSpace into a generic METS-based structure, that can be used to migrate DSpace content to another system that supports AIP's (DSpace or non-DSpace). DuraCloud is an extention of this as one could then backup the AIP to the cloud storage. |
| Curation System , a framework for building and running tasks to help a Curator preserve and improve your repository contents.
|
| Automated Unit Testing of core code -- helps the developers ensure that DSpace is as bug free and stable as possible. Unit Testing coupled with continuous integration on our bamboo server allows us to validate every change to the DSpace code base. Thus letting us know immediately if something changed broke another feature. |
| Improved Google Scholar metadata exposure. Additional citation_ tags have been exposed to allow the Google Scholar crawler to find better associate repository metadata and PDF content. |
| PowerPoint text extraction, for searching within PowerPoint slides |
| Top 10 Most Visited items list, available for the overall site. |
...
- *New localization - *We have made localization for Serbian language, need several days to finish quality evaluation..
- Bojan Suzic 10/27 -- according to documentation in Release Procedure it can be accepted before final release?
- Peter Dietz 11/07 -- Correct, language packs can be updated between releases, it is best to get it finished before the final release in December though.
...
Organizational
Release Coordination
- Release Coordinator: Peter Dietz, Ohio State University Libraries
- Release Coordinator: Tim Donohue, DuraSpace
Timeline and Proceeding
Release Timeline:
- August 13, 2010 : Milestone 1 - "Feature Decision Day"
- October 22, 2010 : Feature Freeze
- October 29, 2010 : Final Documentation "Due Date"
- November 5, 2010 : Release Candidate 1
- November 8-19, 2010 : 1.7 Testathon
- December 3, 2010 : Release Candidate 2
- December 6-15, 2010 : Final Testing / Bug Fixing
- December 17, 2010 : Final Release
Release Process needs to proceed according to the following Maven release process: Release Procedure
Postponed for A Future Release
The following projects were considered for 1.7, but were not stable enough to be included. They need further review and development from the stakeholders before they are suitable for widespread use, they may be considered for a future release of DSpace. The next release they will be reconsidered for is 1.8
- REST API - Using standard web services to CRUD DSpace Objects. A product of previous GSOC.
- SWORD Client for DSpace – (Robin Taylor, and possibly Richard Jones & Stuart Lewis)
- would allow DSpace to push/submit content to other SWORD enabled repositories
- For closed & open access repositories – add a button to transfer content from a closed to an open repository.
- CGIProposal -- (Richard Rodgers/MIT)
- would allow for type-based submission processes (e.g. Theses/Dissertations could have different submission steps than articles/papers).unmigrated-wiki-markup
- based on the \[Item type based submission patch\|http://jira.dspace.org/jira/browse/DS-464\] picked up by Robin Taylor (initially a GSoC project)
- Context Guided Ingest – define an interface, where any submission code can write "attributes" and can retrieve those again later on. Can add any new attributes/values that you want for your submission code. Could be serialized to XML (using input-forms.xml) OR have an implementation of that service that stores in DB (recommended). JPA2?
- seems similar to SimpleStorage Service (user centered storage of state info) – Mark Diggory.
- Rewrite of Creative Commons licensing (MIT)
- would improve upon the features of the current CC licensing submission step
- Currently only against XMLUI from MIT
- Legacy problem – do we update old license to new or not? Currently MIT runs 'split version' with old licenses looking like old, and new look like new.
Overview
Content Tools