Data Package Quality Report
PackageId: knb-lter-cap.680.1
Report Date/Time: 2020-02-03T15:32:52
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.680.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	https://eml.ecoinformatics.org/eml-2.2.0	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: 'https://eml.ecoinformatics.org/eml-2.2.0'	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: 'https://eml.ecoinformatics.org/eml-2.2.0'	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.	91 '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.	91 '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.	91 '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	12 words found.			EML Best Practices, v.2, p. 13
14	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.)	2020-02-03			EML Best Practices v.2, p. 17
15	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.	156 words found.			EML Best Practices
16	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: Max_MODIS_NDVI_2001.tif
Entity Identifier: Max_MODIS_NDVI_2001.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1335491 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Max_MODIS_NDVI_2001.tif
12	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.	acb3758c486f868a223e4d15a69466ab	acb3758c486f868a223e4d15a69466ab	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1335491	1335491	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Max_MODIS_NDVI_2002.tif
Entity Identifier: Max_MODIS_NDVI_2002.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1304933 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Max_MODIS_NDVI_2002.tif
12	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.	80e590a7ceecaa13c091deff04635025	80e590a7ceecaa13c091deff04635025	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1304933	1304933	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Max_MODIS_NDVI_2003.tif
Entity Identifier: Max_MODIS_NDVI_2003.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1323699 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Max_MODIS_NDVI_2003.tif
12	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.	56605ea4e9f204bd4b694ed05a75c011	56605ea4e9f204bd4b694ed05a75c011	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1323699	1323699	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Max_MODIS_NDVI_2004.tif
Entity Identifier: Max_MODIS_NDVI_2004.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1319019 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Max_MODIS_NDVI_2004.tif
12	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.	35c06e18588312a15c179fc5e9ff4a57	35c06e18588312a15c179fc5e9ff4a57	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1319019	1319019	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Max_MODIS_NDVI_2005.tif
Entity Identifier: Max_MODIS_NDVI_2005.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1328309 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Max_MODIS_NDVI_2005.tif
12	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.	08838e20ab202fa268c04aa4c9fe9762	08838e20ab202fa268c04aa4c9fe9762	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1328309	1328309	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Max_MODIS_NDVI_2006.tif
Entity Identifier: Max_MODIS_NDVI_2006.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1299993 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Max_MODIS_NDVI_2006.tif
12	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.	a75cd57391a417cb62b61b81cadfd195	a75cd57391a417cb62b61b81cadfd195	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1299993	1299993	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Max_MODIS_NDVI_2007.tif
Entity Identifier: Max_MODIS_NDVI_2007.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1302471 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Max_MODIS_NDVI_2007.tif
12	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.	31fff42b1f77ca836b87197d058a0948	31fff42b1f77ca836b87197d058a0948	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1302471	1302471	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Max_MODIS_NDVI_2008.tif
Entity Identifier: Max_MODIS_NDVI_2008.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1332619 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Max_MODIS_NDVI_2008.tif
12	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.	d32d4212c88b70a57bb430afce618596	d32d4212c88b70a57bb430afce618596	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1332619	1332619	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Max_MODIS_NDVI_2009.tif
Entity Identifier: Max_MODIS_NDVI_2009.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1313569 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Max_MODIS_NDVI_2009.tif
12	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.	990dde085a5101fb24db631b0e523e11	990dde085a5101fb24db631b0e523e11	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1313569	1313569	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Max_MODIS_NDVI_2010.tif
Entity Identifier: Max_MODIS_NDVI_2010.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1320453 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Max_MODIS_NDVI_2010.tif
12	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.	11613ff022786741dd74500a7caa732c	11613ff022786741dd74500a7caa732c	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1320453	1320453	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Max_MODIS_NDVI_2011.tif
Entity Identifier: Max_MODIS_NDVI_2011.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1317599 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Max_MODIS_NDVI_2011.tif
12	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.	c5f0f8d7db1245f1152ac13995be215c	c5f0f8d7db1245f1152ac13995be215c	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1317599	1317599	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Max_MODIS_NDVI_2012.tif
Entity Identifier: Max_MODIS_NDVI_2012.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1321935 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Max_MODIS_NDVI_2012.tif
12	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.	a972432d4b1a457f97f466336904194e	a972432d4b1a457f97f466336904194e	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1321935	1321935	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Max_MODIS_NDVI_2013.tif
Entity Identifier: Max_MODIS_NDVI_2013.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1318535 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Max_MODIS_NDVI_2013.tif
12	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.	60353ef0573668940fd74928471ad1d0	60353ef0573668940fd74928471ad1d0	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1318535	1318535	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Max_MODIS_NDVI_2014.tif
Entity Identifier: Max_MODIS_NDVI_2014.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1309799 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Max_MODIS_NDVI_2014.tif
12	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.	0390ad6bce6df521170598b9e040b458	0390ad6bce6df521170598b9e040b458	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1309799	1309799	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Max_MODIS_NDVI_2015.tif
Entity Identifier: Max_MODIS_NDVI_2015.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1320103 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Max_MODIS_NDVI_2015.tif
12	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.	67f8217e0289e115143fccb34623bcf7	67f8217e0289e115143fccb34623bcf7	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1320103	1320103	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Max_MODIS_NDVI_2016.tif
Entity Identifier: Max_MODIS_NDVI_2016.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1302847 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Max_MODIS_NDVI_2016.tif
12	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.	19fbf30385b30543d7624969527c2d96	19fbf30385b30543d7624969527c2d96	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1302847	1302847	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Max_MODIS_NDVI_2017.tif
Entity Identifier: Max_MODIS_NDVI_2017.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1324057 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Max_MODIS_NDVI_2017.tif
12	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.	9eae7af391958a187aa525e3ca4bf215	9eae7af391958a187aa525e3ca4bf215	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1324057	1324057	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Max_MODIS_NDVI_2018.tif
Entity Identifier: Max_MODIS_NDVI_2018.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1332303 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Max_MODIS_NDVI_2018.tif
12	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.	419ebd62c96288e2229004545b95872a	419ebd62c96288e2229004545b95872a	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1332303	1332303	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Mean_MODIS_NDVI_2001.tif
Entity Identifier: Mean_MODIS_NDVI_2001.tif
#	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	24
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1707251 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Mean_MODIS_NDVI_2001.tif
12	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.	1a3d6db9eeba21b2f915889284f2d7e0	1a3d6db9eeba21b2f915889284f2d7e0	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1707251	1707251	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Mean_MODIS_NDVI_2002.tif
Entity Identifier: Mean_MODIS_NDVI_2002.tif
#	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	24
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1665075 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Mean_MODIS_NDVI_2002.tif
12	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.	17e39bfb74c674c9ff3c18c44d47c2b9	17e39bfb74c674c9ff3c18c44d47c2b9	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1665075	1665075	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Mean_MODIS_NDVI_2003.tif
Entity Identifier: Mean_MODIS_NDVI_2003.tif
#	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	24
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1696523 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Mean_MODIS_NDVI_2003.tif
12	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.	7dee1418c5f68d91b9e368ff7235261c	7dee1418c5f68d91b9e368ff7235261c	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1696523	1696523	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Mean_MODIS_NDVI_2004.tif
Entity Identifier: Mean_MODIS_NDVI_2004.tif
#	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	24
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1690153 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Mean_MODIS_NDVI_2004.tif
12	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.	8f4c7e11cf0d475a8bdf401ed456a354	8f4c7e11cf0d475a8bdf401ed456a354	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1690153	1690153	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Mean_MODIS_NDVI_2005.tif
Entity Identifier: Mean_MODIS_NDVI_2005.tif
#	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	24
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1718831 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Mean_MODIS_NDVI_2005.tif
12	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.	f3207d5d44f74260ab112be70fc5e92d	f3207d5d44f74260ab112be70fc5e92d	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1718831	1718831	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Mean_MODIS_NDVI_2006.tif
Entity Identifier: Mean_MODIS_NDVI_2006.tif
#	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	24
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1682985 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Mean_MODIS_NDVI_2006.tif
12	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.	c4074aa0c462691214ec544528ff3ee1	c4074aa0c462691214ec544528ff3ee1	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1682985	1682985	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Mean_MODIS_NDVI_2007.tif
Entity Identifier: Mean_MODIS_NDVI_2007.tif
#	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	24
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1675083 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Mean_MODIS_NDVI_2007.tif
12	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.	91d4a563e8593354f909d08d1bb23083	91d4a563e8593354f909d08d1bb23083	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1675083	1675083	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Mean_MODIS_NDVI_2008.tif
Entity Identifier: Mean_MODIS_NDVI_2008.tif
#	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	24
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1704569 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Mean_MODIS_NDVI_2008.tif
12	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.	e85c2a2c4343d663bb5b0b31542e33c8	e85c2a2c4343d663bb5b0b31542e33c8	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1704569	1704569	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Mean_MODIS_NDVI_2009.tif
Entity Identifier: Mean_MODIS_NDVI_2009.tif
#	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	24
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1687891 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Mean_MODIS_NDVI_2009.tif
12	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.	cfac37f8cd48192088f7db277c92cac4	cfac37f8cd48192088f7db277c92cac4	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1687891	1687891	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Mean_MODIS_NDVI_2010.tif
Entity Identifier: Mean_MODIS_NDVI_2010.tif
#	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	24
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1699955 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Mean_MODIS_NDVI_2010.tif
12	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.	d1af418ee52ddb060ce68e245cfc03ad	d1af418ee52ddb060ce68e245cfc03ad	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1699955	1699955	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Mean_MODIS_NDVI_2011.tif
Entity Identifier: Mean_MODIS_NDVI_2011.tif
#	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	24
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1685323 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Mean_MODIS_NDVI_2011.tif
12	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.	85ec94024130cb4c3345e7a4a1c908d2	85ec94024130cb4c3345e7a4a1c908d2	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1685323	1685323	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Mean_MODIS_NDVI_2012.tif
Entity Identifier: Mean_MODIS_NDVI_2012.tif
#	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	24
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1689071 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Mean_MODIS_NDVI_2012.tif
12	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.	326572d432dc049e875cebecaa0ef686	326572d432dc049e875cebecaa0ef686	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1689071	1689071	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Mean_MODIS_NDVI_2013.tif
Entity Identifier: Mean_MODIS_NDVI_2013.tif
#	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	24
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1692307 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Mean_MODIS_NDVI_2013.tif
12	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.	93b6835103c502d4e355f431185e3db5	93b6835103c502d4e355f431185e3db5	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1692307	1692307	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Mean_MODIS_NDVI_2014.tif
Entity Identifier: Mean_MODIS_NDVI_2014.tif
#	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	24
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1706289 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Mean_MODIS_NDVI_2014.tif
12	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.	fe43b427a2f5ae10506dba3e869b5ff9	fe43b427a2f5ae10506dba3e869b5ff9	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1706289	1706289	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Mean_MODIS_NDVI_2015.tif
Entity Identifier: Mean_MODIS_NDVI_2015.tif
#	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	24
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1702693 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Mean_MODIS_NDVI_2015.tif
12	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.	365b95f409038daf4ffb12246a1af717	365b95f409038daf4ffb12246a1af717	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1702693	1702693	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Mean_MODIS_NDVI_2016.tif
Entity Identifier: Mean_MODIS_NDVI_2016.tif
#	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	24
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1686499 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Mean_MODIS_NDVI_2016.tif
12	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.	5e8388b3135d0898ddfed2bfc92a4fef	5e8388b3135d0898ddfed2bfc92a4fef	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1686499	1686499	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Mean_MODIS_NDVI_2017.tif
Entity Identifier: Mean_MODIS_NDVI_2017.tif
#	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	24
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1699149 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Mean_MODIS_NDVI_2017.tif
12	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.	b744d98fa9db0763c2612ea7b9280551	b744d98fa9db0763c2612ea7b9280551	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1699149	1699149	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Mean_MODIS_NDVI_2018.tif
Entity Identifier: Mean_MODIS_NDVI_2018.tif
#	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	24
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1700133 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Mean_MODIS_NDVI_2018.tif
12	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.	73d44319c87a814ab77a020a358444f3	73d44319c87a814ab77a020a358444f3	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1700133	1700133	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Min_MODIS_NDVI_2001.tif
Entity Identifier: Min_MODIS_NDVI_2001.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1235807 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Min_MODIS_NDVI_2001.tif
12	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.	670bbb9885954c491926155be788eb77	670bbb9885954c491926155be788eb77	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1235807	1235807	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Min_MODIS_NDVI_2002.tif
Entity Identifier: Min_MODIS_NDVI_2002.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1196085 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Min_MODIS_NDVI_2002.tif
12	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.	15cf8bd5f6edeb9e7cde5c8effafd473	15cf8bd5f6edeb9e7cde5c8effafd473	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1196085	1196085	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Min_MODIS_NDVI_2003.tif
Entity Identifier: Min_MODIS_NDVI_2003.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1230179 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Min_MODIS_NDVI_2003.tif
12	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.	0cb622bb6eb681609683c0ede35f5d79	0cb622bb6eb681609683c0ede35f5d79	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1230179	1230179	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Min_MODIS_NDVI_2004.tif
Entity Identifier: Min_MODIS_NDVI_2004.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1221069 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Min_MODIS_NDVI_2004.tif
12	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.	884a58750cdfb894ba19fc99b5e2bf6e	884a58750cdfb894ba19fc99b5e2bf6e	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1221069	1221069	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Min_MODIS_NDVI_2005.tif
Entity Identifier: Min_MODIS_NDVI_2005.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1241305 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Min_MODIS_NDVI_2005.tif
12	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.	26cb4def07bf799864092f08efec4f46	26cb4def07bf799864092f08efec4f46	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1241305	1241305	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Min_MODIS_NDVI_2006.tif
Entity Identifier: Min_MODIS_NDVI_2006.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1221873 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Min_MODIS_NDVI_2006.tif
12	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.	d0c38208ab765cf6afcbb5888726e342	d0c38208ab765cf6afcbb5888726e342	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1221873	1221873	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Min_MODIS_NDVI_2007.tif
Entity Identifier: Min_MODIS_NDVI_2007.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1205125 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Min_MODIS_NDVI_2007.tif
12	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.	255edb3d0d9f05f6a49d12d075478e02	255edb3d0d9f05f6a49d12d075478e02	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1205125	1205125	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Min_MODIS_NDVI_2008.tif
Entity Identifier: Min_MODIS_NDVI_2008.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1243227 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Min_MODIS_NDVI_2008.tif
12	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.	7a8cb1b50d4f3f4c606c9431ca8b542a	7a8cb1b50d4f3f4c606c9431ca8b542a	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1243227	1243227	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Min_MODIS_NDVI_2009.tif
Entity Identifier: Min_MODIS_NDVI_2009.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1229355 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Min_MODIS_NDVI_2009.tif
12	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.	189bef7e19f2d15d235d618bbfedc134	189bef7e19f2d15d235d618bbfedc134	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1229355	1229355	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Min_MODIS_NDVI_2010.tif
Entity Identifier: Min_MODIS_NDVI_2010.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1244707 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Min_MODIS_NDVI_2010.tif
12	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.	725d9a18cb1e8549f7fba659e0264bba	725d9a18cb1e8549f7fba659e0264bba	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1244707	1244707	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Min_MODIS_NDVI_2011.tif
Entity Identifier: Min_MODIS_NDVI_2011.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1224703 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Min_MODIS_NDVI_2011.tif
12	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.	d451d777adaf045855d7bdb3adea7dce	d451d777adaf045855d7bdb3adea7dce	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1224703	1224703	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Min_MODIS_NDVI_2012.tif
Entity Identifier: Min_MODIS_NDVI_2012.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1221519 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Min_MODIS_NDVI_2012.tif
12	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.	876186989151c85486a3d8eef37a309d	876186989151c85486a3d8eef37a309d	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1221519	1221519	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Min_MODIS_NDVI_2013.tif
Entity Identifier: Min_MODIS_NDVI_2013.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1224591 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Min_MODIS_NDVI_2013.tif
12	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.	06588fb4fab3c28d77ec9ba3acd687d3	06588fb4fab3c28d77ec9ba3acd687d3	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1224591	1224591	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Min_MODIS_NDVI_2014.tif
Entity Identifier: Min_MODIS_NDVI_2014.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1224551 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Min_MODIS_NDVI_2014.tif
12	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.	9d06a95c3e79d271d4b9a11a3a082b55	9d06a95c3e79d271d4b9a11a3a082b55	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1224551	1224551	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Min_MODIS_NDVI_2015.tif
Entity Identifier: Min_MODIS_NDVI_2015.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1239361 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Min_MODIS_NDVI_2015.tif
12	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.	96c7b454252f23ee29483c866d358ce4	96c7b454252f23ee29483c866d358ce4	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1239361	1239361	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Min_MODIS_NDVI_2016.tif
Entity Identifier: Min_MODIS_NDVI_2016.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1226979 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Min_MODIS_NDVI_2016.tif
12	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.	1fe5ebad6730f10010ad9a4eb709d684	1fe5ebad6730f10010ad9a4eb709d684	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1226979	1226979	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Min_MODIS_NDVI_2017.tif
Entity Identifier: Min_MODIS_NDVI_2017.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1231361 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Min_MODIS_NDVI_2017.tif
12	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.	d0b028ed23d8d39741646b4b59f37fc0	d0b028ed23d8d39741646b4b59f37fc0	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1231361	1231361	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Min_MODIS_NDVI_2018.tif
Entity Identifier: Min_MODIS_NDVI_2018.tif
#	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	23
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1216471 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Min_MODIS_NDVI_2018.tif
12	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.	6588fce36709bf7752a0f04fcdb850c9	6588fce36709bf7752a0f04fcdb850c9	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1216471	1216471	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Range_MODIS_NDVI_2001.tif
Entity Identifier: Range_MODIS_NDVI_2001.tif
#	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	25
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1328963 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Range_MODIS_NDVI_2001.tif
12	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.	5e4ff7e56027f73cc8312df8540ab1b2	5e4ff7e56027f73cc8312df8540ab1b2	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1328963	1328963	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Range_MODIS_NDVI_2002.tif
Entity Identifier: Range_MODIS_NDVI_2002.tif
#	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	25
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1295157 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Range_MODIS_NDVI_2002.tif
12	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.	595321ac7ccc3af97a8c412fca77f81f	595321ac7ccc3af97a8c412fca77f81f	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1295157	1295157	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Range_MODIS_NDVI_2003.tif
Entity Identifier: Range_MODIS_NDVI_2003.tif
#	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	25
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1313117 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Range_MODIS_NDVI_2003.tif
12	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.	b5d1b5acf06f947d2b2c17721d5e0a4d	b5d1b5acf06f947d2b2c17721d5e0a4d	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1313117	1313117	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Range_MODIS_NDVI_2004.tif
Entity Identifier: Range_MODIS_NDVI_2004.tif
#	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	25
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1333883 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Range_MODIS_NDVI_2004.tif
12	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.	e191668b0d8257b0596f9320f9ff2ce8	e191668b0d8257b0596f9320f9ff2ce8	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1333883	1333883	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Range_MODIS_NDVI_2005.tif
Entity Identifier: Range_MODIS_NDVI_2005.tif
#	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	25
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1345105 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Range_MODIS_NDVI_2005.tif
12	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.	1acd88083ddf68149e84105728c92796	1acd88083ddf68149e84105728c92796	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1345105	1345105	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Range_MODIS_NDVI_2006.tif
Entity Identifier: Range_MODIS_NDVI_2006.tif
#	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	25
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1292529 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Range_MODIS_NDVI_2006.tif
12	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.	fba45792967e4bcc1e786e2aa3b87af6	fba45792967e4bcc1e786e2aa3b87af6	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1292529	1292529	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Range_MODIS_NDVI_2007.tif
Entity Identifier: Range_MODIS_NDVI_2007.tif
#	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	25
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1295589 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Range_MODIS_NDVI_2007.tif
12	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.	9f63fba013a55e28dbcd33beeefe580b	9f63fba013a55e28dbcd33beeefe580b	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1295589	1295589	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Range_MODIS_NDVI_2008.tif
Entity Identifier: Range_MODIS_NDVI_2008.tif
#	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	25
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1326499 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Range_MODIS_NDVI_2008.tif
12	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.	3bb96f740562dc4bbfa317910a671eca	3bb96f740562dc4bbfa317910a671eca	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1326499	1326499	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Range_MODIS_NDVI_2009.tif
Entity Identifier: Range_MODIS_NDVI_2009.tif
#	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	25
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1304639 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Range_MODIS_NDVI_2009.tif
12	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.	f12a40db86c77de4e4b03aa171925c5c	f12a40db86c77de4e4b03aa171925c5c	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1304639	1304639	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Range_MODIS_NDVI_2010.tif
Entity Identifier: Range_MODIS_NDVI_2010.tif
#	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	25
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1313447 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Range_MODIS_NDVI_2010.tif
12	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.	170382e527ee88ee2ca4c9ea025bcd70	170382e527ee88ee2ca4c9ea025bcd70	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1313447	1313447	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Range_MODIS_NDVI_2011.tif
Entity Identifier: Range_MODIS_NDVI_2011.tif
#	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	25
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1303885 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Range_MODIS_NDVI_2011.tif
12	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.	f00bd43a0b68d13a5d687a5d23044b0a	f00bd43a0b68d13a5d687a5d23044b0a	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1303885	1303885	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Range_MODIS_NDVI_2012.tif
Entity Identifier: Range_MODIS_NDVI_2012.tif
#	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	25
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1311663 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Range_MODIS_NDVI_2012.tif
12	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.	6c2bdff25584acbd361b4cf89abec4c6	6c2bdff25584acbd361b4cf89abec4c6	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1311663	1311663	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Range_MODIS_NDVI_2013.tif
Entity Identifier: Range_MODIS_NDVI_2013.tif
#	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	25
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1310145 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Range_MODIS_NDVI_2013.tif
12	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.	ac0c8a1433edaac73b1b8a2f36b005de	ac0c8a1433edaac73b1b8a2f36b005de	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1310145	1310145	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Range_MODIS_NDVI_2014.tif
Entity Identifier: Range_MODIS_NDVI_2014.tif
#	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	25
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1300573 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Range_MODIS_NDVI_2014.tif
12	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.	710e8b2f5ad02ea16df0b2d543e26581	710e8b2f5ad02ea16df0b2d543e26581	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1300573	1300573	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Range_MODIS_NDVI_2015.tif
Entity Identifier: Range_MODIS_NDVI_2015.tif
#	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	25
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1301193 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Range_MODIS_NDVI_2015.tif
12	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.	0a2f4b734fed3240db7dbe23387095dd	0a2f4b734fed3240db7dbe23387095dd	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1301193	1301193	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Range_MODIS_NDVI_2016.tif
Entity Identifier: Range_MODIS_NDVI_2016.tif
#	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	25
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1300029 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Range_MODIS_NDVI_2016.tif
12	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.	400a87c55d78e7ec08f8d8845a481349	400a87c55d78e7ec08f8d8845a481349	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1300029	1300029	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Range_MODIS_NDVI_2017.tif
Entity Identifier: Range_MODIS_NDVI_2017.tif
#	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	25
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1317955 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Range_MODIS_NDVI_2017.tif
12	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.	78a58f6502044f77bcaef15e017aa2d3	78a58f6502044f77bcaef15e017aa2d3	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1317955	1317955	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Range_MODIS_NDVI_2018.tif
Entity Identifier: Range_MODIS_NDVI_2018.tif
#	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	25
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 1328981 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Range_MODIS_NDVI_2018.tif
12	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.	d39a08571131534e93fd4dd87d0af0dd	d39a08571131534e93fd4dd87d0af0dd	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	1328981	1328981	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Seasonality_MODIS_NDVI_2001.tif
Entity Identifier: Seasonality_MODIS_NDVI_2001.tif
#	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	31
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 2181389 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Seasonality_MODIS_NDVI_2001.tif
12	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.	f78bb865b323b33b276ae842cacc062e	f78bb865b323b33b276ae842cacc062e	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	2181389	2181389	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Seasonality_MODIS_NDVI_2002.tif
Entity Identifier: Seasonality_MODIS_NDVI_2002.tif
#	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	31
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 2204311 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Seasonality_MODIS_NDVI_2002.tif
12	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.	76b8216652d2fbc5641cd8d60cb4c95e	76b8216652d2fbc5641cd8d60cb4c95e	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	2204311	2204311	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Seasonality_MODIS_NDVI_2003.tif
Entity Identifier: Seasonality_MODIS_NDVI_2003.tif
#	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	31
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 2163081 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Seasonality_MODIS_NDVI_2003.tif
12	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.	1e9bb1e1530590ed5bb9034397737ae7	1e9bb1e1530590ed5bb9034397737ae7	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	2163081	2163081	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Seasonality_MODIS_NDVI_2004.tif
Entity Identifier: Seasonality_MODIS_NDVI_2004.tif
#	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	31
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 2157955 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Seasonality_MODIS_NDVI_2004.tif
12	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.	5a9fb2a80a73fc1a77c4475f1954459b	5a9fb2a80a73fc1a77c4475f1954459b	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	2157955	2157955	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Seasonality_MODIS_NDVI_2005.tif
Entity Identifier: Seasonality_MODIS_NDVI_2005.tif
#	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	31
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 2139101 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Seasonality_MODIS_NDVI_2005.tif
12	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.	b319ecf2a4a2ac98b57494a1c472e6c9	b319ecf2a4a2ac98b57494a1c472e6c9	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	2139101	2139101	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Seasonality_MODIS_NDVI_2006.tif
Entity Identifier: Seasonality_MODIS_NDVI_2006.tif
#	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	31
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 2177155 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Seasonality_MODIS_NDVI_2006.tif
12	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.	c297a9f0724f8071781aa711a272e3e5	c297a9f0724f8071781aa711a272e3e5	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	2177155	2177155	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Seasonality_MODIS_NDVI_2007.tif
Entity Identifier: Seasonality_MODIS_NDVI_2007.tif
#	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	31
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 2175891 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Seasonality_MODIS_NDVI_2007.tif
12	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.	93f84d7e9f9c7ea847b845e47c41ac93	93f84d7e9f9c7ea847b845e47c41ac93	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	2175891	2175891	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Seasonality_MODIS_NDVI_2008.tif
Entity Identifier: Seasonality_MODIS_NDVI_2008.tif
#	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	31
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 2175653 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Seasonality_MODIS_NDVI_2008.tif
12	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.	11317c6bfadf9dce6e17795e6a9f133b	11317c6bfadf9dce6e17795e6a9f133b	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	2175653	2175653	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Seasonality_MODIS_NDVI_2009.tif
Entity Identifier: Seasonality_MODIS_NDVI_2009.tif
#	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	31
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 2166545 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Seasonality_MODIS_NDVI_2009.tif
12	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.	7160f0a79c5afccf4f958e9062117ac7	7160f0a79c5afccf4f958e9062117ac7	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	2166545	2166545	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Seasonality_MODIS_NDVI_2010.tif
Entity Identifier: Seasonality_MODIS_NDVI_2010.tif
#	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	31
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 2154455 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Seasonality_MODIS_NDVI_2010.tif
12	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.	f6a7b88a757cca79c61597632dcc6e6c	f6a7b88a757cca79c61597632dcc6e6c	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	2154455	2154455	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Seasonality_MODIS_NDVI_2011.tif
Entity Identifier: Seasonality_MODIS_NDVI_2011.tif
#	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	31
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 2182967 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Seasonality_MODIS_NDVI_2011.tif
12	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.	6821eea44376bbd96077d8712abf3e6e	6821eea44376bbd96077d8712abf3e6e	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	2182967	2182967	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Seasonality_MODIS_NDVI_2012.tif
Entity Identifier: Seasonality_MODIS_NDVI_2012.tif
#	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	31
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 2180637 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Seasonality_MODIS_NDVI_2012.tif
12	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.	3dfa95ff1254a4ccfb2de5d74cf4d1c5	3dfa95ff1254a4ccfb2de5d74cf4d1c5	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	2180637	2180637	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Seasonality_MODIS_NDVI_2013.tif
Entity Identifier: Seasonality_MODIS_NDVI_2013.tif
#	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	31
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 2177763 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Seasonality_MODIS_NDVI_2013.tif
12	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.	15406a40c6b50e05895734c4adf6c24e	15406a40c6b50e05895734c4adf6c24e	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	2177763	2177763	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Seasonality_MODIS_NDVI_2014.tif
Entity Identifier: Seasonality_MODIS_NDVI_2014.tif
#	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	31
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 2152235 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Seasonality_MODIS_NDVI_2014.tif
12	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.	dd318dab597e75b9de24db6ef500702a	dd318dab597e75b9de24db6ef500702a	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	2152235	2152235	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Seasonality_MODIS_NDVI_2015.tif
Entity Identifier: Seasonality_MODIS_NDVI_2015.tif
#	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	31
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 2167201 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Seasonality_MODIS_NDVI_2015.tif
12	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.	6057487a966255217fbf7f69f32966c5	6057487a966255217fbf7f69f32966c5	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	2167201	2167201	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Seasonality_MODIS_NDVI_2016.tif
Entity Identifier: Seasonality_MODIS_NDVI_2016.tif
#	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	31
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 2168577 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Seasonality_MODIS_NDVI_2016.tif
12	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.	3f88c411c3bd3c52f022e0bfab787a16	3f88c411c3bd3c52f022e0bfab787a16	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	2168577	2168577	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Seasonality_MODIS_NDVI_2017.tif
Entity Identifier: Seasonality_MODIS_NDVI_2017.tif
#	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	31
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 2159385 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Seasonality_MODIS_NDVI_2017.tif
12	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.	329fd4f41a6957f1ac938a346d97f5dd	329fd4f41a6957f1ac938a346d97f5dd	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	2159385	2159385	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Seasonality_MODIS_NDVI_2018.tif
Entity Identifier: Seasonality_MODIS_NDVI_2018.tif
#	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	31
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	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 2161231 and size unit specified as 'byte'.	Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).	Include an entity size in bytes	Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8	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.
9	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	Cannot display NON-PLAIN TEXT DATA
10	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
11	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/Seasonality_MODIS_NDVI_2018.tif
12	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.	2bf4d346ffcc92144301a5c738e45636	2bf4d346ffcc92144301a5c738e45636	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.
13	entitySizeCongruence	valid	Type: congruency System: knb On failure: error	Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.	Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.	2161231	2161231	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.