Topic: archives

topics > computer science > information > Group: information retrieval

software maintenance

archiving Information in Hypertext
compressed data
configuration management
database change management
database security
deletion of information
file system reliability
immutable files and data
information services
persistent data structure
programming environment
read-only and write-once file systems
revision delta
searching the Web
software change management
temporal database
text compression
version control


Archives are the organized records pertaining to an organization [American Heritage]. They are information that is preserved even when the information isn't accessed or modified. They substantiate current figures and the organization itself. They help keep current activities realistic, and act as a monitor.

Computer-based systems provide new possibilities for record archival, because information can be stored automatically at fairly low cost.

With computers there is a temptation to store everything, and to continually increase the amount of storage available. Such an approach is self-defeating because valuable information becomes lost in a sea of garbage. Instead all information should be time-stamped, and the longer information is retained, the more it should be interrelated and duplicated. Without a dynamic archive, old information becomes increasingly difficult to retrieve.

Static archive also increases the potential influences on current activity. For example old records can be taken out of context and used to damage an organization. With static archive the positive uses of information decrease over time while the negative uses increase. (cbb 6/83)

Subtopic: non-deletion up

Quote: most existing databases for real-world systems require non-deletion; e.g., financial accounts [»copeG3_1980]
Quote: can implement non-deletion by periodic checkpoint and an audit trail [»copeG3_1980]
Quote: information assigned to component databases by date and type; once a day, archive current database and create a new component database [»giffDK12_1985]
Quote: record abandoned plans and designs; helps transfer the project plan to the design team; helps avoid misdirected, low-level design decisions [»colwRP_2006]

Subtopic: retiring informaiton up

Quote: must specify how information is retired; otherwise it can always effect the future even though out of context [»cbb_1980, OK]

Subtopic: recovering archived info up

Quote: archived information becomes increasingly difficult to recover the longer it is stored [»cbb_1980, OK]

Subtopic: freeze software configurations, local copies up

Quote: freeze configurations of local applications; avoids spontaneous replacement of dependent components; need private copies [»briaM10_1999]

Subtopic: reliability without backups up

Quote: a design goal was a highly reliable file system which did not need independent backups [»corbFJ_1979]

Subtopic: temporal databases up

Quote: use a transaction-time database for backup by time-splitting modified nodes [»lomeD_1993]

Subtopic: logging up

Quote: reliable notification by a logger process that handles all messages; logs messages; adds an issue number to published notices (archived) [»cherDR4_1984]

Subtopic: tape archives up

Quote: maximize tape speed by double-buffering and small-sized writes; avoids repositioning [»drizL7_1993]
Quote: very large databases cannot use dump tapes and update logs because reading a 1-terabyte dump will take days [»silbA10_1991]

Subtopic: personal archives up

Quote: users of file systems must keep track of files and the cluttered relationships between them [»nelsTH1_1988]
Quote: users failed at establishing elaborate filing schemes for archived information; too much time and effort [»barrD7_1995]
Quote: for most users old information is generally not useful information; not worth archiving
Quote: personal, computer files are ephemeral, working, or archival; users archived little information

Subtopic: file revisions up

Quote: compress multiple versions of programs and data with deltas, i.e., an edit sequence from one to the other [»tichWF11_1984]

Subtopic: read-only archives up

Quote: file system for a WORM disk and a disk cache; read-only snapshots at any time by flushing the cache (a few seconds); assumes unbounded capacity [»quinS12_1991]
Quote: backup a volume by creating a read-only clone then dumping to tape; users can restore files from clone

Related Topics up

Group: software maintenance   (14 topics, 368 quotes)

Topic: archiving Information in Hypertext (6 items)
Topic: compressed data (16 items)
Topic: configuration management (25 items)
Topic: database change management (12 items)
Topic: database security (12 items)
Topic: deletion of information (11 items)
Topic: file system reliability (26 items)
Topic: immutable files and data (59 items)
Topic: information services (17 items)
Topic: persistent data structure (37 items)
Topic: programming environment (46 items)
Topic: read-only and write-once file systems (8 items)
Topic: revision delta (18 items)
Topic: searching the Web (53 items)
Topic: software change management (48 items)
Topic: temporal database (25 items)
Topic: text compression (17 items)
Topic: timestamps (19 items)
Topic: version control
(34 items)

Updated barberCB 3/04
Copyright © 2002-2008 by C. Bradford Barber. All rights reserved.
Thesa is a trademark of C. Bradford Barber.