Data model of RED FLAGS

Input data

Notice tabs on TED

Tab ID Notice tab Visible when Contains
0 Current language CL differs from OL very few translated parts of notice
1 Original language everytime whole original notice
2 Summary CL differs from OL mix of previous two
3 Data everytime notice metadata in CL
4 Document family min. 2 notices in family links and very few metadata of notices in family

(CL = current language set on the website, OL = original language of the notice)

Data model (memory)

Data classes and field names in Red Flags engine follow the information structure and terminology found on TED.

You can find the model classes in the following packages:

The most important class is Notice. It contains fields that represent the chapters of a notice. The type definitions of these fields are located in model.noticeparts package:

Also there is Data class for the Data tab, which contains a field for each table row.

Other classes in model package are representing data types:

Document families are not managed in separate classes, a document family ID is stored in Notice objects instead. The document family ID is the ID of the first notice of the family.

See them in details here: Data classes

Database schema

It is only relevant if you are using MySQLExporter and db=1 in your configuration (details).

The database schema is made based on the model classes described above, however there are some differences. A lot of tables include a noticeId field to connect the records to the appropriate notice, and N-M like relations are stored in one table called te_relationdescriptor.

Tables detailed: