Startup code for first assignment in Databaskonstruktion
Find a file
Zion Martincich 4171fe0b70 Redundant Modification
Update README.md

Create DataModel Info.md

testing a way to handel data info with .md idk what i am realy doing
2026-09-08 13:44:58 +02:00
Assets SQL Datasystem + Readme Fix 2026-09-08 13:43:51 +02:00
Code SQL Datasystem + Readme Fix 2026-09-08 13:43:51 +02:00
DataModel Info.md Redundant Modification 2026-09-08 13:44:58 +02:00
DataModel.jpg Datamodel 2026-09-08 13:44:49 +02:00
ER_diagram.svg SQL Datasystem + Readme Fix 2026-09-08 13:43:51 +02:00
LICENSE Initial commit 2026-08-31 15:21:23 +00:00
README.md SQL Datasystem + Readme Fix 2026-09-08 13:43:51 +02:00

Overview

I was appointed to Group B, which handles the "Desinformatör" class. For this, we needed to gather all the information that can be found regarding that class from the documentation: https://his.instructure.com/courses/9943

ER model

The following diagram shows the modified version of the EER Schema that can be found in Fig 1 from the documentation.

ER or EER Model

Relations

Agent(name, nr, Lön, unamn, kommentarer)

Disinfo(name, Rate, Specialite, Kampanj)

Incident(Nr, Name, Gata, Plats)

Operation(Kodnmt, Startdatum, Slutdatum, SR, Kommentar)

Kampanj(Nr, Name, SR, Startdatum, Slutdatum, kommentar)

Undanflukter(Title, Typ, Halt, Rate)

Requirements

A few lines containing a general description of the requirements

Desinfo

  • A disinformation spreader may not work on more than five campaigns at the same time

  • The number of completed campaigns and the percentage of successful campaigns must be calculable

  • The disinformation spreader can read and create rows in the campaign and pretext tables

Incident / Observation

  • When a disinformation spreader is assigned to an incident, this must appear directly in the interface

  • The disinformation spreader can read all information about observations and incidents that have occurred

  • The disinformation spreader can see all observations for an incident and the trustworthiness of the people who reported them

Campaign

  • Start date and end date must be set; the end date must be later than the start date

  • A campaign can be ongoing but must have a start date

  • If the gap between the start and end date is more than five weeks, the length is automatically set to five weeks

  • Success rate is stored as an integer

Pretext

  • A campaign may contain at most three different pretexts

  • A single incident may use at most ten different pretexts across its campaigns

  • Truthfulness must be between 0.1% and 95%

  • When a pretext is no longer referenced by any campaign, it is removed from the database

Behold my work

MrBeholder