National Security Administrator
This document describes the tasks a National Security Administrator can perform through the E2 Web Application.

Version History
Version
Date
Description
E2 release
0.3
30/09/24
ECCAIRS2 National Security Administrator’s task.pdf .pdf
v2.40
0.4
20/11/2025
Migrated ECCAIRS2 National Security Administrator’s task.pdf  to BookStack, incorporating structural adjustments for web-native documentation. Reviewed and updated introduction section.
v2.40

Terms and abbreviations
Term/Abbreviation
Description
API
Application Programming Interface
BO
Batch Operation
CSV
Comma-separated values
ECCAIRS
European Co-ordination Centre for Aircraft Incident Reporting Systems
E2
ECCAIRS 2
ECR
European Central Repository
ERCS
European Risk Classification Scheme
NAA
National Aviation Authority
M2M
Machine-to-Machine, automated exchange of data between systems without human intervention
OC
Occurrence
OR
Original Report
PDF
Portable Document Format
SIA
Safety Investigation Authority
SR
Safety Recommendation
VR
Validated Report
WT
Word Template
XLS
Excel Spreadsheet
XML
Extensible Markup Language
XSD
XML Schema Definition
For each entity or attribute in the taxonomy, you can find its definition with detailed information, an explanation, and possible values in the Taxonomy Browser.

Table of Contents
Table of Contents
Version History
Terms and abbreviations
1. Introduction & Accessing
1.1. Introduction
1.2. Accessing ECCAIRS 2
1.3. Sign in
1.4. Reset Password
2. Home
3. Data Management
3.1. Queries
3.2.Libraries
3.3 Batch operations
3.4. Batch operations groups
3.5. Word Templates
4. Taxonomy Browser
4.1. Introducion
4.2. View a Taxonomy
4.3. View Release Notes
4.4. Download XML
4.5. Download CSV and XSD files
4.6. Taxonomy Management
4.7. Set  Custom Taxonomy properties
4.8. Delete a Custom Taxonomy
4.9. Taxonomy version number and name
5. Views Management
5.1. Introduction
5.2. Sections
5.3. Views
5.4 Webforms
6. Administration
6.1. Administration menu
6.2. General Settings
6.3.  Roles and Permissions
6.4. Content Management
6.5. Others
7. My account
7.1. My account menu
7.2. Personal Details
7.3. Query-based notifications
7.4. Object-base notifications
7.5. Favourite View
7.6 Custom Column
7.7. Export by Atributte
7.8. Default Queries
8. ECCAIRS 2 Help

1. Introduction & Accessing

1.1. Introduction
ECCAIRS 2 is the European platform designed for the efficient and secure management of occurrence reports in the field of aviation. These reports are submitted to the system by reporters or organizations, such as airlines, maintenance organisations, or other aviation stakeholders. The collection, validation, and follow-up of reports are essential tasks that contribute directly to the continuous improvement of operational safety.
The process is primarily managed by Occurrence Officers from aviation Authorities of each country. To reduce manual workload, the system also allows for the automation of repetitive or large-scale tasks through batch operations. As a result, the system requires prior configuration and ongoing maintenance, which are handled by National Security Administrator.
This document describes all the tasks a National Security Administrator can perform through the ECCAIRS Web Application once logged in. It applies to National Aviation Authorities and Safety Investigation Authorities Administrators.
Tasks that can be performed by the National Security Administrator include:
Data Management:
Querys:
Create, edit, and share queries with conditions.
Integration with batch operations.
Batch Operations:
Automate actions on reports (e.g., update, share, process).
Schedule manual or continuous execution.
Word Templates: Export reports in Word format.
Taxonomy Management: Custom taxonomy management.
Views and Sections:
Create sections and views with attributes, images, and text.
Customize web forms for reporters.
Administration:
Manage organizations, groups, and users.
Set permissions, roles, and auto-filled attributes.
Set Notifications.
Migration of E5Z files (OC)
Upload and Validation of E5X files (OR)

1.2. Accessing ECCAIRS2
Follow these steps to access the Reporting Portal to Report an Occurrence:
 Go to E2 Central Hub homepage.
 Click on the 'Report an Occurrence' banner.
You will be redirected to the Reporting Portal homepage.
You can access the ECCAIRS 2 Web Application the  by clicking on 'SIGN IN TO ECCAIRS'.
If you do not yet have an account, contact your Authority  administrator to create a new one.

1.3. Sign in
Important notes
Correct Access URL
If you have created a shortcut to the URL https://api.aviationreporting.eu/idp/login, please be aware that this address points to the dedicated login server only. When accessed directly, the system does not know where to redirect the user after authentication, resulting in a failed or incomplete login process.
To ensure proper access and functionality, always use the official entry point:
Valid URL: https://e2.aviationreporting.eu
This address initiates the login flow correctly and allows the system to return you to the appropriate reporting environment after authentication.
Automatic Time Zone Configuration
For the time being it’s essential that your device’s time zone is set to automatic. If your local time doesn’t match the server time, the system may interpret your authentication token as expired—even if it was just generated.
How to ensure your time zone is set automatically:
On Windows: Go to Settings → Time & Language → Date & Time Enable:
“Set time automatically”
“Set time zone automatically”
On macOS: Go to System Preferences → Date & Time Check the box: “Set time zone automatically using current location”
On mobile devices (Android/iOS): Make sure “Automatic date & time” is enabled in your system settings.
This configuration ensures your access token remains valid and prevents login issues related to time synchronization.
Sign in
To sign in, please follow these steps: 
Visit the E2 Reporting Portal at https://e2.aviationreporting.eu/.
Click on 'SIGN IN TO ECCAIRS'. You will be redirected to the following page: 
Fill out your Username and Password.
Click on 'SIGN IN TO ECCAIRS'. The system will display the following page:
Please check your email. The system will send a one-time security code to the email address linked to your user account. The message will be sent from the address 'do-not-reply@aviationreporting.eu'.
Enter your security code and click 'SUBMIT'. You will be redirected to the 'Home' page. 

1.4. Reset Password
To reset your password if you've forgotten it, please follow these steps:
Visit the E2 Reporting Portal at https://e2.aviationreporting.eu/.
Click on 'SIGN IN TO ECCAIRS'. You will be redirected to the following page:
Click on the 'Forgot your password?' link and fill out your username (not your email):
Click 'RECOVER PASSWORD'. You will receive an email with instructions on how to recover the password. 
If you're already signed in, you can reset your password via your user icon:
Click 'Reset password' The system will display:
Fill-in the formular and click 'SUBMIT'.

2. Home (Landing page)
When the Administrator accesses the E2 Web Application or when navigating its sections and clicks on ‘Home’, the system displays the landing page:
 
On top of the page, in the right-side corner, the system displays the Administrator’s username and a bell with the number of unread notifications, if any, and a link to access the Help Desk:
 
Below the menus bar, the system displays filter buttons with the number of:
·        Original Reports: all OR-related notifications (N/A for Administrators)
·        Validated Reports: all VR-related notifications (N/A for Administrators)
·        Occurrences: all OC-related notifications (N/A for Administrators)
·        Safety Recommendations: all SR-related notifications (N/A for Administrators)
·        Sharing Notifications: all notifications related to elements (queries, libraries or word templates) shared with the Administrator
Below those buttons, the system displays the list of notifications:
 
By default, the list only includes the unread notifications, including:
·        The query-based notifications the Administrator has defined for the Authority
·        The Administrator defines the query-based notifications through ‘My account’. See Query-based notifications for further details on these notifications.
 The Administrator can update the results through the ‘All’, ‘Read’ and ‘Unread’ tabs above the list.
The Administrator can also restrict the results through the filter buttons mentioned above.
Each notification of the list is divided into columns:
·        A check box: to select the specific notification.
·        Mail and delete icon: if the mail is open, it is read so the icon can mark it as ‘unread’; if close, it is unread, so the icon can mark it as ‘read’. The delete icon deletes the notification after a confirmation message.
·        Type: All, OR, VR, OC, safety recommendations, queries, libraries or word templates. In the case of an Administrator, only All, queries, libraries or word templates apply.
·        Action: The options are All, creation, update, deletion, and shared. The action dropdown menu can filter it. In the case of Administrator, only All and shared applies.
·        Notification: it summarises the notified action, i.e. John Smith has shared a new word template named ‘Word Template 1’ with you. Click here to open it. 
·        Origin: it provides the author of the notified action.
·        Date: apart from the date of the notified action, it includes a filter to search based on the date.
Above the list of notifications, the system displays the following tabs:
 
After selecting the specific notification, the Administrator can click it to mark it as read, mark it as unread or delete the notification.
The Clear All button removes all the filters and shows the default list of notifications for the specific Administrator.

3. Data Management
This menu of the E2 portal includes queries, batch operations, batch operations groups and word templates.

3.1. Queries
Queries are a powerful tool the Officers can use to filter occurrences, validated reports and original reports through various stages in the E2. Also, safety recommendations should be made if the officer belongs to a Safety Investigation Authority.
 
3.1.1. Queries overview and Libraries tree view
In the Queries section, the Administrator can create queries, share them with other users or manage queries shared by other users with the Administrator.
The Administrator has to open the 'Data Management’ menu at the top of the page, then click on the 'Queries' option (Data Management > Queries). The system will display the Queries menu:
 
On the left panel, there is a view of the Libraries tree. It includes all the libraries available to the Administrator. Those are the folders that can have categories and subcategories. Find more information about these libraries in the Libraries section. The libraries available to the Administrator are: My Personal Libraries, the Local Common Library, the Common BO Library, the National Shared Library, and the Shared with Me Library. 
Administrators can click on the corresponding libraries, and the content will be displayed in the queries overview in the right panel.
On the Queries menu, Administrators will have all the folders available, but only the queries will be accessible to them, although the Libraries tree view is the same.
On the right, there will be the list of default Queries. It shows the first Library with the content of the Tree view, as seen in the image above. The list shows the corresponding folder or category of the library and below its subcategories if existing, and the queries.
The columns that also work as filters are the following:
·        Name: It shows the category, its subcategories, and the queries if they exist. Administrators can unfold the folders through the arrows.
·        The ‘BO’ column shows a green tick if the query is used in a batch operation. N/A for SRIS queries for the moment.
·        Author: it is the username of the author of the query
·        Date: Creation date.
·        ‘To Lobby’ column shows a green tick if the query can be exported to another environment and a red cross if it cannot be exported to another environment because it contains Custom Attributes.
3.1.2. Query builder - creation of a query
The Administrator can create queries in My Personal Libraries and the Local Common Library. The Administrator must click the 'New Query' button to create a new one in the selected library or folder. (This New Query button is unavailable when navigating through ‘Shared with me Libraries’ and ‘Lobby Libraries, whose queries can be executed and copied by Administrators but neither created nor edited nor deleted.) A new window will be displayed with the Query Builder:
 The Query Builder allows the Administrator to build queries to search original reports, validated reports, and occurrences or safety recommendations, depending on whether the Administrator’s Authority is a National Aviation Authority, a Safety Investigation Authority or both, with Attributes or metadata fields that meet the given conditions.
The queries are executed against the reports indexed in Elastic Search.
The Administrator has to fill in the unique Query Name for each Administrator query and select a Library, category or subcategory where to store the query. See the Libraries section for more information.
Before executing, exporting or saving a query from the query builder, it is required to select over which reports the query will be executed on the ‘Count Number of Items’ section:
ECCAIRS queries (based on ECCAIRS Taxonomy)
 
They will be activated as soon as the mandatory fields of the query are filled.
·        Original Reports
·        Validated Reports
·        Occurrences
·        Occurrence shared with me: Occurrences shared by other Authorities with my Authority.
·        Occurrence + Shared: My major occurrences and the ones shared by other Authorities with my Authority
·        ECR: All occurrences shared with the ECR by my own and other Authorities. 
 
SRIS queries (based on SRIS Taxonomy)
 
They will be activated as soon as the mandatory fields of the query are filled.
·        Safety Recommendations 
·        ECR: All safety recommendations shared with the ECR by mine and other Authorities. 
3.1.3. Query conditions – Attributes and metadata
Once in the Query Builder, the Administrator has to select the query parameters to set each rule by clicking on ‘Select Attribute’ under the ‘Conditions’ section.
 
The system will display a modal window where the Administrator can choose between:
For ECCAIRS queries (based on ECCAIRS Taxonomy)
·        Attributes: Any of the Attributes available for the Administrator’s Authority Taxonomy:
 
·        Metadata: additional information found at the database level that can be relevant for the Administrator to query by:
 
ü  e2id – E2 identificator
ü  Audit fields – they refer to the information of the specific version of the report
o         au_creation_date
o         au_creation_user
o         au_modification_date
o         au_modification_user
ü  blocked – it is set to TRUE when a batch operation blocks the report to prevent the users from editing it
ü  has_automatic_changes – it is set to TRUE when the report has had any automatic changes, coming from the OR, that no Administrator has acknowledged yet
ü  has_conflicts – it is set to NOT NULL if the report (VR or OC) has any conflicts coming from an OR update
ü  last_shared_ecr – it determines the last time the OC was shared with the ECR
ü  organisation name – the name of the Organisation of the reporter, if applicable
ü  personal_details – it is set to NOT NULL if there is any personal information from the reporter.
ü  receiving__date – it determines when the OR was sent to the Authority.
ü  reporting_entity_id – id of the reporting Entity 
ü  reporting_method – what reporting method was chosen to report the OR 
ü  responsible_entities_id –  Authority to which the report belongs.
ü  Status – the report status
ü  Version – version number
SRIS queries (based on SRIS Taxonomy)
·        Attributes: Any of the Attributes available for the Officer’s Authority Taxonomy:
 
·        Metadata: additional information found at the database level that can be relevant for the Officer to query by:
 
ü  e2id – E2 identifier of SRs
ü  Audit fields – they refer to the information of the specific version of the report:
o         au_creation_date: the date when the report has been created
o         au_creation_user: user who has created the report
o         au_modification_date: the last date the report was updated
o         au_modification_user: the previous user to update the report
ü  blocked – it is set to TRUE when the report is blocked to prevent the users from editing it
ü  last_shared_ecr – it determines the last time the SR was shared with the ECR
ü  responsible_entities_id – id of the responsible Entity (Authority in E2)
ü  status – the report status
ü  Version – version number
3.1.4.  Query structure
The queries are made at least by one rule in a group. A rule is a condition the search made by the query has to meet. 
Queries can also include various rules and or groups of rules. A query can include one or more existing queries (subqueries). 
A rule contains a condition to be met concerning an Attribute or metadata field. Layouts and operators vary depending on the Attribute and metadata field type, i.e.:
If the Administrator selects Air temperature as an Attribute, the system will display ‘Value’ as the only possible selectable layout and the Select operator filter:
 
This will also generate a ‘Decimals’ field to be filled out by the Administrator.
Attributes
·        Alphanumeric and Text Attributes or metadata fields can be searched in documents by a complete word using the layout ‘Value (Word)’ or by a string of characters using the layout ‘Text’. i.e.:
ü  Value (Word) as in ‘Aircraft’ (complete word)
ü  Text begins with ‘Airc’ (a string of characters)
Data Type
Layout
Operators
Alphanumeric, Text
Value (Word)
equal
does not equal
in
not in
is null
is not null
Text
in
not in
begins with
does not begin with
ends with
does not end with
is null
is not null
·        Code Attributes can be searched in documents using layouts:
ü  Value: selecting one or more values of the Value List
ü  Level: when the Value List has more than one level, selecting all the values of a branch (level) in the Value List, starting from the selected value(s)
ü  Alias: when the Value List has alias(es), selecting one of them
Data Type
Layout
Operators
Code
Value
equal
does not equal
in
not in
is null
is not null
Level
* if the Value List has more than one level
equal
does not equal
in
not in
is null
is not null
Alias
* if the Value List has alias(es)
in
not in
begins with
does not begin with
ends with
does not end with
·        Code and Additional Text, Code or Alternative Text Attributes can be searched in documents using layouts:
ü  Value: selecting one or more values of the Value List
ü  Level: when the Value List has more than one level, selecting all the values of a branch in the Value List
ü  Alias: when the Value List has alias(es), select one of them.
ü  Text: typing a string of characters
Data Type
Layout
Operators
Code and Additional Text, Code or Alternative Text
Value
equal
does not equal
in
not in
is null
is not null
Level
* if the Value List has more than one level
equal
does not equal
in
not in
is null
is not null
Alias
* if the Value List has alias(es)
in
not in
begins with
does not begin with
ends with
does not end with
Text
Used to search in the Text part of the Attribute
in
not in
begins with
does not begin with
ends with
does not end with
is null
is not null
·        Date and DateTime Attributes can be searched in documents using layouts:
ü  Value: when searching by date or range of dates 
ü  Date of the Month (1-31): when searching by the day of the month
ü  Date of Week (1-7): when searching by the day of the week
ü  Month (1-12): when searching by the month
ü  Year: when searching by year
Data Type
Layout
Operators
Date, DateTime
Value
equal
does not equal
less than
less or equal
greater than
greater or equal
between
not between
Day of the Month (1-31)
equal
does not equal
less than
less or equal
greater than
greater or equal
between
not between
Day of Week (1-7)
equal
does not equal
less than
less or equal
greater than
greater or equal
between
not between
Month
equal
does not equal
less than
less or equal
greater than
greater or equal
between
not between
Year
equal
does not equal
less than
less or equal
greater than
greater or equal
between
not between
·        Time Attributes can be searched in documents using layouts:
ü  Value: when searching by hours and minutes
Data Type
Layout
Operators
Time
Value
equal
does not equal
less than
less or equal
greater than
greater or equal
between
not between
is null
is not null
·        Latitude and Longitude Attributes can be searched in documents using layouts:
ü  Value: when searching by degrees, minutes and seconds or range of them
Data Type
Layout
Operators
Latitude, Longitude
Value
equal
does not equal
less than
less or equal
greater than
greater or equal
between
not between
is null
is not null
·        Decimal Attributes can be searched in documents using layouts:
ü  Value: when searching by a decimal number
Data Type
Layout
Operators
Decimals
Value
equal
does not equal
less than
less or equal
greater than
greater or equal
between
not between
is null
is not null
·        Number Attributes can be searched in documents using layouts:
ü  Value: when searching by an integer number
Data Type
Layout
Operators
Number
Value
equal
does not equal
less than
less or equal
greater than
greater or equal
between
not between
is null
is not null
·        ECCAIRS Resource Locator Attributes can be searched in documents using layouts:
ü  File Name: When searching by the Name of an attached field
ü  Description: When searching by the description given in the attached field 
Data Type
Layout
Operators
ECCAIRS Resource Locator
File Name
equal
does not equal
in
not in
is null
is not null
Description
equal
does not equal
in
not in
is null
is not null
·        ECCAIRS Embedded data Attributes can be searched in documents using layouts:
ü  ECCAIRS number: when searching the former document's ECCAIRS number
Data Type
Layout
Operators
ECCAIRS Embedded Data
ECCAIRS number
in
not in
begins with
does not begin with
ends with
does not end with
is null
is not null
·        ECCAIRS Data link Attributes can be searched in documents using layouts:
ü  ECCAIRS number: when searching the former document's ECCAIRS number
Data Type
Layout
Operators
ECCAIRS Data Link
ECCAIRS number
in
not in
begins with
does not begin with
ends with
does not end with
is null
is not null
Groups can include one or more rules and one or more groups combined with AND/OR clauses. The Administrator must click the ‘Add Rule’ button to add more rules. For groups, on the ‘Group’ tab. If the Administrator wants different sets of rules to be evaluated together, the Administrator must click the 'Add group' button. The Administrator can also add groups to other groups.
Groups and rules can be rearranged, dragging and dropping them where needed.
At the top centre of each group are the OCCURRENCE/ENTITY alternative tabs, which show whether conditions of the given Attributes shall be met in any instance of the Entity or if the conditions shall be met in the same instance of the Entity. Thus, when specifying restrictions in a query, the restrictions can be evaluated across all the entities of a record at once OR can be assessed to each Entity of a record one by one. By default, the restrictions of a query will be evaluated across all the entities of a record at once, with the 'Occurrence' option selected by default. 
With the selector 'Occurrence/Entity', the Administrator can change that, and the restrictions will be evaluated Entity by Entity. There is a limitation in creating groups based on the restriction selected here. If a group is restricted to Entity, no more groups can be added inside that "Entity" group. 
Example of search by occurrence and by Entity: 
1.       OCCURRENCE: If we want to obtain the Occurrences where the Manufacturer model (21) is equal to ‘BOEING > 787’ and the Aircraft altitude (22) is greater than 1000 ft, independently if the conditions are met in different aircraft of an occurrence:
  
2.       ENTITY: If we want to obtain the Occurrences where the Manufacturer model (21) is equal to ‘BOEING > 787’ and the Aircraft altitude (22) is greater than 1000 ft when the conditions are met in the same aircraft.
 
The Administrator can set rules with AND/OR clauses and combine them as needed with groups by clicking on the ‘Group tab’ and selecting AND/OR clauses, i.e.:
 
Subqueries: The Administrator can add a subquery to the query through the ‘Query’ tab. The aim is to add an existing query available for the Administrator to the current query. When the Administrator clicks on the ‘Query’ tab, the system will display the subquery section:
 
The Administrator has to click on ‘Select Query’, and the system will display a window to select the subquery:
 
The Administrator must select a query from the available libraries and click ‘Add’. The system will add the subquery to the conditions of the current query.
3.1.5. Query action buttons
Once the query is completed, the following options are available:
·        Cancel button: the system will return to the Queries page.
·        Execute button: N/A to the Administrator unless they have the Officer’s role. 
·        Save button: The system will save the query in the list of queries of the selected library and display the table of queries with the new query on the queries page. 
·        Export button: N/A to the Administrators unless they have the Officer’s role.
3.1.6. Query Management
The Queries menu displays the table of queries of the corresponding Library, category or subcategory selected in the Libraries tree:
 
3.1.6.1.  Editing a query
Only Queries of ‘My Personal Libraries’ and ‘the Local Common library’ are editable for the Administrator. If a query is associated with a BO or query-based notification, it is not editable. In those cases, the query is visible through the ‘View button’ of the 3-dot menu or by double-clicking on the query on the table of queries.
The Administrator has to double-click on the specific editable query of the queries list or click on the ‘Edit’ option of the query’s 3-dot menu, and the system will display the editing page of the query:
 
The Administrator must introduce the needed update and click ‘Save’. See Query action buttons for further details.
This page also provides:
·        Elastic Query viewer button: it accesses the Elastic Query Viewer window as follows,
 
·        Query viewer button: it opens the query viewer window as follows,
 
3.1.6.2. Duplicating a query
All queries available to the Administrator, no matter the library or category, can be duplicated by the Administrator.
The Administrator has to click on the copy icon of the 3-dot menu of the specific query of the list of queries, and the system will display the ‘Copy Query’ window:
 It is like the editing page above but with the mandatory Library field empty. The Administrator has to fill in the Library field with a different Library than the original one, and then the Execute and Export button will be activated. The Save button does not work unless a Library is selected. The Administrator must introduce the needed update and click ‘Save’. See the Query action buttons section for further details.
3.1.6.3. Sharing a query
The Administrator can only share queries of ‘My Personal Libraries’. Only the queries not involved in a batch operation or a query-based notification can be shared.
The Administrator has to click on the ‘Share’ option of the 3-dot menu of the specific query of the list of queries, and the system will display the Share query window:
 
The Administrator has to select ‘Share to User’, and then the system will display the ‘Users’ tab below.
 
 The Administrator has to click on ‘Users’, and the system will display the Available Users section:
 
As long as there are available users, the Administrator can check the specific Users, click on the ‘ADD’ button, and then click the ‘Save’ button. 
The system will save the updates of the query in the database and return to the list of queries that will have added a Shared icon to the specific query:
 
The Administrator then can click on the ‘Edit share’ option that will be added to the 3-dot menu of that query and add more users or remove some of them.
3.1.6.4.  ‘To Lobby’ function
This functionality allows the Administrator to export the query to other E2 environments.
The Administrator can click on the ‘To Lobby’ option of the 3-dot menu of the specific query of the list of queries, and the system will display the ‘To Lobby’ window:
 
 
The Administrator has to fill in the mandatory Name and Description fields, select the Authorities of the environments displayed below and click on the ‘To Lobby’ button. The system returns to the queries menu and displays a message on the success of transferring the query to the specific Authority/ies Lobby library.
3.1.6.5. Deleting a query
Only My Personal Libraries and Local Common Libraries queries can be deleted by the Administrator.
They can only be deleted if not involved in a BO or query-based notification.
The Administrator has to click on the ‘Delete’ option of the specific query 3-dot menu of the list of queries. The system will delete it and update the table of queries accordingly.

3.2. Libraries
All information in this section concerning the creation and management of libraries applies to Queries, Word Templates, Batch operations, and Views. 
The system provides the Libraries available to the Administrator on the left panel of the menu:
3.2.1. My Personal Libraries
The objects stored in personal libraries are only available to the owner of the libraries. The owner can decide to share a particular object from the Personal libraries or share the complete library with other Authority users. Only users with permission to execute queries will be eligible. 
3.2.2. Local Common Library
The objects stored in the Local Common Library are available for all Authority users with permissions to that kind of object. Administrators can create queries in the Local Common Library.
3.2.3.  Shared with me libraries
When the library owner or object has shared it with the Administrator, they appear under these users' ‘Shared with me libraries’. They can execute the queries or copy them to their Personal Libraries but can neither edit nor delete those Libraries.
3.2.4. Lobby Libraries
They are the Libraries where the Administrator receives the objects transferred through the ‘To Lobby’ functionality. The Administrator can view and execute the queries or copy them to their personal libraries but can neither edit nor delete those Libraries.
3.2.5. Creation of a library
Once in the ‘Data management’ ‘Queries’ menu, the Administrator has to click on ‘New Library’, and the system will display a modal window to create the Library:
 
The Administrator has to fill in the mandatory Name field, the Description (if needed), and the Sharing mode, which can be ‘Personal’ or ‘Share to User’.
If ‘Share to User’ is selected, the system will display a section to identify the user/s with whom we wish to share the library:
 
The Administrator has to select the specific users through the check box and click the ‘Add’ button, which will be activated. The selected users will be available on the ‘Selected Users’ tab.
The Administrator has to click on ‘Save’ for both Personal or Shared to User, and the Library will be saved accordingly. It will appear in the left pane under ‘My Personal Libraries’ in the Libraries tree.
 
If the created library is ‘Shared to user’, it will show the ‘Shared’ icon 
. 
3.2.6. Library Management
The system provides Deletion, adding category, and editing buttons next to each library under My Personal Libraries of the Administrator.
 
 
3.2.6.1. Deleting a Library:
The Administrator can only delete the Libraries under My Personal Libraries.
The Administrator has to click on the Delete icon (rubbish) next to the specific Library, and the system will delete the library from the My Personal Libraries tree as long as it no longer has any queries; otherwise, the system will display a warning message and will not delete the library. The Libraries tree will be updated accordingly.
3.2.6.2. Adding a category or folder to a Library
The Administrator can only add a category to My Personal Libraries and the Local Common Library.
The Administrator has to click on the ‘+’ button next to the specific library, and the system will display a folder below the Library:
 
The Administrator has to type a Name and click on ‘Intro’:
 
The folder or category will be added to the tree and will be available to store queries of the Administrator:
 
Next to the folder or category, the management buttons will appear as follows:
 
The category can only be deleted if it does not include queries or word templates.
The ‘+’ button is to add subcategories. It works the same way as adding categories to the Library.
The edit button only updates the name, not the location of the category.
3.2.6.3. Editing a Library
The Administrator can edit the Libraries of My Personal Libraries and the Local Common Libraries.
The Administrator has to click on the editing (pencil) icon next to the specific Library, and the system will display the editing window:
 
This page is the same as the library creation window in the previous section. The Administrator must update the corresponding fields and click ‘Save’. The changes will be saved in the database and Libraries tree. 

3.3. Batch operations
With Batch Operations (BO), only available for National Aviation Authorities at present, the Administrator performs actions over the safety data automatically, in bulk, without needing to change each individual report. These are some examples of these actions:
·        Update, insert, delete Attribute
·        Share reports
·        Process Original reports, Validated reports, Occurrences in various forms and states
The Administrator manages the BOs through the BO menu of the Data management section:
 
The BO menu shows a left pane with the Libraries tree view, with the Local Common Library and its Common Batch Operation library where the BOs are stored and organised (in it and its subcategories).
Next to the Libraries tree, the system displays the table of BOs of the Common Batch Operation library. It can include subcategories divided into columns, which also work as filters:
·        Name: unique for each BO.
·        Enabled: a green tick shows if it is enabled. 
·        Status: drafted, released or archived. The status cannot be released as long as it has not been published.
·        Author: of the BO.
·        Date: of the creation of the BO.
Review the documentation on 'How to use MABOs' for more updated information on multiple action batch operations.
3.3.1. BO Management
3.3.1.1             Create a batch operation
Once the Administrator is in the BO menu, they must click on the ‘New Batch Operation’ button above the table of BOs.
The system displays the ‘New BO’ window:
 
The Administrator has to fill in the following fields:
·        Object type that can be OR, VR or OC
·        Name: that has to be unique
·        Library: it can be the Common Batch Operation library or its categories/subcategories.
·        Schedule: The Administrator has to select Manual or Continuous
ü  Manual: The action defined in the batch operation will be applied to the documents that meet the conditions expressed in the query of that manual batch operation when the BO is executed. 
When selected, the system will display the ‘Undo toggle’ deactivated. The Administrator can leave it like that or activate it so that the system will display the ‘Minutes’ field. The Administrator has to fill it in.
 
The ‘Minutes’ field sets the time the Administrator has to undo the execution of the BO’s grace period during which the action executed by the batch operation can be undone. 
Manual batch operations can be based on queries with ‘Ask me later’ rules. When the ‘Undo’ is set and the BO saved, the ‘Undo toggle’ is disabled from the 3-dot menu.
ü  Continuous: These are executed automatically every time a document is saved and meet the conditions expressed in the query of the continuous batch operation. One or more continuous batch operations can be triggered when the document being saved meets the conditions of each of the queries of these batch operations. In that case, they are executed in alphabetic order. In continuous batch operations, it is not possible to define a grace period during which the action can be undone and cannot be based on queries with the ‘Ask me later’ rule.
·        Query: The Administrator must select among the queries in the selected library.
·        Actions: Generally, batch operations actions are only applied over unlocked documents in Status=Open. 
The possible actions that a batch operation can execute depend on the object type (report): 
Document Type
 
Possible Actions
Preconditions to execute BO
Document status
Document version
OR
Process original report to validated
OPEN
Minor
VR
Integrate into occurrence
OPEN
Minor
Insert, Update, Delete, Copy, Move, Merge Attributes
OPEN
Minor
OC
Share document to ECR
OPEN
Minor, Major
Make a major version
OPEN
Minor
Make a major version & Share it with ECR
OPEN
Minor
Share the document with Authorities
OPEN
Minor, Major
Make a major version & Share with Authorities
OPEN
Minor
Unshare occurrence
OPEN
Minor, Major
Insert, Update, Delete, Copy, Move, Merge Attributes
OPEN
Minor, Major
Also, on the BO creation page, the Actions selection provides the following options:
For ORs: The Administrator will select the ‘Process as a validated report’ in the Actions menu:
 
For VRs: 
·        Concerning reports: Integrate into OC. 
The Administrator selects it, and the system will display the similarity check toggle:
 
If the system does not find OCs similar to the VRs resulting from executing the BO query, the system will integrate those VRs into new OCs. 
If the system finds similar OCs, then the system will not apply the action when the BO is executed. VRs will not be integrated into OCs.
 ·        Concerning Attributes: The Administrator has to select between Insert, Update, Delete, Copy or Move Attributes.
ü  Insert Attribute: The Administrator selects this option, and the system will display an ‘ADD’ button to select an Attribute:
 
The Administrator clicks on the ADD button, and the system will display the Taxonomy browser with all the Attributes available for the Administrator:
 
The Administrator must select the Attribute and click the ‘Confirm’ button.
When it is selected, the system will display it below the action field and will present, next to it, a field or fields to complete. In the example, a Code and Additional Text Attribute with a ‘Select Attribute value’ ADD button. This field is mandatory unless the ‘Ask me later’ check box is ticked.
 
The Administrator must click the ‘ADD’ button or check the ‘Ask later’ check box. 
The ADD button opens the Select Attribute value window that will display selectable Attributes of the same item of the Attribute previously selected (source):
 
The Administrator has to select only an Attribute and click the Confirm button. The system will add the selected value to the Action section of the BO:
 
Below it, there will be an optional ‘additional text’ field. The ‘Selected Value’ field or fields displayed by the system match the previously selected Attribute and vary depending on that previously selected Attribute.
When executing the BO, the selected Attribute and its value will be inserted into the chosen VRs. 
If Administrators check the ‘Ask later’ option instead of filling in the value when executing the BO, the system will prompt the user for the needed information.
Once the Attribute has been selected, the system allows the Administrator to add a condition through the ‘Action condition’ toggle that will display the Selected Attribute field:
 
The Administrator will have to select an Attribute through the ADD button. The list of Attributes will come from the same Entity as the previously selected Attribute to be inserted. The Select Layout and Select Operator menus are filled as in the section Query conditions - Attributes and metadata. 
ü  Update Attribute: It is to update an Attribute value of the VR. The Administrator selects the ‘Update Attribute’ on the Actions menu, and the system will display the ‘Select Attribute’ ADD button. The function is similar to the ‘Insert Attribute, ' with the only difference being in the result; when executing the BO, the system will update the value of the selected Attribute.
ü  Delete Attribute: This action deletes an Attribute of the VR. The Administrator selects this option in the Actions menu, and the system will display the ‘Select Attribute’ ADD button. The system adds the selected Attribute. When executing this BO, the system will delete the selected Attribute from the VRs that meet the requirements of the BO.
ü  Copy Attribute: The Administrator clicks on ‘Copy Attribute’ on the Actions menu of the BO window, and the system displays the mandatory Original field and Target field sections:
 
The Administrator has to click on the ADD ‘Select Attribute’ button of the Original field, and the system will display the Taxonomy browser where to select the Attribute to be copied.
Once selected, the Administrator has to click on ‘Select Attribute’ in the Target field section, and it will display a list of Attributes of the same Entity as one of the Original field Attributes.
 
The Administrator will select the specific Attribute and click on the ‘Confirm’ button that is enabled when the Attribute is selected.
The system will display the ‘Mismatch information’ section, warning on the different sizes of the selected Attributes of the original and target fields, which can impact the success of the execution of the BO:
 
Below it, the system displays the following mandatory menus:
If it exists, the selectable values are:
o         Replace: This means that if the original field Attribute exists in the VRs and meets the requirements of the BO, the system will replace it with the target field.
o         Skip: This means that if the original field Attribute exists in the VRs that meet the requirements of the BO, the system will not apply the selected action to those BOs.
o         Do not replace it with NULL: If the original field Attribute in the VRs meets the requirements of the BO, the system will not replace the Attribute's value with null.
If it does not exist, the selectable values for this option are:
o         Replace: This means that if the original field Attribute does not exist in the VRs meeting the requirements of the BO, the system will replace it with the target field.
o         Skip: This means that if the Original field Attribute does not exist in the VRs meeting the requirements of the BO, the system will not apply the selected action to those BOs.
o         Do not replace it with NULL: If the Original field Attribute does not exist in the VRs meeting the requirements of the BO, the system will not replace the Attribute's value with null.
ü  Move Attributes: this option moves the selected Attribute value to another Attribute of the same Entity. Thus, the Administrator has to select ‘Move Attribute’ on the Actions menu of the BO window, and the system will enable the ADD Select Attribute button. This works in the same way as the Copy Attribute option with the difference that it always replaces the Target field Attribute with the Original field Attribute, so there are options for when it exists and when it does not:
  
So, when the BO is executed, the original field is replaced with the target field.
ü  Merge Attributes: this option allows to merge two attributes into one. The restriction that applies is that both attributes must be the same datatype. Depending on the datatype selected the options are as detailed in the following table:
Datatype
Options to merge
Target Field
Notes
Latitude and Longitude
N/A
N/A
Excluded from this action. Not possible to merge them.
Text
Text + Text attributes
Separator field is not mandatory and will have maximum 5 characters
Second attribute selected to merge.
Any other text attribute.
If length of the merge exceeds the characters allowed in Target field, the string will be cut from the end until reduce it enough
Number and Decimal
Add (+), subtract (-), multiply (*), divide (/)
Can be between two fields or a constant field
Cannot be neither of the two fields used in the BO Action
System will ignore a division by 0.
Constant field can be any number (negative inclusive)
Date (between two dates)
Subtract operator only. Date 1 - Date 2
Any Numerical or String type
Result can be negative
Date (between one date and a constant)
Add or subtract operators available.
 
Can be a custom attribute
Constant field can be any number (negative inclusive)
DateTime (between two dates)
Subtract operator only. Date 1 - Date 2
Cannot be neither of the two fields used in the BO Action
String type attributes only
Result can be negative
DateTime (between one date and a constant)
Add or subtract operators available
Must be a DateTime or String attribute
Can be a custom attribute
Ignore the seconds.
No round ups (11:00:59 is 11:00)
Constant field can be any number (negative inclusive)
Time
Add or subtract operators available
Cannot be neither of the two fields used in the BO Action
String type attributes only
 
·        Email notification toggle: if activated, it sends an email with the result of the execution of the BO.
For OCs:
·        Concerning Reports:
ü  Share document to ECR: this option displays this window:
 
The Administrator has to decide if including the attachments through the ‘Include Attachments’ toggle is deactivated by default.
The Deidentify Attributes toggle opens a window to select the specific Attributes to be de-identified when the report is shared. The Administrator updates the Sharing settings and clicks on ‘Share’. When the Administrator executes the BO, the system will share the executed query's results with the ECR once all the mandatory fields are filled out. This action only works with OCs in the major version.
o         Make a major version: This action will make the OCs meet the results of the BO query and turn it into a major version. This option only works on Open and not blocked OCs.
o         Make a major version and Share it with ECR: it is the mix of the two previous options; it makes a major version and shares it with ECR. Therefore, it applies to open (not blocked) OCs. Once selected in the menu, the system displays the Share to ECR window as in the Share to ECR option explained before.
o         Share with Authorities: this option applies only to open, not blocked, major OCs to be shared with Authorities. It opens this window:
 
It works similarly to Share to ECR, but the Administrator has to select the specific Authorities by clicking on the Authorities drop-down menu:
 
If appropriate, the Administrator must update the Attachments, de-identify Attributes, and click the ‘Share’ button. The selected Authorities will be set in the Actions field. When the Administrator executes this BO, the system will make major the OCs meeting the requirements of the query of the BO and will share them as long as they can be subject to turning into major (open and not blocked).
o         Unshare Occurrence: This action is to unshare OCs that have been shared with ECR or Authorities. Once the Administrator selects this option in the Actions menu, when the BO is saved and executed, the system will unshare all the OCs meeting the requirements of the query triggered through this BO as long as they are shared.
The status of the BO is ‘Draft’ as long as it is not saved.
Once the Administrator has filled all the mandatory fields, you must now click on the ‘Save’ button:
 
The system will save the new BO in the database and the table of BOs:
 
3.3.1.2. Edit a batch operation   
The Administrator has to double-click on the Name of the BO in the list of BOs or click on the ‘Edit BO’ option of the 3-dot menu of the list of BOs:
 
The system displays the Edit BO window:
 
The Administrator has to update the necessary fields, leaving all the mandatory fields with content, and click the ‘Save’ button. The system will save the updates in the database, and the BO will be updated accordingly.
3.3.1.3. Copy a batch operation
The Administrator has to click on the ‘Copy BO’ option of the 3-dot menu of the BO at the table of BOs, and the system will display the Copy BO window:
 
It is similar to the Edit BO page, but the Name field is empty; all the fields are completed except the Name. The Administrator has to fill in the Name field and can update any of the other fields. Then, the Administrator has to click on ‘Save’.
The BO will be saved in the database with the new name and the other updates, if any. The system will return to the table of BOs, which will be updated accordingly.
The BO will be saved in the Draft version. Draft BOs can be edited, published, copied and deleted.
3.3.1.4. Publish a batch operation
Only draft BOs can be published. The Administrator has to click on ‘Publish BO’ at the 3-dot menu of the specific draft BO of the list, and the system will turn the status of the BO to ‘Released’, and the BO will be published. 
The list of BOs will be updated by marking the ‘Enabled’ section of the corresponding BO with a green tick.
Once a BO is published, it can be disabled through the ‘Disable’ option of its 3-dot menu at the list of BO.
3.3.1.5. Disable a batch operation
Only published BOs can be disabled. The ‘Disable’ option will be available for this BO in the 3-dot menu of the list of BOs. The Administrator has to click on it, and the BO will be disabled. 
The list of BOs will be updated, with the green tick removed from the ‘Enabled’ section of the corresponding BO.
Once the BO is disabled, if it is manual, it cannot be executed; if continuous, it stops being executed. It will only be re-executed if it has the enabled status.
3.3.1.6. Enable a batch operation
Only disabled BOs can be enabled. The ‘Enable’ option will be available for these BOs in the 3-dot menu of the list of BOs. 
The list of BOs will be updated by marking the ‘Enabled’ section of the corresponding BO with a green tick.
The Administrator has to click on it, and the BO will be enabled. Once the BO is enabled, if manual, it can be executed again; if continuous, it will be continuously executed.
3.3.1.7. Archive a batch operation
Only BOs that are not draft status can be archived. The Administrator has to click on the ‘Archive’ option of the 3-dot menu of the BO at the list of BOs, and the system will archive the BO. The status will turn to ‘Archived’ in the list of BOs.
The archived BOs can be viewed, copied, and deleted but are neither edited nor published.
3.3.1.8. Manual execution
The execute option is available in the 3-dot menu of the BOs of the list only for manual and published BOs. The Administrator has to click on the option, and the system will execute the BO. 
If the query of the BO has an ‘Ask later’ field, the system will display a window to fill in the field of the query:
 
The ‘Execute query’ button will be enabled once the empty field is filled.
The system will display a message indicating if the execution was a success. If no records or only a few records meet the BO's requirements, the user will be prompted to proceed.
If the execution was a success or if the Administrator confirmed the execution after a message, then the Administrator has to click on the View results option of the 3-dot menu of that BO at the list of results, and the system will display the BO results page:
 
It shows the table of results of the execution in the current month. There are tabs to access the last month, last 6 months or Custom (where the Administrator can set the period).
The table provides the following information per column that can be used as filters:
·        User Name: the author of the execution
·        Execution Name: the system generates a unique name for each execution result, joining the Name of the BO and a correlative number
·        BO Type: if manual or continuous
·        Status: 
ü  Processed OK
ü  Processed with errors: the results file will depict the errors
ü  In Progress: the execution has not finished yet
ü  Cancelled: BO was cancelled
ü  Undo completed: the BO was completely undone
ü  In the grace period (for manual BOs with the Undo toggle activated), the BO can be undone.
ü  Created: the BO was just requested to be executed
ü  Undo in progress: the Undo process is taking place. Once it is completed, the BO is undone.
·        Number of records processed: number of records processed through the BO.
·        Number of records not processed: The number of records did not meet the BO's requirements, so the query's action was not applied to them.
·        Started date time: of the execution.
·        Finished date time: of the execution.
·        Results: it provides a download icon to download an xls file with the results of the execution:
 
Or:
 
The results file explains the number of records processed and not processed and the reasons for this. It indicates the affected reports.
The results of the specific manual BO will also be available through the Execution results page of the BO menu. See further details in the Execution results page section.
3.3.1.9.   Continuous execution
The continuous BO are executed all the time; they are not applied over stored reports meeting the requirements of the BO, but over the updates of reports or new reports when saved. 
The results of these BOs can be accessed through the view results option of the specific BO of the 3-dot menu of the list of BOs or the Execution results page in the following section.
3.3.1.10.  Execution results page
The BO menu provides an Execution results button above the list of BOs:
 
The Administrator button clicks on it, and the system displays the Execution results page:
 
The table includes all the executions performed by the Administrator. The function is the same as that described form. See it for further details.

3.4. Batch operation groups
Batch Operations groups are composed of manual BOs that execute one after the other and can be scheduled daily, weekly or monthly overnight.
The Data management section provides a BO group menu:
 
It provides a table of BO groups with the following columns per each BO group row:
·        Name: unique for each one
·        Description: This field is optional
·        Enabled: if it is already activated (green tick) or not (empty=disabled)
·        Schedule: it can be daily, weekly or monthly
Above the table of BO groups, the system displays the ‘New BO group’ button.
3.4.1. BO Group Management
3.4.1.1. Create a batch operation group
The system clicks on the ‘New Batch Operation Group’ above the table of BO groups on the BO group menu page, and the system displays the ‘New Batch Operations Group’ window:
 
The Administrator has to fill in the mandatory fields:
·        Name: unique for each BO group
·        Schedule: it can be daily, weekly or monthly. The Administrator has to select one of them to enable the BO group once all the mandatory fields are complete.
·        Available BOs: This is the table of BOs available for the group; they must be enabled, released, and manually BOs. They also have to provide any result when being manually executed.
Moreover, Administrators can fill out the optional Description field.
The Administrator has to activate the ‘Enabled’ toggle if appropriate. The Administrator has to select the specific BOs displayed on the ‘Selected BOs’ pane and click the ‘Save’ button.
The system will save the data in the database and add the saved BO group to the list of BO groups.
The system will trigger, if enabled, the created BO group with the selected schedule during the nights.
3.4.1.2. Edit a batch operation group
The Administrator has to click on the Edit option of the 3-dot menu of the specific BO group at the list of BO groups, and the system will display the ‘Update BO group’ page:
 
The Administrator must update the fields and click the ‘Save’ button. The system will save the update in the database, and the table of BO groups will be updated accordingly.
3.4.1.3             Delete a batch operation group
The Administrator has to click on the Delete option of the 3-dot menu of the specific BO group in the list of BO groups. The system will delete the BO group from the database, and the table of BO groups will be updated accordingly. The table will no longer display the deleted record.

3.5. Word Templates
Officers use Word Templates in ECCAIRS2 to export reports in Word format. The Word template has to include the complete path of the Attributes according to the Authority’s released Taxonomy so that the system can fill each template field with the Attribute's corresponding value in the report.
Each table in the Word Template corresponds to an Entity in the Taxonomy. i.e.:
 
The Word Template will have tags included in token « » with the following characteristics:
·        Attribute: A
·        Attribute Custom: AC
·        Entity: E
·        Separation token: .
·        ID: TaxonomyCode
Examples:
·        «E1.A1» -> ENTITY.1.ATTRIBUTE.1
·        «E1.E45.AC1» -> ENTITY.1.ENTITY.45.ATTRIBUTES_CUSTOM.1
Depending on the Attribute data type, it should be indicated what part of the Attribute will be included in the Word Template:
Attribute Data Type
Field
Example
Date, Time, Text, Alphanumeric, Number
content (default)
«E1.A1»
Code
content (default)
«E1.A1»
Code and Additional Text
content (default)
additionalText
«E1.A1»
«E1.A1.additionalText»
Code or Alternative Text
content (default)
alternativeText
«E1.A1»
«E1.A1.alternativeText»
Decimal
content (default)
unit
«E1.A1»
«E1.A1.unit»
ECCAIRS Resource Locator
filename (default)
description
«E1.A1»
«E1.A1.description»
ECCAIRS Embedded Data
eccairsNumber (default)
«E1.A1»
ECCAIRS Data Link
eccairsNumber (default)
«E1.A1»
Latitude & Longitude
 
«E1.A1.degree»
«E1.A1.minutes»
«E1.A1.seconds»
«E1.A1.direction»
Once the Word template is configured, the Administrator can save it into E2 libraries. This is the second menu of Data management:
 
It shares the Libraries tree with the Queries menu and the option to create and manage Libraries and categories. All information in the section Libraries is also applicable here concerning the creation and management of the libraries.
3.5.1. Word Template Management
3.5.1.1. Create a Word Template
The Administrator can create a Word Template (from now on WT) within ‘My Personal Libraries’ and ‘The Local Common Library’.
The Administrator has to select the specific Library or category, click on ‘New WT’ on top of the page, and the system will display a modal window to create it:
 
The Administrator has to fill in the Name that has to be different from the existing ones, upload the needed word file to the Template section through the ‘Select file’ button or drag and drop it to the section and select a Library, a category or a subcategory.
The description field is optional.
Then, the Administrator has to click on the ‘Save’ button. The system will save the WT in the database, return to the WTs page, and add the specific WT to the table of WTs.
 
The saved WT will be available to the officers in the export options for the reports in Word format. Management of the Word Templates
The WT table is divided into columns that can also work as filters:
·        Name: unique for each WT
·        Author: it will be the Administrator
·        Date: Creation date
In the final section of each WT row, there is a 3-dot menu.
3.5.1.2. Edit a Word Template
The Administrator has to double-click on the Name of the specific WT of the list of WTs or click on the ‘Edit’ option of the 3-dot menu of the WT on the list, and the system will display the Edit window:
 
The Name field cannot be updated; only the other fields of the WT, including the library, can be updated.
The Administrator has to update the corresponding fields, leave the mandatory fields filled, and click ‘Save’. The system will save the updates in the database and return to the WT menu with the updated list of WTs.
3.5.1.3. Copy a Word Template
This option allows you to copy the Word templates.
The Administrator has to click on the ‘Copy’ option of the 3-dot menu of the WT on the list, and the system will display the Copy WT window:
 
The management of this window is the same as the editing option above, with the only difference being that the Name field can be updated, and the Administrator can select a different Library than the one where the WT was stored before.
3.5.1.4. Share a Word Template
The Administrator has to click on the ‘Share’ option of the 3-dot menu of the WT on the list, and the system will display the Share WT window: 
 
This option works the same way as the ‘Share a query’ in the Query Management section, with the only difference being what is shared.
3.5.1.5. Download a Word Template
The Administrator has to click on the ‘Share’ option of the 3-dot menu of the WT on the list of WTs, and the system will download the WT.
3.5.1.6. Delete a Word Template
The Administrator has to click on the ‘Delete’ option of the 3-dot menu of the WT on the list of WTs, and the system will delete it from the database and update the list of WTs accordingly.

4. Taxonomy

4.1. Introduction
The E2 system is built around the ECCAIRS Taxonomy, constituted by ADREP Taxonomy + ECCAIRS/EU specific Taxonomy. While most of it is centrally maintained, per specific governance through the NA’s established Data and Quality Working Group, there is also the possibility for Authorities to maintain their own Custom Taxonomy, which allows them to adapt their usage of E2 to their own processes. The same applies to the SRIS Taxonomy for safety recommendations.
To access the Taxonomies, the National Security Administrator has to access the Taxonomy menu.
 The system will display the list of Taxonomies in force for the Authority of the National Security Administrator. It includes the Custom and Central Taxonomies released and ECCAIRS and SRIS Taxonomies depending on the Authority type (NAA, SIA or both).
 
National Security Administrators can filter ‘All’, ECCAIRS and SRIs Taxonomies through the tabs displayed above the table.
The table of Taxonomies present the following columns that also work as filters:
·        Name: unique for each Taxonomy
·        Version: your digits separated by dots
·        Status: it can be:
ü  Archived
ü  Draft
ü  Released
·        Taxonomy Reference: it can be:
ü  ECCAIRS
ü  SRIS
·        Description
·        Release Date
·        Languages: for now, there are not translations
If the National Security Administrator has the National Taxonomy Administrator role, the list of Taxonomies will also include the Authority's Custom Taxonomies in all the status, if exist. 
The last section of each row provides a 3-dots menu with the following options for archived Taxonomies:
 
The Released Taxonomies provide the following options:
 
The Custom Project option is shown only if a Draft version of the Taxonomy does not exist. 
The Draft Taxonomies provide the following options:

4.2. View a Taxonomy
National Security Administrators have to click on the 3-dots menu ‘View' option and the system will display the Taxonomy Structure tab.
The Taxonomy tree and the search bar are displayed on the left side of the screen. They can be hidden by clicking on the 'arrow' icon. The left panel is resizable by clicking on the 3-dots menu and moving it to the left or to the right. 
The National Security Administrator can navigate through the tree by unfolding the arrows and clicking on the displayed elements. On the right side, the information of the selected element will be displayed.
 
Note that the View option only provides view menus and not editing or management options.
4.2.1. Search box
It is under the Structure Tab. The Value list tab and its navigation is explained in the Taxonomy Values Lists section.
Entities and Attributes can be found by typing the Taxonomy Code or the Description in the Search box. 
·        By Taxonomy Code:
 
·        By Description:
 
If the National Security Administrator clicks on the 'Advanced search' button, a layer with more filters will be displayed.  
 
For each filter the National Security Administrator can select as many values as needed. Then, the National Security Administrator has to click on the 'Search' button to refresh the tree with the introduced filters.
 
 
The Taxonomy tree can be ordered alphabetically by clicking on the 'A-Z' icon or 'Z-A' icon: 
 
All item of the Taxonomy tree can be collapsed and expanded through the following buttons: 
 
4.2.2. Filter the information
The National Security Administrators can filter the table of Parent Entities, Child Entities and Attributes by typing the term to be searched in the filter row. They can restrict the results by clicking on the '
 filter' button, by default 'contains' condition is selected. 
To delete the filter, the National Security Administrator has to click on the ' 
 clear filter' icon.
 
4.2.2.1             View detailed information
To view more information of the select Entity, the National Security Administrator has to click on the 'eye' icon.
 
To view more information about the Parent Entities, Child Entities or Attributes, the National Security Administrator has to click the 'eye' icon that appears while moving the mouse over the row.
 
A slide-in panel with the element information will be displayed when clicking on the' eye' icon. The National Security Administrator has to click outside the panel to close it and go back to the previous screen.
 
4.2.3. Taxonomy structure
ECCAIRS and SRIS Taxonomies have the same structure:
·        Entities
·        Attributes
·        Value Lists
·        Values
4.2.3.1. Entities
·        Entities are used to represent items to which a set of Attributes can be associated. 
·        An Entity can be, for example, the “Aircraft" involved in the incident-accident or the related “Events" description.
·        There may be multiple instances of an Entity since more than one of these items can be involved in an occurrence.
·        Entities may have child entities: “Engine" is child Entity of the “Aircraft" Entity.
·        Entities can be linked to other entities.
4.2.3.2.  Entities information
Entities in the Taxonomy tree are marked with 
 icon. When the Entity is a Linked Entity, it is also marked in green colour.
The following information will be displayed in the right side of the screen when the National Security Administrator clicks on an Entity in the Taxonomy tree:
·        Entity information: A brief summary of the selected Entity
·        Parent Entities: The list of its parent Entities
·        Child Entities: The list of its children Entities
·        Attributes. The list of its Attributes
The National Security Administrator have to click on each tab (Parent Entities, Child Entities, Attributes) to view its information.
 
4.2.3.3. Attributes
Attributes describe properties/values associated to an Entity. 
An Attribute of the “Aircraft” Entity is, for instance, its "manufacturer/model".
Attributes can have single or multiple values.
Attributes can be of the following types:
·        Number
·        Decimals
·        Text
·        Alphanumeric
·        Date
·        Time
·        DateTime
·        Longitude
·        Latitude
·        Code
·        Code and Additional Text
·        Code or Alternative Text
·        ECCAIRS Resource Locator
·        ECCAIRS Data Link
·        ECCAIRS Embedded Data
4.2.3.4. Attributes information
The Attributes are marked with 
 icon in the Taxonomy tree.
The National Security Administrator can view the information of an Attribute from two places in the Taxonomy Browser:
·        Finding it on the Taxonomy tree and clicking on it.
·        Selecting the Entity the Attribute belongs to and clicking on the 'Attribute' tab. The National Security Administrator will see all the Attributes of the selected Entity.
 
Click on the 'Eye' icon to view the detailed information.
·        Definition tab:
 
·        Values tab: 
If the Attribute has a predefined value List. In the Values tree, the National Security Administrator can navigate through the values by clicking on each element. The selected Value will display its definition and the Values can be searched by Taxonomy code or Description and ordered alphabetically.
4.2.4. Taxonomy Values Lists
The list of predefined values an Attribute can have is defined in a Value List. The Value List can have multiple level where values are organized in a tree mode. Value list can have Alias.
The National Security Administrator have to click on the Taxonomy Value Lists tab to obtain the list of Value Lists of the Taxonomy:
 
The table of Value Lists provides the following columns that also work as filters:
·        ID: it is the internal id automatically generated and unique for each Value List
·        Description: unique for each Value List and mandatory
·        Custom: for National Security Administrators it is always ’No’. Only Authorities can manage Custom Value Lists
·        Levels: number of levels of the Value List
·        Explanation: optional
·        Identifier: unique for each Value List which does not change with Taxonomy releases
The last section of each row provides a 3-dots menu with the options to be explained.
 
4.2.4.1. View a Value List
National Security Administrators have to click on ‘View Value List’ option of the 3-dots menu of the specific Value List and the system will display the View page:
 It displays the Value tree in the left panel according to the Value List levels.
National Security Administrators have to click on one of the Value of the Value tree and the system will show its details in the right panel:
Definition:
·        Value ID: identifier of the Value in the Value List. unique for each Value in the Value List which does not change with Taxonomy releases
·        Description: mandatory free text field
·        Detailed Description: mandatory free text field
·        XSD Tag: it reproduces the information of the Value ID
·        Domains: optional drop-down menu with the Domains to be selected
·        Special Value: drop-down menu with the following options:
·        Normal: Selected by default
·        None
·        Other
·        Unknown
·        Parent: it is not editable
Value Alias:
·        Alias: name of the Alias
·        Value: Alias value for the given Value
·        Default: Yes/No
4.2.4.2. View Value List Properties
National Security Administrators have to click on ‘View Value List Properties’ option of the 3-dots menu of the specific Value List and the system will display the View Value List Properties page:
 
It provides the following fields:
·        Identifier: unique for each Value List which does not change with Taxonomy releases
·        Description: name of the Value List
·        Detailed Description: optional free text field
·        Explanation: mandatory free text field
·        Levels: number of levels
·        Custom toggle: not applicable for Central Taxonomies Value Lists
Below the fields there is the Alias information with the structure for the table of Alias (Alias Name and Actions columns).

4.3. View Release Notes
It opens the Release Notes of the specific Taxonomy:   
The page provides the following tabs with the corresponding release notes:
·        Entities: added, changed and delete entities
·        Linked entities: added or delete links between entities
·        Attributes: added, changed and deleted Attributes
·        Value List: added, changed and deleted Value Lists
·        Values: added, changed and deleted values in Value Lists

4.4. Download XML
It downloads the Taxonomy in XML format.

4.5. Download CSV and XSD files
It downloads a zip of the Taxonomy in the selected formats.

4.6. Taxonomy Management
As mentioned, National Aviation Authorities and Safety Investigation Authorities can maintain their own Custom Taxonomy, which allows them to adapt their usage of E2 to their own processes.
4.6.1. Create a Custom Taxonomy
National Security Administrators have to click on ‘Custom Project’ option of the 3-dots menu of the specific Central released Taxonomy of the list, if a Custom released Taxonomy does not exist yet.
If a Custom released Taxonomy exists for the Authority, the 'Custom Project' option of the 3-dots menu will be available on it and the system will create a Draft version of that Custom Taxonomy where the changes can be done. 
 
 
Once created, the Draft version of the Custom Taxonomy will be displayed in the list of Taxonomies:
 
4.6.2.Taxonomy management - Structure
National Security Administrators have to click on ‘Edit Project’ option of the 3-dots menu of the specific Draft Custom Taxonomy of the list. The system will display the editing page:
 
At Authority level, only Custom Attributes and Custom Value Lists can be updated.
4.6.3. Attributes Management
National Security Administrators have to click on the Attributes tab of the specific Entity at the Entities information page, and the system will display the table of Central and Custom Attributes defined for that Entity:
 
Above the table, there is a ‘New Attribute’ button for the Authority to create new Custom Attributes.
The table of Attributes provides the following columns that also work as filters:
·        ID: automatically generated, mandatory and unique for each Attribute (Taxonomy code)
·        Description: unique for each Attribute and mandatory
·        Custom: if it is Custom Attribute, it will provide a green tick
·        Mandatory: it sets if the Attribute is Mandatory or Optional
·        Multiple Values: it sets if the Attribute is singled value, limited or multiple values
The last section of each row provides an Edit and a Delete icon.
4.6.3.1. Create a Custom Attribute:
National Security Administrators have to click on ‘New Attribute’ button above the table of Attributes and the system will display the New Attribute page:
 
National Security Administrators have to fill in at least the Description which is the only mandatory field.
XSD Tag and Type are empty and not editable.
The Taxonomy Reference, Domain and the Parent are automatically set and not editable.
The Custom Attribute field is not editable and is set to on by default.
The rest are optional or editable.
Definition Information:
·        Detailed: free text field
·        Explanation: free text field
·        Group: drop-down menu to select among the available groups
·        Personal Data toggle: deactivated by default. If activated, the Attribute corresponds to personal data
Instance information:
·        By default, Optional is set. National Security Administrators can update it to Mandatory.
·        Multiple Values: by default, Unlimited Values is set. National Security Administrators can update it to Single or Limited
Values Information:
·        Attribute Type: drop-down menu to select:
ü  Manual Entry
ü  Predefined Value List
·        Data Type: drop-down menu depending on the Attribute Type to select:
ü  Manual Entry
o         Alphanumeric
o         Date
o         DateTime
o         Decimals
o         Eccairs Data Link
o         Eccairs Embedded Data
o         Eccairs Reource Locator
o         Latitude
o         Longitude
o         Number
o         Text
o         Time
ü  Predefined Value List
o         Code
o         Code and Additional Text
o         Code or Alternative Text
·        Value List: name of the Value List to associate to Predefined Value List Custom Attributes. It can be a Value List of the Central Taxonomy or a Value List of the Custom Taxonomy
Advanced Properties Information:
·        For Manual Entry Attributes (depending on the data type):
ü  Case type:
o         None
o         Uppercase
o         Lowercase
o         ProperCase
o         FirstLetter
ü  Limit Low
ü  Limit High
ü  Input Mask
ü  Output Mask.
·        For Predefined Value List Attributes:
ü  Case type:
o         None
o         Uppercase
o         Lowercase
o         ProperCase
o         FirstLetter
National Security Administrators have to fill in the mandatory information and the needed optional information and click on ‘Save’ button. The system will save the Custom Attribute in the database and will add it to the Taxonomy browser of the Custom Taxonomy and to the table of Attributes of the specific Entity.
4.6.3.2. Edit a custom Attribute
National Security Administrators have to click on the Edit icon of the specific Custom Attribute of the table of Attributes of the Entity and the system will display the Edit Attribute page: 
 
It is like the previously explained New Attribute page with the addition of the ID, automatically generated and with the XSD Tag Generator button if the Attribute was created in the current Draft version of the Custom Taxonomy for the first time.
This button opens the following radio buttons:
 
·        Use Description: selected by default. It makes use the Description set for the Attribute to generate the XSD Tag.
·        Use Identifier: if selected, the XSD Tag is generated through a Taxonomy Code.
National Security Administrators can update the needed fields always leaving the mandatory information filled. Then, they have to click on the ‘Save’ button and the system will update the information in the database and in the table of Attributes.
National Security Administrators can edit Central Attributes only to provide an Alternative Text to its description which can be shown in the Views where it is indicated. For example, to translate the Attribute Description to the Authority's preferred language. 
4.6.3.3. Delete a Custom Attribute:
National Security Administrators have to click on Delete icon of the specific Custom Attribute at the table of Attributes and the system will display a warning message, if National Security Administrators confirm the action the Custom Attribute will be deleted from the database, from the table of Attributes and from the Taxonomy browser of the specific Custom Taxonomy.
Only Custom Attributes created in the Draft version of the Taxonomy can be completely deleted. If an Attribute already exists in a Custom Taxonomy that has been released or a Custom Taxonomy that is archived, it cannot be deleted but inactivated.
4.6.4. Taxonomy management – Value List
Once in the Draft version of the Custom Taxonomy, National Security Administrators can click on the Value List tab:
 
and the system will display the Value List tab with the table of Value lists:
 
Above the table there is a ‘New Value List’ button for the Authority to create new Custom Value Lists.
The table of Value Lists provides the following columns that also work as filters:
·        ID: it is the internal id automatically generated and unique for each Value List
·        Description: unique for each Value List and mandatory
·        Custom: (Yes) if it is a Custom Value List belonging to the Authority's Custom Taxonomy or (No) it the Value List belongs to the Central Taxonomy
·        Levels: number of levels of the Value List
·        Explanation: optional
·        Identifier: unique for each Value List which does not change with Taxonomy releases
The last section of each row provides a 3-dots menu with the options to be explained.
This section can provide a locker meaning the Value List is locked to an export process, it will not be unlocked unless a new version of the Value List is imported to the system or it is unlocked by the user who exported it and there is not an import process running.
4.6.4.1. Create a Custom Value List         
National Security Administrators have to click on ‘New Value List’ above the table of Value Lists (See image above) and the system will provide the New Value List page:
 
It provides the following fields:
·        Description: it is mandatory and has to be unique
·        Detailed Description: optional free text field
·        Explanation: mandatory free text field
·        Levels: number of levels. By default, the system sets 1 but it is editable to a max of 10 levels
·        Custom toggle: not editable for National Security Administrators and enabled
Below the fields there is the Alias information with the ‘Add Alias’ button and below the structure for the table of Alias (Alias Name and Actions columns).
National Security Administrators have to fill in the mandatory and the needed information, including the Aliases, if required. To add Aliases, National Security Administrators have to click on ‘Add Alias’ and the system will open the Alias drop-down menu:
 
It provides the Alias Support Table of the Administration menu. See section Support Tables for more details. National Security Administrator has to select an Alias and click on the Disk icon that will be enabled. The X icon is to discard the selection.
Once the Alias is selected, the Disk Save icon turns into a Delete icon:
 
National Security Administrators can repeat the operation as many times as needed. Then they have to click on ‘Save’ button and the system will save the Custom Value List in the database and will add it to the table of Value Lists.
4.6.4.2. Edit a Custom Value List
Only not locked Custom Value Lists can be edited. National Security Administrators have to click on ‘Edit Value List’ option of the 3-dots menu of the specific Custom Value List and the system will display the Edit Value List page:
 
National Security Administrators have to add Values to it through the New Value button. This button opens the Value information of the Custom Value List page:
 
It provides a Definition area with the following fields:
·        Value ID: numeric field and automatically generated but editable. If edited, XSD tag field, which is not editable and is based on the Value ID, will be updated with the same value
·        Description: mandatory free text field
·        Alternative description: which will be shown in the Views where it is indicated. Authorities can use this filed to translate the description of the value to another language.
·        Detailed Description: mandatory free text field
·        XSD Tag: not editable. It reproduces the information of the Value ID
·        Domains: not editable for Custom Value Lists
·        Special Value: drop-down menu with the following options:
ü  Normal: Selected by default
ü  None
ü  Other
ü  Unknown
·        Parent: it is not editable
It also provides a Value Alias area with the list of Aliases of the Value List, if exist:
 
National Security Administrators have to fill in the Value and check the ‘Default’ check box if needed.
If no Alias had been added to this Custom Value List, to add it, National Security Administrators have to do it through the ‘Set Value List Properties’ option of the 3-dots menu of the Custom Value List at the table of Value Lists. To be explained in later sections.
Once National Security Administrators have filled in the mandatory information and the needed information, the system saves the information in the database and updates the information of the Custom Value List and the table of Value Lists.
 
To Add more values, National Security Administrators have to click on the specific Value of the left pane and the ‘New Value’ button will be activated and the right panel will disappear.
 
Then National Security Administrators can click on ‘New Value’ to add another value.
National Security Administrators can update the editable information always keeping the mandatory information filled in and click on ‘Save’. The system will save the information in the database and will return to the table of Value Lists with the updated information.
National Security Administrators can edit Central Value Lists only to provide an Alternative Text to its values which can be shown in the Views where it is indicated. For example, to translate the Value Description to the Authority's preferred language. 
4.6.4.3. View a Value List
This option is only available in the 3-dots menu of the specific Custom Value List if it is locked or in the 3-dots menu of the specific Central Value List. National Security Administrators have to click on ‘View Value List’ option of the 3-dots menu and the system will display the View Value List page:
 
It is like the previously explained editing page but it is not editable.
4.6.4.4. Set Custom Value List Properties
National Security Administrators have to click on the Set Value List Properties option of the 3-dots menu of the table of Custom Value Lists and the system will display the Set Value List Properties page:
 
The page provides the same information as the New page plus an automatically generated Identifier. The functionality works in the same terms of the creation page previously explained. 
Note that if an Alias is removed from the list, the related values, if existing, will also be deleted.
National Security Administrators can update the needed fields always keeping the mandatory information field. Then they have to click on ‘Save’ button and the system will save the updates in the database and will update the table of Value Lists accordingly.
4.6.4.5. View Value List Properties
This option is only available in the 3-dots menu of the specific Custom Value List if the Value List is locked or in the 3-dots menu of the specific Central Value List. National Security Administrators have to click on ‘View Value List Properties’ option of the 3-dots menu and the system will display the View Value List Properties page.
It is like the Set Value List Properties page of the previous section but it is not editable.
4.6.4.6. Copy Value List
National Security Administrators have to click on the Copy Value List option of the 3-dots menu of the table of Value Lists and the system will display the Copy Value List page:
 
It reproduces the content of the specific Custom or Central Value List properties page and adds ‘COPY’ to the Description of the Custom Value List. National Security Administrators can update the needed fields always keeping the mandatory information filled and then they have to click on ‘Save’ button. The system will save the copied Custom Value List in the database and will add it to the table of Value Lists.
4.6.4.7.  Delete a Custom Value List
National Security Administrators have to click on the Delete Value List option of the 3-dots menu of the table of Value Lists and the system will display a warning message, National Security Administrators have to confirm the action and the system will delete the Custom Value List from the database.
A Value List cannot be deleted if it is being referenced in an Attribute.
National Security Administrator cannot delete Central Value Lists.
4.6.4.8. Export a Value List to Excel
National Security Administrators have to click on the Export Value List option of the 3-dots menu of the table of Value Lists and the system will display the following warning disclaimer:
 
If National Security Administrators accept, the system will download an Excel with the Value List information; at the same time, the Value List will be locked and the system will display a locker on this Value List at the table of Value Lists.
4.6.4.9. Import a Value List from Excel
National Security Administrators have to update the needed fields in the excel file of the previous section. When the file is ready, National Security Administrators have to click on the ‘Import from Excel’ option of the 3-dots menu of the specific Custom Value List at the table of Value Lists and the system will display a Select File window:
 
National Security Administrators have to upload the file to the window through the Select Files button or by dragging and dropping it. Then, they have to click on ‘Yes’ button. The system will display a warning message:
 
National Security Administrators have to confirm the action and the system will update the information of the Custom Value List in the database. This process can take some time so the system will send an email to the National Security Administrator when the process is finished.
National Security Administrators can use the export and import Value List options for Central Value List to update the Alternative Texts of the Values Description.
4.6.5. Review and correct inconsistencies and Release a Custom Taxonomy
National Security Administrators can check the inconsistencies of a Draft Custom Taxonomy through the Check inconsistencies icon placed on top of the Taxonomy manager:
 
This icon 
   reviews the inconsistencies, and the system will highlight in red in the Structure tab the items providing the inconsistencies, i.e.:
 
If there are inconsistencies in the Value List tab, it is also highlighted in red.
Once National Security Administrators find the inconsistencies and fix them, National Security Administrators can click on the Release icon:
 
This icon 
 publishes the Custom Taxonomy unless there are still inconsistencies, in that case, the system will display a message warning it.
Instead of through this icon, National Security Administrators can click on ‘Release’ option of the 3-dots menu of the Draft Custom Taxonomy of the list. This option publishes the Custom Taxonomy unless there are still inconsistencies, in that case, the system will display a message warning it.

4.7. Set Custom Taxonomy properties
National Security Administrators have to click on ‘Set Properties’ option of the 3-dots menu of the specific Not Archived Custom Taxonomy of the list. The system will display the specific Taxonomy Properties page:
 
The only editable fields are the following:
·        Name: it is mandatory and unique for each Taxonomy
·        Description: optional
National Security Administrators can update the fields and click on ‘Save’, the system will save the information in the database and the table of Taxonomies will be updated accordingly.

4.8.
Only Draft Custom Taxonomies can be deleted at Authority level. National Security Administrators have to click on ‘Delete’ option of the 3-dots menu of the specific Custom Taxonomy of the list and the system will display a warning message. National Security Administrators have to confirm the action and the system will delete the Custom Taxonomy from the database and from the table of Taxonomies.

4.9. Taxonomy version number and name
The Custom Taxonomy version and name is built as follows: 
·         ‘ECCAIRS Aviation’ string concatenated with:
·         Authority code - taken from the Authority details, followed by an underscore. i.e. BE_
·         Four-digit version code, which shows the Central Taxonomy version on which the Custom is based. i.e. 8.0.3.1
·         Custom version number, in parenthesis. E.g. (C1)
 

5. Views Management

5.1. Introduction
A View is a visual representation of ordered data (Attributes) concerning a safety event (accident or incident) to facilitate human analysis and its collection and introduction in a report. Views are groups of Topics placed in a particular sequence (hierarchical tree). 
The specific Views available depend on the particular Authority the E2 user is connected to and their user roles. 
Administrators can build Authority Views in E2. They can access the Views management through the ‘Views management’ menu displayed in the bar:
 
This menu is divided into Sections, Views and Webforms:

5.2. Sections
A section is a cohesive set of Attributes of the Central or Custom Taxonomy depicting a sub-domain of a safety event registered in an E2 report.
The Views consist of sections. As long as a section is associated with a view, the section cannot be edited.
Administrators can access and manage ‘Sections’ by clicking on ‘Sections’ of the ‘Views management’ menu (image above).
The system will display the Sections management page:
 
The Sections available to the Administrator are saved under the Local Common Library, Sections folder or its subfolders.
The table of sections displays the folder where Sections are stored and the following columns that also work as filters:
·         Name: unique for each Section
·         Taxonomy: The Administrator can only select the last released version
·         Based on Entity: it sets the Entity of the Taxonomy on which the section is based
·         View: the view to which it is associated
Above the table, there is a ‘New section’ button to create sections.
5.2.1. Section Management
5.2.1.1. Create a section
The Administrator can create a section through the ‘New Section’ button above the table of sections. The Administrator has to click on this button, and the system will display the Section page:
 
The mandatory fields are the following:
·         Type: ECCAIRS or SRIS, depending on the Authority type
·         Section Name: unique for each section
·         Taxonomy: it sets by default the last released version
·         Library: it sets the ‘Sections’ Library under the Local Common Library. If existing, it could be a subfolder of sections
·         Based on Entity: it displays the Taxonomy tree, so the Administrator has to select an Entity or sub-Entity
The not mandatory fields are only Description and Detailed, which is like a long Description.
The Administrator must fill in all the mandatory fields and click the ‘Save’ button.
The system will save the data in the database and display the new section in the list of sections.
5.2.1.2. Preview a section            
The Administrator has to click on the ‘Preview’ option of the 3-dot menu of the specific section, and the system will display the Preview page of that section:
 
The fields are not editable since it is a Preview page.
5.2.1.3. Copy a section  
The Administrator has to click on the ‘Copy’ option of the 3-dot menu of the specific section. The system will add a section to the table of sections with the same name + ‘Copy’, i.e., if the copied section is called ‘Custom’, the resulting section is called ‘Custom-Copy’; it will be identical to the copied section with the addition of ‘Copy’ in the name.
5.2.1.4. Edit a section
Only sections not being used in Views will provide the' Edit' option in the 3-dot menu of the table of sections.
The Administrator has to click on the ‘Edit Section’ option of the 3-dot menu of the specific section, and the system will display the ‘Edit’ page:
 
5.2.1.5. Layouts
The system displays the ‘Layout’ tab by default, where the Administrator has to select a number of columns (from one to four) or a table layout. The system will add as many sections in the different layouts as needed:
 
Above the added layouts, the system provides a ‘Title’ area with a configuration icon:
 
The Administrator can update it by clicking through the icon.
The system will display an Edit window:
 
The Based on Entity field will be filled in by default with the Entity in which the section is based.
By default, the Title field will be filled in with a copy of that Entity. This field will be editable by Administrators.
The Visible toggle will be activated by default. The Administrator can deactivate it and make it invisible.
Each one of the fields below the Title area can be updated through the configuration icon, as well as being moved or deleted:
 
The configuration icon displays an edit window where the Administrator can update the Based on Entity field. The entities provided in the Based on Entity drop-down menu are children of the Based on Entity of the current section. The Administrator can update the field and click on the Save button:
 
The rubbish icon deletes the specific field, and the Administrator can alter the order of the fields by clicking the arrows.
5.2.1.6. Element
The second tab of the Section preview page is the Elements tab. The Administrator can click on this tab next to the Layout tab, and the system displays: 
 
The Administrator can add a free text field, an image, or Attributes through this tab.
The Administrator has to drag the specific elements and drop them in the necessary fields individually.
Free text: When dropping it, the system will open a Free text window:
 
The user must fill it in with text and click on Save. Once saved, the system will display the Free text Attribute in the selected field:
 
Image: to add an image, the Administrator has to drag the ‘Image’ element to the specific field, and the system will open the upload image window:
 
The Administrator has to click on ‘Upload file’, and the system will open the image browser. The Administrator has to select an image and click on the Save button.
The system will add the image element to the selected field:
 
Attribute: The Administrator has to drag the ‘Attribute’ icon and drop it in the desired field. The system will open the Attribute window:
 
Therein, the Administrator has to fill in the 
·         Attribute: this drop-down menu provides the Attributes of the Entity of the section (Occurrence in this case)
·         Show as: depending on the selected Attribute datatype. This drop-down menu offers different options, i.e., combo box, radio button, tree-view, etc.
·         Mode: By default, the system provides ‘Definition+Value’, but Definition Only or Only Value instead can be selected
·         Show Desc.: This field does not appear when selecting the ‘Only Value’ Mode. When appearing, by default, it sets Short description, but the following are also available:
ü  Description
ü  Explanation
ü  Extended
·         Definition Label: By default, it sets ‘Left’, but the Administrator can also select ‘Top’
·         Tooltip: it is set by the system once the Attribute is selected; it includes the Attribute number, as referred to in the Taxonomy, and a Taxonomy definition that the Administrator can extend
·         Value check: By default, it sets ‘Optional’, meaning that filling this Attribute in the section is not mandatory. The Administrator can put ‘Required’ if the field is compulsory in the section.
Once the Administrator has filled in the mandatory fields, they have to click on the Save button, and the system saves the updates of the section in the database and returns to the ‘Edit section’ page in the Elements tab, including the selected Attribute in the chosen field.
 
The Administrator can click on the ‘Preview’ button above the tabs, and the system will display the Preview page for that section, with the layout and elements previously selected:
 
5.2.1.7. Edit properties of the section
The Administrator has to click on the ‘Edit Section properties’ option of the 3-dot menu of the specific section, and the system will display the Edit Section properties page:
 
All the fields are editable except the Taxonomy and the ‘Based on Entity’, which is the Entity selected through the section creation process. The Type can be chosen amongst ECCAIRS and SRIS only if the Authorities are dual (NAA and SIA).
The ‘Used in Views’ in the example is empty because this section is not associated with any view yet, but when used, this association is not editable through this page. The association is created through the ‘Views’ menu.
The Administrator must update the desired fields and click the ‘Save’ button. The system will save the database updates and update the table of sections accordingly.
5.2.1.8. Delete a section
The Administrator can only delete the sections if they are not used in a view.
The Administrator has to click on the ‘Delete’ option of the 3-dot menu of the specific section, and the system will display a confirmation message. Suppose the Administrator confirms the action and the section is not used. In that case, the system will be deleted from the database, a message will be displayed on the section deletion, and the section of the table of sections will be removed.

5.3. Views
Views are made of sections grouped into topics based on a Taxonomy Entity.
Views and Topics only change the way the data becomes visible. Reports created in any View can be looked at in any other View since the Attributes that contain the information are always shared.
The Administrator has to unfold Views management and click on ‘Views’, and the system will display the Views menu:
 
The left page shows the Libraries available to the Administrator:
The Central Common Library: it is an EASA ECCAIRS level library. The Authority’s Administrator cannot add views to this library, edit or delete them; only preview and copy them and view their properties.
Local Common Library: The views of this Library are available to Authority users with the correct privileges. The Administrator can create views in its View folder or subfolders and manage them: edit, delete, copy, and preview.
Lobby Library: They are the Libraries where the Administrator receives the Views (and queries) transferred through the ‘To Lobby’ functionality. Administrators can view, access the views, or copy them to the Local Common Library ( Views libraries, but neither edit nor delete them in the Lobby Library.
List of Views: The system displays in the centre of the page the table or list of Views, with the following columns per each view row working as filters:
·         Name: it is an internal term for a view. It is unique for each view
·         Display Name: it is unique and how it is displayed to the users of the E2 platform
·         Release number: it is composed of four groups of numbers
·         Status: can be Draft, Released or Archived
·         Webform: to which it is associated
·         Taxonomy reference: on which the view is built: ECCAIRS or SRIS Taxonomy;
·         Sections: the sections used in the view
·         To Lobby: if the view can be transferred to another environment or Authority.
Above the table, the system displays the ‘New View’ button.
5.3.1. Views Management
5.3.1.1. Create a view
The Administrator can create a View in the Local Common Library but not in the Lobby.
The Administrator has to click on the specific folder of the desired Library where to store the new view, click on ‘New View’ above the table of views, and the system will open the ‘New View’ page:
 
·         The type is ECCAIRS or SRIS, depending on the Taxonomy under which the View is built.
·         Taxonomy is always the last released version available for the Authority, and it is not an editable field.
·         View Name is an internal mandatory name the Administrator has to assign to the View. It is unique for each View.
·         Display Name: it is the mandatory Name of the View displayed by the platform to all users
·         Description: it is optional
·         Library: Mandatory field. Administrators can select Local Common Library locations.
·         Release Number: Mandatory. It is composed of four groups of numbers, all mandatory.
·         Status: Draft, Release and Archived are not eligible on the creation page
·         Use Alternative Texts toggle: To indicate that the alternative texts assigned to the Attributes and values in the Custom Taxonomy of the Authority will be used in the view
The Administrator has to fill in all the mandatory fields as needed.
Below the fields is the Roles table with all the available roles, where the Administrator has to select Create, Edit, and Read rights for the corresponding roles.
Once Administrators have selected the roles’ rights, they have to click the ‘Save’ button.
The system will save the data in the database and will add the new view to the table of views of the Views menu.
5.3.1.2. Edit a view
To edit a View, Administrators have to click on the ‘Edit View’ option of the 3-dot menu of the specific view at the table of Views. The system will display the ‘Edit View’ page:
 
·         On the left side, there is the 'Topic tree.'
·         On the right side, there is the Topic definition for ‘Occurrence’ (‘Recommendation’ for SRIS-based views) or the added topic in the Topic tree (see next section for further detail)
5.3.1.3. Edit the root topic
The root topic depends on the root Entity of the Taxonomy the View is based on:
·         ‘Occurrence’ for ECCAIRS Taxonomy
·         ‘Recommendation’ for SRIS Taxonomy
From now on, we will refer to ‘Occurrence’, but it also applies to ‘Recommendation’ topic.
The first topic, 'Occurrence', is editable on the left pane.          
 
 
Administrators must click the ‘ADD’ icon next to ‘Occurrence’, and the system will add a field below ‘All Sections’.
 Administrators have to introduce a Name and click on the OK icon. The system will add the topic to the left pane under the ‘Occurrence’ topic:
 
The topic will provide a Delete icon next to it. At the same time, the Topic Definition page will bring the created topic to the Name field (See image above).
On the right side of the screen, Administrators can edit the topic properties by changing the mandatory name and the identifier (optional field).
Update the icon
There are different predefined icons. You can select one through the icon selector:
 
Pattern Composer
When viewing a record, the text shown in the Topic tree results from executing the formula in the text-pattern associated with the topic when creating the view.
When creating a topic within a view, the text pattern used in the Topic tree can be constructed by clicking the 'Pattern Composer' button.
A new window to select Attribute property combinations will be displayed.
Administrators can add several elements and configure the way they are displayed.
Select and configure an Element (Show and Show as Description mandatory drop-down menus). Click on the 'Add element' button to add it to the Pattern Composer:
 
The Element will be added to the ‘Element List’ on the right side of the right panel:
Administrators can add as many elements as needed and can organise the way the elements are shown in the pattern by dragging and dropping them in the Elements list:
To edit or delete an existing element, click on the 'Edit' or 'Delete' button that appears while hovering:
 
When Administrators have added all the needed elements, they have to click on the ‘Save’ button below the list. The system will save the update in the database and will return to the Edit View page with the Taxonomy code of the selected elements on the ‘Text pattern’ field:
  
The composed pattern helps users fill in the information once the specific view is saved and published and the user accesses it, i.e., through a VR; when the user accesses the specific section when adding a sub-Entity, the system displays the available topics for the particular view:
 
After selecting it, the system will display the topic, and the chosen elements in the pattern composer will be available, so when filling them in, the topic's name will be added to the element information. i.e.:
 
Users have to fill in the fields, and the Aircraft topic will add the Attributes to the topic:
 
There is a delete icon to delete the information on the top right corner of the right corner.
Taxonomy
The Taxonomy area is below the Text Pattern, as shown below:
 
·         ‘Based on’: mandatory field to set the Entity in which the topic is based. For the ‘Occurrence’ topic, it is not editable. Administrators can select other entities at this drop-down menu when topics have been added in the left panel to ‘Occurrence’:
 
But the system will display a warning message:
 
·         Max instance: it sets the number of instances of the same Entity that can be included in the occurrence when using this view. Depending on the Entity selected, the system will set this field as:
ü  ‘Unlimited’ or ‘Maximum’: the number of instances the Entity can have based on what is defined in the Taxonomy.
ü  ‘At Most’: where Administrators have to fill in the maximum instances that can be included in the Entity when using this view.
·         Display mode: By default, it is ‘Tabs’, and Administrators can update it to ‘Lists’.
Add sections         
The area below the Taxonomy is ‘Sections’. The available sections depend on the Entity on which the topic is based:
 
Administrators can add or remove Sections to a View by dragging and dropping Sections between these 2 columns. The Administrator can also organise the order:
 
Administrators can also set the selected sections to the ‘Read Only’ version through the ‘Read Only’ toggle displayed next to each selected section.
Once all the mandatory fields are filled out, Administrators can click the ‘Save’ button below the selected sections.
The system will save the new topic in the database.
Administrators can preview the View through the ‘Preview’ button at the top of the Edit View page.
The added sections will be available in the left panel by unfolding ‘All Sections’:
  
5.3.1.4. Preview a view
Administrators must click on the ‘Preview’ option of the 3-dot menu of the specific view at the table of views. The system will display the Preview page of the selected view:
 
5.3.1.5.  Duplicate a view
Copying or duplicating a View generates an exact copy in the same Library and folder. The only difference is the new one has a ‘-copy’ reference in the name.
Administrators must click on the ‘Copy’ option of the 3-dot menu of the specific view at the table of views.
The system will generate the exact copy in the table of views with the same name + ‘-Copy’ added to it.
5.3.1.6. Publish a view
Administrators must click on the ‘Publish’ option of the 3-dot menu of the specific view at the table of views. The system will publish the view in the views menus of the E2 Web Application, such as the VR menu.
The Edit View menu will not be available in Published Views.
The Publish option of the 3-dot menu will turn into Unpublish for published view. This option will unpublish the specific view.
5.3.1.7. Transfer a view to Lobby
Administrators can transfer views to the Lobby Library if they are published and do not contain Custom Attributes. To do so, Administrators must click on the ‘To Lobby’ option in the 3-dot menu of the specific view in the table of views. The system will display the ‘To Lobby’ window, where to select the Authorities of the environments with which transfer the view:
 
 
Administrators must fill in the Name and Description fields and select the Authorities of the specific environments. Then, they have to click on ‘To Lobby’.
The system will save the update in the database and transfer the view to the Lobby library of the selected Authorities.
5.3.1.8. Archive a view
Only released views not being used by any role can be archived by the Administrator. Administrators must click on the ‘Archive’ option of the 3-dot menu of the specific view at the table of views. The system will archive the view accordingly.
When a view is archived, it is a good practice to unlink all the sections involved before archiving so the sections can be edited to be used in other views.
The Archive 3-dot option will turn into a ‘Restore’ 3-dot option that will reset the view.
5.3.1.9. Edit view properties
Administrators can edit the view properties through the ‘Edit View properties’ option of the specific View. This option opens the View Properties page:
 
This page is like the View creation page with the addition of the Navigation mode, where the system sets ‘Topic tree’ by default. Administrators can select ‘Table of content’ instead.
When the Table of Contents is selected, a configuration icon is displayed next to this tab. Administrators have to click on it, and the system will display the Table of Content Configuration window:
 
Administrators have to click the specific topics of the left column, which will appear in the right column:
 
Next to each selected topic, the system will display a Delete and an Edit icon:
 
The Delete button is used to delete the selected topic, and the Edit button allows the Administrator to choose a different name for the topic.
Once finished, Administrators will click on Save, and the system will return to the Edit Properties page.
 Administrators have to update the needed fields and click on ‘Save’.
The system will save the updates in the database, and the table of views will be updated accordingly.
5.3.1.10. Delete a view
Only views that are not being used by any role can be deleted. Administrators must click on the ‘Delete’ 3-dot option for the specific view in the table of views. The system will display a confirmation message. If Administrators confirm the action, the system will delete the view of the database and remove it from the table of views. If any role were using the view, the system would display a message explaining that deletion is impossible for that reason.

5.4. Webforms
Webforms are E2 platform digital forms available through which reporters of the E2 Web Application can introduce ORs. They are composed of Views.
Administrators can create, edit, view, publish and unpublish their views, and regarding ECCAIRS webforms, they can view, enable and disable them. Webforms cannot be deleted.
To access this menu, the Administrator has to unfold Views management at the E2 Web Application and click on ‘Webforms’, and the system will display the Webforms menu:
 
It displays the ‘All’ tab with all Webforms, including the Organisation and the Individual webforms. Next to it are the Organisation tab, with the list of Organisation webforms and the Individual tab, with the table of Individual webforms.
All the tables have the following columns, all working as filters except for the icon: 
·         Icon: unique for each webform.
·         Name: unique for each webform
·         Description: to describe the webform
·         View: that is associated with the webform
·         Usage: can be organisation or individual
·         Unregistered reporting: available for unregistered reporters
·         Enabled: green tick for enabled
·         Created by: the author of the webform, that can be ECCAIRS or the Authority Administrators
·         Created on: creation date
The last column has a 3-dot menu to manage each webform.
Administrators can alter the order in which the webforms appear in the Reporting Portal by dragging and dropping the rows in the Organisation and Individual tabs.
5.4.1. Webform Management
5.4.1.1. Create a new webform
Administrators have to click on the ‘New Webform’ button above the table, and the system will display the Webform creation page:
 
Administrators have to fill in the mandatory fields:
·         Icon: the drop-down menu provides all the available icons
·         Name: has to be different to the existing ones
·         View: the drop-down menu provides all the available views. Only views not used in other webforms can be selected and saved.
·         Usage: Administrators have to select Individual or Organisation Reporting if the webform is going to be addressed to individual reporters or Organisation reporters
·         Available for Unregistered Reporting toggle: deactivated by default. If activated, the webform will be available for non-registered reporters of the E2 Reporting Portal.
·         Status toggle: by default, it is disabled. If activated, it is enabled so when the webform is saved. The webform will be available in the E2 Reporting Portal to report ORs
The Description field is optional.
Once Administrators have filled out all mandatory fields, they have to click the ‘Save’ button. The system will save the new webform and add the webform to the ‘All’ table and the table of the selected usage, individual or organisation.
5.4.1.2. Edit a webform
Only disabled non-ECCAIRS’ webforms can be edited.
Administrators have to click on the ‘Edit webform’ option of the 3-dot menu of the specific webform of the table, and the system will display the ‘Edit webform’ page:
 
The function is the same as in the previous version. Once Administrators click the Save button, the system will save the update in the database and add the update to the webform tables.
5.4.1.3. View a webform
Administrators have to click on the View webform option of the 3-dot menu of the specific webform of the table, and the system will display the ‘View webform’ page:
 
It is similar to the previously described ‘Edit webform’ option. However, the fields are not editable, and it includes a ‘Preview’ button which accesses the webform as displayed in the E2 Reporting Portal when the users are filling it:
 

6. Administration

6.1 Administration menu
It is accessible through the navigation bar and includes the following menus:
 
·         General Settings
·         Accounts & Permissions
·         Content Management
·         Others

6.2. General Settings
6.2.1. Organisation Management
Organisations are defined locally by a user enrolled in the National Security Administrator role. When defining organisations, it can be assigned the webforms that will be used by that organisation when reporting ORs via the E2 Reporting Portal. It can also be determined through predefined Attributes automatically filling with the predefined value when the organisation's users create new ORs.
Administrators have to unfold ‘Administration’ and click on ‘Organisation Management’ under ‘General Settings’. The system will display the Organisation Management menu:
 
It displays a table of organisations with the following columns per Organisation row, which also work as filters:
·         Name: it is unique for each organisation
·         Phone: it is not mandatory
·         Created by: the Administrator that created the organisation 
·         Creation date: the date when the organisation was created in E2
The last column provides a delete and edit icon per each organisation, as follows:
 
Above the table, on the right side, there are the following buttons:
·         Import Organisations and Users
·         New Organisation
6.2.1.1. Create an organisation
Administrators have to click on ‘New Organisation’ above the table of organisations, and the system will display the ‘New Organisation’ page:
 
The mandatory fields are the following:
·         Organisation Name: it has to be unique for each organisation
·         Responsible NAA: the system sets the Authority to which the Administrator belongs. By default, it is not editable.
·         E5X: by default, it is ‘Allow Incremental E5X’. Administrators can select ‘Block E5X’ or ‘Allow Total E5X’ instead:
ü  Block E5X will not allow users of this organisation to import ORs through E5X files
ü  ‘Allow incremental E5X’ refers to importing all the versions of the ORs through the E5X; it means the first version of each OR and all their updates.
ü  ‘Allow Total E5X’ refers to import only the last version of the ORs
·         Username: it refers to the user that will be created when the organisation is created
·         First name: first name of the user that will be created when the organisation is created
·         Last name: first name of the user that will be created when the organisation is created
·         Email address: User email will be created when the organisation is created. Preferred language: by default, it is English, which is not editable.
The optional fields are the following:
·         Organisation Group: drop-down menu providing the organisation groups to be selected, if any
·         Phone: telephone number of the organisation
·         Responsible contact fields: all of them are optional. They are to contact the responsible of the organisation:
ü  Full name: it is referred to the responsible contact of the organisation
ü  Email address: it is referred to the responsible contact of the organisation
ü  Phone: telephone number of the responsible contact
·         User account fields: the following fields are optional:
ü  Description concerning the username
ü  Phone related to the user account
ü  Job Title
Administrators have to fill in the mandatory fields and click the ‘Save’ button. The system will save the data in the database, create a new organisation with the new user, and add it to the organisation's table.
The created organisational user will have the Reporter and Organisation Administrator roles assigned automatically.
6.2.1.2. Edit an organisation
Administrators have to click on the Edit icon of the specific organisation of the table of organisations, and the system will display the Edit organisation page: 
 
6.2.1.3. Detail tab
The page displays a Detail tab, which reproduces the Organisation creation page, with the addition of an Organisation ID, which is not editable by the system. See the previous section for further details on the fields.
Administrators can update the needed fields.
Moreover, it transforms the user accounts area with a table of accounts with the user accounts for the current organisation.
The table is preceded by a check box and the following columns that can be used as filters:
·         Username: of the account
·         Email: to which the account is associated
·         Organisation Name: as set in the creation page or later edited
·         Organisation ID: as generated by the system, it is unique for each organisation
·         Parent organisation: the organisation from which the organisation is child
·         Disabled: it shows a green tick if the account is disabled
·         Blocked: green tick if disabled
·         Deleted: green tick if deleted
·         Roles: by default, the system assigns the accounts created by Administrators to the Reporter organisation' Administrator role
·         Created by: the author of the account
·         Created on: date of the account’s creation
·         Last access on: date of last access to the account
The last section of the table per each row provides a 3-dot menu with Edit and Export options.
Above the table, there is a ‘Show Deletion Requests’ that shows, if existing, the accounts whose users have requested their deletion.
6.2.1.4. Add more account users to the Organisation
Administrators can add users through the ‘New user’ button above the accounts table.
This button opens the User account details page:
Administrators have to fill in the mandatory fields:
·         Username
·         First Name
·         Last Name
·         Email address
The ‘Disabled’ toggle will be activated and deactivated once the created user activates it through the email they receive after its creation.
The blocked toggle is deactivated; Administrators must activate it if needed to block the account.
Administrators can fill in the optional fields.
At the bottom of the page, the system displays a Roles table, where Administrators can select the roles for the user account. The available roles are Organisation Administrator, Organisation Autofilled Attributes and Reporter. Administrators can choose any one or both. They must fill in the mandatory fields and click the ‘Save’ button. The system will save the data in the database and add the account to the Edit Organisation page.
6.2.1.5. Edit a user account
Administrators can edit an account once on the Edit an Organisation page. They have to click on the abovementioned Edit option of the 3-dot menu of the specific account, and the system will display the Edit user account page:
 
It is the same page as the previous one (adding a user account) but already has the data filled in. 
Only the following fields will be editable:
·         Description
·         Disabled toggle
·         Blocked toggle
·         First Name
·         Last Name
·         Phone
·         Email Address
·         Job Title
·         Roles
Administrators can update the needed fields, always keeping the mandatory fields filled. 
Then, they have to click on the Save button, and the system will save the updates in the database, and the list of user accounts will be updated accordingly.
6.2.1.6. Export a user account
Individual export: Administrators have to click on the Export option of the 3-dot menu of the specific account at the table of accounts. The system will directly export it to an Excel (XLS) file.
Multiple export: Alternatively, administrators can select the checkboxes of specific accounts in the accounts table.
Administrators can also select all the accounts at a time by checking the check box on the left of the Username column.
 
 Then, they must click the Export icon above the table on the left.
 The system will directly export them to an XLS file.
6.2.1.7.   Webforms tab
Through this tab, administrators select the webforms available to the organisation’s users when accessing the E2 Reporting Portal, which is among the organisation's webforms defined at the Authority level.
Administrators have to click on the Webforms tab of the Edit Organisation page, and the system will display the Webforms tab:
 
The left panel displays the list of organisation webforms available, with a checkbox to be selected.
Administrators can check the needed webforms and click the ADD button in the middle of the page.
The selected webforms will be added to the right panel where Administrators can order them by dragging and dropping them as needed:
 
Then, Administrators have to click on the ‘Save’ button, and the webforms are saved for the specific organisation.
6.2.1.8. Autofilled Attributes tab
This tab is to help users when filling the webforms in the E2 Reporting Portal. Thus, it allows us to select Attributes and give them a value, so when users of that organisation are filling a webform, those Attributes are predefined.
Administrators have to click on the ‘Autofilled Attributes’ tab, and the system will display the ‘Autofilled Attributes’ page:
 
The left panel provides the ‘Available Attributes’ with the Taxonomy browser.
Administrators have to make a search through the filter or navigate through the tree to select specific Attributes. Administrators have to select the particular Attributes, one by one, and click on the ‘ADD’ button:
 
The system will transfer the Attribute to the right panel:
 
Each selected Attribute of the right panel will provide an Edit and a Delete icon.
To fill in the value, Administrators have to click on the edit icon, and the system will display a window to fill in the specific value:
 
The type of value to be provided by the system will depend on the specific Attribute data type.
In the case above, Administrators have to click on ‘Select Attribute Value’, and the system will open a Select Attribute value window:
 
Administrators have to select a value and click the ‘Confirm’ button. The system will display a window to save the value. The system will add the value to the selected Attribute in the right panel:
 
Then, Administrators have to click ‘Save’, and the system will add the selected Attributes to the specific organisation.
6.2.1.9. Delete an organisation
Administrators have to click on the Delete icon of the specific organisation on the table of organisations, and the system will display a confirmation message:
 
If Administrators confirm, the system will delete the organisation from the database and remove the organisation from the table of organisations. The users from the deleted organisation cannot report ORs anymore but the previously existing ones are kept and those already sent to the corresponding Authority can be manage by the Authority Officers, if they need it.
6.2.1.10. Import organisation and users
Administrators can import the organisation's and its users' data through the ‘Import Organisation & Users’ button above the table of organisations. This button opens the ‘Import Organisation & Users’ window:
 
Administrators must select Organisations or Users, and the ‘Download template’ option will be activated. Then, Administrators have to click on ‘Download template’, and the system will download an xls template, which Administrators have to fill in with the data of Organisations or Users depending on the selection. Once the template is filled, they have to upload it to the system through the ‘Select files’ button or by dragging and dropping it to the File area of the window:
 
Administrators must click the ‘Import’ button, and the Organisations or Users will be imported into the system, adding the imported data to its database.
6.2.2 Organisation Group management
Administrators can group organisations of the same type to assign them the same webforms or auto-filled Attributes.
When selecting this option, the following table is displayed:
 
It presents the table of Organisation Groups with the following columns that also work as filters:
·         Name: unique for each record
·         Description: it is optional
·         Organisations included: it has to include at least one organisation. The same organisation cannot belong to various groups.
·         Created by: the author of the group
·         Created on: the creation date
On the last column of each row, there is a Delete and Edit icon.
Above the table, the system displays the ‘New Organisation Group’ button.
6.2.2.1.  Create an Organisation Group
Administrators have to click on ‘New Organisation Group’ above the table, and the system will display the ‘New Organisation Group’ page:
 
The page provides the following fields:
·         Name: unique for each group and mandatory
·         Description: optional description of the group
·         The left panel has a table of organisations with two columns:
ü  Organisations: Organisations already associated with a group display a Group icon next to their name on the table
ü  Current Group, if existing
·         Right panel with a table of the selected organisations with the following columns:
ü  Selected Organisation.
ü  Current Group.
Administrators have to fill in at least the Name of the group and can click on ‘Save’ to save the group without organisations.
To create a group with associated organisations, apart from filling in the name, Administrators have to select through the check box the organisation/s needed, click on the ADD button, and they will be transferred to the table of organisations chosen:
 
When clicking on ‘ADD’, if any of the selected organisations have a predefined configuration, the system will display a confirmation message since, if it is confirmed, the predefined configuration will be lost for that organisation.
Administrators can remove the selected organisations from the right panel through the' REMOVE' button.
Administrators have to click the ‘Save’ button, and the system will save the data in the database. A new Organisation Group will be added to the Organisation Groups table.
Note that if any of the selected organisations already belongs to a group, when Administrators click on ‘Save’, the system will display a confirmation message since, if the information is saved, those organisations will be associated with the new group but not the previous group anymore; the association with the previous group will be removed.
6.2.2.2. Edit an Organisation Group
Administrators must click the Edit icon of the specific group in the Organisation Groups table. The system will display the Edit Organisation Group page:
 
The functioning of this page is like the Creation page described in the previous section. See it for further details. Administrators have to make the needed updates and click on the Save button. The system will save the updates in the database, and the table of Organisation Groups will be saved accordingly.
6.2.2.3. Delete an Organisation Group
Administrators click the Delete icon of the specific group in the Organisation Groups table. The system will delete the Organisation Group from the database.
6.2.3. Parent Organisation Management
The Parent Organisation is a concept to identify some organisations that supervise other organisations. They can be defined by a user enrolled on the National Security Administrator role at the Authority level.
Parent Organisation Management is the third option of the ‘Administration>General Settings’ menu:
 
It displays the table of Parent Organisations with the following columns also working as filters:
·         Name: unique for each record
·         Description: Optional
·         Organisations included: organisations associated with the parent organisation.
·         Created on: Creation date
·         Created by: the author (Administrator)
On the last section of each row, each record provides an Edit and Delete icon when hovering over the section.
Above the table, the system provides the ‘New Parent Organisation’ button.
6.2.3.1. Create a parent organisation
Administrators have to click on ‘New Parent Organisation’ above the table, and the system will display the ‘New Parent Organisation’ page:
 
The page provides the following fields:
·         Name: mandatory and unique for each parent organisation
·         Description: Optional
·         Responsible NAA: the system sets by default to which the current Administrator belongs. It is not editable
·         Responsible contact information:
ü  Full name: optional
ü  Email: Optional
ü  Phone: Optional
·         Organisations:
ü  The left panel shows a table of organisations in two columns:
o         The Organisation. Organisations associated with another parent organisation display an icon next to their name on the table.
o         The associated parent organisation, if existing.
ü  Right panel with a table of the selected organisations with the following columns:
o         Selected Organisation.
o         Current Group.
Administrators have to fill in at least the Name and can click on ‘Save’ to save the parent organisation without organisations associated with it.
To create a parent organisation with associated organisations, apart from filling in the name, Administrators have to select through the check box the organisation/s needed, click on the ADD button, and they will be transferred to the table of selected organisations:
 
When clicking on ‘ADD’ if any of the selected organisations have a predefined configuration, the system will display a confirmation message since, if it is confirmed, the predefined configuration will be lost for that organisation.
Administrators can remove the selected organisations from the right panel through the' REMOVE' button.
Administrators have to click the ‘Save’ button, and the system will save the data in the database. A new Parent Organisation will be added to the table of Parent Organisations.
Note that if any of the selected organisations already belongs to a parent, when Administrators click on ‘Save’, the system will display a confirmation message since if the information is saved, those organisations will be associated with the new parent organisation but not the previous parent anymore; the association with the previous parent organisation will be removed.
6.2.3.2. Edit a parent organisation
Administrators click the Edit icon on the last section of the row of the specific parent organisation of the table. The system will display the Edit parent organisation page:
 
Its functionality is the same as in the previous section. See it for further details. Administrators can update the needed fields and click the ‘Save’ button. The system will save the updates in the database, and the table of parent organisations will be updated accordingly.
6.2.4. Authority settings
In the fourth option of the Administration>General Settings menu, you can find the following settings:
 
The page provides the Authority settings of the current Administrator, including the Authority type, country, Authority code, and Region.
6.2.4.1. Settings tab
By default, the system displays the Settings tab below the Authority information with the following fields:
·         Reporting Portal:
ü  Own reporting system: disabled by default. It sets if the Authority has its own reporting system
ü  Registration required:  disabled by default. It determines whether or not the reporter's registration is required.
ü  Ensure backward compatibility with E5X (No/Yes), which is only available for Plan B Authorities. By default, it is enabled, ensuring compatibility with the Taxonomy 4.1.0.7.
·         Identificator Composer: it determines the pattern that the File Number will follow for all the reports automatically generated in the Authority:
ü  Administrators can customise it based on Attributes, text, dates or a sequence of numbers. They can also concatenate conditions to customize the File Number further based on their needs.
ü  In the Identificator text field, Administrators will preview the changes made in the Identificator composer edition section.
ü  By clicking the 
  'add' icon, Administrators can add as many conditions as needed.
ü  If you want to delete a condition, click the 
    ‘delete’ icon.
 
It must, at least, have an incremental number to guarantee the uniqueness of the file number.
·         User account: Disable after no activity period: Set, by default, at 90 days. Administrators can update it to another number of days.
Once the period is reached, the system will send an email to the user informing about the inactivation of the account giving him or her 14 days more to login into E2 before the user account is deactivated.
Once Administrators have filled in the tab as desired, they have to click on ‘Save’ before accessing the ‘Deidentify Attributes’ tab.
6.2.4.2. Deidentify Attributes tab
When sharing an occurrence or safety recommendation with other Authorities or the ECR, the Officers can de-identify Attributes.
The Administrator selects the Attributes that will potentially be deidentified through this tab.
The tab provides two panels:
 
On the left is the Taxonomy browser, where Administrators must select the Attributes to be de-identified. Administrators have to select the specific Attributes and click on the ‘ADD’ button so they will be transferred to the right panel (Selected Attributes):
 
Administrators can remove the selected Attributes from the list through the Delete icon next to each selected Attribute.
Administrators must save the information before accessing other tabs. Otherwise, the data will not be saved.
6.2.4.3. Way of Contact tab
This tab provides the following table of Administrative Contacts:
 
Each row presents an administrative contact and the related emails. Every time the ‘Way of Contact’ defined in this table is triggered, an email will be sent to the email addresses specified in this field. For example, if a Reporter makes a Registration Request, an email will be sent to these addresses to inform them about the new request.
Administrators are not able to create the contacts. They can only edit the email, which is editable through the Edit icon on the last section of each row.
The icon appears when hovering over the section.
Administrators have to click on the icon, and the system opens the email field of the specific row:
 
Once Administrators introduce an email(s) in the correct format, the Disc (Save) icon is activated. Administrators must click on it, and the email will be updated in the database.
6.2.4.4. Sharing of Attachments tab
This tab aims to select the authorities that will be available to the users of the current authority for sharing OCs and SRs.
It displays a list of E2 authorities with a check box for each OC and SR (disabled or enabled depending on the authority type – NAA/SIA). The columns work as filters:
 
Administrators must select the desired Authorities to which the attachments in OCs or SRs can be shared and click on ‘Save’. The system will save the updates in the database.
6.2.4.5. IP Whitelist tab
The users who want to access the public API methods, via Swagger or otherwise must have their IPs whitelisted.
This tab shows the whitelisted IPs:
 
Each row provides its IP and Description. The last section corresponds to the Delete and Edit icons that only appear when hovering over the section.
6.2.4.6.  Create an IP
Administrators have to click on the ‘New IP’ button above the table that adds a new row to the table:
 
The IP is mandatory and unique for each record, and the Description is optional.
Administrators must fill in at least the IP address in the IP column and click the ‘Save’ icon. The system will save the data in the database, and the new whitelisted IP is created.
6.2.4.7. Delete an IP
Administrators have to click on the Delete icon of the specific IP, and the system will delete it from the database.
6.2.4.8. Autofilled Attributes tab
 
The management of this functionality works as Section ‘Autofilled Attributes’ of the Organisation. See the Autofilled Attributes tab section for details. The difference is that Autofilled Attributes of the Organisation works for the webforms of that organisation, and this case is restricted to VRs and OCs created from scratch by the Authority Officers.
6.2.4.9. Custom Columns Templates tab
Through this page, the Administrator can select the Attributes available in the lists of ORs, VRs, OCs or SRs (according to the Authority type) in the corresponding ‘Safety Data’ or ‘Safety Recommendations’ menus of the Officers belonging to that Authority and the Attributes available in the landing page of the Reporting Portal for their reporters.
This tab is divided into sections, one per document list:
 
All the sections are managed in the same way, as follows:
The left pane includes a search filter and the MetaColumns, with all its Attributes checked by default:
 
Below is the Taxonomy Central or Custom, if existing for that Authority, through which the Officer can navigate to select more Attributes. See Taxonomy for further details on its navigation.
The right pane provides the selected metacolumns and Attributes. By default, the system provides a list of metacolumns and Attributes.
 
The officer can hide them through the eye icon next to each one.
The rubbish icon is to delete the Attribute of the table of reports.
The arrow next to the eye icon is to set the order of each Attribute:
 
Administrators can also alter their order by dragging and dropping them.
When the Administrator is updating the Attributes, before saving the updates, they can always click on the ‘Reset’ button below the list of selected Attributes so that the system will set the ‘Selected Attributes’ page to the default selection and order. 
Once the Administrator has updated the selected Attributes and metacolumns, they have to click on the ‘Save’ button, and the Custom columns will be updated based on the selected Attributes.
6.2.4.10. Default Queries
This is the last tab in the Authority settings section:
 
 
Through this page, the Administrator can select the queries that the system triggers when opening the ORs, the VRs, the OCs or the SRs menus (according to the Authority Type – NAA/SIA) of the users of its Authority.
The Administrator has to click on the ‘+’ icon of the query field, and the system will open the Select Query window:
 
 
Therein, Administrators have to select the specific query. If clicking on the ‘Save’ button, the query will be applied to users of this Authority who have not selected their own queries; if clicking on ‘Save for all’, the query will be applied to all the users of this Authority.

6.3. Roles and Permissions
This option of the Administration menu provides the following submenus:
·        Roles Management
·        User Management
·        Registration Requests
·        Groups Management
6.3.1 Roles Management
Permissions among the E2 Web Applications can be provided to different types of users through roles.
Administrators have to click on ‘Roles Management’ on the image above, and the system provides the following page:
 
It provides the table of Roles with the following columns that also work as filters:
·        Name: Identification of the Role
·        Hierarchy: At the Administrator level, the options are only:
ü  Authority Administrator
ü  Custom
ü  Reporter
Each group of permissions is directly related to the role’s hierarchy. This way, when a role with hierarchy level X is created, only the permissions related to hierarchy level X will be available to be assigned to the new role.
Type: NAA (National Aviation Authority) or SIA (Safety Investigation Authorities).
The last section of each row provides the following icons: 
 Which are aimed at deleting, copying and editing each Role.
Above the table, the system displays the ‘New Role’ button.
6.3.1.1. Create a new role
Administrators have to click the ‘New Role’ button above the table of Roles of the Roles Management menu. The system will open the ‘Role’ page:
 
The following fields are mandatory:
·        Type: it is by default 
ü  NAA, for Authorities of this type, 
ü  SIA, for Authorities of this type and
ü  Editable, for NAA/SIA Authorities
·        Name: it has to be unique for each role
·        Description: it can be the same as other roles.
Hierarchy: a drop-down menu with the options Authority Administration, Custom and Reporter
Depending on the hierarchy selected on this menu, the Basic Permissions table displayed at the bottom of the page will be updated. Filling them is mandatory to save the role.  For example:
·        Authority Administrator: the system will provide the following table of Basic Permissions
 
Administrators must select Create, Edit, Read and/or Delete Permissions for each role and click ‘Save’.
Note that there is no checkbox for some options, i.e. Create Authority Settings; Create and Edit Original Reports.
·        Authority: it is not editable. The system sets the Authority of the current Administrator by default.
·        Query: Administrators can select a query at the Queries drop-down menu. It will provide the Queries the current Administrator has previously saved through the Queries menu (Data Management). See the Queries section for further details on how to manage queries.
·        Role Type: By default, the system sets ‘Individual’, but Administrators can also select ‘Organisation’ or ‘Parent Organisation’.
 The selected query will restrict the records that can be accessed by users registered in that role to only those resulting from the execution of the query.
Administrators can select the ‘Advanced Permissions’ by clicking on that tab.
This tab provides the ‘Report’ Advanced Permissions, by default, to be selected (Image below). The content varies depending on the chosen hierarchy. For example, the following table corresponds to the Authority Administrator.
 
The advanced permissions are grouped into Reports, Data Management, Users & Roles, Taxonomy, Other, and E2 Central Hub. The Administrator can select any of these groups to provide the required permissions to the role and click the ‘Save’ button.
Occurrence Views: through this tab, Administrators can select the actions the users of this role can perform when using a particular View and save the selection. Otherwise, the role cannot be saved.
This tab is as follows:
 
It provides a table of views with all the views available for the current Authority. See Views management for further details on the Views.
Through the checkboxes, Administrators can select the permissions to access the specific View concerning a report's Creation, Edition and Read mode.
Enrolled users: displays the users assigned to this role. This list is built automatically, so Administrators cannot enrol new users from here. See the following section, User Management, for further details.
6.3.1.2. Edit a role
Administrators have to click on the pencil Edit button of the specific Role of the table, and the system will display the Edit Role page:
 
The management page is the same as the New Role page in the previous section. See it for further details. Administrators must update the needed fields and keep all the mandatory fields filled in. Then, they have to click on ‘Save’; the updates will be saved in the database, and the Roles table will be updated accordingly.
Note: The Users Enrolled tab is not editable. Through the Users management, Administrators can assign a role to a user, so this will be seen in the ‘Enrolled users tab’ of the Role page:
 
6.3.1.3. Duplicate a role
Administrators must click the ‘Copy’ icon of the specific Role, and the system will display the Role page. It is the same as the Edit page. Administrators have to update at least the Name field and keep the mandatory information filled. Then, they have to click on Save, and the updates will be saved in the database, and the roles table will be updated accordingly.
6.3.1.4. Delete a role
Administrators have to click on the ‘Delete’ icon for the specific role of the table, and the system will display a confirmation message because the action cannot be reversed. If Administrators confirm the action, the role will be deleted from the database and removed from the roles table.
6.3.2. User management
Administrators have to click on ‘User management’ under ‘Administration-Roles and Permissions’, and the system will display this menu:
 
It displays the table of users, which includes the users created through this management and those created through the ‘Organisation Management’ option. See the section on Organisation Management for further details.
Each table row is preceded by a checkbox to select each row.
The first column is a checkbox to select all the tables. The rest of the columns also work as filters:
·        Username: it is unique for each record.
·        Email: it can be the same as other users’ email.
·        Organisation Name: if the User belongs to an organisation, this column will indicate its name.
·        Organisation ID: It will set the organisation ID to which the user belongs if it exists.
·        Parent Organisation: It identifies the parent organisation if it exists.
·        Disabled: When disabled, the field will display a ‘green tick’. By default, the users are created disabled.
·        Blocked: if the user is blocked, the field will display a ‘green tick.’
·        Deleted: if the user is deleted, the field will display a ‘green tick’ (N/A)
·        Roles: it sets the Roles assigned to the user
·        Created by: the author of the user
·        Created on: Date of creation of the user
·        Last access on: Date of last access of the user to the E2 Web Application
Each row's last section has a 3-dot menu providing the Edit and Export options. Note: Administrators cannot delete the users. They can disable and block them.
Above the table in the left corner, another Export option exists for multiple export processes.
On the right-side corner is a ‘Show Deletion Requests’ toggle, disabled; if activated, the table will show users' requests to delete their accounts.
Above the toggle, there is a ‘New User’ button.
6.3.2.1.  Create a new user
Administrators have to click the ‘New User’ button above the table:
 
It sets the following fields:
·        Account Type: by default, it is Individual; Administrators can update it to Organisation
·        Authority: it is not editable. It sets the current Authority of the Administrator
·        Organisation: it is not editable for Individual users. It sets the user’s organisation for Organisation users
·        Username: it has to be unique for each User
·        Description: This field is optional
·        Creation Date: This field is not editable and is set by the system automatically when the record is created.
·        Modification Date: This field is not editable and is set by the system automatically when the record is updated
·        Last Activity: This field is not editable and is set by the system automatically when the user accesses their account in the E2 Web Application
·        Disabled toggle: by default, the account is disabled until the user activates it through the activation email.
·        Blocked toggle: by default, it is not enabled, and the account is not blocked. If enabled, the account is blocked
·        Properties:
ü  First Name: It is mandatory and refers to the User
ü  Last Name: It is mandatory and refers to the User
ü  Phone: it is optional
ü  Email address: it is mandatory and refers to the User
ü  Preferred language: it is not editable, and by default, it is English
ü  Job Title: it is optional
·        Roles: It lists all the roles available to the Administrator. The list varies depending on the type of user. The previous image shows the roles of Individual users (non-organisational users). For Organisations, it is as follows:
 
Administrators must fill in all the mandatory information, select the new User's corresponding roles, and click ‘Save’. The system will save the new user in the database and add the user to the user table in alphabetical order.
6.3.2.2. Edit a user
Administrators have to click on the ‘Edit’ option of the 3-dot button at the table of Users, and the system will open the ‘User Account Details’ page:
 
It is like the creation page, but the Account Type is not editable; the creation and modification Dates are already automatically set; if they exist, the Last Activity field is also automatically set.
Administrators have to make the needed updates and click on ‘Save’, and the information will be saved as long as they have kept the mandatory fields filled. The updates will be saved in the database, and the roles table will be updated accordingly.
6.3.2.3. Export a user
Individual export process for users
Administrators have to click on the ‘Export’ option for the specific User of the table of Users, and the system will automatically export that user to an Excel file.
Multiple export process for users
Administrators have to select the specific users through the check boxes of the specific rows or select all the tables through the checkbox provided next to the table columns and click on the ‘Export’ option displayed above the table. The system will email the Administrator a link to download the resulting zip file with the Excel files corresponding to the selected users.
6.3.3. Registration request
Administrators have to click on the Registration Request menu under Accounts & Permissions (Administration menu), and the system will display the table of registration requests for the specific Authority:
 
This table presents all the registration requests for this Authority introduced through individual reporters' E2 Reporting Portal registration page.
The table provides the following columns that also work as filters:
·        First Name
·        Last Name
·        Email
·        Username: unique for each user
·        Reason to register
·        Status: it can be pending, accepted or rejected
·        Register date: date and time of the request
On the last section of each row, there is a 3-dot menu that provides the following options:
 
·        Accept User: It accepts the user, and the user status turns to ‘Accepted’ in the request table. The system will send an email to the user through which to activate the account. The 3-dot menu will disappear from the specific request at the table.
·        Deny User: it denies the registration request. An email will be sent to the requester; the request status will turn to ‘Rejected’ in the table of requests. The Accept option will remain in the 3-dot menu of the request at the table. At the same time, the system will send an email to the candidate informing them of the request’s rejection.
6.2.4.  Groups management
Groups are made of users to which some action in the E2 Web Application can be applied, like notifications. See Notifications Manager section for more details.
Administrators have to click on Groups Management under Accounts & Permissions (Administration menu), and the system will display the Groups Management menu:
 
It provides a table of Groups with the following columns also working as filters:
·        Name: unique for each Group
·        Description: Optional
In the last section of each row, there is a 3-dot menu with the following options:
·        Edit Group
·        Delete Group
Above the table, there is a ‘New Group’ button.
6.2.4.2. Create a new group
Administrators have to click on the ‘New Group’ button, and the system will display the New Group page:
 
The fields are the following:
·        Name: it is the only mandatory field.
·        Description: it is optional
·        Available Users: it displays the table of active users, excluding organisation users, of the specific Authority. They are added to the Selected Users tab by selecting the needed users through the checkboxes and transferring them to the ‘Selected Users’ tab through the ADD button. The Users can also be removed from the ‘Selected Users’ tab through the ‘Remove’ button.
The system will save the new group in the database, and the group will be added to the group table.
6.2.4.3. Edit a group
Administrators have to click on ‘Edit Group’ on the 3-dot menu of the specific group at the table of groups, and the system will display the Edit Users Group page:
 
Administrators must update the needed information by always keeping the name filled out and clicking on ‘Save’.
The updates will be saved in the database, and the system will return them to the table of groups with the table updated.
6.2.4.4. Delete a group
Administrators have to click on ‘Delete’ on the 3-dot menu of the specific group at the table of groups, and the system will delete the group from the database and remove it from the table of groups.

6.4. Content Management
6.4.1. Support Tables
Administrators can access and see the Support Tables by clicking on Administration-Content Management-Support Tables. This menu is only for Administrator information purposes. Administrators cannot manage or edit the information; they can only view it. These tables support the ECCAIRS/SRIS and Custom Taxonomies and are handled at the ECCAIRS Central Administration level.
The system will display the Support Tables menu:
 
It displays a left panel with the list of all the tables, accessible by clicking on them:
·        Alias
·        Attributes Groups
·        Conversion Factors
·        Domains
·        Management Units
·        Measurement Unit Classes
6.4.1.1. Alias
By default, the system first displays the Alias table (Image below). It shows the following columns that also work as filters:
 
·        ID: Unique and mandatory for each table
·        Name: Unique and compulsory for each table
·        Description: Optional
·        Disabled: green tick if disabled; otherwise, enabled
6.4.1.2. Attribute groups
To access it, Administrators have to click on this table on the left pane, and the system will display it:
 
In this case, the table presents the following columns:
·        ID: Unique and mandatory for each Attribute group
·        Description: Unique and mandatory for each Attribute group
·        Detail: Long explanation of the Attribute Group
·        Explanation: it reproduces the description
·        Languages: This will provide the translations of each Attribute not currently activated.
Above the table, the system provides a file translation button that is currently unavailable.
6.4.1.3. Conversion factors
It includes conversion factors applicable in the Taxonomy.
To access it, Administrators have to click on this table on the left pane, and the system will display it:
 
The table displays the following columns that also work as filters:
·        ID: Unique and mandatory for each conversion factor
·        From Unit: it refers to a measure unit from which a value comes
·        To Unit: it is the measuring unit to which an original value of a different measure unit has to be converted
·        Constant Value: refers to the value of the ‘To Unit’ measure unit which is considered ‘Constant’ conditions, i.e. 32 º Celsius
·        Factor: It is the conversion factor that transforms from unit to unit. i.e.: 1 day =24 h or 1440 minutes; 24 times an hour is a day. 
6.4.1.4. Domains
To access this tab, Administrators have to click on it on the left pane, and the system will display this table:
 
 
The columns that also work as filters are the following:
·        ID: unique and mandatory for each domain
·        Description: unique and mandatory for each domain
·        Detailed: optional sort of long description
·        Explanation: optional description, mostly reproducing the description
·        Taxonomy reference: if it corresponds to ECCAIRS or to SRIS.
·        Languages: This will provide the translations of each Attribute, but this option is currently unavailable.
Above the table, the system provides a file translation button that is currently unavailable.
6.4.1.5. Measurement Units
To access this tab, Administrators have to click on it on the left pane, and the system will display this table:
 
The columns (that also work as filters) are the following:
·        ID: unique and mandatory for each unit
·        Class: unique and mandatory for each unit
·        Description: unique and mandatory for each unit
·        Detailed: Optional added description
·        Explanation: Optional long description
·        Languages: This will provide the translations of each Attribute, but this option is currently unavailable.
Above the table, the system provides a file translation button that is currently unavailable.
Moreover, the system displays a ‘Conversion Factor’ button above the table, which accesses the previously explained ‘Conversion Factor’ table.
6.4.1.6.  Measurement Unit Classes
Administrators have to click on this table on the left pane, and the system will display it:
 
 
In this case, the table presents the following columns:
·        ID: Unique and mandatory for each Attribute group
·        Description: Unique and mandatory for each Attribute group
·        Detail: Long explanation of the Attribute Group
·        Explanation: it reproduces the description
·        Languages: This will provide the translations of each Attribute, but this option is currently unavailable.
Above the table, the system provides a file translation button that is currently unavailable.
6.4.2. Reference Tables
The Reference Tables store Attribute values related to each other to help the users fill in the forms with adequate information. See the ‘ECCAIRS2 - Occurrence Officers’ tasks’ document for further details on its use.
Administrators can feed the values that trigger the reference tables used in the webforms and views in those centrally defined as collaborative reference tables.
Administrators have to click on ‘Administration – Content Management – Reference Tables’, and the system will display the Reference Tables menu:
 
 
The Table provides the following columns that also work as filters:
·        ID: mandatory and unique for each table
·        Description: unique for each table
·        Detailed: optional added description
·        Status: can be Draft or Release
The last section of each row is a 3-dot menu with the following options:  
View Table Properties:
Administrators have to click on this option of the 3-dot menu of the specific table row of the table, and the system will display the Table Properties page:
 It provides the following fields:
·        ID: unique and mandatory for each table
·        Description: unique and mandatory for each table
·        Detailed Description: optional long description
·        Explanation: optional
·        Status: it can be Draft, Release or Archived
·        Based on Entity: it is an Entity of the Taxonomy
Below the fields, there are two panels:
·        The left panel is ‘Triggering Attributes’: it provides the Taxonomy from which the triggering Attribute is selected
·        The right panel is ‘Available Attributes’: it provides the selected Attributes that will provide information to be filled in the webforms.
Above the page, there is a ‘Download CSV template’ that downloads the template with the information of the panels. Administrators must download it and fill in the values indicating the start and final validity dates. It is uploaded to the system with the information filled in through the table values option.
Table values: 
Administrators have to click on this option of the 3-dot menu of the specific table row of the table and the system will display the Table values page:  
The table will display a table with the triggering values for the specific reference table. The columns are the following:
·        ID: unique and automatic for each value
·        Trigger Value: It is the value users have to type when filling in the webforms and views to open the reference table
·        From Date: The triggering Attributes are valid. This column refers to the Start Date.
·        To Date: It is the final date of the triggering Attributes
Above the table, there is an Import table button. It opens the Import table window:
 
Administrators must select the CSV with the information to be imported or drag it and drop it in the file area. By default, the system selects ‘Full Clean Up’; this option deletes the previous version and uploads the new values for the reference table.
If Administrators only want to add updates on the Values, they have to click on ‘Incremental Update’. They have to click the ‘Import table’ button, and the information will be transferred to the table of values.
6.4.3.  Notifications Manager
E2 can notify selected users of the creation, update, deletion, or sharing of actions over reports that meet the conditions of a query through query-based notifications. 
To configure Authority notification, Administrators have to click on ‘Administration – Content Management – Notifications Manager’ and the system will display the ‘Notifications Manager’ menu:
 
It displays the table of Notifications with the following columns that work as filters:
·        Notifications Name: it is unique and mandatory for each notification
·        Source: the safety event to which the query will be applied, which can be ORs, VRs, OCs or SRs (according to the Authority type) to determine if the notification will be sent
·        Triggering Action: The action that will cause the execution of the query. It can be Create, Delete or Update a Safety Event.
·        Query Name: it refers to the query on whose execution the notification informs
The last section of each Notification row provides an Edit and a Delete icon:
 
Above the table, the system displays a ‘New Notification’ button.
6.4.3.1.  Create a notification
Administrators have to click the ‘New Notification’ button above the table of Notifications (See image above), and the system will display the ‘New Notification’ page:
 
It provides the following fields:
·        Name: it is mandatory and has to be unique
·        Source: Mandatory drop-down menu providing the following options:
ü  OR
ü  VR
ü  OC
ü  Safety Recommendation: only for SIA’s
·        Library: Mandatory field. The +ADD icon opens a Library window where the Administrator have to select a folder under the National shared library:
 
·        Query: +ADD icon opens the selected Library window, presenting the Libraries tree view on the left. Administrators must select a folder, and the system will provide queries preceded by radio buttons to be selected in the right panel. Administrators have to choose a query and click on the ‘ADD’ button:
 
·        Action: a mandatory drop-down menu with the options ‘Update’, ‘Create’, and ‘Delete’. Administrators can select as many of them as desired. They are the triggering actions, so the query will be triggered when the selected Action is applied to the selected Source.
·        To: It is mandatory, and it indicates to whom the notification will be sent
ü  If Role is selected, the system displays a Table of Available Roles:
 
 
 The Table of Roles provides the following columns that also work as filters:
o         Name
o         Hierarchy
o         Authority: to which the role belongs. It will be the Administrator’s Authority.
Administrators have to select the needed roles and click on ADD, and the selected roles will be added to the ‘Selected Roles’ page. Administrators can access the Selected Roles tab by clicking on ‘Selected Roles’. This tab will display the list of selected Roles and a ‘Remove’ button to bring Roles to the ‘Available Roles’ tab.
 
ü  If User is selected, below the system displays the table of active users, excluding organisation users:
 
It displays the Users created by this Administrator.
The table is divided into columns that also work as filters:
o         Username: unique for each User
o         First Name
o         Last Name
o         Roles
The table's function (to add and remove users) is similar to managing the abovementioned roles table.
ü  If User Group is selected, the system displays the table of Users Groups:
 
It displays the list of User Groups created by the Administrator, with the following columns also working as filters:
o         Name: unique for each one
o         Description: it is optional
The table's function to add and remove users is like managing the abovementioned table of roles.
 ·        Notifications toggle: by default, it is activated. This means a notification will appear for the selected users on their landing page.
ü  Email: enabled by default. A notification email will be sent to the selected Users.
ü  Email Frequency: the options are the following:
o         Every time: the notification email will be sent any time the selected action takes place with the results of the query execution
o         Monthly: the notification email will be sent once a month
o         Weekly: it will be sent once a week
o         Daily: it will be sent once a day
 
Administrators must fill in all the mandatory information and click ‘Save’. The system will save as many notifications as Actions selected in the Actions drop-down menu in the database. Moreover, it will add those notifications to the Table of notifications. Their Names will consist of the Name introduced in the ‘New Notification’ page and each Action selected in the Actions drop-down menu: 
 
6.4.3.2. Edit a notification
Administrators have to click on the Edit icon, and the system will display the ‘Edit Notification’ Page:
 
The fields are the same as those on the New Notification page explained in the previous section. The Source and the Actions are not editable. Administrators must select the ‘To’ information, update the needed fields, and click ‘Save’. The system will save the update in the database, and the table of notifications will be updated accordingly.
6.4.3.3. Delete a notification
Administrators must click the Delete icon, and the system will display a warning message to confirm the action. If Administrators confirm the action, the system will delete the notification from the database and remove the notification from the notification table.

6.5. Others
The Menus under Administration – Others are the following:
 
6.5.1.   External APIs
There is a set of methods that can be accessed via API. It is accessed by selecting the ‘Administration - Others – External APIs’ menu option.
 
Administrators can select the icons to access the available methods, classified by repository. It will access Swagger, which helps users consume the API services. 
 
 
The attached document provides further information on all the methods available for API users. 
 
 
 
6.5.2.   Migration
This option of the Administration menu displays the migration window as follows:
 
E5Z is the extension given to compressed XML files in ECCAIRS2 that contain one or more occurrences (OCs or SRs) in XML format. If it contains attachments, E5Z files can also include folders with the same name as the corresponding XML.
The Administrator has to select the files through the ‘Select files’ button or by dragging and dropping them in the E5Z files section and clicking on ‘Generate Occurrence’ or ‘Generate Safety Recommendation’ if the Administrator’s Authority is an SIA.
A maximum of 50 files and 600 MB is allowed.
When migrating Occurrences, the system validates if an occurrence already exists in the Authority by checking the following Attributes of the ECCAIRS Central Taxonomy:
·        Responsible Entity (453)
·        File Number (452)
A new version of the occurrence will be created if there is a match. Otherwise, a new occurrence is created.
Thus, for new OCs, the system will display a message explaining the OC has been generated. (Simultaneously, the system emails the Administrator to inform them of the migration result). Then the Administrator has to click on ‘View results’. The system will display the list of migrations with the most recent on the top of the table:
 
The list indicates per column the following data concerning each migration process by which migrations can be filtered:
·        Username: the author of the migration
·        Filename: of the E5Z file
·        Authority to which the Administrator belongs
·        Total reports: number of total OCs
·        Total attachments: number of total attachments
·        Number of loaded reports
·        Number of loaded attachments
·        Initial Process Date
·        Final Process Date
·        Migration Date
·        Migration status: it can be the following:
 
If the Administrator moves the mouse over the last column of the migration row, the system will display two icons:
 
The download icon downloads an Excel file with the information of the migration results per XML of the E5Z file, i.e.:
 
The eye icon accesses a view page with the results of the migration, as follows:
 
Above the panel, on the right side, there is a Download option that downloads the view page in PDF format.
The first section of the page is the Results section, which indicates the status of the process: whether it has been successfully migrated or has been processed with errors, not migrated or partially migrated. 
The central panel shows a percentage drawing showing the number of processed reports and their status.
The left panel indicates the following:
·        File ID
·        User ID
·        Authority Name
·        Initial Process Date
·        Final Process Date
·        Migration Origin
The right panel refers to the attachment and indicates the total number of successfully migrated and un-migrated attachments.
The second part of the page, below, is the Reports section with the table of reports included in the migration:
 
It presents a report per row, and per report, the following columns can also be used as filters:
·        The XML ID: Unique for each one
·        The File Name: Unique for each one
·        Total Attachments (included in the XML)
·        Number of loaded attachments
·        Migration status: it can be successfully migrated or has been processed with errors, not migrated or partially migrated
·        Message: With the E2 ID for the OC in case of a successful migration, like in the image above, or it can be messages explaining the cause of a failed or final migration as follows: 
If the user clicks on the arrow at the beginning of a report’s row, the system displays the attachments’ list of that OC below the list:
 
 
The list presents the attachment of the specific OC, if it exists, with one attachment per row. Each row is divided into columns that can be used as filters:
·        Attachment ID: unique for each one
·        Attachment Name: also unique
·        Migration Status: migrated, partially migrated, processed with errors, not migrated
·        Message: Referring to the success of the migration or explaining the cause of a partial migration, with error or not migrated.
The last section of the view page is the attachment list:
 
It presents the list of all the attachments of all the OCs of the list of reports. The information is the same as the attachment per report.
6.5.3.  Upload E5X files
This option of the Administration menu displays the Upload E5X files window:
 
E5X is the extension given to compressed XML files in ECCAIRS2 that contain one or more original reports (ORs) in XML format. E5X files can also contain folders with the same name as the corresponding XML.
The Administrator has to select the files through the ‘Select files’ button or by dragging and dropping them in the E5X files section and clicking on ‘Upload E5X’.
The system will display a message warning that the process can take some time and will communicate if the process has been successful.
In parallel, the system emails the Administrator: Your request to upload the ‘DEMO.e5x content to ECCAIRS2 has been successfully received'.
When the process has finished, the system will send another message on the status of the process.
Then, the Administrator has to click on ‘View upload results’, and the system will display the view page providing the list of all the uploads by date order, with the last upload in first place:
 
The list functions like the migration process but with original reports instead of OCs. See the previous section for further details.
6.5.4.  Validate E5Xfiles
This option of the administration menu displays the following window:
 
The Administrator has to select the files through the ‘Select files’ button or by dragging and dropping them in the E5X files section and clicking on ‘Validate E5X’.
The system displays a message once it is validated. At the same time, the system sends an email to the Administrator on the result of the validation. The Administrator has to click on ‘View validation results’, and the system opens the following Results page:
 
It presents a table with the processed validations, with the most recent ones in the first place. The columns per each validation row are the following (they can also be used as filters):
·        Username: the author of the validation
·        Filename: of the E5X file
·        Authority to which the Administrator belongs
·        Total reports: number of total ORs
·        Total attachments: number of total attachments
·        Initial Process Date
·        Final Process Date
·        Validation status: it can be
 
On the last column of the specific validation row, the Administrator can mouse over, and a download icon will appear.
 
 
The Administrator can click on it to download an XLS file with the results of the validation:
 

7. My account

7.1. My account menu
This menu is accessible once the Administrator clicks on their username:
 
The Administrator clicks on it, and the system displays ‘My Account’ page.

7.2. Personal Details
This is the first tab of “My Account” page.
The first tab is ‘General’, indicating the type of account (individual or organisation) and the edit page for the personal details. 
The personal details fields are the following:
·        Authority: not editable, to which the Administrator belongs
·        Organisation: not applicable for Administrators
·        Username: of the Administrator, it is not editable
·        Description: optional field and editable
·        First name: of the Administrator, editable mandatory field
·        Last name: of the Administrator, editable mandatory field
·        Phone: optional and editable
·        Email: mandatory and editable
·        Preferred language: mandatory and editable; doesn’t affect system behaviour at this stage of development.
·        Job title: optional and editable
·        ‘I want to receive an email when I submit an ‘OR’ toggle·        
·        Token: it connects the Administrator to the API. It is not editable. It provides a copy icon to copy it        
·        Delete my account icon: it requests the Administrators to delete the account after a confirmation message.
The Administrator can update the editable fields by clicking the ‘Save’ button. The system will save the updates on the Personal details in the database.

7.3. Query-based notifications
Even though it is available for Administrators, this tab only applies if the Administrator also have an Officer role. If so, refer to the Occurrence Officer manual for details.

7.4. Object-based notifications
Even though it is available for Administrators, this tab only applies if the Administrator also have an Officer role. If so, refer to the Occurrence Officer manual for details.

7.5. Favourite Views
Even though it is available for Administrators, this tab only applies if the Administrator also have an Officer role. If so, refer to the Occurrence Officer manual for details.

7.6. Custom Column
Even though it is available for Administrators, this tab only applies if the Administrator also have an Officer role. If so, refer to the Occurrence Officer manual for details.

7.7.	Export by Attribute
Even though it is available for Administrators, this tab only applies if the Administrator also have an Officer role. If so, refer to the  Occurrence Officer manual for details.

7.8. Default queries
Even though it is available for Administrators, this tab only applies if the Administrator also have an Officer role. If so, refer to the Occurrence Officer manual for details.

8. ECCAIRS 2 Help Desk
Administrators can access the E2 Help Desk through the Help Desk icon displayed on the top bar of the E2 Web Application in the right-hand corner:
  
Administrators can click on this icon, and the system will open the Help Desk page in a new tab on the web browser. They can start to communicate with the Help Desk through this Jira tool: