Difference between revisions of "IBF DiversityMobile and Data Synchronisation"
| Line 1: | Line 1: | ||
| − | The Diversity Workbench database framework consists of single application components collaborating through agreed software interfaces. The goal of '''IBF DiversityMobile and Data Synchronisation''' is the organisation of the gathering of data in the field by setting up DiversityMobile. This component is set up to enter, modify, or – if necessary – delete ecological and biological monitoring data in the field via a mobile device. The [[IBF Mobile Process Modeling]]demonstrated the complexity of this | + | The Diversity Workbench database framework consists of single application components collaborating through agreed software interfaces. The goal of '''IBF DiversityMobile and Data Synchronisation''' is the organisation of the gathering of data in the field by setting up DiversityMobile. This component is set up to enter, modify, or – if necessary – delete ecological and biological monitoring data in the field via a mobile device. The [[IBF Mobile Process Modeling]] demonstrated the complexity of this process. Currently, the data model of DiversityMobile is retained fully compatible with the data model of DiversityCollection which is the component for the storage of collection and observation data within the Diversity Workbench. The field data retrieved via the mobile device using the DiversityMobile client are stored in a database on this device. This local database contains a set of definitions, e.g., lists of taxonomic names and project-specific settings. Moreover, the user might choose to download field data from DiversityCollection, already stored there. Furthermore, it is planned to allow data import directly from web services e.g. for taxonomic or other biological backbone data. As soon as the user starts gathering data in the field, additional data are added to the mobile database. This includes the option that the mobile database contains subsets of data from the central DiversityCollection database. Hence, the upload of field data to the central database and the dataflow to and from DiversityMobile, e.g. to avoid duplicates, needs to be strictly organized by a complex synchronisation process. This also concerns GPS and multimedia data. The user can access the synchronisation component via a special interface which will be installed on his personal computer. This component connects the mobile database with a data repository e.g. via the internet. The synchronization data are stored in a separate database. This database is linking the data items on the client-side with data items on the server-side using Global Unique Identifiers (GUIDs). The data are stored in the local master database DiversityCollection. For a further consistent data flow it is crucial that the database is set up at an institutional data repository which acts as GBIF data provider like the IT Center of the Staatliche Naturwissenschaftliche Sammlungen Bayerns. There the GUID is connected with a persistent Uniform Resource Identifier (URI). The latter is published and accessed by global networks like GBIF. |
Revision as of 17:11, 2 November 2009
The Diversity Workbench database framework consists of single application components collaborating through agreed software interfaces. The goal of IBF DiversityMobile and Data Synchronisation is the organisation of the gathering of data in the field by setting up DiversityMobile. This component is set up to enter, modify, or – if necessary – delete ecological and biological monitoring data in the field via a mobile device. The IBF Mobile Process Modeling demonstrated the complexity of this process. Currently, the data model of DiversityMobile is retained fully compatible with the data model of DiversityCollection which is the component for the storage of collection and observation data within the Diversity Workbench. The field data retrieved via the mobile device using the DiversityMobile client are stored in a database on this device. This local database contains a set of definitions, e.g., lists of taxonomic names and project-specific settings. Moreover, the user might choose to download field data from DiversityCollection, already stored there. Furthermore, it is planned to allow data import directly from web services e.g. for taxonomic or other biological backbone data. As soon as the user starts gathering data in the field, additional data are added to the mobile database. This includes the option that the mobile database contains subsets of data from the central DiversityCollection database. Hence, the upload of field data to the central database and the dataflow to and from DiversityMobile, e.g. to avoid duplicates, needs to be strictly organized by a complex synchronisation process. This also concerns GPS and multimedia data. The user can access the synchronisation component via a special interface which will be installed on his personal computer. This component connects the mobile database with a data repository e.g. via the internet. The synchronization data are stored in a separate database. This database is linking the data items on the client-side with data items on the server-side using Global Unique Identifiers (GUIDs). The data are stored in the local master database DiversityCollection. For a further consistent data flow it is crucial that the database is set up at an institutional data repository which acts as GBIF data provider like the IT Center of the Staatliche Naturwissenschaftliche Sammlungen Bayerns. There the GUID is connected with a persistent Uniform Resource Identifier (URI). The latter is published and accessed by global networks like GBIF.
Scientists in this workpackage: Prof. Dr. S. Jablonski, T. Schneider, B. Volz