DB Model 2014 - Revision history

Judy: /* gps. ee_tracker (table) */

2014-10-23T09:47:35Z

‎gps. ee_tracker (table)

2014-10-23T09:31:26Z

‎gps.ee_individual_limited (view)

2014-10-23T09:29:45Z

‎gps.ee_individual_limited (view)

2014-10-23T09:27:07Z

‎gps.ee_individual (table)

2014-10-23T09:05:25Z

‎gps.ee_shared_track_session_limited (view)

2014-10-23T08:34:33Z

‎Track sessions

2014-08-12T13:11:41Z

2014-08-12T13:11:06Z

2014-08-01T11:50:43Z

‎gps.uva_warning102 (table)

2014-08-01T11:49:03Z

‎gps.uva_trackingfile_messages (table)

@@ Line 790: / Line 790: @@
 |version||int4||YES||Optimistic locking field. Ignore it as a user.
 |-
-|x_o||numeric(30,6)||YES||Accelerometer calibration: offset on the x (or surge) axis
+|x_o||numeric(30,6)||YES||Accelerometer calibration: offset on the x (surge) axis
 |-
-|x_s||numeric(30,6)||YES||Accelerometer calibration: sensitivity on the x (or surge) axis
+|x_s||numeric(30,6)||YES||Accelerometer calibration: sensitivity on the x (surge) axis
 |-
-|y_o||numeric(30,6)||YES||Accelerometer calibration: offset on the y (or sway) axis
+|y_o||numeric(30,6)||YES||Accelerometer calibration: offset on the y (sway) axis
 |-
-|y_s||numeric(30,6)||YES||Accelerometer calibration: sensitivity on the y (or sway) axis
+|y_s||numeric(30,6)||YES||Accelerometer calibration: sensitivity on the y (sway) axis
 |-
-|z_o||numeric(30,6)||YES||Accelerometer calibration: offset on the z (or heave) axis
+|z_o||numeric(30,6)||YES||Accelerometer calibration: offset on the z (heave) axis
 |-
-|z_s||numeric(30,6)||YES||Accelerometer calibration: sensitivity on the y (or heave) axis
+|z_s||numeric(30,6)||YES||Accelerometer calibration: sensitivity on the y (heave) axis
 |}

@@ Line 467: / Line 467: @@
 Each row represents bird's details that your memberships allow you to see.
-This view replaces the old gps.uva_individual_limited.
+This view replaces the old gps.uva_individual_limited. It joins, among others, the following tables: ee_individual and ee_species.
 {| class="wikitable"

@@ Line 485: / Line 485: @@
 |sex||varchar||NO||Sex (M=male, F=female, X=unknown/unspecified)
 |-
-|mass||numeric(5,0)||YES||Mass (ideally, in grams)
+|mass||numeric(5,0)||YES||Mass (grams)
 |-
 |start_date||timestamp||NO||Date before which the bird is not relevant.

@@ Line 444: / Line 444: @@
 |end_date||timestamp||NO||Date at which the bird is no longer relevant
 |-
-|mass||numeric(5,0)||YES||Mass (ideally, in grams)
+|mass||numeric(5,0)||YES||Mass (grams)
 |-
 |operated_date||timestamp||NO||Recording of the last time the row was edited

@@ Line 86: / Line 86: @@
 ==== ''gps.''ee_''shared''_track_session_limited (view) ====
-Shows information of the track sessions that other projects are sharing with your projects and within which dates.
+In some cases you may be interested in sharing data from an individual bird with all users from a specific project, you can then provide that project with access to that individual bird for a specific period of time.  This is called "sharing".  To view information that has been shared with other projects, use the shared views. To make data available for viewing on the UvA-BiTS website each project administrator must also "share" the tracker for the period of interest with the website project (key_name = 'WWW').
 {| class="wikitable"

@@ Line 12: / Line 12: @@
 By editing the start and end dates, administrators of the project that this track session belongs to, can delimit (and therefore, establish) when the coupling makes sense (or is to be understood as useful).
-Whenever a tracker is attached to a bird, a track session must be started to indicate that the tracking data that is received is already live data. If the tracker is separated from the bird, the tracking data ceases to make sense, so the track session's end date should be set to denote it has ended. New track sessions can be started if the tracker is re-attached to a bird (possibly the same as before, or maybe a different one) afterwards.
+Whenever a tracker is attached to a bird, a track session must be started (start_date) to indicate that the tracking data that is received is already live data. If the tracker is separated from the bird, the tracking data ceases to make sense, so the track session's end date should be set to denote it has ended. New track sessions can be started if the tracker is re-attached to a bird (possibly the same as before, or maybe a different one) afterwards.
 ==== ''gps.''ee_track_session (table) ====

← Older revision		Revision as of 13:11, 12 August 2014
Line 1:		Line 1:
−	From the users' perspective, the database is split into two schemas: ''admin'' and ''gps''. The ''gps'' schema is meant for data that should be readily available for users, and that they may edit via the services (software tools) offered to that effect. The ''admin'' schema is meant to host data only accessible for the ~~administration users~~ of e-Ecology.	+	From the users' perspective, the database is split into two schemas: ''admin'' and ''gps''. The ''gps'' schema is meant for data that should be readily available for users, and that they may edit via the services (software tools) offered to that effect. The ''admin'' schema is meant to host data only accessible for the administrators of e-Ecology.

	The following tables are available		The following tables are available

← Older revision		Revision as of 11:50, 1 August 2014
Line 1,265:		Line 1,265:
	\|line\|\|text\|\|YES\|\|The actual line in the file		\|line\|\|text\|\|YES\|\|The actual line in the file
	\|}		\|}
		+
		+	==== ''gps.''ee_warning_limited (view) ====
		+
		+	Shows the warning data for trackers that your memberships allow you to see.
		+
		+	It has the same fields as [[#gps.uva_warning102 (table)\|gps.uva_warning102]].
		+
		+	It replaces the old gps.uva_warning_limited view.

@@ Line 1,238: / Line 1,238: @@
 |-
 |line_number||int4||YES||Line in the file where the message is reported
 |}