Data Package Quality Report
PackageId: knb-lter-cap.661.1
Report Date/Time: 2019-03-08T14:58:42
Dataset Report
#	Identifier	Status	Quality Check	Name	Description	Expected	Found	Explanation	Suggestion	Reference
1	packageIdPattern	valid	Type: metadata System: lter On failure: error	packageId pattern matches "scope.identifier.revision"	Check against LTER requirements for scope.identifier.revision	'scope.n.m', where 'n' and 'm' are integers and 'scope' is one of an allowed set of values	knb-lter-cap.661.1
2	emlVersion	valid	Type: metadata System: lter On failure: error	EML version 2.1.0 or beyond	Check the EML document declaration for version 2.1.0 or higher	eml://ecoinformatics.org/eml-2.1.0 or higher	eml://ecoinformatics.org/eml-2.1.1	Validity of this quality report is dependent on this check being valid.
3	schemaValid	valid	Type: metadata System: knb On failure: error	Document is schema-valid EML	Check document schema validity	schema-valid	Document validated for namespace: 'eml://ecoinformatics.org/eml-2.1.1'	Validity of this quality report is dependent on this check being valid.
4	parserValid	valid	Type: metadata System: knb On failure: error	Document is EML parser-valid	Check document using the EML IDs and references parser	Validates with the EML IDs and references parser	EML IDs and references parser succeeded	Validity of this quality report is dependent on this check being valid.
5	schemaValidDereferenced	valid	Type: metadata System: lter On failure: error	Dereferenced document is schema-valid EML	References are dereferenced, and the resulting file validated	schema-valid	Dereferenced document validated for namespace: 'eml://ecoinformatics.org/eml-2.1.1'	Validity of this quality report is dependent on this check being valid.
6	keywordPresent	valid	Type: metadata System: lter On failure: warn	keyword element is present	Checks to see if at least one keyword is present	Presence of one or more keyword elements	21 'keyword' element(s) found
7	methodsElementPresent	valid	Type: metadata System: lter On failure: warn	A 'methods' element is present	All datasets should contain a 'methods' element, at a minimum a link to a separate methods doc.	presence of 'methods' at one or more xpaths.	1 'methods' element(s) found			EML Best Practices, p. 28
8	coveragePresent	valid	Type: metadata System: lter On failure: warn	coverage element is present	At least one coverage element should be present in a dataset.	At least one of geographicCoverage, taxonomicCoverage, or temporalCoverage is present in the EML.	1 'coverage' element(s) found
9	geographicCoveragePresent	info	Type: metadata System: lter On failure: info	geographicCoverage is present	Check that geographicCoverage exists in EML at the dataset level, or at least one entity's level, or at least one attribute's level.	geographicCoverage at least at the dataset level.	1 'geographicCoverage' element(s) found	Many but not all datasets are appropriate to have spatial coverage.	If sampling EML is used within methods, does that obviate geographicCoverage? Or should those sites be repeated or referenced?	EML Best Practices v.2, p. 22-23. "One geographicCoverage element should be included, whose boundingCoordinates describe the extent of the data....Additional geographicCoverage elements may be entered at the dataset level if there are significant distances between study sites and it would be confusing if they were grouped into one bounding box." 6 decimal places.
10	taxonomicCoveragePresent	info	Type: metadata System: lter On failure: info	taxonomicCoverage is present	Check that taxonomicCoverage exists in EML at the dataset level, or at least one entity's level, or at least one attribute's level.	taxonomicCoverage at least at the dataset level.	0 'taxonomicCoverage' element(s) found	Only when taxa are pertinent to the dataset will they have taxonomicCoverage.	Could search title, abstract, keywords for any taxonomic name (huge). Could search keywordType="taxonomic".	EML Best Practices v.2, p. 25
11	temporalCoveragePresent	info	Type: metadata System: lter On failure: info	temporalCoverage is present	Check that temporalCoverage exists in EML at the dataset level, or at least one entity's level, or at least one attribute's level.	temporalCoverage at least at the dataset level.	1 'temporalCoverage' element(s) found	LTER wants to search datasets by time; the best place to search is the dataset level temporal coverage.	Most datasets have a temporal range.	EML Best Practices v.2, p. 24
12	pastaDoiAbsent	valid	Type: metadata System: lter On failure: error	An alternateIdentifier with a DOI system attribute that looks like it is generated by PASTA should not be present	Reject the data package if it contains an alternateIdentifier DOI that looks like PASTA generated it.	No PASTA DOIs are expected to be found in the uploaded data package	No PASTA DOI alternateIdentifier elements found	PASTA DOI values might appear in an uploaded data package (by various mechanisms). PASTA will assign a DOI after the upload has completed successfully, so an initial one should not be there.
13	titleLength	valid	Type: metadata System: lter On failure: warn	Dataset title length is at 5 least words.	If the title is shorter than 5 words, it might be insufficient. Title word count between 7 and 20 including prepositions and numbers.	Between 7 and 20 words	15 words found.			EML Best Practices, v.2, p. 13
14	fundingPresence	warn	Type: metadata System: lter On failure: warn	check to see if funding element is present	Checks to see if the funding element is included.	the funding element is expected to be included	funding not found	Searches will want to display datasets by funder or grant id.	Include the funding source, please.
15	pubDatePresent	valid	Type: metadata System: lter On failure: warn	'pubDate' element is present	Check for presence of the pubDate element	The date that the dataset was submitted for publication in PASTA must be included. (The EML schema does not require this element, but when present, it does constrain its format to YYYY-MM-DD or just YYYY. Citation format uses only the YYYY portion even if a full date is entered.)	2019-03-08			EML Best Practices v.2, p. 17
16	datasetAbstractLength	valid	Type: metadata System: lter On failure: warn	Dataset abstract element is a minimum of 20 words	Check the length of a dataset abstract and warn if less than 20 words.	An abstract is 20 words or more.	207 words found.			EML Best Practices
17	duplicateEntityName	valid	Type: metadata System: lter On failure: error	There are no duplicate entity names	Checks that content is not duplicated by other entityName elements in the document	entityName is not a duplicate within the document	No duplicates found	Data Manager requires a non-empty, non-duplicate entityName value for every entity	Declare a non-empty entityName and ensure that there are no duplicate entityName values in the document
Entity Report
Entity Name: 661_annual_mean_temperature_3c8318355e8992464a6f349b9a356b3d.zip
Entity Identifier: 661_annual_mean_temperature_3c8318355e8992464a6f349b9a356b3d.zip
#	Identifier	Status	Quality Check	Name	Description	Expected	Found	Explanation	Suggestion	Reference
1	entityNameLength	valid	Type: metadata System: knb On failure: warn	Length of entityName is not excessive (less than 100 char)	length of entity name is less than 100 characters	entityName value is 100 characters or less	64
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	integrityChecksumPresence	valid	Type: metadata System: lter On failure: warn	A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1	Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.	At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.	true	PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.	Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
8	displayDownloadData	info	Type: data System: knb On failure: info	Display downloaded data	Display the first kilobyte of data that is downloaded	Up to one kilobyte of data should be displayed	*** BINARY DATA ***
9	urlReturnsData	valid	Type: congruency System: knb On failure: error	URL returns data	Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.	A data entity that matches the metadata	true			http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
10	onlineURLs	valid	Type: congruency System: knb On failure: error	Online URLs are live	Check that online URLs return something	true	true	Succeeded in accessing URL: https://data.gios.asu.edu/datasets/cap/661_annual_mean_temperature_3c8318355e8992464a6f349b9a356b3d.zip
11	integrityChecksum	valid	Type: congruency System: lter On failure: error	Compare the metadata checksum for an entity to the checksum of the downloaded entity	Two possible responses: valid if checksums match; error if checksums do not match.	3c8318355e8992464a6f349b9a356b3d	3c8318355e8992464a6f349b9a356b3d	Matching checksums will ensure data integrity during upload to the repository.	If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
Entity Report
Entity Name: 661_annual_precip_2202aab124d96592360dacb80eeabd62.zip
Entity Identifier: 661_annual_precip_2202aab124d96592360dacb80eeabd62.zip
#	Identifier	Status	Quality Check	Name	Description	Expected	Found	Explanation	Suggestion	Reference
1	entityNameLength	valid	Type: metadata System: knb On failure: warn	Length of entityName is not excessive (less than 100 char)	length of entity name is less than 100 characters	entityName value is 100 characters or less	54
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	integrityChecksumPresence	valid	Type: metadata System: lter On failure: warn	A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1	Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.	At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.	true	PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.	Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
8	displayDownloadData	info	Type: data System: knb On failure: info	Display downloaded data	Display the first kilobyte of data that is downloaded	Up to one kilobyte of data should be displayed	*** BINARY DATA ***
9	urlReturnsData	valid	Type: congruency System: knb On failure: error	URL returns data	Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.	A data entity that matches the metadata	true			http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
10	onlineURLs	valid	Type: congruency System: knb On failure: error	Online URLs are live	Check that online URLs return something	true	true	Succeeded in accessing URL: https://data.gios.asu.edu/datasets/cap/661_annual_precip_2202aab124d96592360dacb80eeabd62.zip
11	integrityChecksum	valid	Type: congruency System: lter On failure: error	Compare the metadata checksum for an entity to the checksum of the downloaded entity	Two possible responses: valid if checksums match; error if checksums do not match.	2202aab124d96592360dacb80eeabd62	2202aab124d96592360dacb80eeabd62	Matching checksums will ensure data integrity during upload to the repository.	If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
Entity Report
Entity Name: 661_isothermality_b3067855893567b0950e6e02593579bc.zip
Entity Identifier: 661_isothermality_b3067855893567b0950e6e02593579bc.zip
#	Identifier	Status	Quality Check	Name	Description	Expected	Found	Explanation	Suggestion	Reference
1	entityNameLength	valid	Type: metadata System: knb On failure: warn	Length of entityName is not excessive (less than 100 char)	length of entity name is less than 100 characters	entityName value is 100 characters or less	54
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	integrityChecksumPresence	valid	Type: metadata System: lter On failure: warn	A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1	Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.	At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.	true	PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.	Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
8	displayDownloadData	info	Type: data System: knb On failure: info	Display downloaded data	Display the first kilobyte of data that is downloaded	Up to one kilobyte of data should be displayed	*** BINARY DATA ***
9	urlReturnsData	valid	Type: congruency System: knb On failure: error	URL returns data	Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.	A data entity that matches the metadata	true			http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
10	onlineURLs	valid	Type: congruency System: knb On failure: error	Online URLs are live	Check that online URLs return something	true	true	Succeeded in accessing URL: https://data.gios.asu.edu/datasets/cap/661_isothermality_b3067855893567b0950e6e02593579bc.zip
11	integrityChecksum	valid	Type: congruency System: lter On failure: error	Compare the metadata checksum for an entity to the checksum of the downloaded entity	Two possible responses: valid if checksums match; error if checksums do not match.	b3067855893567b0950e6e02593579bc	b3067855893567b0950e6e02593579bc	Matching checksums will ensure data integrity during upload to the repository.	If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
Entity Report
Entity Name: 661_max_temperature_2856a0f483cbb72cee89193118ee883f.zip
Entity Identifier: 661_max_temperature_2856a0f483cbb72cee89193118ee883f.zip
#	Identifier	Status	Quality Check	Name	Description	Expected	Found	Explanation	Suggestion	Reference
1	entityNameLength	valid	Type: metadata System: knb On failure: warn	Length of entityName is not excessive (less than 100 char)	length of entity name is less than 100 characters	entityName value is 100 characters or less	56
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	integrityChecksumPresence	valid	Type: metadata System: lter On failure: warn	A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1	Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.	At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.	true	PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.	Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
8	displayDownloadData	info	Type: data System: knb On failure: info	Display downloaded data	Display the first kilobyte of data that is downloaded	Up to one kilobyte of data should be displayed	*** BINARY DATA ***
9	urlReturnsData	valid	Type: congruency System: knb On failure: error	URL returns data	Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.	A data entity that matches the metadata	true			http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
10	onlineURLs	valid	Type: congruency System: knb On failure: error	Online URLs are live	Check that online URLs return something	true	true	Succeeded in accessing URL: https://data.gios.asu.edu/datasets/cap/661_max_temperature_2856a0f483cbb72cee89193118ee883f.zip
11	integrityChecksum	valid	Type: congruency System: lter On failure: error	Compare the metadata checksum for an entity to the checksum of the downloaded entity	Two possible responses: valid if checksums match; error if checksums do not match.	2856a0f483cbb72cee89193118ee883f	2856a0f483cbb72cee89193118ee883f	Matching checksums will ensure data integrity during upload to the repository.	If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
Entity Report
Entity Name: 661_mean_precip_coldest_0de6132d57d4af9f378e89b7e98106a7.zip
Entity Identifier: 661_mean_precip_coldest_0de6132d57d4af9f378e89b7e98106a7.zip
#	Identifier	Status	Quality Check	Name	Description	Expected	Found	Explanation	Suggestion	Reference
1	entityNameLength	valid	Type: metadata System: knb On failure: warn	Length of entityName is not excessive (less than 100 char)	length of entity name is less than 100 characters	entityName value is 100 characters or less	60
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	integrityChecksumPresence	valid	Type: metadata System: lter On failure: warn	A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1	Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.	At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.	true	PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.	Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
8	displayDownloadData	info	Type: data System: knb On failure: info	Display downloaded data	Display the first kilobyte of data that is downloaded	Up to one kilobyte of data should be displayed	*** BINARY DATA ***
9	urlReturnsData	valid	Type: congruency System: knb On failure: error	URL returns data	Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.	A data entity that matches the metadata	true			http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
10	onlineURLs	valid	Type: congruency System: knb On failure: error	Online URLs are live	Check that online URLs return something	true	true	Succeeded in accessing URL: https://data.gios.asu.edu/datasets/cap/661_mean_precip_coldest_0de6132d57d4af9f378e89b7e98106a7.zip
11	integrityChecksum	valid	Type: congruency System: lter On failure: error	Compare the metadata checksum for an entity to the checksum of the downloaded entity	Two possible responses: valid if checksums match; error if checksums do not match.	0de6132d57d4af9f378e89b7e98106a7	0de6132d57d4af9f378e89b7e98106a7	Matching checksums will ensure data integrity during upload to the repository.	If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
Entity Report
Entity Name: 661_mean_precip_driest_98b0616ba92514dd5ab29312fb5aaf30.zip
Entity Identifier: 661_mean_precip_driest_98b0616ba92514dd5ab29312fb5aaf30.zip
#	Identifier	Status	Quality Check	Name	Description	Expected	Found	Explanation	Suggestion	Reference
1	entityNameLength	valid	Type: metadata System: knb On failure: warn	Length of entityName is not excessive (less than 100 char)	length of entity name is less than 100 characters	entityName value is 100 characters or less	59
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	integrityChecksumPresence	valid	Type: metadata System: lter On failure: warn	A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1	Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.	At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.	true	PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.	Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
8	displayDownloadData	info	Type: data System: knb On failure: info	Display downloaded data	Display the first kilobyte of data that is downloaded	Up to one kilobyte of data should be displayed	*** BINARY DATA ***
9	urlReturnsData	valid	Type: congruency System: knb On failure: error	URL returns data	Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.	A data entity that matches the metadata	true			http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
10	onlineURLs	valid	Type: congruency System: knb On failure: error	Online URLs are live	Check that online URLs return something	true	true	Succeeded in accessing URL: https://data.gios.asu.edu/datasets/cap/661_mean_precip_driest_98b0616ba92514dd5ab29312fb5aaf30.zip
11	integrityChecksum	valid	Type: congruency System: lter On failure: error	Compare the metadata checksum for an entity to the checksum of the downloaded entity	Two possible responses: valid if checksums match; error if checksums do not match.	98b0616ba92514dd5ab29312fb5aaf30	98b0616ba92514dd5ab29312fb5aaf30	Matching checksums will ensure data integrity during upload to the repository.	If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
Entity Report
Entity Name: 661_mean_precip_warmest_c8f5f277db79dd6ebad5a7e1b0f48357.zip
Entity Identifier: 661_mean_precip_warmest_c8f5f277db79dd6ebad5a7e1b0f48357.zip
#	Identifier	Status	Quality Check	Name	Description	Expected	Found	Explanation	Suggestion	Reference
1	entityNameLength	valid	Type: metadata System: knb On failure: warn	Length of entityName is not excessive (less than 100 char)	length of entity name is less than 100 characters	entityName value is 100 characters or less	60
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	integrityChecksumPresence	valid	Type: metadata System: lter On failure: warn	A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1	Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.	At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.	true	PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.	Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
8	displayDownloadData	info	Type: data System: knb On failure: info	Display downloaded data	Display the first kilobyte of data that is downloaded	Up to one kilobyte of data should be displayed	*** BINARY DATA ***
9	urlReturnsData	valid	Type: congruency System: knb On failure: error	URL returns data	Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.	A data entity that matches the metadata	true			http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
10	onlineURLs	valid	Type: congruency System: knb On failure: error	Online URLs are live	Check that online URLs return something	true	true	Succeeded in accessing URL: https://data.gios.asu.edu/datasets/cap/661_mean_precip_warmest_c8f5f277db79dd6ebad5a7e1b0f48357.zip
11	integrityChecksum	valid	Type: congruency System: lter On failure: error	Compare the metadata checksum for an entity to the checksum of the downloaded entity	Two possible responses: valid if checksums match; error if checksums do not match.	c8f5f277db79dd6ebad5a7e1b0f48357	c8f5f277db79dd6ebad5a7e1b0f48357	Matching checksums will ensure data integrity during upload to the repository.	If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
Entity Report
Entity Name: 661_mean_precip_wettest_9f71bcad742d9b8bcb09b65ed4055800.zip
Entity Identifier: 661_mean_precip_wettest_9f71bcad742d9b8bcb09b65ed4055800.zip
#	Identifier	Status	Quality Check	Name	Description	Expected	Found	Explanation	Suggestion	Reference
1	entityNameLength	valid	Type: metadata System: knb On failure: warn	Length of entityName is not excessive (less than 100 char)	length of entity name is less than 100 characters	entityName value is 100 characters or less	60
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	integrityChecksumPresence	valid	Type: metadata System: lter On failure: warn	A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1	Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.	At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.	true	PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.	Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
8	displayDownloadData	info	Type: data System: knb On failure: info	Display downloaded data	Display the first kilobyte of data that is downloaded	Up to one kilobyte of data should be displayed	*** BINARY DATA ***
9	urlReturnsData	valid	Type: congruency System: knb On failure: error	URL returns data	Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.	A data entity that matches the metadata	true			http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
10	onlineURLs	valid	Type: congruency System: knb On failure: error	Online URLs are live	Check that online URLs return something	true	true	Succeeded in accessing URL: https://data.gios.asu.edu/datasets/cap/661_mean_precip_wettest_9f71bcad742d9b8bcb09b65ed4055800.zip
11	integrityChecksum	valid	Type: congruency System: lter On failure: error	Compare the metadata checksum for an entity to the checksum of the downloaded entity	Two possible responses: valid if checksums match; error if checksums do not match.	9f71bcad742d9b8bcb09b65ed4055800	9f71bcad742d9b8bcb09b65ed4055800	Matching checksums will ensure data integrity during upload to the repository.	If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
Entity Report
Entity Name: 661_mean_temperature_coldest_b5ce4f7f5c9d1f5fad73420664614c2d.zip
Entity Identifier: 661_mean_temperature_coldest_b5ce4f7f5c9d1f5fad73420664614c2d.zip
#	Identifier	Status	Quality Check	Name	Description	Expected	Found	Explanation	Suggestion	Reference
1	entityNameLength	valid	Type: metadata System: knb On failure: warn	Length of entityName is not excessive (less than 100 char)	length of entity name is less than 100 characters	entityName value is 100 characters or less	65
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	integrityChecksumPresence	valid	Type: metadata System: lter On failure: warn	A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1	Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.	At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.	true	PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.	Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
8	displayDownloadData	info	Type: data System: knb On failure: info	Display downloaded data	Display the first kilobyte of data that is downloaded	Up to one kilobyte of data should be displayed	*** BINARY DATA ***
9	urlReturnsData	valid	Type: congruency System: knb On failure: error	URL returns data	Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.	A data entity that matches the metadata	true			http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
10	onlineURLs	valid	Type: congruency System: knb On failure: error	Online URLs are live	Check that online URLs return something	true	true	Succeeded in accessing URL: https://data.gios.asu.edu/datasets/cap/661_mean_temperature_coldest_b5ce4f7f5c9d1f5fad73420664614c2d.zip
11	integrityChecksum	valid	Type: congruency System: lter On failure: error	Compare the metadata checksum for an entity to the checksum of the downloaded entity	Two possible responses: valid if checksums match; error if checksums do not match.	b5ce4f7f5c9d1f5fad73420664614c2d	b5ce4f7f5c9d1f5fad73420664614c2d	Matching checksums will ensure data integrity during upload to the repository.	If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
Entity Report
Entity Name: 661_mean_temperature_driest_d7aa435330040e28a8d050fa6eae0146.zip
Entity Identifier: 661_mean_temperature_driest_d7aa435330040e28a8d050fa6eae0146.zip
#	Identifier	Status	Quality Check	Name	Description	Expected	Found	Explanation	Suggestion	Reference
1	entityNameLength	valid	Type: metadata System: knb On failure: warn	Length of entityName is not excessive (less than 100 char)	length of entity name is less than 100 characters	entityName value is 100 characters or less	64
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	integrityChecksumPresence	valid	Type: metadata System: lter On failure: warn	A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1	Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.	At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.	true	PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.	Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
8	displayDownloadData	info	Type: data System: knb On failure: info	Display downloaded data	Display the first kilobyte of data that is downloaded	Up to one kilobyte of data should be displayed	*** BINARY DATA ***
9	urlReturnsData	valid	Type: congruency System: knb On failure: error	URL returns data	Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.	A data entity that matches the metadata	true			http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
10	onlineURLs	valid	Type: congruency System: knb On failure: error	Online URLs are live	Check that online URLs return something	true	true	Succeeded in accessing URL: https://data.gios.asu.edu/datasets/cap/661_mean_temperature_driest_d7aa435330040e28a8d050fa6eae0146.zip
11	integrityChecksum	valid	Type: congruency System: lter On failure: error	Compare the metadata checksum for an entity to the checksum of the downloaded entity	Two possible responses: valid if checksums match; error if checksums do not match.	d7aa435330040e28a8d050fa6eae0146	d7aa435330040e28a8d050fa6eae0146	Matching checksums will ensure data integrity during upload to the repository.	If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
Entity Report
Entity Name: 661_mean_temperature_warmest_006c0ea2f6fbc63256bcfbf50c782e7d.zip
Entity Identifier: 661_mean_temperature_warmest_006c0ea2f6fbc63256bcfbf50c782e7d.zip
#	Identifier	Status	Quality Check	Name	Description	Expected	Found	Explanation	Suggestion	Reference
1	entityNameLength	valid	Type: metadata System: knb On failure: warn	Length of entityName is not excessive (less than 100 char)	length of entity name is less than 100 characters	entityName value is 100 characters or less	65
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	integrityChecksumPresence	valid	Type: metadata System: lter On failure: warn	A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1	Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.	At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.	true	PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.	Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
8	displayDownloadData	info	Type: data System: knb On failure: info	Display downloaded data	Display the first kilobyte of data that is downloaded	Up to one kilobyte of data should be displayed	*** BINARY DATA ***
9	urlReturnsData	valid	Type: congruency System: knb On failure: error	URL returns data	Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.	A data entity that matches the metadata	true			http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
10	onlineURLs	valid	Type: congruency System: knb On failure: error	Online URLs are live	Check that online URLs return something	true	true	Succeeded in accessing URL: https://data.gios.asu.edu/datasets/cap/661_mean_temperature_warmest_006c0ea2f6fbc63256bcfbf50c782e7d.zip
11	integrityChecksum	valid	Type: congruency System: lter On failure: error	Compare the metadata checksum for an entity to the checksum of the downloaded entity	Two possible responses: valid if checksums match; error if checksums do not match.	006c0ea2f6fbc63256bcfbf50c782e7d	006c0ea2f6fbc63256bcfbf50c782e7d	Matching checksums will ensure data integrity during upload to the repository.	If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
Entity Report
Entity Name: 661_mean_temperature_wettest_1de2e6fe41727d74055bafe4da800d16.zip
Entity Identifier: 661_mean_temperature_wettest_1de2e6fe41727d74055bafe4da800d16.zip
#	Identifier	Status	Quality Check	Name	Description	Expected	Found	Explanation	Suggestion	Reference
1	entityNameLength	valid	Type: metadata System: knb On failure: warn	Length of entityName is not excessive (less than 100 char)	length of entity name is less than 100 characters	entityName value is 100 characters or less	65
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	integrityChecksumPresence	valid	Type: metadata System: lter On failure: warn	A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1	Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.	At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.	true	PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.	Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
8	displayDownloadData	info	Type: data System: knb On failure: info	Display downloaded data	Display the first kilobyte of data that is downloaded	Up to one kilobyte of data should be displayed	*** BINARY DATA ***
9	urlReturnsData	valid	Type: congruency System: knb On failure: error	URL returns data	Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.	A data entity that matches the metadata	true			http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
10	onlineURLs	valid	Type: congruency System: knb On failure: error	Online URLs are live	Check that online URLs return something	true	true	Succeeded in accessing URL: https://data.gios.asu.edu/datasets/cap/661_mean_temperature_wettest_1de2e6fe41727d74055bafe4da800d16.zip
11	integrityChecksum	valid	Type: congruency System: lter On failure: error	Compare the metadata checksum for an entity to the checksum of the downloaded entity	Two possible responses: valid if checksums match; error if checksums do not match.	1de2e6fe41727d74055bafe4da800d16	1de2e6fe41727d74055bafe4da800d16	Matching checksums will ensure data integrity during upload to the repository.	If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
Entity Report
Entity Name: 661_min_temperature_527e9c5bd72cf94329669f83a1ae61b8.zip
Entity Identifier: 661_min_temperature_527e9c5bd72cf94329669f83a1ae61b8.zip
#	Identifier	Status	Quality Check	Name	Description	Expected	Found	Explanation	Suggestion	Reference
1	entityNameLength	valid	Type: metadata System: knb On failure: warn	Length of entityName is not excessive (less than 100 char)	length of entity name is less than 100 characters	entityName value is 100 characters or less	56
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	integrityChecksumPresence	valid	Type: metadata System: lter On failure: warn	A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1	Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.	At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.	true	PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.	Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
8	displayDownloadData	info	Type: data System: knb On failure: info	Display downloaded data	Display the first kilobyte of data that is downloaded	Up to one kilobyte of data should be displayed	*** BINARY DATA ***
9	urlReturnsData	valid	Type: congruency System: knb On failure: error	URL returns data	Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.	A data entity that matches the metadata	true			http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
10	onlineURLs	valid	Type: congruency System: knb On failure: error	Online URLs are live	Check that online URLs return something	true	true	Succeeded in accessing URL: https://data.gios.asu.edu/datasets/cap/661_min_temperature_527e9c5bd72cf94329669f83a1ae61b8.zip
11	integrityChecksum	valid	Type: congruency System: lter On failure: error	Compare the metadata checksum for an entity to the checksum of the downloaded entity	Two possible responses: valid if checksums match; error if checksums do not match.	527e9c5bd72cf94329669f83a1ae61b8	527e9c5bd72cf94329669f83a1ae61b8	Matching checksums will ensure data integrity during upload to the repository.	If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
Entity Report
Entity Name: 661_precip_driest_dec9e83843777ab876e500ab9f844e8a.zip
Entity Identifier: 661_precip_driest_dec9e83843777ab876e500ab9f844e8a.zip
#	Identifier	Status	Quality Check	Name	Description	Expected	Found	Explanation	Suggestion	Reference
1	entityNameLength	valid	Type: metadata System: knb On failure: warn	Length of entityName is not excessive (less than 100 char)	length of entity name is less than 100 characters	entityName value is 100 characters or less	54
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	integrityChecksumPresence	valid	Type: metadata System: lter On failure: warn	A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1	Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.	At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.	true	PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.	Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
8	displayDownloadData	info	Type: data System: knb On failure: info	Display downloaded data	Display the first kilobyte of data that is downloaded	Up to one kilobyte of data should be displayed	*** BINARY DATA ***
9	urlReturnsData	valid	Type: congruency System: knb On failure: error	URL returns data	Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.	A data entity that matches the metadata	true			http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
10	onlineURLs	valid	Type: congruency System: knb On failure: error	Online URLs are live	Check that online URLs return something	true	true	Succeeded in accessing URL: https://data.gios.asu.edu/datasets/cap/661_precip_driest_dec9e83843777ab876e500ab9f844e8a.zip
11	integrityChecksum	valid	Type: congruency System: lter On failure: error	Compare the metadata checksum for an entity to the checksum of the downloaded entity	Two possible responses: valid if checksums match; error if checksums do not match.	dec9e83843777ab876e500ab9f844e8a	dec9e83843777ab876e500ab9f844e8a	Matching checksums will ensure data integrity during upload to the repository.	If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
Entity Report
Entity Name: 661_precip_seasonality_cb12ed8b2b18d0fe3e8f830d7ca72fbd.zip
Entity Identifier: 661_precip_seasonality_cb12ed8b2b18d0fe3e8f830d7ca72fbd.zip
#	Identifier	Status	Quality Check	Name	Description	Expected	Found	Explanation	Suggestion	Reference
1	entityNameLength	valid	Type: metadata System: knb On failure: warn	Length of entityName is not excessive (less than 100 char)	length of entity name is less than 100 characters	entityName value is 100 characters or less	59
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	integrityChecksumPresence	valid	Type: metadata System: lter On failure: warn	A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1	Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.	At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.	true	PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.	Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
8	displayDownloadData	info	Type: data System: knb On failure: info	Display downloaded data	Display the first kilobyte of data that is downloaded	Up to one kilobyte of data should be displayed	*** BINARY DATA ***
9	urlReturnsData	valid	Type: congruency System: knb On failure: error	URL returns data	Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.	A data entity that matches the metadata	true			http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
10	onlineURLs	valid	Type: congruency System: knb On failure: error	Online URLs are live	Check that online URLs return something	true	true	Succeeded in accessing URL: https://data.gios.asu.edu/datasets/cap/661_precip_seasonality_cb12ed8b2b18d0fe3e8f830d7ca72fbd.zip
11	integrityChecksum	valid	Type: congruency System: lter On failure: error	Compare the metadata checksum for an entity to the checksum of the downloaded entity	Two possible responses: valid if checksums match; error if checksums do not match.	cb12ed8b2b18d0fe3e8f830d7ca72fbd	cb12ed8b2b18d0fe3e8f830d7ca72fbd	Matching checksums will ensure data integrity during upload to the repository.	If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
Entity Report
Entity Name: 661_precip_wettest_b3a97bf308467a707dc2b9e21190da2d.zip
Entity Identifier: 661_precip_wettest_b3a97bf308467a707dc2b9e21190da2d.zip
#	Identifier	Status	Quality Check	Name	Description	Expected	Found	Explanation	Suggestion	Reference
1	entityNameLength	valid	Type: metadata System: knb On failure: warn	Length of entityName is not excessive (less than 100 char)	length of entity name is less than 100 characters	entityName value is 100 characters or less	55
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	integrityChecksumPresence	valid	Type: metadata System: lter On failure: warn	A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1	Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.	At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.	true	PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.	Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
8	displayDownloadData	info	Type: data System: knb On failure: info	Display downloaded data	Display the first kilobyte of data that is downloaded	Up to one kilobyte of data should be displayed	*** BINARY DATA ***
9	urlReturnsData	valid	Type: congruency System: knb On failure: error	URL returns data	Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.	A data entity that matches the metadata	true			http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
10	onlineURLs	valid	Type: congruency System: knb On failure: error	Online URLs are live	Check that online URLs return something	true	true	Succeeded in accessing URL: https://data.gios.asu.edu/datasets/cap/661_precip_wettest_b3a97bf308467a707dc2b9e21190da2d.zip
11	integrityChecksum	valid	Type: congruency System: lter On failure: error	Compare the metadata checksum for an entity to the checksum of the downloaded entity	Two possible responses: valid if checksums match; error if checksums do not match.	b3a97bf308467a707dc2b9e21190da2d	b3a97bf308467a707dc2b9e21190da2d	Matching checksums will ensure data integrity during upload to the repository.	If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
Entity Report
Entity Name: 661_temperature_annual_range_88da06649a42b7c95d7aa11d83992b11.zip
Entity Identifier: 661_temperature_annual_range_88da06649a42b7c95d7aa11d83992b11.zip
#	Identifier	Status	Quality Check	Name	Description	Expected	Found	Explanation	Suggestion	Reference
1	entityNameLength	valid	Type: metadata System: knb On failure: warn	Length of entityName is not excessive (less than 100 char)	length of entity name is less than 100 characters	entityName value is 100 characters or less	65
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	integrityChecksumPresence	valid	Type: metadata System: lter On failure: warn	A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1	Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.	At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.	true	PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.	Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
8	displayDownloadData	info	Type: data System: knb On failure: info	Display downloaded data	Display the first kilobyte of data that is downloaded	Up to one kilobyte of data should be displayed	*** BINARY DATA ***
9	urlReturnsData	valid	Type: congruency System: knb On failure: error	URL returns data	Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.	A data entity that matches the metadata	true			http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
10	onlineURLs	valid	Type: congruency System: knb On failure: error	Online URLs are live	Check that online URLs return something	true	true	Succeeded in accessing URL: https://data.gios.asu.edu/datasets/cap/661_temperature_annual_range_88da06649a42b7c95d7aa11d83992b11.zip
11	integrityChecksum	valid	Type: congruency System: lter On failure: error	Compare the metadata checksum for an entity to the checksum of the downloaded entity	Two possible responses: valid if checksums match; error if checksums do not match.	88da06649a42b7c95d7aa11d83992b11	88da06649a42b7c95d7aa11d83992b11	Matching checksums will ensure data integrity during upload to the repository.	If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
Entity Report
Entity Name: 661_temperature_diurnal_range_a2a916c22f835d726d750b79efb0a7e7.zip
Entity Identifier: 661_temperature_diurnal_range_a2a916c22f835d726d750b79efb0a7e7.zip
#	Identifier	Status	Quality Check	Name	Description	Expected	Found	Explanation	Suggestion	Reference
1	entityNameLength	valid	Type: metadata System: knb On failure: warn	Length of entityName is not excessive (less than 100 char)	length of entity name is less than 100 characters	entityName value is 100 characters or less	66
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	integrityChecksumPresence	valid	Type: metadata System: lter On failure: warn	A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1	Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.	At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.	true	PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.	Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
8	displayDownloadData	info	Type: data System: knb On failure: info	Display downloaded data	Display the first kilobyte of data that is downloaded	Up to one kilobyte of data should be displayed	*** BINARY DATA ***
9	urlReturnsData	valid	Type: congruency System: knb On failure: error	URL returns data	Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.	A data entity that matches the metadata	true			http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
10	onlineURLs	valid	Type: congruency System: knb On failure: error	Online URLs are live	Check that online URLs return something	true	true	Succeeded in accessing URL: https://data.gios.asu.edu/datasets/cap/661_temperature_diurnal_range_a2a916c22f835d726d750b79efb0a7e7.zip
11	integrityChecksum	valid	Type: congruency System: lter On failure: error	Compare the metadata checksum for an entity to the checksum of the downloaded entity	Two possible responses: valid if checksums match; error if checksums do not match.	a2a916c22f835d726d750b79efb0a7e7	a2a916c22f835d726d750b79efb0a7e7	Matching checksums will ensure data integrity during upload to the repository.	If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
Entity Report
Entity Name: 661_temperature_seasonality_8acb10a4e551eab829a9852605f3ae1f.zip
Entity Identifier: 661_temperature_seasonality_8acb10a4e551eab829a9852605f3ae1f.zip
#	Identifier	Status	Quality Check	Name	Description	Expected	Found	Explanation	Suggestion	Reference
1	entityNameLength	valid	Type: metadata System: knb On failure: warn	Length of entityName is not excessive (less than 100 char)	length of entity name is less than 100 characters	entityName value is 100 characters or less	64
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	integrityChecksumPresence	valid	Type: metadata System: lter On failure: warn	A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1	Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.	At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.	true	PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.	Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
8	displayDownloadData	info	Type: data System: knb On failure: info	Display downloaded data	Display the first kilobyte of data that is downloaded	Up to one kilobyte of data should be displayed	*** BINARY DATA ***
9	urlReturnsData	valid	Type: congruency System: knb On failure: error	URL returns data	Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.	A data entity that matches the metadata	true			http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
10	onlineURLs	valid	Type: congruency System: knb On failure: error	Online URLs are live	Check that online URLs return something	true	true	Succeeded in accessing URL: https://data.gios.asu.edu/datasets/cap/661_temperature_seasonality_8acb10a4e551eab829a9852605f3ae1f.zip
11	integrityChecksum	valid	Type: congruency System: lter On failure: error	Compare the metadata checksum for an entity to the checksum of the downloaded entity	Two possible responses: valid if checksums match; error if checksums do not match.	8acb10a4e551eab829a9852605f3ae1f	8acb10a4e551eab829a9852605f3ae1f	Matching checksums will ensure data integrity during upload to the repository.	If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.