The SEURAT philosophy is one of "Data Inclusivity". Include the data, whatever the form or location. With respect to databases, this means SEURAT will hook up to any database.
Have Multiple Databases? No Problem.
SEURAT is designed from the ground-up for a multi-database, multi-schema environment. Simply map each new database and you can search information for one, some or all databases as well as see what kind of information is available in each. SEURAT is flexible enough to accomodate multiple databases including ones from different vendors and each with its own database schema.
Have Databases from Different Vendors? No Problem.
SEURAT uses the open Java Database Connectivity framework, meaning it can talk to any database. What's more, it can simultaneously use multiple databases from the same or different vendors. For example, you can configure SEURAT to use an Oracle, MySQL, and PostgreSQL database simultaneously.
Have Different Databases Schemas? No Problem.
All you need to do is tell SEURAT (through its "meta-data" mapping file) which tables and columns of your database contain representations of the entities Project, Compound, Structure, Lot, Sample, Assay Results, Notebook and Scientist and how to navigate from one table to the next and SEURAT will do the rest.
Deployed SEURAT, then got New Database Tables? No Problem.
You can add access to the data in new database tables after you have deployed SEURAT at your site by adding configuration information.
Work with CROs? No Problem.
Do you work with partners or CROs who are providing flat files, using different databases & schemas, and even using different identifiers? You can make partner data (WDI, compound vendors, Kinase and GPCR databases…) both structure searchable and available to your researchers right alongside your corporate compounds by:
- Configuring SEURAT to access CRO databases directly
- Loading CRO data into one or more existing SEURAT native databases (running in Oracle, PostgreSQL or MySQL) from SD and CSV files