1.7 Why

Objective is to conserve, offer access and preserve intelligibility of electronic archives.

• Conception was made in order to provides redundancy, trace-ability and a shared HTML access.
• MEDIATEX make possible to rebuild the system mainly from its external supports (Notice: according that up to date catalogue and extraction meta-data are available on supports too). This feature avoid too much entropy and ease migration/restitution.
• It aims to provide a strong “storage” layer on which we should build a whole OAIS system. In that sense, it should provide a positive context for preservation operations, in prevision of time when the actual storage technologies will become outdated.
• It tries to provide a dedicated workaround for the CAP theorem, using GIT merges. (The also known as Brewer’s theorem states that it is impossible for a distributed computer system to simultaneously provide all three of the following guarantees: Consistency, Availability and Partition tolerance.)
• The just uploaded data are not safe: RPO (Recovery Point Objective) is roughly either 1 month (on supports) or 1 day (on caches). But next, for managed data, the RTO (Recovery Time Objective) should be null: DRP (Disaster Recovery Plan) simply consists on adding new servers to the collection (main configuration is already handle by the collection) and to include the new public IP addresses into the actual DNS round-Robbin’s pool.

Why not use MEDIATEX:

• Not designed to handle millions of archives.
• Is a prototype and still need to be optimised.
• Must not occult the forgetting right. As data are burned on optical disks, it is complicated to erase only a part of them.