IBF DiversityMobile and Data Synchronisation - Revision history

Triebel at 09:28, 30 March 2015

2015-03-30T09:28:19Z

Triebel at 09:28, 30 March 2015

2015-03-30T09:28:03Z

Bernhard.volz at 16:27, 1 March 2012

2012-03-01T16:27:27Z

Triebel at 09:45, 4 August 2010

2010-08-04T09:45:48Z

Triebel at 09:45, 4 August 2010

2010-08-04T09:45:34Z

Triebel at 21:29, 3 November 2009

2009-11-03T21:29:52Z

Triebel at 08:15, 3 November 2009

2009-11-03T08:15:15Z

Triebel at 07:45, 3 November 2009

2009-11-03T07:45:39Z

Triebel at 17:43, 2 November 2009

2009-11-02T17:43:25Z

Triebel at 17:39, 2 November 2009

2009-11-02T17:39:09Z

← Older revision		Revision as of 09:28, 30 March 2015
Line 19:		Line 19:

	Scientists in this workpackage: Prof. Dr. S. Jablonski, G. Rollinger, T. Schneider, Dr. B. Volz		Scientists in this workpackage: Prof. Dr. S. Jablonski, G. Rollinger, T. Schneider, Dr. B. Volz
−

	The DFG funded project IBF expired in 2014.		The DFG funded project IBF expired in 2014.

← Older revision		Revision as of 09:28, 30 March 2015
Line 18:		Line 18:


−	Scientists in this workpackage: Prof. Dr. S. Jablonski, T. Schneider, Dr. B. Volz	+	Scientists in this workpackage: Prof. Dr. S. Jablonski, G. Rollinger, T. Schneider, Dr. B. Volz
		+
		+
		+	The DFG funded project IBF expired in 2014.
		+

	[http://www.ai4.uni-bayreuth.de/de/index.html Applied Computer Science IV, University of Bayreuth]		[http://www.ai4.uni-bayreuth.de/de/index.html Applied Computer Science IV, University of Bayreuth]

← Older revision		Revision as of 16:27, 1 March 2012
Line 18:		Line 18:


−	Scientists in this workpackage: Prof. Dr. S. Jablonski, T. Schneider, B. Volz	+	Scientists in this workpackage: Prof. Dr. S. Jablonski, T. Schneider, Dr. B. Volz

	[http://www.ai4.uni-bayreuth.de/de/index.html Applied Computer Science IV, University of Bayreuth]		[http://www.ai4.uni-bayreuth.de/de/index.html Applied Computer Science IV, University of Bayreuth]

← Older revision		Revision as of 09:45, 4 August 2010
Line 21:		Line 21:

	[http://www.ai4.uni-bayreuth.de/de/index.html Applied Computer Science IV, University of Bayreuth]		[http://www.ai4.uni-bayreuth.de/de/index.html Applied Computer Science IV, University of Bayreuth]
		+
		+

	[[IBF DiversityMobile - Internal Sites]]		[[IBF DiversityMobile - Internal Sites]]

← Older revision		Revision as of 09:45, 4 August 2010
Line 20:		Line 20:
	Scientists in this workpackage: Prof. Dr. S. Jablonski, T. Schneider, B. Volz		Scientists in this workpackage: Prof. Dr. S. Jablonski, T. Schneider, B. Volz

		+	[http://www.ai4.uni-bayreuth.de/de/index.html Applied Computer Science IV, University of Bayreuth]

	[[IBF DiversityMobile - Internal Sites]]		[[IBF DiversityMobile - Internal Sites]]

@@ Line 9: / Line 9: @@
 * [[IBF Diversity Workbench and Data Repository]].
-A technical repository will make accessible
+A freely accessible online repository will offer
 *[[DiversityMobile Information Models]]
@@ Line 15: / Line 15: @@
 *[[DiversityMobile Applications]]
-*[[Possible Devices for DiversityMobile]].
+*Information on [[Possible Devices for DiversityMobile]].

← Older revision		Revision as of 08:15, 3 November 2009
Line 3:		Line 3:
	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 developped to enter, modify, or – if necessary – delete ecological and biological monitoring data in the field via a mobile device. The whole process is very complex and modelled by [[IBF Mobile Process Modeling]]. In the concept which is realised within the IBF context the data model of DiversityMobile is held fully compatible with the data model of DiversityCollection. This is the component for the storage of collection and observation data within the Diversity Workbench and fulfill the ABCD standard of TDWG.		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 developped to enter, modify, or – if necessary – delete ecological and biological monitoring data in the field via a mobile device. The whole process is very complex and modelled by [[IBF Mobile Process Modeling]]. In the concept which is realised within the IBF context the data model of DiversityMobile is held fully compatible with the data model of DiversityCollection. This is the component for the storage of collection and observation data within the Diversity Workbench and fulfill the ABCD standard of TDWG.

−	The concrete approach is as follows: The field data retrieved via the mobile device using the DiversityMobile client are stored in a database on this device. The central database DiversityCollection will eventually offer a set of definitions, e.g., lists of taxonomic names and project-specific settings to be uploaded. 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. 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 organised by a complex '''synchronisation process'''. This also concerns GPS and multimedia data. The user will access a synchronisation component via a special interface which will be installed on his personal computer. This component is installed at a data repository and is connected by the user, e.g. via the internet. The synchronization data are stored in another database. This database will be linking the data items on the client-side with data items on the server-side using Global Unique Identifiers (GUIDs). The data processing at the data repository is picked out as a central theme of [[IBF Diversity Workbench and Data Repository]].	+	The concrete approach is as follows: The field data retrieved via the mobile device using the DiversityMobile client are stored in a database on this device. The central database DiversityCollection will eventually offer a set of definitions, e.g., lists of taxonomic names and project-specific settings to be uploaded. 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. 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 organised by a complex '''synchronisation process'''. This also concerns GPS and multimedia data. The user will access a synchronisation component via a special interface which will be installed on his personal computer. This component is installed at a data repository and is connected by the user, e.g. via the internet. The synchronization data are stored in another database. This database will be linking the data items on the client-side with data items on the server-side using Global Unique Identifiers (GUIDs).
		+
		+	The data processing at the data repository is picked out as a central theme of
		+
		+	* [[IBF Diversity Workbench and Data Repository]].
		+
		+	A technical repository will make accessible
		+
		+	*[[DiversityMobile Information Models]]
		+
		+	*[[DiversityMobile Applications]]
		+
		+	*[[Possible Devices for DiversityMobile]].

@@ 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 developped to enter, modify, or – if necessary – delete ecological and biological monitoring data in the field via a mobile device. The whole process is very complex and modelled by [[IBF Mobile Process Modeling]]. In the approach realised within the IBF context the data model of DiversityMobile is held fully compatible with the data model of DiversityCollection. This is the component for the storage of collection and observation data within the Diversity Workbench and fulfill the ABCD standard of TDWG. The field data retrieved via the mobile device using the DiversityMobile client are stored in a database on this device.
+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 developped to enter, modify, or – if necessary – delete ecological and biological monitoring data in the field via a mobile device. The whole process is very complex and modelled by [[IBF Mobile Process Modeling]]. In the concept which is realised within the IBF context the data model of DiversityMobile is held fully compatible with the data model of DiversityCollection. This is the component for the storage of collection and observation data within the Diversity Workbench and fulfill the ABCD standard of TDWG.
-The central database DiversityCollection will eventually offer a set of definitions, e.g., lists of taxonomic names and project-specific settings to be uploaded. 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. 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 organised by a complex '''synchronisation process'''. This also concerns GPS and multimedia data. The user will access a 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 will be linking the data items on the client-side with data items on the server-side using Global Unique Identifiers (GUIDs).
+The concrete approach is as follows: The field data retrieved via the mobile device using the DiversityMobile client are stored in a database on this device. The central database DiversityCollection will eventually offer a set of definitions, e.g., lists of taxonomic names and project-specific settings to be uploaded. 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. 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 organised by a complex '''synchronisation process'''. This also concerns GPS and multimedia data. The user will access a synchronisation component via a special interface which will be installed on his personal computer. This component is installed at a data repository and is connected by the user, e.g. via the internet. The synchronization data are stored in another database. This database will be linking the data items on the client-side with data items on the server-side using Global Unique Identifiers (GUIDs). The data processing at the data repository is picked out as a central theme of [[IBF Diversity Workbench and Data Repository]].

← Older revision		Revision as of 17:43, 2 November 2009
Line 1:		Line 1:
	The Diversity Workbench database framework consists of single application components collaborating through agreed software interfaces.		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 developped to enter, modify, or – if necessary – delete ecological and biological monitoring data in the field via a mobile device. The whole process is very complex and modelled by [[IBF Mobile Process Modeling]]. In the approach realised within the IBF context the data model of DiversityMobile is held fully compatible with the data model of DiversityCollection. This is the component for the storage of collection and observation data within the Diversity Workbench and fulfill the ABCD standard of TDWG. The field data retrieved via the mobile device using the DiversityMobile client are stored in a database on this device. The ~~mobile~~ database ~~is filled up with~~ a set of definitions, e.g., lists of taxonomic names and project-specific settings. Moreover, the user might choose to download field data from ~~the central database~~ 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. 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 organised by a complex synchronisation process. This also concerns GPS and multimedia data. The user will 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 will be linking the data items on the client-side with data items on the server-side using Global Unique Identifiers (GUIDs).	+	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 developped to enter, modify, or – if necessary – delete ecological and biological monitoring data in the field via a mobile device. The whole process is very complex and modelled by [[IBF Mobile Process Modeling]]. In the approach realised within the IBF context the data model of DiversityMobile is held fully compatible with the data model of DiversityCollection. This is the component for the storage of collection and observation data within the Diversity Workbench and fulfill the ABCD standard of TDWG. The field data retrieved via the mobile device using the DiversityMobile client are stored in a database on this device.
		+
		+	The central database DiversityCollection will eventually offer a set of definitions, e.g., lists of taxonomic names and project-specific settings to be uploaded. 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. 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 organised by a complex '''synchronisation process'''. This also concerns GPS and multimedia data. The user will access a 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 will be linking the data items on the client-side with data items on the server-side using Global Unique Identifiers (GUIDs).

← Older revision		Revision as of 17:39, 2 November 2009
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. ~~This~~ process is very complex and modelled by [[IBF Mobile Process Modeling]]. In ~~this~~ approach the data model of DiversityMobile is held 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~~, e. g. a smartphone~~. The database ~~on the smartphone~~ is filled up with 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 will 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 will be linking the data items on the client-side with data items on the server-side using Global Unique Identifiers (GUIDs).	+	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 developped to enter, modify, or – if necessary – delete ecological and biological monitoring data in the field via a mobile device. The whole process is very complex and modelled by [[IBF Mobile Process Modeling]]. In the approach realised within the IBF context the data model of DiversityMobile is held fully compatible with the data model of DiversityCollection. This is the component for the storage of collection and observation data within the Diversity Workbench and fulfill the ABCD standard of TDWG. The field data retrieved via the mobile device using the DiversityMobile client are stored in a database on this device. The mobile database is filled up with a set of definitions, e.g., lists of taxonomic names and project-specific settings. Moreover, the user might choose to download field data from the central database 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. 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 organised by a complex synchronisation process. This also concerns GPS and multimedia data. The user will 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 will be linking the data items on the client-side with data items on the server-side using Global Unique Identifiers (GUIDs).