Exercise 16: Historical Archive

erDiagram

    document {
        string title
        datetime creation_date
        string type
        int key PK "id_document"
        int id_document_state FK "id_document_state"
    }

    archivist {
        string name
        string contact
        int key PK "id_archivist"
    }

    archive {
        string name
        string location
        int key PK "id_archive"
        int id_archivist FK "id_archivist"
        int id_archive_status FK "id_archive_status"
    }

    archive_status {
        string name
        string label
        string uuid
        int key PK "id_archive_status"
    }

    document_state {
        string name
        string label
        string uuid
        int key PK "id_document_state"
    }

    archive_document {
        int key PK "id_archive_document"
        int id_archive FK "id_archive"
        int id_document FK "id_document"
    }

    document_state one--many document : has
    document one--many archive_document : stored_in
    archive one--many archive_document : contains
    archive_status one--many archive:has
    archivist one--many archive : manages

Description #

• The property “name” in the table “document_state” can have the values: “Preserved”, “Damaged”, “Fixed” and “Lost”.

• The property “name” in the table “archive_status” can have the values: “Open” or “Closed”.

• This app manages documents and archives, tracking details such as document type, creation date, and state. It stores information about archivists, their contact details, and the archives they manage. Documents are linked to their respective states and stored in archives. The app tracks which documents are in which archives and which archivist is responsible for each archive.

• In entity document_state, name represents the state that will be displayed on the screen, label represents the value that programmer will use to filter the states, and the uuid represents a value to distinguish the states.

• OBS: The value of the field “uuid” is generated automatically.

Tasks #

• document/archivist/archive/document_state/archive_document: Add, Edit, Delete.

• Create a catalog for entities: “document_state”, “archivist”, “document”, “archive_status” and “archive”.

• Create event listeners for tables that needs validations (e.g., adding a document without a title, archive without location, etc., should not be allowed).

• Add a new entity action at the document level “Repair document”:

  • It will change the document state from “Damaged” to “Fixed”;
  • A document cannot be fixed if it is in the “Preserved” or “Lost” state. If it is → warning message;
  • A document cannot be fixed if it is already in the “Fixed” state.

• Add a new entity action at the document level “Restore document”:

  • It will change the status from “Lost” to “Preserved”;
  • A document cannot be restored if it is in the “Damaged” state If it is → warning message. First it should be repaired if possible, and then restored.
  • A document cannot be restored if it is already in the “Preserved” state.

• Document report: archive situation at document level (total number of archives, document details).

• Archivist report: archive situation at archivist level (total number of archives, document details).

• Archive report: document situation at archive level (total number of documents).