{
  "format": "dataset-manifest/1",
  "slug": "archival-management-insights",
  "version": 2,
  "seed": "archival-management-insights:1",
  "spec": {
    "format": "dataset/1",
    "slug": "archival-management-insights",
    "name": "Archival Management Insights",
    "tagline": "User activities including task executions, backups, and comments on digital archives in government operations.",
    "description": "Digital archives are meticulously managed by government agencies to ensure public records are preserved, accessible, and secure. Efficient operations in this realm include activities such as file compression, extraction, and cloud storage, which play a vital role in maintaining a comprehensive history of public documents. Records range widely from licenses to user-generated content, and the management of these archives is essential for promoting transparency and accountability within government operations. Each entry in the dataset reflects a variety of user activities, with most focusing on routine tasks like executing backups or managing archived files, while less frequent entries provide detailed commentary and updates on the performance of compression methods.\n\nThe primary table, archival_management, holds vital data on each archival activity, including operation types, timestamps, user interactions, and file statuses. Each row represents an individual task performed within the archival management system, allowing developers to analyze patterns and performance metrics. Users can explore how regularly backup tasks are executed, identify potential bottlenecks in archival processes, and assess the effectiveness of different compression profiles over time.\n\nThis dataset is ideal for practicing data analysis and querying skills to answer pertinent questions about operational efficiency, user engagement, and archival integrity. Developers can utilize the data to model trends, generate reports, or even simulate various scenarios to improve archiving processes. Additionally, since the data is synthetic, it allows for experimentation without the constraints of real-world data privacy issues, making it a safe and useful resource for learning and development.",
    "domain": "government",
    "shape": "slowly-changing",
    "useCases": [
      "etl-pipelines",
      "teaching"
    ],
    "keywords": [
      "digital archives",
      "government operations",
      "file management",
      "cloud storage",
      "data analysis",
      "synthetic dataset"
    ],
    "locale": "en",
    "license": "CC0-1.0",
    "version": 1,
    "tables": {
      "archival_management": {
        "description": "This table holds records of digital archive management activities, linking user actions to specific files and compression profiles. Each row represents a unique user activity related to the management of digital archives, with timestamps indicating when the action occurred.",
        "rows": 500,
        "columns": {
          "id": {
            "kind": "pk",
            "description": "Unique identifier for each archive management activity."
          },
          "user_id": {
            "kind": "int",
            "min": 1,
            "max": 100,
            "description": "Identifier for the user performing the action."
          },
          "action": {
            "kind": "enum",
            "values": [
              "compress",
              "extract",
              "backup",
              "comment"
            ],
            "description": "Type of action performed on the digital archive."
          },
          "file_name": {
            "kind": "words",
            "min": 1,
            "max": 3,
            "description": "Name of the file being acted upon.",
            "pool": [
              "report",
              "summary",
              "document",
              "archive",
              "record",
              "file",
              "data",
              "analysis",
              "inventory",
              "log",
              "case",
              "project",
              "assessment",
              "review",
              "history",
              "folder",
              "note",
              "submission",
              "application",
              "request",
              "evidence",
              "finding",
              "update",
              "proposal",
              "plan",
              "strategy",
              "guideline",
              "policy",
              "directive",
              "memorandum",
              "notification",
              "correspondence",
              "transcript",
              "minutes",
              "bulletin",
              "schedule",
              "presentation",
              "brief",
              "overview",
              "statement",
              "resolution",
              "decision",
              "action",
              "task",
              "evaluation",
              "audit",
              "checklist",
              "registry",
              "catalog",
              "index",
              "reporting",
              "communication"
            ]
          },
          "compression_profile": {
            "kind": "enum",
            "values": [
              "standard",
              "high",
              "lossless"
            ],
            "nullable": true,
            "description": "Profile used for compression, if applicable."
          },
          "comment": {
            "kind": "sentence",
            "nullable": true,
            "description": "User comments on the archive action, if provided."
          },
          "timestamp": {
            "kind": "datetime",
            "from": "2022-01-01",
            "to": "2023-12-31",
            "description": "Timestamp of when the action was performed."
          }
        }
      }
    },
    "structure": "single-table",
    "traits": [
      "nullable",
      "timestamped",
      "categorical"
    ],
    "analysisQuestions": [
      "What types of actions are most commonly performed by users?",
      "How does the frequency of file backups change over time?",
      "What compression profiles are preferred for archiving different file types?"
    ],
    "suggestedQueries": [
      {
        "title": "Count of Actions by Type",
        "sql": "SELECT action, COUNT(*) FROM archival_management GROUP BY action;",
        "dialect": "postgres"
      },
      {
        "title": "Daily Backup Frequency",
        "sql": "SELECT DATE(timestamp) AS date, COUNT(*) AS backup_count FROM archival_management WHERE action = 'backup' GROUP BY date ORDER BY date;",
        "dialect": "postgres"
      },
      {
        "title": "Most Common Compression Profiles",
        "sql": "SELECT compression_profile, COUNT(*) FROM archival_management WHERE action = 'compress' GROUP BY compression_profile;",
        "dialect": "postgres"
      },
      {
        "title": "User Actions Over Time",
        "sql": "SELECT DATE(timestamp) AS date, action, COUNT(*) FROM archival_management GROUP BY date, action ORDER BY date;",
        "dialect": "postgres"
      }
    ],
    "usageScenarios": [
      {
        "title": "ETL Pipeline Development",
        "body": "Data engineers can use this dataset to build and test ETL pipelines, ensuring that data is correctly extracted from the archival management system, transformed to meet business needs, and loaded into data warehouses for analysis. The variety of user actions and timestamps provides a realistic scenario for pipeline validation."
      },
      {
        "title": "Teaching Data Analysis",
        "body": "Educators can leverage this dataset in classroom settings to teach students about data analysis techniques, particularly in the context of government operations. Students can practice querying, aggregating, and visualizing data, learning valuable skills that apply to real-world archival management."
      },
      {
        "title": "Process Improvement Analysis",
        "body": "Government officials and analysts can utilize this dataset to identify trends in archival management activities, enabling them to assess the efficiency of current processes. By analyzing the frequency and types of actions, they can make informed decisions about resource allocation and process improvements."
      }
    ]
  },
  "counts": {
    "archival_management": 500
  },
  "stats": {
    "archival_management": {
      "rows": 500,
      "columns": {
        "id": {
          "nulls": 0,
          "distinct": 500,
          "min": 1,
          "max": 500
        },
        "user_id": {
          "nulls": 0,
          "distinct": 97,
          "min": 1,
          "max": 100
        },
        "action": {
          "nulls": 0,
          "distinct": 4,
          "min": "backup",
          "max": "extract"
        },
        "file_name": {
          "nulls": 0,
          "distinct": 381
        },
        "compression_profile": {
          "nulls": 42,
          "distinct": 3,
          "min": "high",
          "max": "standard"
        },
        "comment": {
          "nulls": 50,
          "distinct": 447
        },
        "timestamp": {
          "nulls": 0,
          "distinct": 500,
          "min": "2022-01-02 07:43:05",
          "max": "2023-12-27 18:55:25"
        }
      }
    }
  },
  "artifacts": [
    {
      "file": "csv/archival_management.csv",
      "format": "csv",
      "table": "archival_management",
      "key": "datasets/archival-management-insights/v2/csv/archival_management.csv",
      "url": "https://database-sample-website.s3.eu-north-1.amazonaws.com/datasets/archival-management-insights/v2/csv/archival_management.csv",
      "bytes": 55819,
      "sha256": "14f3505f16531d11af3b7e6ef20a610d7ad40aede4e72407a69a7cb0f4faba7a",
      "rows": 500,
      "contentType": "text/csv; charset=utf-8"
    },
    {
      "file": "archival-management-insights.json",
      "format": "json",
      "table": null,
      "key": "datasets/archival-management-insights/v2/archival-management-insights.json",
      "url": "https://database-sample-website.s3.eu-north-1.amazonaws.com/datasets/archival-management-insights/v2/archival-management-insights.json",
      "bytes": 134292,
      "sha256": "31116c2f42d98bed431332cf9812cd1bd3009d680f609bf8345585777d8c6d7c",
      "rows": null,
      "contentType": "application/json; charset=utf-8"
    },
    {
      "file": "sql/postgres.sql",
      "format": "sql-postgres",
      "table": null,
      "key": "datasets/archival-management-insights/v2/sql/postgres.sql",
      "url": "https://database-sample-website.s3.eu-north-1.amazonaws.com/datasets/archival-management-insights/v2/sql/postgres.sql",
      "bytes": 67871,
      "sha256": "0546cad971495b9216811777736a824be6d33ba2a898b42881640aa18c01b892",
      "rows": null,
      "contentType": "application/sql; charset=utf-8"
    },
    {
      "file": "sql/mysql.sql",
      "format": "sql-mysql",
      "table": null,
      "key": "datasets/archival-management-insights/v2/sql/mysql.sql",
      "url": "https://database-sample-website.s3.eu-north-1.amazonaws.com/datasets/archival-management-insights/v2/sql/mysql.sql",
      "bytes": 67745,
      "sha256": "a04b9070ebbacaa9664e06d5c692580383be73f20475d9088c6aca18b8765a44",
      "rows": null,
      "contentType": "application/sql; charset=utf-8"
    },
    {
      "file": "sql/mssql.sql",
      "format": "sql-mssql",
      "table": null,
      "key": "datasets/archival-management-insights/v2/sql/mssql.sql",
      "url": "https://database-sample-website.s3.eu-north-1.amazonaws.com/datasets/archival-management-insights/v2/sql/mssql.sql",
      "bytes": 70249,
      "sha256": "bb2d99586dd303e50c559ae960feb4626516657807e8c1d7a98f52ba962ff1a9",
      "rows": null,
      "contentType": "application/sql; charset=utf-8"
    },
    {
      "file": "sql/sqlite.sql",
      "format": "sql-sqlite",
      "table": null,
      "key": "datasets/archival-management-insights/v2/sql/sqlite.sql",
      "url": "https://database-sample-website.s3.eu-north-1.amazonaws.com/datasets/archival-management-insights/v2/sql/sqlite.sql",
      "bytes": 67709,
      "sha256": "978332b7ec9eb51c62553509a13656250d6ec59edf36f0aafb177742cf8c9b90",
      "rows": null,
      "contentType": "application/sql; charset=utf-8"
    },
    {
      "file": "prisma/seed.ts",
      "format": "prisma-seed",
      "table": null,
      "key": "datasets/archival-management-insights/v2/prisma/seed.ts",
      "url": "https://database-sample-website.s3.eu-north-1.amazonaws.com/datasets/archival-management-insights/v2/prisma/seed.ts",
      "bytes": 114528,
      "sha256": "41e1521a53e1b493f2ad5271767a07a177252cdfcf5ac567fa99c3a3a6f231ae",
      "rows": null,
      "contentType": "application/typescript; charset=utf-8"
    },
    {
      "file": "django/fixtures.json",
      "format": "django-fixture",
      "table": null,
      "key": "datasets/archival-management-insights/v2/django/fixtures.json",
      "url": "https://database-sample-website.s3.eu-north-1.amazonaws.com/datasets/archival-management-insights/v2/django/fixtures.json",
      "bytes": 162261,
      "sha256": "8423f513fb467e08b94ff75fa2c891404bb254c1dc346a3705a3529a3106ab37",
      "rows": null,
      "contentType": "application/json; charset=utf-8"
    }
  ],
  "publishedAt": 1788766079125,
  "updatedAt": 1788777515354
}