Database Data Management

From Archivematica
Revision as of 17:24, 19 September 2012 by Joseph (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Main Page > Development > Development documentation > Database Data Management

Contents

For the 1.0 Release

The data for the transcoder will need to be maintained by the FPR. The table structure will be maintained by the package.

All pk INT's will be replaced will UUIDs. This will allow for local customizations to be distinguished from the original data provided in archivematica.

All tables will have a replaces UUID column added. This column will be populated when a provided rule is replaced with an updated/custom one. As part of the update, the system will need to

Last updated.

Development

To separate data for the transcoder, we'll be using a series of mysql dumps. Once the FPR data is seperate, the developer can work on a means of populating that into their database, with the columns they require, and getting them into the database through an API.

For the 1.1 Release

Development

Editing Data

For the future Releases

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox