compared with
Current by Maria Todorova
on Oct 07, 2011 14:58.

This line was removed.
This word was removed. This word was added.
This line was added.

Changes (10)

View Page History

h2. Web Site: [ArchiveSpace|]

Web Site: [ArchiveSpace|]

The project is still in Design phase. There are some good analysis and design documents: [Specifications|]

The ArchivesSpace community is building an open-source web application to manage descriptive information for archives, manuscripts, and digital objects.

h2. General Architecture

At heart, the application will consist of:
In addition, we are proposing that the the overall system architecture allow for the user community to develop new main record types, supporting record types, and sub-record types, or to extend the functionality of core areas. In other words, the overall architecture must be extensible. As a design principle, it must be possible to add additional functional areas without requiring any changes to the application core, that is to say without modifying storage architecture (e.g.table structures), object model, and API/libraries for the functional areas that are described below.

h2. Three Main Modules

Main modules represent the most important functional areas of the application and are the areas where most staff and public users will interact with the system. Using these modular areas, staff users will create, edit, and delete records, as well as establish relationships between five record types:
* In practical terms, the digital object may represent a surrogate of the entire resource/resource component record or only a portion of the resource/resource component record.

h2. Six Supporting Modules

The supporting modules will allow for the creation of supporting records that sit in a many-to-many relationships with accession resource, resource components, digital objects, and digital object component records. For example, one or more subject record may be linked to one or more resource records, each staff user record is required to have an associated repository, and so on. the permissible relationships are as spelled out in the specifications and are shown in summary form in the draft entity relationship diagram.

Location sub-records (consists of a linked location record and additional attribute values, as defined in location specification.)
For example, within the context of a particular resource record, a user can launch a method to create a date statement, extent statement, external document statement, or rights management statement. Each of those statement sub-records can be attached to one and only one parent record.

From Maria:
The project is still in Design phase. There are some good analysis and design documents: [Specifications| specifications/]