Data Package Quality Report
PackageId: edi.10.1
Report Date/Time: 2020-04-29T11:26:36
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.10.1
2	emlVersion	valid	Type: metadata System: lter On failure: error	EML version 2.1.0 or beyond	Check the EML document declaration for version 2.1.0 or higher	eml://ecoinformatics.org/eml-2.1.0 or higher	eml://ecoinformatics.org/eml-2.1.1	Validity of this quality report is dependent on this check being valid.
3	schemaValid	valid	Type: metadata System: knb On failure: error	Document is schema-valid EML	Check document schema validity	schema-valid	Document validated for namespace: 'eml://ecoinformatics.org/eml-2.1.1'	Validity of this quality report is dependent on this check being valid.
4	parserValid	valid	Type: metadata System: knb On failure: error	Document is EML parser-valid	Check document using the EML IDs and references parser	Validates with the EML IDs and references parser	EML IDs and references parser succeeded	Validity of this quality report is dependent on this check being valid.
5	schemaValidDereferenced	valid	Type: metadata System: lter On failure: error	Dereferenced document is schema-valid EML	References are dereferenced, and the resulting file validated	schema-valid	Dereferenced document validated for namespace: 'eml://ecoinformatics.org/eml-2.1.1'	Validity of this quality report is dependent on this check being valid.
6	keywordPresent	valid	Type: metadata System: lter On failure: warn	keyword element is present	Checks to see if at least one keyword is present	Presence of one or more keyword elements	4 '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.	0 '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	9 words found.			EML Best Practices, v.2, p. 13
14	fundingPresence	valid	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	NIH NIEHS: 1P42ES025589-01A1
15	pubDatePresent	valid	Type: metadata System: lter On failure: warn	'pubDate' element is present	Check for presence of the pubDate element	The date that the dataset was submitted for publication in PASTA must be included. (The EML schema does not require this element, but when present, it does constrain its format to YYYY-MM-DD or just YYYY. Citation format uses only the YYYY portion even if a full date is entered.)	2020-04-24			EML Best Practices v.2, p. 17
16	datasetAbstractLength	warn	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.	18 words found.	An abstract helps a user determine if the dataset is useful for a specific purpose. An abstract is usually a paragraph.	Add an abstract.	EML Best Practices
17	duplicateEntityName	valid	Type: metadata System: lter On failure: error	There are no duplicate entity names	Checks that content is not duplicated by other entityName elements in the document	entityName is not a duplicate within the document	No duplicates found	Data Manager requires a non-empty, non-duplicate entityName value for every entity	Declare a non-empty entityName and ensure that there are no duplicate entityName values in the document
Entity Report
Entity Name: Run 1_NT_NS_library_S1_R1_001
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	29
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 650475373 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run1_NT_NS_library_S1_R1_001.fastq.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.	ebfb0745b71d3492745e6a5a69db4f40	ebfb0745b71d3492745e6a5a69db4f40	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.	650475373	650475373	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Run 1_NT_STIM_library_S2_R1_001
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	31
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 537196504 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run1_NT_STIM_library_S2_R1_001.fastq.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.	fd615aadd1c29f7186e65e15888e8cd5	fd615aadd1c29f7186e65e15888e8cd5	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.	537196504	537196504	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Run 1_As_1um_library_S3_R1_001
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	30
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 410503803 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run1_As_1um_libray_S3_R1_001.fastq.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.	e318615eb0cfc4c630e6ed70bc8955ce	e318615eb0cfc4c630e6ed70bc8955ce	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.	410503803	410503803	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Run 1_As_10um_library_S4_R1_001
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	31
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 258911275 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run1_As_10um_libray_S4_R1_001.fastq.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.	8849fa6a7a429f5f0baa22dfe963e3bd	8849fa6a7a429f5f0baa22dfe963e3bd	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.	258911275	258911275	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Run 1_UA_3um_library_S5_R1_001
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	30
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 654539638 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run1_UA_3uM_libray_S5_R1_001.fastq.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.	0482ab0bc6f02d7b35e064e63e4cd0ef	0482ab0bc6f02d7b35e064e63e4cd0ef	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.	654539638	654539638	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Run 1_UA_30um_library_S6_R1_001
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	31
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 347962076 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run1_UA_30uM_S6_R1_001.fastq.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.	f01078a440dcb945ec1b07e9239f13d4	f01078a440dcb945ec1b07e9239f13d4	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.	347962076	347962076	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Run 1_As_1um_UA_3uM_library_S7_R1_001
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	37
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 171861289 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run1_As_1um_UA_3uM_S7_R1_001.fastq.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.	a82bb4a59bb7d960eb97d2bd65b86430	a82bb4a59bb7d960eb97d2bd65b86430	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.	171861289	171861289	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Run 2_NT_NS_library_S8_R1_001
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	29
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 373744038 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run2_NT_NS_library_S8_R1_001.fastq.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.	7b7689e6dd79f8a5116968292f410603	7b7689e6dd79f8a5116968292f410603	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.	373744038	373744038	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Run 2_NT_STIM_library_S9_R1_001
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	31
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 419787283 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run2_NT_STIM_library_S9_R1_001.fastq.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.	6e056c3be54a51738763b2330d9cf6bc	6e056c3be54a51738763b2330d9cf6bc	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.	419787283	419787283	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Run 2_As_1um_library_S10_R1_001
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	31
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 576765366 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run2_As_1um_libray_S10_R1_001.fastq.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.	0f9a396f2715486747daf26bbd264394	0f9a396f2715486747daf26bbd264394	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.	576765366	576765366	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Run 2_As_10um_library_S11_R1_001
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	32
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 376362763 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run2_As_10um_libray_S11_R1_001.fastq.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.	bea8d9680b57a35ab6bc464201bfa8f0	bea8d9680b57a35ab6bc464201bfa8f0	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.	376362763	376362763	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Run 2_UA_3um_library_S12_R1_001
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	31
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 436483441 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run2_UA_3uM_libray_S12_R1_001.fastq.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.	dfe8947ef57cfd5b3078838426c2ab9e	dfe8947ef57cfd5b3078838426c2ab9e	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.	436483441	436483441	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Run 2_UA_30um_library_S13_R1_001
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	32
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 409836809 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run2_UA_30uM_libray_S13_R1_001.fastq.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.	3250ea8620d7b68d9dc31c0984f5ce61	3250ea8620d7b68d9dc31c0984f5ce61	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.	409836809	409836809	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Run 2_As_1um_UA_3uM_library_S14_R1_001
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	38
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 264576601 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run2_As_1um_3uM_UA_libray_S14_R1_001.fastq.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.	a5d1f67722073371ad39837c259753b3	a5d1f67722073371ad39837c259753b3	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.	264576601	264576601	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Run 3_NT_NS_library_S15_R1_001
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	30
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 359921932 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run3_NT_NS_library_S15_R1_001.fastq.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.	2b572a0b753ae1555c5fcfe4fcc80e0b	2b572a0b753ae1555c5fcfe4fcc80e0b	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.	359921932	359921932	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Run 3_NT_STIM_library_S16_R1_001
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	32
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 510016947 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run3_NT_STIM_library_S16_R1_001.fastq.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.	eb9b4dfacc7ebc697775009fb3e80a88	eb9b4dfacc7ebc697775009fb3e80a88	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.	510016947	510016947	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Run 3_As_1um_library_S17_R1_001
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	31
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 306090058 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run3_As_1um_libray_S17_R1_001.fastq.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.	fb40d00523caf8d1bff977a6ecbb28a5	fb40d00523caf8d1bff977a6ecbb28a5	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.	306090058	306090058	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Run 3_As_10um_library_S18_R1_001
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	32
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 496633306 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run3_As_10um_libray_S18_R1_001.fastq.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.	2a75d2a6b8c353e9d8a0d345ea5fd302	2a75d2a6b8c353e9d8a0d345ea5fd302	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.	496633306	496633306	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Run 3_UA_3um_library_S19_R1_001
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	31
2	entityDescriptionPresent	valid	Type: metadata System: lter On failure: warn	An entity description is present	Check for presence of an entity description.	EML Best practices pp. 32-33, "...should have enough information for a user..."	true	With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3	numHeaderLinesPresent	info	Type: metadata System: knb On failure: info	'numHeaderLines' element is present	Check for presence of the 'numHeaderLines' element.	Document contains 'numHeaderLines' element.	No 'numHeaderLines' element found	If data file contains header lines, 'numHeaderLines' must be specified.	Add 'numHeaderLines' element if needed.
4	numFooterLinesPresent	info	Type: metadata System: knb On failure: info	'numFooterLines' element is present	Check for presence of the 'numFooterLines' element.	Document contains 'numFooterLines' element.	No 'numFooterLines' element found	If data file contains footer lines, 'numFooterLines' must be specified.	Add 'numFooterLines' element if needed.
5	fieldDelimiterValid	info	Type: metadata System: knb On failure: error	Field delimiter is a single character	Field delimiters should be one character only	A single character is expected	null	A fieldDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6	recordDelimiterPresent	info	Type: metadata System: knb On failure: warn	Record delimiter is present	Check presence of record delimiter. Check that the record delimiter is one of the suggested values.	A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A	null	A recordDelimiter value is not checked for binary entities or entities with an externally defined format		http://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7	entitySizePresence	valid	Type: metadata System: knb On failure: warn	Check for presence of an entity size element	Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.	Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.	Found entity size element with value of 456845731 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run3_UA_3uM_libray_S19_R1_001.fastq.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.	4e5621f44806042ec635106cce8f8bfe	4e5621f44806042ec635106cce8f8bfe	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.	456845731	456845731	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Run 3_UA_30um_library_S20_R1_001
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	32
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 355690231 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run3_UA_30uM_libray_S20_R1_001.fastq.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.	87fec0b320cb0af83796c4eaf66aac7f	87fec0b320cb0af83796c4eaf66aac7f	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.	355690231	355690231	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.
Entity Report
Entity Name: Run 3_As_1um_UA_3uM_library_S21_R1_001
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	38
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 411560456 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.	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://james.edirepository.org/RNAseq/Run3_As_1um_3uM_UA_libray_S21_R1_001.fastq.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.	98fe18d373e0e51d029db1294e3310b8	98fe18d373e0e51d029db1294e3310b8	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.	411560456	411560456	Examining the entity size is a method for checking that this is the correct entity.	Check the entity size.