Date: Tue, 19 Mar 2024 03:20:56 -0400 (EDT) Message-ID: <1430701675.8679.1710832856048@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8678_1877294046.1710832856048" ------=_Part_8678_1877294046.1710832856048 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This is the place for the ArchReviewWorkingPrinciples text, wiki= fied so the ArchReview group can revise and expand on it.
1. DSpace is primarily open source software for building digital= repositories.
DSpace is intended to be free and open source software for digital repos= itories that enables services for access, provision, stewardship and re-use= of digital assets with a focus on educational and research materials; i.e.= to fulfill the mission of the DSpace Consortium.
2. DSpace will be usable based purely on free and open source so= ftware.
Although setups including custom and/or proprietary features and technol= ogies will be possible, it will always be possible to deploy DSpace using o= nly free and open source software.
3. DSpace will have a decoupled, stable, and application-neutral= core.
DSpace will always have a "core" system that supports a variety of highe= r-level applications, whose full scope is not bounded unnecessarily. It wil= l define stable APIs to enable diverse and innovative applications and func= tionality to be built on this core, without need to modify the source code = of the core.
4. While usable for a variety of applications, DSpace will retai= n useful "out-of-the-box" functionality for common use cases.
DSpace cannot support all the variable and emerging definitions and inno= vations in the repository space in a single interface application. DSpace w= ill provide out-of-the-box functionality for a common set of use cases (e.g= . an Open Access preprints application, a general content archive) that can= be installed with minimum possible effort, as well as modular support for = the easy construction of new applications.
5. DSpace will employ and support existing, open standards where= possible and practical.
For all DSpace functionality, open and established standards (when avail=
able) will be employed to
=E2=80=93 promote interoperability of various kinds with other systems, =
=E2=80=93 support the migration of data into or out of other systems,
=E2=80=93 leverage external development wherever possible
But there are practical considerations of the maturity of particular stand=
ards that will be considered before implementing it.
6. DSpace releases should be minimally disruptive.
The architecture should reinforce good behavior in making changes/custom= izations/improvements to future releases of the system, so that upgrades ar= e minimally disruptive for current adopters.
7. DSpace will support an exit strategy for content.
It will be possible to export all data necessary for the future re-use a= nd stewardship of content held in a DSpace repository, in open, well-docume= nted formats, for enabling migration into other systems and/or backup.
8. DSpace will continue to evolve.
There are many unsolved problems associated with stewardship of digital = materials, which will require research and experimentation (including some = failures) to solve. In addition to providing a robust, stable and functiona= l system, DSpace will enable innovation and experimentation, and will be de= signed with the knowledge that future development and re-architecting will = inevitably be necessary.