Proposed scope of 6.0 release

From ICISWiki

Jump to: navigation, search

We had a short discussion on TDM_Use-Cases_Data_Models_and_Schemata_6.0. We propose to work on this schema in the wiki. The proposal is that we finalize the schema by the end of the year. Please note this a proposal and it has only been discussed at the ICIS mini meeting in July and in various meetings with some ICIS collaborators. Please make your comments known.

In the scope of the version we propose to be the following:

  • Avoid any changes that will break existing applications
    • With the exception of GEMS and OMS, this will only involve the addition of new fields to cope with OMS
    • OMS is the ontology management system and it is a completely new component (agreed at the July ICIS meeting)
    • GEMS version 6.0 is a complete reworking. A script will be provided to convert 5.5 to 6.0. For IWIS, IMIS and IRIS we will do this conversion in CRIL.
  • We propose that version 6.0 is an intermediate version in the context of the GCP Molecular Breeding Platform (MBP).
    • The existing standalone applications will be tested with version 6.0 (with the exception of an GEMS applications), however they may not make use of the complete 6.0 schema (for example OMS)
    • Some parts of the old schema, specifically those that rely on types, with be redundant in version 6.0, but will be retained for backward compatibility (OMS will be used for ICIS types etc, making for example the udflds and methods tables redundant)
    • All new tools developed (specifically in MBP) will work with version 6.0, making use of the full schema
    • No existing 5.5 tables or fields will be removed but it will be assumed that the table and field names will be in lower case.
  • We propose that version 7.0 is not a backward compatible version which may use of only the new applications developed specifically for 6.0 onwards
    • Tables and fields will be renamed to improve readability of the schema
    • Existing applications will not work with version 7.0
    • Tables and fields to be removed in 7.0 will be marked as depreciated in 6.0
    • Any new applications must be easily configurable to allow table and field changes and to cope with SQL differences in DBMS (either via a abstraction layer such as Hibernate or direct DBMS specific SQL)

We have divided the schema development and documentation work by component.

GEMS – Clarissa Pimentel

DMS – Arllet Portugal

GEMS – Weng Tulod

IMS – Jean Sabado

OMS – Rosemary Shrestha

Retrieved from "http://www.cropinfo.org/icis/index.php/Proposed_scope_of_6.0_release"
Personal tools