EPA/600/C-19/114 | July 2019
www.epa.gov/homeland-security-research
United States
Environmental Protection
Agency
&EPA
The Retried iAtion DAta
Repository (RADAR) Tool
Chemical
Biological
Radiological
Resources
Office of Research and Development

-------
MEMORANDUM
DATE: November 28, 2017
SUBJECT: System Components, Entity Relationship Diagram, and Future
Enhancements for the RemediAtion DAta Repository (RADAR) Web-based
Tool
1.	Introduction
This memorandum describes the final system components, database entity relationship
diagram (ERD), and future enhancements for the RemediAtion DAta Repository (RADAR)
Web-based tool. The tool provides a simple, user-friendly interface to search and explore
National Homeland Security Research Center (NHSRC)-generated data using web services to
communicate with the database. The tool is intended for a wide audience including scientists,
engineers, and researchers.
2.	System Components
The front-end component powers the user experience. It provides the interface to the
user to allow interaction with all the pages, data, document access, etc. The front-end also
utilizes a subset of the data that drive the application and support several operational and
navigational features. The front-end presentation component consists of HTML 5, CSS,
JavaScript, and API web services consumption. The front-end was implemented with React.js
with Redux.
The back-end powers the website and consists of web servers, databases, and the server-
side programming components and business logic. The back-end component provides web
services to supply data to the front-end, as needed, based on user actions. Back-end data are
stored in a MySQL database and server-side programming in the middle-tier was implemented

-------
Entity Relationship Diagram
L_FILE_TYPE
DATA.FILETYPE
BDTJD
LTIER1
W TIER1JD
L_TIER2
T1ER2JD
BDTJD
TIER3JD
L_PROJECT_TYPE
$ PROJECTTYPEJD
TIER4JD
L_SOURCE_TYPE
SOURCETVPE_ID
RADAR
RemediAtion DAta Repository
DAT A_AN D_RESOU RC E
DAR_ID
DAR_TABLE_NAME
DAR_TITLE
DAR_CITATION
DAR.YEAR
DAR_DESC_SHORT
DAR_DESC_LONG
FILETYPE
TIER1_DESC
PROJECTTYPE
SOURCETYPE
DAR_LOADED_BY
DAR_LOADED_DATE
UPDATED_BY
UPDATED.DATE
D_RADDECON_JAPAN
$ DATAJD
DAR_ID
FILE_NAME
TARGET
SURFACE
TOPOGRAPHY " j
D.BIODECON
DATA ID

DAR ID

ID

EntryDate

ENRec

Ref

Phys State

GrimeDirt

AppMeth

Loading

ContTimeDesc



NOTEBOOK
§ ID
USERS JD
DARJD
CREATED.AT
UPDATED_AT
PASSWORD_RESETS
§ ID
EMAIL
TOKEN
CREATED_AT
Memorandum
November 28, 2017
Page 2
OAUTH_REFRESH_T OKENS
OAUTH_AUTH_CODES
USERS
OAUTH_PERSONAL_ACCESS_CLIENTS
OAUTH_ACCESS_T OKENS
OAUTH.CUENTS
Database Entity Relationship Diagram

-------
Memorandum
November 28, 2017
Page 3
4.	Hosting
The RADAR prototype is currently hosted in a temporary cloud environment. Following
a prototype review phase, EPA will navigate the application deployment process to facilitate a
transition to an EPA-approved environment. Activities will include:
•	Determination of the most appropriate deployment environment
•	Completion of application security reviews and security plans
•	Completion of application readiness reviews and checklists
•	Transition to EPA's environment
•	Testing and deployment to development, staging and production environments
It is recommended that an evaluation be performed of whether a cost-sharing opportunity for
multiple NHSRC applications (e.g., share a dedicated server with I-WASTE modernization)
deployed to a dedicated server in EPA's traditional hosting environment provides a more cost
effective option than current cloud offerings. The technology in which the tool is developed
could be deployed in either environment.
5.	Potential Future Features
Throughout prototype development, many additional features were identified as potential
future enhancements for consideration. A listing of features to consider is provided below:
1. Create Admin Module Functions
a.	Create an admin user management feature to approve/deny account requests and
access and log usage data
b.	Enhance user account management features
i.	Allow users to recover their password if they forget it
ii.	Implement registration confirmation whereby when users register an
account, they must confirm their e-mail address before they can log in
iii.	Implement new registration notification mechanism
c.	Develop a data registry mechanism/standard operating procedures (SOPs)
i.	Establish requirements and protocol for proposing new data sets to include
in the repository
ii.	Establish a workflow to propose, review, approve, and publish data sets
iii.	Specify required metadata and keyword tagging
d.	Design an admin module to modify (add, edit, delete) tool metadata used
throughout
i.	Categories
ii.	Keywords

-------
Memorandum
November 28, 2017
Page 4
2.	Enhance Search Results
a.	Enhance Filter Panel - Provide more sophisticated prompts whereby counts of
sources associated with keywords can be included and dynamically updated based
on layering additional filters
b.	Create a Manage Notebook Feature - Provide a mechanism to Manage Notebook
(e.g., like Quick Cart View) to allow users to "uncheck" and remove data sets
added to their notebook without having to find the search result entry on the page
c.	Enable Dynamic Results Entry/Available Data Tab - Create dynamic listing of
available data fields based on data registry input (e.g., Identify fields upon upload
that should be listed on the available data tab); Require data field descriptions to
improve context display
d.	Evaluate applicability and feasibility of ElasticsearchHo improve data mining
opportunities as repository grows over time
3.	Enhance View Notebook
a.	Define and implement a header to describe each data table (e.g., source, date, etc.)
b.	Implement "Merge Data" - Create functionality to merge "relatively similar"
datasets into a single data table
i. Need to define business rules for when datasets can be aggregated (e.g.,
within the same category and at least one keyword in common)
c.	Allow users to reorder or filter their notebook
d.	Offer expanded data set views - Currently, datasets displayed in View Notebook
are abbreviated to improve performance (implemented with the react-virtualized
library). If users want the full data set, they can download the data.
The prototype is optimized for search/filter. Consider offering a pop-out view or
send user to a new page optimized for selected data (selected columns and filtered
set if applicable).
e.	Consider (facilitated through a data registry mechanism) initially displayed
specific default columns to manage initial display rather than load all possible
columns
4.	Dynamic Stats Tab
a. Create a dynamic data feed to source the treemap of research coverage accessible
from the Stats tab
5.	Enhanced Widget Features
a. Consider what features to offer and how to facilitate creating tools/calculators
using data stored in the repository
6.	General
a.	Incorporate a data loading indicator for large data sets (e.g., BioDecon widget
load time and View Notebook data sets)
b.	Consider storing keyword terms searched by users to quantify what information
users seek
c.	Where appropriate, incorporate "upcoming feature" indicators to alert users
d.	Consider utility of incorporating a decision tree framework to assist users in
identifying the most relevant data stored in the repository

-------
Memorandum
November 28, 2017
Page 5

-------