Integrated Rules - Revision history

PeerSchwirtz: /* Check whether the value for measurement and fact is a number */

2012-11-07T11:25:18Z

Check whether the value for measurement and fact is a number

← Older revision		Revision as of 13:25, 7 November 2012
Line 172:		Line 172:

	/DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue		/DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue

	/DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue		/DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue

	/DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactText		/DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactText

	/DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactText		/DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactText

Line 179:		Line 182:

	MaF data type field values have to be a number		MaF data type field values have to be a number



	=== Check whether Record basis is mapped ===		=== Check whether Record basis is mapped ===

PeerSchwirtz at 10:03, 7 November 2012

2012-11-07T10:03:59Z

← Older revision		Revision as of 12:03, 7 November 2012
Line 4:		Line 4:


	=== 1 Atomized Genus elements should start with a single uppercase character followed ny a non-empty sequence of lower-case characters ===		=== Atomized Genus elements should start with a single uppercase character followed ny a non-empty sequence of lower-case characters ===


Line 19:		Line 19:


	=== 2 Check whether collection date fields conform to specification in ABCD 2.06 ===		=== Check whether collection date fields conform to specification in ABCD 2.06 ===


Line 35:		Line 35:


	=== 3 Check numeric ranges of site coordinates latitude value ===		=== Check numeric ranges of site coordinates latitude value ===


Line 48:		Line 48:


	=== 4 Check numeric ranges of site coordinates longitude value ===		=== Check numeric ranges of site coordinates longitude value ===


Line 61:		Line 61:


	=== 5 Check syntactical correctness of ABCD elements used for email addresses ===		=== Check syntactical correctness of ABCD elements used for email addresses ===


Line 73:		Line 73:


	=== 6 Check whether country element conforms with ISO3166 ===		=== Check whether country element conforms with ISO3166 ===


Line 86:		Line 86:


	=== 7 Check whether scientific name is known by zoological name service ===		=== Check whether scientific name is known by zoological name service ===


Line 99:		Line 99:


	=== 8 Check whether scientific name is known by botanical name service ===		=== Check whether scientific name is known by botanical name service ===


Line 113:		Line 113:


	=== 9 Check whether field for multimedia object type uses mime types ===		=== Check whether field for multimedia object type uses mime types ===


Line 127:		Line 127:


	=== 10 Check whether multimedia object file is available ===		=== Check whether multimedia object file is available ===


Line 140:		Line 140:


	=== 11 Check whether multimedia object has an associated copyright statement ===		=== Check whether multimedia object has an associated copyright statement ===


Line 153:		Line 153:


	=== 12 Check whether rule 7 and rule 8 find the scientific name ===		=== Check whether rule 7 and rule 8 find the scientific name ===


Line 166:		Line 166:


	=== 13 Check whether the value for measurement and fact is a number ===		=== Check whether the value for measurement and fact is a number ===


Line 182:		Line 182:


	=== 14 Check whether Record basis is mapped ===		=== Check whether Record basis is mapped ===

PeerSchwirtz at 10:02, 7 November 2012

2012-11-07T10:02:49Z

← Older revision		Revision as of 12:02, 7 November 2012
Line 1:		Line 1:
	This page is a working document containing an evolving set of rules which will be contineously implemented into the data integrity service and quality toolkit. So far, only a few examples have been included. The numbering scheme will also be used to specify the set of rules to be applied when using the integrity service.		This page is a working document containing an evolving set of rules which will be contineously implemented into the data integrity service and quality toolkit. So far, only a few examples have been included. The numbering scheme will also be used to specify the set of rules to be applied when using the integrity service.

			* ABCD Schema (http://www.bgbm.org/TDWG/CODATA/Schema/ABCD_1.20/ABCD-1.20.html#complexType_ReferenceType_Link03B5BC30)

PeerSchwirtz at 10:01, 7 November 2012

2012-11-07T10:01:08Z

← Older revision		Revision as of 12:01, 7 November 2012
Line 1:		Line 1:
	This page is a working document containing an evolving set of rules which will be contineously implemented into the data integrity service and quality toolkit. So far, only a few examples have been included. The numbering scheme will also be used to specify the set of rules to be applied when using the integrity service.		This page is a working document containing an evolving set of rules which will be contineously implemented into the data integrity service and quality toolkit. So far, only a few examples have been included. The numbering scheme will also be used to specify the set of rules to be applied when using the integrity service.

	~~----~~

PeerSchwirtz at 10:00, 7 November 2012

2012-11-07T10:00:56Z

← Older revision		Revision as of 12:00, 7 November 2012
Line 1:		Line 1:
	This page is a working document containing an evolving set of rules which will be contineously implemented into the data integrity service and quality toolkit. So far, only a few examples have been included. The numbering scheme will also be used to specify the set of rules to be applied when using the integrity service.		This page is a working document containing an evolving set of rules which will be contineously implemented into the data integrity service and quality toolkit. So far, only a few examples have been included. The numbering scheme will also be used to specify the set of rules to be applied when using the integrity service.


	----		----

PeerSchwirtz at 10:00, 7 November 2012

2012-11-07T10:00:44Z

← Older revision		Revision as of 12:00, 7 November 2012
Line 1:		Line 1:
	This page is a working document containing an evolving set of rules which will be contineously implemented into the data integrity service and quality toolkit. So far, only a few examples have been included. The numbering scheme will also be used to specify the set of rules to be applied when using the integrity service.		This page is a working document containing an evolving set of rules which will be contineously implemented into the data integrity service and quality toolkit. So far, only a few examples have been included. The numbering scheme will also be used to specify the set of rules to be applied when using the integrity service.


	----		----

PeerSchwirtz at 10:00, 7 November 2012

2012-11-07T10:00:29Z

← Older revision		Revision as of 12:00, 7 November 2012
Line 1:		Line 1:
	This page is a working document containing an evolving set of rules which will be contineously implemented into the data integrity service and quality toolkit. So far, only a few examples have been included. The numbering scheme will also be used to specify the set of rules to be applied when using the integrity service.		This page is a working document containing an evolving set of rules which will be contineously implemented into the data integrity service and quality toolkit. So far, only a few examples have been included. The numbering scheme will also be used to specify the set of rules to be applied when using the integrity service.



	~~== Integrity Rules ==~~


	~~1 Atomized Genus element~~
	~~2 Collection date fields~~
	~~3 Site coordinate latitude~~
	~~4 Site coordinate longitude~~
	~~5 Syntax of email elements~~
	~~6 ISO country element~~
	~~7 Scientific name (zoology)~~
	~~8 Scientific name (botany)~~
	~~9 Mime type for multimedia objects~~
	~~10 Check whether multimedia object file is available~~
	~~11 Check whether multimedia object has an associated copyright statement~~
	~~12 Check whether rule 7 and rule 8 find the scientific name~~
	~~13 Check whether the value for measurement and fact is a number~~
	~~14 Check whether Record basis is mapped~~



	----		----

PeerSchwirtz at 09:59, 7 November 2012

2012-11-07T09:59:55Z

← Older revision		Revision as of 11:59, 7 November 2012
Line 1:		Line 1:
	This page is a working document containing an evolving set of rules which will be contineously implemented into the data integrity service and quality toolkit. So far, only a few examples have been included. The numbering scheme will also be used to specify the set of rules to be applied when using the integrity service.		This page is a working document containing an evolving set of rules which will be contineously implemented into the data integrity service and quality toolkit. So far, only a few examples have been included. The numbering scheme will also be used to specify the set of rules to be applied when using the integrity service.


	~~----~~


Line 45:		Line 42:
	[A-Z][a-z]+		[A-Z][a-z]+






Line 65:		Line 59:






	=== 3 Check numeric ranges of site coordinates latitude value ===		=== 3 Check numeric ranges of site coordinates latitude value ===
Line 80:		Line 71:
	-90.0 <= lat <= 90.0		-90.0 <= lat <= 90.0






Line 97:		Line 85:




	=== 5 Check syntactical correctness of ABCD elements used for email addresses ===		=== 5 Check syntactical correctness of ABCD elements used for email addresses ===
Line 112:		Line 99:

	=== 6 Check whether country element conforms with ISO3166 ===		=== 6 Check whether country element conforms with ISO3166 ===



Line 124:		Line 112:

	=== 7 Check whether scientific name is known by zoological name service ===		=== 7 Check whether scientific name is known by zoological name service ===



Line 136:		Line 125:

	=== 8 Check whether scientific name is known by botanical name service ===		=== 8 Check whether scientific name is known by botanical name service ===



Line 159:		Line 149:

	Use http://www.ietf.org/rfc/rfc2046.txt		Use http://www.ietf.org/rfc/rfc2046.txt



Line 188:		Line 177:




	=== 12 Check whether rule 7 and rule 8 find the scientific name ===		=== 12 Check whether rule 7 and rule 8 find the scientific name ===
Line 201:		Line 189:
	Use rule 7 and rule 8		Use rule 7 and rule 8




Line 219:		Line 206:




	=== 14 Check whether Record basis is mapped ===		=== 14 Check whether Record basis is mapped ===

PeerSchwirtz: Created page with "This page is a working document containing an evolving set of rules which will be contineously implemented into the data integrity service and quality toolkit. So far, only a few..."

2012-11-07T09:56:04Z

Created page with "This page is a working document containing an evolving set of rules which will be contineously implemented into the data integrity service and quality toolkit. So far, only a few..."

New page

This page is a working document containing an evolving set of rules which will be contineously implemented into the data integrity service and quality toolkit. So far, only a few examples have been included. The numbering scheme will also be used to specify the set of rules to be applied when using the integrity service.

----

== Integrity Rules ==

1 Atomized Genus element
2 Collection date fields
3 Site coordinate latitude
4 Site coordinate longitude
5 Syntax of email elements
6 ISO country element
7 Scientific name (zoology)
8 Scientific name (botany)
9 Mime type for multimedia objects
10 Check whether multimedia object file is available
11 Check whether multimedia object has an associated copyright statement
12 Check whether rule 7 and rule 8 find the scientific name
13 Check whether the value for measurement and fact is a number
14 Check whether Record basis is mapped

----

=== 1 Atomized Genus elements should start with a single uppercase character followed ny a non-empty sequence of lower-case characters ===

ABCD elements:

/DataSets/DataSet/Units/Unit/Identifications/Identification/Result/TaxonIdentified/ScientificName/NameAtomised/Zoological/GenusOrMonomial
/DataSets/DataSet/Units/Unit/Identifications/Identification/Result/TaxonIdentified/ScientificName/NameAtomised/Botanical/GenusOrMonomial

Regular expression:

[A-Z][a-z]+

=== 2 Check whether collection date fields conform to specification in ABCD 2.06 ===

ABCD elements:

/DataSets/DataSet/Units/Unit/Gathering/DateTime/ISODateTimeBegin
/DataSets/DataSet/Units/Unit/Gathering/DateTime/ISODateTimeEnd
/DataSets/DataSet/Units/Unit/Identifications/Identification/Date/ISODateTimeBegin
/DataSets/DataSet/Units/Unit/Identifications/Identification/Date/ISODateTimeEnd

Regular expression:

\d\d\d\d(\-(0[1-9]|1[012])(\-((0[1-9])|1\d|2\d|3[01])(T(0\d|1\d|2[0-3])(:[0-5]\d){0,2})?)?)?|\-\-(0[1-9]|1[012])(\-(0[1-9]|1\d|2\d|3[01]))?|\-\-\-(0[1-9]|1\d|2\d|3[01])

=== 3 Check numeric ranges of site coordinates latitude value ===

ABCD elements:

/DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/LatitudeDecimal

Rule:

-90.0 <= lat <= 90.0

=== 4 Check numeric ranges of site coordinates longitude value ===

ABCD elements:

/DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/LongitudeDecimal

Rule:

-180.0 <= lon <= 180.0

=== 5 Check syntactical correctness of ABCD elements used for email addresses ===

ABCD elements:

All elements with email-addresses

Regular expression:

^([a-zA-Z0-9_\-\.\+]+)@([a-zA-Z0-9\-\.]+)$

=== 6 Check whether country element conforms with ISO3166 ===

ABCD elements:

/DataSets/DataSet/Units/Unit/Gathering/Country/ISO3166Code

Rule:

Use 2- or 3-letter ISO country code (ISO3166-1).

=== 7 Check whether scientific name is known by zoological name service ===

ABCD elements:

/DataSets/DataSet/Units/Unit/Identifications/Identification/Result/TaxonIdentified/ScientificName/FullScientificNameString

Rule:

Use Zoological Name Service

=== 8 Check whether scientific name is known by botanical name service ===

ABCD elements:

/DataSets/DataSet/Units/Unit/Identifications/Identification/Result/TaxonIdentified/ScientificName/FullScientificNameString

Rule:

Use Botanical Name Service

=== 9 Check whether field for multimedia object type uses mime types ===

ABCD elements:

/DataSets/DataSet/Units/Unit/MultiMediaObjects/MultiMediaObject/FileURI
/DataSets/DataSet/Units/Unit/MultiMediaObjects/MultiMediaObject/Format

Rule:

Use http://www.ietf.org/rfc/rfc2046.txt

=== 10 Check whether multimedia object file is available ===

ABCD elements:

/DataSets/DataSet/Units/Unit/MultiMediaObjects/MultiMediaObject/File

Rule:

HTTP HEAD request

=== 11 Check whether multimedia object has an associated copyright statement ===

ABCD elements:

/DataSets/DataSet/Units/Unit/MultiMediaObjects/MultiMediaObject/IPR/Copyrights/Copyright/Text

Rule:

Copyright element has to be non-empty.

=== 12 Check whether rule 7 and rule 8 find the scientific name ===

ABCD elements:

/DataSets/DataSet/Units/Unit/Identifications/Identification/Result/TaxonIdentified/ScientificName/FullScientificNameString

Rule:

Use rule 7 and rule 8

=== 13 Check whether the value for measurement and fact is a number ===

ABCD elements:

/DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/LowerValue
/DataSets/DataSet/Units/Unit/Gathering/Altitude/MeasurementOrFactAtomised/UpperValue
/DataSets/DataSet/Units/Unit/Gathering/Depth/MeasurementOrFactText
/DataSets/DataSet/Units/Unit/Gathering/Height/MeasurementOrFactText

Rule:

MaF data type field values have to be a number

=== 14 Check whether Record basis is mapped ===

ABCD elements:

/DataSets/DataSet/Units/Unit/RecordBasis

Rule:

Record basis field has to be mapped