Data Package Quality Report
PackageId: edi.409.1
Report Date/Time: 2021-08-12T16:54:25
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	edi.409.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	11 'keyword' element(s) found
7	methodsElementPresent	valid	Type: metadata System: lter On failure: warn	A 'methods' element is present	All datasets should contain a 'methods' element, at a minimum a link to a separate methods doc.	presence of 'methods' at one or more xpaths.	1 'methods' element(s) found			EML Best Practices, p. 28
8	coveragePresent	valid	Type: metadata System: lter On failure: warn	coverage element is present	At least one coverage element should be present in a dataset.	At least one of geographicCoverage, taxonomicCoverage, or temporalCoverage is present in the EML.	1 'coverage' element(s) found
9	geographicCoveragePresent	info	Type: metadata System: lter On failure: info	geographicCoverage is present	Check that geographicCoverage exists in EML at the dataset level, or at least one entity's level, or at least one attribute's level.	geographicCoverage at least at the dataset level.	1 'geographicCoverage' element(s) found	Many but not all datasets are appropriate to have spatial coverage.	If sampling EML is used within methods, does that obviate geographicCoverage? Or should those sites be repeated or referenced?	EML Best Practices v.2, p. 22-23. "One geographicCoverage element should be included, whose boundingCoordinates describe the extent of the data....Additional geographicCoverage elements may be entered at the dataset level if there are significant distances between study sites and it would be confusing if they were grouped into one bounding box." 6 decimal places.
10	taxonomicCoveragePresent	info	Type: metadata System: lter On failure: info	taxonomicCoverage is present	Check that taxonomicCoverage exists in EML at the dataset level, or at least one entity's level, or at least one attribute's level.	taxonomicCoverage at least at the dataset level.	0 'taxonomicCoverage' element(s) found	Only when taxa are pertinent to the dataset will they have taxonomicCoverage.	Could search title, abstract, keywords for any taxonomic name (huge). Could search keywordType="taxonomic".	EML Best Practices v.2, p. 25
11	temporalCoveragePresent	info	Type: metadata System: lter On failure: info	temporalCoverage is present	Check that temporalCoverage exists in EML at the dataset level, or at least one entity's level, or at least one attribute's level.	temporalCoverage at least at the dataset level.	1 'temporalCoverage' element(s) found	LTER wants to search datasets by time; the best place to search is the dataset level temporal coverage.	Most datasets have a temporal range.	EML Best Practices v.2, p. 24
12	pastaDoiAbsent	valid	Type: metadata System: lter On failure: error	An alternateIdentifier with a DOI system attribute that looks like it is generated by PASTA should not be present	Reject the data package if it contains an alternateIdentifier DOI that looks like PASTA generated it.	No PASTA DOIs are expected to be found in the uploaded data package	No PASTA DOI alternateIdentifier elements found	PASTA DOI values might appear in an uploaded data package (by various mechanisms). PASTA will assign a DOI after the upload has completed successfully, so an initial one should not be there.
13	titleLength	valid	Type: metadata System: lter On failure: warn	Dataset title length is at 5 least words.	If the title is shorter than 5 words, it might be insufficient. Title word count between 7 and 20 including prepositions and numbers.	Between 7 and 20 words	19 words found.			EML Best Practices, v.2, p. 13
14	fundingPresence	warn	Type: metadata System: lter On failure: warn	check to see if funding element is present	Checks to see if the funding element is included.	the funding element is expected to be included	funding not found	Searches will want to display datasets by funder or grant id.	Include the funding source, please.
15	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.	82 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: water_age_CCE_1994.tar
Entity Identifier:
#	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	22
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 322263158 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_1994.tar.gz
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.	8b22bf5c72c405aab93e44a6aa5b7d79	8b22bf5c72c405aab93e44a6aa5b7d79	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.	322263158	322263158	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_1995.tar
Entity Identifier:
#	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	22
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 322888799 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_1995.tar.gz
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.	bbcd0dd039b8e58fa7a540f22eb8242c	bbcd0dd039b8e58fa7a540f22eb8242c	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.	322888799	322888799	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_1996.tar
Entity Identifier:
#	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	22
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 322588452 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_1996.tar.gz
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.	9a5d2df1137bb4cbe8b18c0568a7d7df	9a5d2df1137bb4cbe8b18c0568a7d7df	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.	322588452	322588452	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_1997.tar
Entity Identifier:
#	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	22
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 324228594 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_1997.tar.gz
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.	fef5bba7dbacfabcb009d45cafbec0fc	fef5bba7dbacfabcb009d45cafbec0fc	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.	324228594	324228594	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_1998.tar
Entity Identifier:
#	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	22
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 323637346 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_1998.tar.gz
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.	8ecab4c5a70af897a0dbefb002235b37	8ecab4c5a70af897a0dbefb002235b37	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.	323637346	323637346	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_1999.tar
Entity Identifier:
#	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	22
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 323410461 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_1999.tar.gz
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.	cc61e5878f163b540db8e8d86402fd76	cc61e5878f163b540db8e8d86402fd76	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.	323410461	323410461	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_2000.tar
Entity Identifier:
#	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	22
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 324018213 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_2000.tar.gz
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.	dd7727593de81adba7e2a9f7039c1a8c	dd7727593de81adba7e2a9f7039c1a8c	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.	324018213	324018213	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_2001.tar
Entity Identifier:
#	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	22
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 323998992 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_2001.tar.gz
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.	581f0387d9589de0324a9dbbaf292fd5	581f0387d9589de0324a9dbbaf292fd5	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.	323998992	323998992	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_2002.tar
Entity Identifier:
#	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	22
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 324405822 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_2002.tar.gz
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.	dc770a9047bf24246aefe2d036b89ff8	dc770a9047bf24246aefe2d036b89ff8	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.	324405822	324405822	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_2003.tar
Entity Identifier:
#	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	22
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 324075482 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_2003.tar.gz
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.	4826cfc49016971d0f7090dafeea4c9d	4826cfc49016971d0f7090dafeea4c9d	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.	324075482	324075482	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_2004.tar
Entity Identifier:
#	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	22
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 325445897 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_2004.tar.gz
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.	318765e7bc6b039f244c6438dd042fd4	318765e7bc6b039f244c6438dd042fd4	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.	325445897	325445897	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_2005.tar
Entity Identifier:
#	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	22
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 324663301 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_2005.tar.gz
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.	c092ebea6203d2b9df2172389d5aafdb	c092ebea6203d2b9df2172389d5aafdb	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.	324663301	324663301	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_2006.tar
Entity Identifier:
#	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	22
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 325366554 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_2006.tar.gz
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.	294e3d1f83c643fb7a2a39fe3b4bc8d5	294e3d1f83c643fb7a2a39fe3b4bc8d5	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.	325366554	325366554	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_2007.tar
Entity Identifier:
#	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	22
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 324314191 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_2007.tar.gz
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.	7511e274923cc8469df4f3c29d381671	7511e274923cc8469df4f3c29d381671	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.	324314191	324314191	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_2008.tar
Entity Identifier:
#	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	22
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 324013371 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_2008.tar.gz
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.	650a0fb23b0c0a1e45b6c6765c8a9487	650a0fb23b0c0a1e45b6c6765c8a9487	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.	324013371	324013371	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_2009.tar
Entity Identifier:
#	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	22
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 325149355 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_2009.tar.gz
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.	7c06594729936ccb4837887e4014e1bf	7c06594729936ccb4837887e4014e1bf	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.	325149355	325149355	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_2010.tar
Entity Identifier:
#	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	22
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 323880016 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_2010.tar.gz
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.	c1a214f3d72ab3de73e089d6baa6050e	c1a214f3d72ab3de73e089d6baa6050e	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.	323880016	323880016	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_2011.tar
Entity Identifier:
#	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	22
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 323587551 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_2011.tar.gz
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.	3b077aa4431f407ab2bac36140757913	3b077aa4431f407ab2bac36140757913	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.	323587551	323587551	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_2012.tar
Entity Identifier:
#	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	22
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 323524953 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_2012.tar.gz
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.	19b4c1bb7c831f078abe99e463e7d09c	19b4c1bb7c831f078abe99e463e7d09c	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.	323524953	323524953	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_2013.tar
Entity Identifier:
#	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	22
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 324376313 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_2013.tar.gz
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.	4ac246632ff83a0391cfe69866db886a	4ac246632ff83a0391cfe69866db886a	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.	324376313	324376313	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_2014.tar
Entity Identifier:
#	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	22
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 325249209 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_2014.tar.gz
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.	d870a635d4ffef98473808b0c1ea4093	d870a635d4ffef98473808b0c1ea4093	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.	325249209	325249209	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_2015.tar
Entity Identifier:
#	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	22
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 325300629 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_2015.tar.gz
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.	7141d8bbd9d76c606c9152b8703c3192	7141d8bbd9d76c606c9152b8703c3192	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.	325300629	325300629	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_2016.tar
Entity Identifier:
#	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	22
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 323791256 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_2016.tar.gz
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.	778c7bd644e2597495e58cf1bfcae263	778c7bd644e2597495e58cf1bfcae263	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.	323791256	323791256	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_2017.tar
Entity Identifier:
#	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	22
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 323129822 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_2017.tar.gz
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.	c4e08240d3f44b51cd99e5e03ed92137	c4e08240d3f44b51cd99e5e03ed92137	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.	323129822	323129822	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_2018.tar
Entity Identifier:
#	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	22
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 63525428 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_2018.tar.gz
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.	04cc1e61f31ef2c2451e7dd43f04b46d	04cc1e61f31ef2c2451e7dd43f04b46d	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.	63525428	63525428	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: water_age_CCE_2019.tar
Entity Identifier:
#	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	22
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 50116580 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/water_age_CCE_2019.tar.gz
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.	564d8540690599511825a10313a1dbfd	564d8540690599511825a10313a1dbfd	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.	50116580	50116580	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: LTER_Data_Submission_Form_WaterAge_PChabert
Entity Identifier:
#	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	43
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 17784 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://sam.edirepository.org/user-data/CCE-46f754775fffff05979ba412f5a29318/uploads/data/LTER_Data_Submission_Form_WaterAge_PChabert.xlsx
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.	5b249f8939399d9394346104f2d85175	5b249f8939399d9394346104f2d85175	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.	17784	17784	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.