1. REMI Database Antall Fernandes

2. REMI ● A relational database to facilitate data - metadata organization of various research studies. ● Interface into such a system is currently a restful web-based interface.

3. System Layout

4. ● Application developed on Ruby on Rails ● Representational State Transfer (REST) software architecture ● Apache as web server ● Also used to service uploads and downloads (subject to change based on performance)

5. Entity Relationship Diagram

6. Entity Relationship ● An Experiment can be of 9 different subtypes. ● An Experiment has one Researcher (User) ● User can have many Roles ● An Experiment can have many Files associated with it ● One file are associate itself with another file

7. Table Design(... to change)

8. Component/System Design

9. User Roles <= System Administrator Data Authorizer => <= Contributors Public Users =>

10. Authorization: System Administrator ● Manages ● Users ● Roles ● Permission based on Roles ● Categories and Sub Categories ● Change system configurations ● Display formats

11. Authorization: Data Authenticator ● Manages the data being uploaded to the system ● In charge of ● auditing the data ● publishing the data

12. Authorization: Contributors ● Can contribute data to the system ● Experiments ● Files associated with the experiment ● Subjects ● Machine Info

13. Authorization: Public Users ● 'Public User' as a user role entity does not exist within the system ● Any user that uses the system and has no roles assigned to him automatically is part of the 'Public User' category ● As a public user you are only allowed to search and download files from the system.

14. Thank You