Data Package Quality Report
PackageId: edi.979.1
Report Date/Time: 2022-11-18T11:17:31
Dataset Report
# Identifier Status Quality Check Name Description Expected Found Explanation Suggestion Reference
1packageIdPatternvalid
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 valuesedi.979.1
2emlVersionvalid
Type:metadata
System:lter
On failure:error
EML version 2.1.0 or beyondCheck the EML document declaration for version 2.1.0 or highereml://ecoinformatics.org/eml-2.1.0 or higherhttps://eml.ecoinformatics.org/eml-2.2.0Validity of this quality report is dependent on this check being valid.
3schemaValidvalid
Type:metadata
System:knb
On failure:error
Document is schema-valid EMLCheck document schema validityschema-validDocument validated for namespace: 'https://eml.ecoinformatics.org/eml-2.2.0'Validity of this quality report is dependent on this check being valid.
4parserValidvalid
Type:metadata
System:knb
On failure:error
Document is EML parser-validCheck document using the EML IDs and references parserValidates with the EML IDs and references parserEML IDs and references parser succeededValidity of this quality report is dependent on this check being valid.
5schemaValidDereferencedvalid
Type:metadata
System:lter
On failure:error
Dereferenced document is schema-valid EMLReferences are dereferenced, and the resulting file validatedschema-validDereferenced document validated for namespace: 'https://eml.ecoinformatics.org/eml-2.2.0'Validity of this quality report is dependent on this check being valid.
6keywordPresentvalid
Type:metadata
System:lter
On failure:warn
keyword element is presentChecks to see if at least one keyword is presentPresence of one or more keyword elements11 'keyword' element(s) found
7methodsElementPresentvalid
Type:metadata
System:lter
On failure:warn
A 'methods' element is presentAll 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) foundEML Best Practices, p. 28
8coveragePresentvalid
Type:metadata
System:lter
On failure:warn
coverage element is presentAt 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
9geographicCoveragePresentinfo
Type:metadata
System:lter
On failure:info
geographicCoverage is presentCheck that geographicCoverage exists in EML at the dataset level, or at least one entity's level, or at least one attribute's level.geographicCoverage at least at the dataset level.1 'geographicCoverage' element(s) foundMany 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.
10taxonomicCoveragePresentinfo
Type:metadata
System:lter
On failure:info
taxonomicCoverage is presentCheck 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) foundOnly 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
11temporalCoveragePresentinfo
Type:metadata
System:lter
On failure:info
temporalCoverage is presentCheck 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) foundLTER 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
12pastaDoiAbsentvalid
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 presentReject 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 packageNo PASTA DOI alternateIdentifier elements foundPASTA 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.
13titleLengthvalid
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 words21 words found.EML Best Practices, v.2, p. 13
14fundingPresencewarn
Type:metadata
System:lter
On failure:warn
check to see if funding element is presentChecks to see if the funding element is included.the funding element is expected to be includedfunding not foundSearches will want to display datasets by funder or grant id.Include the funding source, please.
15datasetAbstractLengthvalid
Type:metadata
System:lter
On failure:warn
Dataset abstract element is a minimum of 20 wordsCheck the length of a dataset abstract and warn if less than 20 words.An abstract is 20 words or more.165 words found.EML Best Practices
16duplicateEntityNamevalid
Type:metadata
System:lter
On failure:error
There are no duplicate entity namesChecks that content is not duplicated by other entityName elements in the documententityName is not a duplicate within the documentNo duplicates foundData Manager requires a non-empty, non-duplicate entityName value for every entityDeclare a non-empty entityName and ensure that there are no duplicate entityName values in the document
Entity Report
Entity Name: stations_SMSCG
Entity Identifier:
# Identifier Status Quality Check Name Description Expected Found Explanation Suggestion Reference
1entityNameLengthvalid
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 charactersentityName value is 100 characters or less14
2entityDescriptionPresentvalid
Type:metadata
System:lter
On failure:warn
An entity description is presentCheck for presence of an entity description.EML Best practices pp. 32-33, "...should have enough information for a user..."trueWith entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3numHeaderLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numHeaderLines' element is presentCheck for presence of the 'numHeaderLines' element.Document contains 'numHeaderLines' element.'numHeaderLines' element: 1
4numFooterLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numFooterLines' element is presentCheck for presence of the 'numFooterLines' element.Document contains 'numFooterLines' element.No 'numFooterLines' element foundIf data file contains footer lines, 'numFooterLines' must be specified.Add 'numFooterLines' element if needed.
5fieldDelimiterValidvalid
Type:metadata
System:knb
On failure:error
Field delimiter is a single characterField delimiters should be one character onlyA single character is expected,A valid fieldDelimiter value was foundhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6recordDelimiterPresentvalid
Type:metadata
System:knb
On failure:warn
Record delimiter is presentCheck 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\r\nA valid recordDelimiter value was foundhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7numberOfRecordsPresencevalid
Type:metadata
System:knb
On failure:warn
Is the numberOfRecords element present?Warn the user if the numberOfRecords check is not presentA number of records element is expected for this entitynumberOfRecords element foundThis is a valuable check that we have the correct table.
8entitySizePresencevalid
Type:metadata
System:knb
On failure:warn
Check for presence of an entity size elementLook 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 5071 and size unit specified as 'byte'.Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).Include an entity size in bytes Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
9integrityChecksumPresencevalid
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-1Check 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.truePASTA 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.
10attributeNamesUniquevalid
Type:metadata
System:knb
On failure:warn
Attribute names are uniqueChecks if attributeName values are unique in the table. Not required by EML.Unique attribute names.trueA good table does not have duplicate column names.EML Best Practices
11displayDownloadDatainfo
Type:data
System:knb
On failure:info
Display downloaded dataDisplay the first kilobyte of data that is downloadedUp to one kilobyte of data should be displayed
12urlReturnsDatavalid
Type:congruency
System:knb
On failure:error
URL returns dataChecks 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 metadatatruehttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
13onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: https://ezeml.edirepository.org/user-data/iep-6f022aeb59daaf04006d61b9f2d3a887/uploads/Suisun%20Marsh%20Salinity%20Control%20Gates/stations_SMSCG.csv
14integrityChecksumvalid
Type:congruency
System:lter
On failure:error
Compare the metadata checksum for an entity to the checksum of the downloaded entityTwo possible responses: valid if checksums match; error if checksums do not match.33e2fc1fedcf83144041fb946fb3dbb133e2fc1fedcf83144041fb946fb3dbb1Matching 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.
15entitySizeCongruencevalid
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.50715071Examining the entity size is a method for checking that this is the correct entity.Check the entity size.
16databaseTableCreatedvalid
Type:metadata
System:knb
On failure:error
Database table createdStatus of creating a database tableA database table is expected to be generated from the EML attributes.A database table was generated from the attributes descriptionCREATE TABLE stations_SMSCG("Project" TEXT,"StationCode" TEXT,"StationName" TEXT,"Longitude" FLOAT,"Latitude" FLOAT,"WQ" TEXT,"Zoops" TEXT,"Phyto" TEXT,"Clams" TEXT);
17examineRecordDelimitervalid
Type:congruency
System:knb
On failure:warn
Data are examined and possible record delimiters are displayedIf no record delimiter was specified, we assume that \r\n is the delimiter. Search the first row for other record delimiters and see if other delimiters are found.No other potential record delimiters expected in the first row.No other potential record delimiters were detected. A valid record delimiter was previously detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
18displayFirstInsertRowinfo
Type:data
System:knb
On failure:info
Display first insert rowDisplay the first row of data values to be inserted into the database tableThe first row of data values should be displayedEMP, D22, D22, -121.8288889, 38.06444444, N, Y, Y, N
19onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: file:///home/pasta/local/data/edi.979.1/877edca4c29ec491722e9d20a049a31c
20tooFewFieldsvalid
Type:congruency
System:knb
On failure:error
Data does not have fewer fields than metadata attributesCompare number of fields specified in metadata to number of fields found in a data recordNo errors detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#dataFormat
21tooManyFieldsvalid
Type:congruency
System:knb
On failure:error
Data does not have more fields than metadata attributesCompare number of fields specified in metadata to number of fields found in a data recordNo errors detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#dataFormat
22dataLoadStatusvalid
Type:congruency
System:knb
On failure:warn
Data can be loaded into the databaseStatus of loading the data table into a databaseNo errors expected during data loading or data loading was not attempted for this data entityThe data table loaded successfully into a database
23numberOfRecordsvalid
Type:congruency
System:knb
On failure:warn
Number of records in metadata matches number of rows loadedCompare number of records specified in metadata to number of records found in data9494The expected number of records (94) was found in the data table.
24headerRowAttributeNamesinfo
Type:congruency
System:lter
On failure:info
Header row is displayed alongside attribute namesCompare the content of the data header row to the content of EML attribute names.No expectation, information only Customer should evaluate the findings
25dateFormatMatchesvalid
Type:congruency
System:lter
On failure:warn
Date format in metadata matches datadateTime/formatString in attribute metadata is from the preferred list, and the data matches. A non-match generates only a warn.Format string is preferred, and all data values match the format stringData values matched the specified formatString.Dates should be consistently formatted and match the formatString in metadata.
Entity Report
Entity Name: gatedailylog_1988-2021
Entity Identifier:
# Identifier Status Quality Check Name Description Expected Found Explanation Suggestion Reference
1entityNameLengthvalid
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 charactersentityName value is 100 characters or less22
2entityDescriptionPresentvalid
Type:metadata
System:lter
On failure:warn
An entity description is presentCheck for presence of an entity description.EML Best practices pp. 32-33, "...should have enough information for a user..."trueWith entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3numHeaderLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numHeaderLines' element is presentCheck for presence of the 'numHeaderLines' element.Document contains 'numHeaderLines' element.'numHeaderLines' element: 1
4numFooterLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numFooterLines' element is presentCheck for presence of the 'numFooterLines' element.Document contains 'numFooterLines' element.No 'numFooterLines' element foundIf data file contains footer lines, 'numFooterLines' must be specified.Add 'numFooterLines' element if needed.
5fieldDelimiterValidvalid
Type:metadata
System:knb
On failure:error
Field delimiter is a single characterField delimiters should be one character onlyA single character is expected,A valid fieldDelimiter value was foundhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6recordDelimiterPresentvalid
Type:metadata
System:knb
On failure:warn
Record delimiter is presentCheck 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\nA valid recordDelimiter value was foundhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7numberOfRecordsPresencevalid
Type:metadata
System:knb
On failure:warn
Is the numberOfRecords element present?Warn the user if the numberOfRecords check is not presentA number of records element is expected for this entitynumberOfRecords element foundThis is a valuable check that we have the correct table.
8entitySizePresencevalid
Type:metadata
System:knb
On failure:warn
Check for presence of an entity size elementLook 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 1256728 and size unit specified as 'byte'.Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).Include an entity size in bytes Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
9integrityChecksumPresencevalid
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-1Check 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.truePASTA 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.
10dateTimeFormatStringvalid
Type:metadata
System:knb
On failure:warn
dateTime/formatString specified in metadata is from a preferred set of valuesCertain features of dateTime data formats are preferred, eg, ISO 8601, 4-digit years. This check looks at metadata to see if the dateTime format is in that preferred list.A formatString value that is a member of the preferred set is expected.YYYY-MM-DDA preferred format string was found.Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
11attributeNamesUniquevalid
Type:metadata
System:knb
On failure:warn
Attribute names are uniqueChecks if attributeName values are unique in the table. Not required by EML.Unique attribute names.trueA good table does not have duplicate column names.EML Best Practices
12displayDownloadDatainfo
Type:data
System:knb
On failure:info
Display downloaded dataDisplay the first kilobyte of data that is downloadedUp to one kilobyte of data should be displayed
13urlReturnsDatavalid
Type:congruency
System:knb
On failure:error
URL returns dataChecks 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 metadatatruehttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
14onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: https://ezeml.edirepository.org/user-data/iep-6f022aeb59daaf04006d61b9f2d3a887/uploads/Suisun%20Marsh%20Salinity%20Control%20Gates/SMSCG_GateDailyLog_1988-2021.csv
15integrityChecksumvalid
Type:congruency
System:lter
On failure:error
Compare the metadata checksum for an entity to the checksum of the downloaded entityTwo possible responses: valid if checksums match; error if checksums do not match.a92a27d4997764836cfa8ca79dd3616ea92a27d4997764836cfa8ca79dd3616eMatching 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.
16entitySizeCongruencevalid
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.12567281256728Examining the entity size is a method for checking that this is the correct entity.Check the entity size.
17databaseTableCreatedvalid
Type:metadata
System:knb
On failure:error
Database table createdStatus of creating a database tableA database table is expected to be generated from the EML attributes.A database table was generated from the attributes descriptionCREATE TABLE gatedailylog_1988_2021("Date" TIMESTAMP,"Flashboards" TEXT,"Gate1" TEXT,"Gate2" TEXT,"Gate3" TEXT,"Remark" TEXT,"Operating" TEXT);
18examineRecordDelimitervalid
Type:congruency
System:knb
On failure:warn
Data are examined and possible record delimiters are displayedIf no record delimiter was specified, we assume that \r\n is the delimiter. Search the first row for other record delimiters and see if other delimiters are found.No other potential record delimiters expected in the first row.No other potential record delimiters were detected. A valid record delimiter was previously detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
19displayFirstInsertRowinfo
Type:data
System:knb
On failure:info
Display first insert rowDisplay the first row of data values to be inserted into the database tableThe first row of data values should be displayed1988-11-01, IN, OP, OP, OP, full bore operation, Operating normally
20onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: file:///home/pasta/local/data/edi.979.1/8585dd61b0a275f93492d36795cd8a53
21tooFewFieldsvalid
Type:congruency
System:knb
On failure:error
Data does not have fewer fields than metadata attributesCompare number of fields specified in metadata to number of fields found in a data recordNo errors detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#dataFormat
22tooManyFieldsvalid
Type:congruency
System:knb
On failure:error
Data does not have more fields than metadata attributesCompare number of fields specified in metadata to number of fields found in a data recordNo errors detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#dataFormat
23dataLoadStatusvalid
Type:congruency
System:knb
On failure:warn
Data can be loaded into the databaseStatus of loading the data table into a databaseNo errors expected during data loading or data loading was not attempted for this data entityThe data table loaded successfully into a database
24numberOfRecordsvalid
Type:congruency
System:knb
On failure:warn
Number of records in metadata matches number of rows loadedCompare number of records specified in metadata to number of records found in data1211712117The expected number of records (12117) was found in the data table.
25headerRowAttributeNamesinfo
Type:congruency
System:lter
On failure:info
Header row is displayed alongside attribute namesCompare the content of the data header row to the content of EML attribute names.No expectation, information only Customer should evaluate the findings
26dateFormatMatchesvalid
Type:congruency
System:lter
On failure:warn
Date format in metadata matches datadateTime/formatString in attribute metadata is from the preferred list, and the data matches. A non-match generates only a warn.Format string is preferred, and all data values match the format stringData values matched the specified formatString.Dates should be consistently formatted and match the formatString in metadata.
Entity Report
Entity Name: WQdata_smscg_2018-2021
Entity Identifier:
# Identifier Status Quality Check Name Description Expected Found Explanation Suggestion Reference
1entityNameLengthvalid
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 charactersentityName value is 100 characters or less22
2entityDescriptionPresentvalid
Type:metadata
System:lter
On failure:warn
An entity description is presentCheck for presence of an entity description.EML Best practices pp. 32-33, "...should have enough information for a user..."trueWith entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3numHeaderLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numHeaderLines' element is presentCheck for presence of the 'numHeaderLines' element.Document contains 'numHeaderLines' element.'numHeaderLines' element: 1
4numFooterLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numFooterLines' element is presentCheck for presence of the 'numFooterLines' element.Document contains 'numFooterLines' element.No 'numFooterLines' element foundIf data file contains footer lines, 'numFooterLines' must be specified.Add 'numFooterLines' element if needed.
5fieldDelimiterValidvalid
Type:metadata
System:knb
On failure:error
Field delimiter is a single characterField delimiters should be one character onlyA single character is expected,A valid fieldDelimiter value was foundhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6recordDelimiterPresentvalid
Type:metadata
System:knb
On failure:warn
Record delimiter is presentCheck 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\nA valid recordDelimiter value was foundhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7numberOfRecordsPresencevalid
Type:metadata
System:knb
On failure:warn
Is the numberOfRecords element present?Warn the user if the numberOfRecords check is not presentA number of records element is expected for this entitynumberOfRecords element foundThis is a valuable check that we have the correct table.
8entitySizePresencevalid
Type:metadata
System:knb
On failure:warn
Check for presence of an entity size elementLook 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 108403291 and size unit specified as 'byte'.Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).Include an entity size in bytes Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
9integrityChecksumPresencevalid
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-1Check 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.truePASTA 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.
10dateTimeFormatStringvalid
Type:metadata
System:knb
On failure:warn
dateTime/formatString specified in metadata is from a preferred set of valuesCertain features of dateTime data formats are preferred, eg, ISO 8601, 4-digit years. This check looks at metadata to see if the dateTime format is in that preferred list.A formatString value that is a member of the preferred set is expected.YYYY-MM-DDThh:mm:ssZA preferred format string was found.Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
11attributeNamesUniquevalid
Type:metadata
System:knb
On failure:warn
Attribute names are uniqueChecks if attributeName values are unique in the table. Not required by EML.Unique attribute names.trueA good table does not have duplicate column names.EML Best Practices
12displayDownloadDatainfo
Type:data
System:knb
On failure:info
Display downloaded dataDisplay the first kilobyte of data that is downloadedUp to one kilobyte of data should be displayed
13urlReturnsDatavalid
Type:congruency
System:knb
On failure:error
URL returns dataChecks 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 metadatatruehttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
14onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: https://ezeml.edirepository.org/user-data/iep-6f022aeb59daaf04006d61b9f2d3a887/uploads/Suisun%20Marsh%20Salinity%20Control%20Gates/WQdata_smscg_2018-2021_FlaggedBadRemoved_clean.csv
15integrityChecksumvalid
Type:congruency
System:lter
On failure:error
Compare the metadata checksum for an entity to the checksum of the downloaded entityTwo possible responses: valid if checksums match; error if checksums do not match.b65f48f934762cccd96f6a5dfb6daf62b65f48f934762cccd96f6a5dfb6daf62Matching 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.
16entitySizeCongruencevalid
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.108403291108403291Examining the entity size is a method for checking that this is the correct entity.Check the entity size.
17databaseTableCreatedvalid
Type:metadata
System:knb
On failure:error
Database table createdStatus of creating a database tableA database table is expected to be generated from the EML attributes.A database table was generated from the attributes descriptionCREATE TABLE WQdata_smscg_2018_2021("cdec_code" TEXT,"analyte_name" TEXT,"unit_name" TEXT,"time" TIMESTAMP,"value" FLOAT,"qaqc_flag_id" TEXT);
18examineRecordDelimitervalid
Type:congruency
System:knb
On failure:warn
Data are examined and possible record delimiters are displayedIf no record delimiter was specified, we assume that \r\n is the delimiter. Search the first row for other record delimiters and see if other delimiters are found.No other potential record delimiters expected in the first row.No other potential record delimiters were detected. A valid record delimiter was previously detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
19displayFirstInsertRowinfo
Type:data
System:knb
On failure:info
Display first insert rowDisplay the first row of data values to be inserted into the database tableThe first row of data values should be displayedCSE, Specific Conductance, uS/cm, 2018-01-01T00:00:00Z, 3465.8, G
20onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: file:///home/pasta/local/data/edi.979.1/c73753ce273277cae690d14bba8270f0
21tooFewFieldsvalid
Type:congruency
System:knb
On failure:error
Data does not have fewer fields than metadata attributesCompare number of fields specified in metadata to number of fields found in a data recordNo errors detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#dataFormat
22tooManyFieldsvalid
Type:congruency
System:knb
On failure:error
Data does not have more fields than metadata attributesCompare number of fields specified in metadata to number of fields found in a data recordNo errors detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#dataFormat
23dataLoadStatusvalid
Type:congruency
System:knb
On failure:warn
Data can be loaded into the databaseStatus of loading the data table into a databaseNo errors expected during data loading or data loading was not attempted for this data entityThe data table loaded successfully into a database
24numberOfRecordsvalid
Type:congruency
System:knb
On failure:warn
Number of records in metadata matches number of rows loadedCompare number of records specified in metadata to number of records found in data20822212082221The expected number of records (2082221) was found in the data table.
25headerRowAttributeNamesinfo
Type:congruency
System:lter
On failure:info
Header row is displayed alongside attribute namesCompare the content of the data header row to the content of EML attribute names.No expectation, information only Customer should evaluate the findings
26dateFormatMatchesvalid
Type:congruency
System:lter
On failure:warn
Date format in metadata matches datadateTime/formatString in attribute metadata is from the preferred list, and the data matches. A non-match generates only a warn.Format string is preferred, and all data values match the format stringData values matched the specified formatString.Dates should be consistently formatted and match the formatString in metadata.
Entity Report
Entity Name: SMSCG_phytoplankton_formatted_2020-2021
Entity Identifier:
# Identifier Status Quality Check Name Description Expected Found Explanation Suggestion Reference
1entityNameLengthvalid
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 charactersentityName value is 100 characters or less39
2entityDescriptionPresentvalid
Type:metadata
System:lter
On failure:warn
An entity description is presentCheck for presence of an entity description.EML Best practices pp. 32-33, "...should have enough information for a user..."trueWith entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3numHeaderLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numHeaderLines' element is presentCheck for presence of the 'numHeaderLines' element.Document contains 'numHeaderLines' element.'numHeaderLines' element: 1
4numFooterLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numFooterLines' element is presentCheck for presence of the 'numFooterLines' element.Document contains 'numFooterLines' element.No 'numFooterLines' element foundIf data file contains footer lines, 'numFooterLines' must be specified.Add 'numFooterLines' element if needed.
5fieldDelimiterValidvalid
Type:metadata
System:knb
On failure:error
Field delimiter is a single characterField delimiters should be one character onlyA single character is expected,A valid fieldDelimiter value was foundhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6recordDelimiterPresentvalid
Type:metadata
System:knb
On failure:warn
Record delimiter is presentCheck 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\nA valid recordDelimiter value was foundhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7numberOfRecordsPresencevalid
Type:metadata
System:knb
On failure:warn
Is the numberOfRecords element present?Warn the user if the numberOfRecords check is not presentA number of records element is expected for this entitynumberOfRecords element foundThis is a valuable check that we have the correct table.
8entitySizePresencevalid
Type:metadata
System:knb
On failure:warn
Check for presence of an entity size elementLook 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 151213 and size unit specified as 'byte'.Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).Include an entity size in bytes Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
9integrityChecksumPresencevalid
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-1Check 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.truePASTA 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.
10dateTimeFormatStringvalid
Type:metadata
System:knb
On failure:warn
dateTime/formatString specified in metadata is from a preferred set of valuesCertain features of dateTime data formats are preferred, eg, ISO 8601, 4-digit years. This check looks at metadata to see if the dateTime format is in that preferred list.A formatString value that is a member of the preferred set is expected.YYYY-MM-DDA preferred format string was found.Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
11attributeNamesUniquevalid
Type:metadata
System:knb
On failure:warn
Attribute names are uniqueChecks if attributeName values are unique in the table. Not required by EML.Unique attribute names.trueA good table does not have duplicate column names.EML Best Practices
12displayDownloadDatainfo
Type:data
System:knb
On failure:info
Display downloaded dataDisplay the first kilobyte of data that is downloadedUp to one kilobyte of data should be displayed
13urlReturnsDatavalid
Type:congruency
System:knb
On failure:error
URL returns dataChecks 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 metadatatruehttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
14onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: https://ezeml.edirepository.org/user-data/iep-6f022aeb59daaf04006d61b9f2d3a887/uploads/Suisun%20Marsh%20Salinity%20Control%20Gates/SMSCG_phytoplankton_formatted_2020-2021.csv
15integrityChecksumvalid
Type:congruency
System:lter
On failure:error
Compare the metadata checksum for an entity to the checksum of the downloaded entityTwo possible responses: valid if checksums match; error if checksums do not match.f508f43b4e15dd95e1dd919f4a5f5ce8f508f43b4e15dd95e1dd919f4a5f5ce8Matching 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.
16entitySizeCongruencevalid
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.151213151213Examining the entity size is a method for checking that this is the correct entity.Check the entity size.
17databaseTableCreatedvalid
Type:metadata
System:knb
On failure:error
Database table createdStatus of creating a database tableA database table is expected to be generated from the EML attributes.A database table was generated from the attributes descriptionCREATE TABLE SMSCG_phytoplankton_formatted_("station" TEXT,"station_comb" TEXT,"region" TEXT,"collected_by" TEXT,"date" TIMESTAMP,"time_pst" TEXT,"kingdom" TEXT,"phylum" TEXT,"class" TEXT,"genus" TEXT,"taxon" TEXT,"phyto_form" TEXT,"organisms_per_ml" FLOAT,"cells_per_ml" FLOAT,"biovolume_per_ml" FLOAT);
18examineRecordDelimitervalid
Type:congruency
System:knb
On failure:warn
Data are examined and possible record delimiters are displayedIf no record delimiter was specified, we assume that \r\n is the delimiter. Search the first row for other record delimiters and see if other delimiters are found.No other potential record delimiters expected in the first row.No other potential record delimiters were detected. A valid record delimiter was previously detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
19displayFirstInsertRowinfo
Type:data
System:knb
On failure:info
Display first insert rowDisplay the first row of data values to be inserted into the database tableThe first row of data values should be displayedEMP_EZ2-SJR, EZ2-SJR, FT, EMP, 2020-07-09, 07:05:00, Chromista, Bacillariophyta, Bacillariophyceae, Navicula, Navicula cf. weberi, i, 184, 184, 261519.5
20onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: file:///home/pasta/local/data/edi.979.1/4c909be218caba4e63469c1126d17368
21tooFewFieldsvalid
Type:congruency
System:knb
On failure:error
Data does not have fewer fields than metadata attributesCompare number of fields specified in metadata to number of fields found in a data recordNo errors detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#dataFormat
22tooManyFieldsvalid
Type:congruency
System:knb
On failure:error
Data does not have more fields than metadata attributesCompare number of fields specified in metadata to number of fields found in a data recordNo errors detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#dataFormat
23dataLoadStatusvalid
Type:congruency
System:knb
On failure:warn
Data can be loaded into the databaseStatus of loading the data table into a databaseNo errors expected during data loading or data loading was not attempted for this data entityThe data table loaded successfully into a database
24numberOfRecordsvalid
Type:congruency
System:knb
On failure:warn
Number of records in metadata matches number of rows loadedCompare number of records specified in metadata to number of records found in data11551155The expected number of records (1155) was found in the data table.
25headerRowAttributeNamesinfo
Type:congruency
System:lter
On failure:info
Header row is displayed alongside attribute namesCompare the content of the data header row to the content of EML attribute names.No expectation, information only Customer should evaluate the findings
26dateFormatMatchesvalid
Type:congruency
System:lter
On failure:warn
Date format in metadata matches datadateTime/formatString in attribute metadata is from the preferred list, and the data matches. A non-match generates only a warn.Format string is preferred, and all data values match the format stringData values matched the specified formatString.Dates should be consistently formatted and match the formatString in metadata.
Entity Report
Entity Name: SMSCG_Zooplankton_CBNet_2018to2021
Entity Identifier:
# Identifier Status Quality Check Name Description Expected Found Explanation Suggestion Reference
1entityNameLengthvalid
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 charactersentityName value is 100 characters or less34
2entityDescriptionPresentvalid
Type:metadata
System:lter
On failure:warn
An entity description is presentCheck for presence of an entity description.EML Best practices pp. 32-33, "...should have enough information for a user..."trueWith entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3numHeaderLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numHeaderLines' element is presentCheck for presence of the 'numHeaderLines' element.Document contains 'numHeaderLines' element.'numHeaderLines' element: 1
4numFooterLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numFooterLines' element is presentCheck for presence of the 'numFooterLines' element.Document contains 'numFooterLines' element.No 'numFooterLines' element foundIf data file contains footer lines, 'numFooterLines' must be specified.Add 'numFooterLines' element if needed.
5fieldDelimiterValidvalid
Type:metadata
System:knb
On failure:error
Field delimiter is a single characterField delimiters should be one character onlyA single character is expected,A valid fieldDelimiter value was foundhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6recordDelimiterPresentvalid
Type:metadata
System:knb
On failure:warn
Record delimiter is presentCheck 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\nA valid recordDelimiter value was foundhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7numberOfRecordsPresencevalid
Type:metadata
System:knb
On failure:warn
Is the numberOfRecords element present?Warn the user if the numberOfRecords check is not presentA number of records element is expected for this entitynumberOfRecords element foundThis is a valuable check that we have the correct table.
8entitySizePresencevalid
Type:metadata
System:knb
On failure:warn
Check for presence of an entity size elementLook 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 162257 and size unit specified as 'byte'.Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).Include an entity size in bytes Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
9integrityChecksumPresencevalid
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-1Check 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.truePASTA 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.
10dateTimeFormatStringvalid
Type:metadata
System:knb
On failure:warn
dateTime/formatString specified in metadata is from a preferred set of valuesCertain features of dateTime data formats are preferred, eg, ISO 8601, 4-digit years. This check looks at metadata to see if the dateTime format is in that preferred list.A formatString value that is a member of the preferred set is expected.YYYY-MM-DDA preferred format string was found.Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
11attributeNamesUniquevalid
Type:metadata
System:knb
On failure:warn
Attribute names are uniqueChecks if attributeName values are unique in the table. Not required by EML.Unique attribute names.trueA good table does not have duplicate column names.EML Best Practices
12displayDownloadDatainfo
Type:data
System:knb
On failure:info
Display downloaded dataDisplay the first kilobyte of data that is downloadedUp to one kilobyte of data should be displayed
13urlReturnsDatavalid
Type:congruency
System:knb
On failure:error
URL returns dataChecks 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 metadatatruehttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
14onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: https://ezeml.edirepository.org/user-data/iep-6f022aeb59daaf04006d61b9f2d3a887/uploads/Suisun%20Marsh%20Salinity%20Control%20Gates/SMSCG_Zooplankton_CBNet_2018to2021.csv
15integrityChecksumvalid
Type:congruency
System:lter
On failure:error
Compare the metadata checksum for an entity to the checksum of the downloaded entityTwo possible responses: valid if checksums match; error if checksums do not match.c5666c6e6472ed6b2e7699ae5bf6509cc5666c6e6472ed6b2e7699ae5bf6509cMatching 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.
16entitySizeCongruencevalid
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.162257162257Examining the entity size is a method for checking that this is the correct entity.Check the entity size.
17databaseTableCreatedvalid
Type:metadata
System:knb
On failure:error
Database table createdStatus of creating a database tableA database table is expected to be generated from the EML attributes.A database table was generated from the attributes descriptionCREATE TABLE SMSCG_Zooplankton_CBNet_2018to("Project" TEXT,"Year" TEXT,"Survey" FLOAT,"Month" TEXT,"Date" TIMESTAMP,"Station" TEXT,"Time" TEXT,"TowDuration" FLOAT,"Region" TEXT,"TideCode" TEXT,"DepthBottom" FLOAT,"CondSurf" FLOAT,"PPTSurf" FLOAT,"CondBott" FLOAT,"PPTBott" FLOAT,"TempSurf" FLOAT,"TempBottom" FLOAT,"Secchi" FLOAT,"Turbidity" FLOAT,"Microcystis" TEXT,"TotalMeter" FLOAT,"MeterEstimate" TEXT,"Volume" FLOAT,"ACARTELA" FLOAT,"ACARTIA" FLOAT,"DIAPTOM" FLOAT,"EURYTEM" FLOAT,"OTHCALAD" FLOAT,"PDIAPFOR" FLOAT,"PDIAPMAR" FLOAT,"SINOCAL" FLOAT,"TORTANUS" FLOAT,"ALLCALADULTS" FLOAT,"ACANTHO" FLOAT,"LIMNOSPP" TEXT,"LIMNOSINE" FLOAT,"LIMNOTET" FLOAT,"OITHDAV" FLOAT,"OITHSIM" TEXT,"OITHSPP" FLOAT,"OTHCYCAD" FLOAT,"ALLCYCADULTS" FLOAT,"HARPACT" FLOAT,"EURYJUV" FLOAT,"OTHCALJUV" FLOAT,"PDIAPJUV" FLOAT,"SINOCALJUV" FLOAT,"ASINEJUV" FLOAT,"ACARJUV" FLOAT,"DIAPTJUV" FLOAT,"TORTJUV" FLOAT,"ALLCALJUV" FLOAT,"LIMNOJUV" FLOAT,"OITHJUV" FLOAT,"OTHCYCJUV" FLOAT,"ALLCYCJUV" FLOAT,"EURYNAUP" FLOAT,"OTHCOPNAUP" FLOAT,"PDIAPNAUP" FLOAT,"SINONAUP" FLOAT,"ALLCOPNAUP" FLOAT,"BOSMINA" FLOAT,"DAPHNIA" FLOAT,"DIAPHAN" FLOAT,"OTHCLADO" FLOAT,"ALLCLADOCERA" FLOAT,"ASPLANCH" FLOAT,"KERATELA" FLOAT,"OTHROT" FLOAT,"POLYARTH" FLOAT,"SYNCH" FLOAT,"TRICHO" FLOAT,"ALLROTIFERS" FLOAT,"BARNNAUP" FLOAT,"CRABZOEA" FLOAT,"OSTRACOD" FLOAT,"CUMAC" FLOAT);
18examineRecordDelimitervalid
Type:congruency
System:knb
On failure:warn
Data are examined and possible record delimiters are displayedIf no record delimiter was specified, we assume that \r\n is the delimiter. Search the first row for other record delimiters and see if other delimiters are found.No other potential record delimiters expected in the first row.No other potential record delimiters were detected. A valid record delimiter was previously detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
19displayFirstInsertRowinfo
Type:data
System:knb
On failure:info
Display first insert rowDisplay the first row of data values to be inserted into the database tableThe first row of data values should be displayed
20onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: file:///home/pasta/local/data/edi.979.1/98795b108d5c1b34ebce4d8567a962d1
21tooFewFieldsvalid
Type:congruency
System:knb
On failure:error
Data does not have fewer fields than metadata attributesCompare number of fields specified in metadata to number of fields found in a data recordNo errors detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#dataFormat
22tooManyFieldsvalid
Type:congruency
System:knb
On failure:error
Data does not have more fields than metadata attributesCompare number of fields specified in metadata to number of fields found in a data recordNo errors detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#dataFormat
23dataLoadStatusvalid
Type:congruency
System:knb
On failure:warn
Data can be loaded into the databaseStatus of loading the data table into a databaseNo errors expected during data loading or data loading was not attempted for this data entityThe data table loaded successfully into a database
24numberOfRecordsvalid
Type:congruency
System:knb
On failure:warn
Number of records in metadata matches number of rows loadedCompare number of records specified in metadata to number of records found in data581581The expected number of records (581) was found in the data table.
25headerRowAttributeNamesinfo
Type:congruency
System:lter
On failure:info
Header row is displayed alongside attribute namesCompare the content of the data header row to the content of EML attribute names.No expectation, information only Customer should evaluate the findings
26dateFormatMatchesvalid
Type:congruency
System:lter
On failure:warn
Date format in metadata matches datadateTime/formatString in attribute metadata is from the preferred list, and the data matches. A non-match generates only a warn.Format string is preferred, and all data values match the format stringData values matched the specified formatString.Dates should be consistently formatted and match the formatString in metadata.
Entity Report
Entity Name: SMSCG_Zooplankton_Mysid_2018to2019
Entity Identifier:
# Identifier Status Quality Check Name Description Expected Found Explanation Suggestion Reference
1entityNameLengthvalid
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 charactersentityName value is 100 characters or less34
2entityDescriptionPresentvalid
Type:metadata
System:lter
On failure:warn
An entity description is presentCheck for presence of an entity description.EML Best practices pp. 32-33, "...should have enough information for a user..."trueWith entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3numHeaderLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numHeaderLines' element is presentCheck for presence of the 'numHeaderLines' element.Document contains 'numHeaderLines' element.'numHeaderLines' element: 1
4numFooterLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numFooterLines' element is presentCheck for presence of the 'numFooterLines' element.Document contains 'numFooterLines' element.No 'numFooterLines' element foundIf data file contains footer lines, 'numFooterLines' must be specified.Add 'numFooterLines' element if needed.
5fieldDelimiterValidvalid
Type:metadata
System:knb
On failure:error
Field delimiter is a single characterField delimiters should be one character onlyA single character is expected,A valid fieldDelimiter value was foundhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6recordDelimiterPresentvalid
Type:metadata
System:knb
On failure:warn
Record delimiter is presentCheck 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\nA valid recordDelimiter value was foundhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7numberOfRecordsPresencevalid
Type:metadata
System:knb
On failure:warn
Is the numberOfRecords element present?Warn the user if the numberOfRecords check is not presentA number of records element is expected for this entitynumberOfRecords element foundThis is a valuable check that we have the correct table.
8entitySizePresencevalid
Type:metadata
System:knb
On failure:warn
Check for presence of an entity size elementLook 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 25865 and size unit specified as 'byte'.Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).Include an entity size in bytes Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
9integrityChecksumPresencevalid
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-1Check 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.truePASTA 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.
10dateTimeFormatStringvalid
Type:metadata
System:knb
On failure:warn
dateTime/formatString specified in metadata is from a preferred set of valuesCertain features of dateTime data formats are preferred, eg, ISO 8601, 4-digit years. This check looks at metadata to see if the dateTime format is in that preferred list.A formatString value that is a member of the preferred set is expected.YYYY-MM-DDA preferred format string was found.Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
11attributeNamesUniquevalid
Type:metadata
System:knb
On failure:warn
Attribute names are uniqueChecks if attributeName values are unique in the table. Not required by EML.Unique attribute names.trueA good table does not have duplicate column names.EML Best Practices
12displayDownloadDatainfo
Type:data
System:knb
On failure:info
Display downloaded dataDisplay the first kilobyte of data that is downloadedUp to one kilobyte of data should be displayed
13urlReturnsDatavalid
Type:congruency
System:knb
On failure:error
URL returns dataChecks 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 metadatatruehttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
14onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: https://ezeml.edirepository.org/user-data/iep-6f022aeb59daaf04006d61b9f2d3a887/uploads/Suisun%20Marsh%20Salinity%20Control%20Gates/SMSCG_Zooplankton_Mysid_2018to2019.csv
15integrityChecksumvalid
Type:congruency
System:lter
On failure:error
Compare the metadata checksum for an entity to the checksum of the downloaded entityTwo possible responses: valid if checksums match; error if checksums do not match.e7c8f2032b27e9f06fd1584549b7f601e7c8f2032b27e9f06fd1584549b7f601Matching 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.
16entitySizeCongruencevalid
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.2586525865Examining the entity size is a method for checking that this is the correct entity.Check the entity size.
17databaseTableCreatedvalid
Type:metadata
System:knb
On failure:error
Database table createdStatus of creating a database tableA database table is expected to be generated from the EML attributes.A database table was generated from the attributes descriptionCREATE TABLE SMSCG_Zooplankton_Mysid_2018to("Project" TEXT,"Year" TEXT,"Survey" FLOAT,"Month" TEXT,"Date" TIMESTAMP,"Station" TEXT,"Time" TEXT,"TowDuration" FLOAT,"Region" TEXT,"TideCode" TEXT,"DepthBottom" FLOAT,"CondSurf" FLOAT,"PPTSurf" FLOAT,"CondBott" FLOAT,"PPTBott" FLOAT,"TempSurf" FLOAT,"TempBottom" FLOAT,"Secchi" FLOAT,"Turbidity" FLOAT,"Microcystis" TEXT,"TotalMeter" FLOAT,"MeterEstimated" TEXT,"Volume" FLOAT,"Acanthomysis_aspera" FLOAT,"Hyperacanthomysis_longirostris" FLOAT,"Acanthomysis_hwanhaiensis" FLOAT,"Alienacanthomysis_macropsis" FLOAT,"Deltamysis_holmquistae" FLOAT,"Neomysis_kadiakensis" FLOAT,"Neomysis_mercedis" FLOAT,"Unidentified_Mysid" FLOAT,"Americorophium_spinicorne" FLOAT,"Americorophium_stimpsoni" FLOAT,"Ampelisca_abdita" FLOAT,"Corophium_alienense" FLOAT,"Crangonyx_sp" FLOAT,"Gammarus_daiberi" FLOAT,"Grandidierella_japonica" FLOAT,"Hyalella_sp" FLOAT,"Unidentified_Amphipod" FLOAT,"Unidentified_Corophium" FLOAT,"Unidentified_Gammarus" FLOAT);
18examineRecordDelimitervalid
Type:congruency
System:knb
On failure:warn
Data are examined and possible record delimiters are displayedIf no record delimiter was specified, we assume that \r\n is the delimiter. Search the first row for other record delimiters and see if other delimiters are found.No other potential record delimiters expected in the first row.No other potential record delimiters were detected. A valid record delimiter was previously detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
19displayFirstInsertRowinfo
Type:data
System:knb
On failure:info
Display first insert rowDisplay the first row of data values to be inserted into the database tableThe first row of data values should be displayedSTN, 2018, 3, 7, 2018-07-11, Honk, 10:16:00, 10, Suisun Bay (Honker), 3, 1.2, NA, NA, NA, NA, NA, NA, NA, NA, NA, 31314, Y, 52.17, 0, 0.56, 0, 0, 0, 0.42, 0, 0, 0.04, 0, 0, 0, 0, 0.04, NA, 0, 0, 0, 0
20onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: file:///home/pasta/local/data/edi.979.1/bd763cbc95cd3bf4e82bc13af0ff8fbc
21tooFewFieldsvalid
Type:congruency
System:knb
On failure:error
Data does not have fewer fields than metadata attributesCompare number of fields specified in metadata to number of fields found in a data recordNo errors detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#dataFormat
22tooManyFieldsvalid
Type:congruency
System:knb
On failure:error
Data does not have more fields than metadata attributesCompare number of fields specified in metadata to number of fields found in a data recordNo errors detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#dataFormat
23dataLoadStatusvalid
Type:congruency
System:knb
On failure:warn
Data can be loaded into the databaseStatus of loading the data table into a databaseNo errors expected during data loading or data loading was not attempted for this data entityThe data table loaded successfully into a database
24numberOfRecordsvalid
Type:congruency
System:knb
On failure:warn
Number of records in metadata matches number of rows loadedCompare number of records specified in metadata to number of records found in data153153The expected number of records (153) was found in the data table.
25headerRowAttributeNamesinfo
Type:congruency
System:lter
On failure:info
Header row is displayed alongside attribute namesCompare the content of the data header row to the content of EML attribute names.No expectation, information only Customer should evaluate the findings
26dateFormatMatchesvalid
Type:congruency
System:lter
On failure:warn
Date format in metadata matches datadateTime/formatString in attribute metadata is from the preferred list, and the data matches. A non-match generates only a warn.Format string is preferred, and all data values match the format stringData values matched the specified formatString.Dates should be consistently formatted and match the formatString in metadata.
Entity Report
Entity Name: FMWT_STN_ZoopTaxon_Lookup
Entity Identifier:
# Identifier Status Quality Check Name Description Expected Found Explanation Suggestion Reference
1entityNameLengthvalid
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 charactersentityName value is 100 characters or less25
2entityDescriptionPresentvalid
Type:metadata
System:lter
On failure:warn
An entity description is presentCheck for presence of an entity description.EML Best practices pp. 32-33, "...should have enough information for a user..."trueWith entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3numHeaderLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numHeaderLines' element is presentCheck for presence of the 'numHeaderLines' element.Document contains 'numHeaderLines' element.'numHeaderLines' element: 1
4numFooterLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numFooterLines' element is presentCheck for presence of the 'numFooterLines' element.Document contains 'numFooterLines' element.No 'numFooterLines' element foundIf data file contains footer lines, 'numFooterLines' must be specified.Add 'numFooterLines' element if needed.
5fieldDelimiterValidvalid
Type:metadata
System:knb
On failure:error
Field delimiter is a single characterField delimiters should be one character onlyA single character is expected,A valid fieldDelimiter value was foundhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6recordDelimiterPresentvalid
Type:metadata
System:knb
On failure:warn
Record delimiter is presentCheck 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\r\nA valid recordDelimiter value was foundhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7numberOfRecordsPresencevalid
Type:metadata
System:knb
On failure:warn
Is the numberOfRecords element present?Warn the user if the numberOfRecords check is not presentA number of records element is expected for this entitynumberOfRecords element foundThis is a valuable check that we have the correct table.
8entitySizePresencevalid
Type:metadata
System:knb
On failure:warn
Check for presence of an entity size elementLook 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 7603 and size unit specified as 'byte'.Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).Include an entity size in bytes Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
9integrityChecksumPresencevalid
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-1Check 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.truePASTA 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.
10dateTimeFormatStringvalid
Type:metadata
System:knb
On failure:warn
dateTime/formatString specified in metadata is from a preferred set of valuesCertain features of dateTime data formats are preferred, eg, ISO 8601, 4-digit years. This check looks at metadata to see if the dateTime format is in that preferred list.A formatString value that is a member of the preferred set is expected.YYYYA preferred format string was found.Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
11attributeNamesUniquevalid
Type:metadata
System:knb
On failure:warn
Attribute names are uniqueChecks if attributeName values are unique in the table. Not required by EML.Unique attribute names.trueA good table does not have duplicate column names.EML Best Practices
12displayDownloadDatainfo
Type:data
System:knb
On failure:info
Display downloaded dataDisplay the first kilobyte of data that is downloadedUp to one kilobyte of data should be displayed
13urlReturnsDatavalid
Type:congruency
System:knb
On failure:error
URL returns dataChecks 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 metadatatruehttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
14onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: https://ezeml.edirepository.org/user-data/iep-6f022aeb59daaf04006d61b9f2d3a887/uploads/Suisun%20Marsh%20Salinity%20Control%20Gates/FMWT_STN_ZoopTaxon_Lookup.csv
15integrityChecksumvalid
Type:congruency
System:lter
On failure:error
Compare the metadata checksum for an entity to the checksum of the downloaded entityTwo possible responses: valid if checksums match; error if checksums do not match.5d7af0b0a960536fae61bf20c07d84895d7af0b0a960536fae61bf20c07d8489Matching 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.
16entitySizeCongruencevalid
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.76037603Examining the entity size is a method for checking that this is the correct entity.Check the entity size.
17databaseTableCreatedvalid
Type:metadata
System:knb
On failure:error
Database table createdStatus of creating a database tableA database table is expected to be generated from the EML attributes.A database table was generated from the attributes descriptionCREATE TABLE FMWT_STN_ZoopTaxon_Lookup("ZooCode" TEXT,"LifeStage" TEXT,"TaxonName" TEXT,"Phylum" TEXT,"Class" TEXT,"Order" TEXT,"Family" TEXT,"Genus" TEXT,"Species" TEXT,"Start_Year" TIMESTAMP,"Notes" TEXT);
18examineRecordDelimitervalid
Type:congruency
System:knb
On failure:warn
Data are examined and possible record delimiters are displayedIf no record delimiter was specified, we assume that \r\n is the delimiter. Search the first row for other record delimiters and see if other delimiters are found.No other potential record delimiters expected in the first row.No other potential record delimiters were detected. A valid record delimiter was previously detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
19displayFirstInsertRowinfo
Type:data
System:knb
On failure:info
Display first insert rowDisplay the first row of data values to be inserted into the database tableThe first row of data values should be displayedAmpelisca_abdita, All, Ampelisca abdita, Arthropoda, Malacostraca, Amphipoda, Gammaridae, Ampelisca, abdita, 2013,
20onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: file:///home/pasta/local/data/edi.979.1/2247db24327c7c6d562d67a8fde0e937
21tooFewFieldsvalid
Type:congruency
System:knb
On failure:error
Data does not have fewer fields than metadata attributesCompare number of fields specified in metadata to number of fields found in a data recordNo errors detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#dataFormat
22tooManyFieldsvalid
Type:congruency
System:knb
On failure:error
Data does not have more fields than metadata attributesCompare number of fields specified in metadata to number of fields found in a data recordNo errors detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#dataFormat
23dataLoadStatusvalid
Type:congruency
System:knb
On failure:warn
Data can be loaded into the databaseStatus of loading the data table into a databaseNo errors expected during data loading or data loading was not attempted for this data entityThe data table loaded successfully into a database
24numberOfRecordsvalid
Type:congruency
System:knb
On failure:warn
Number of records in metadata matches number of rows loadedCompare number of records specified in metadata to number of records found in data7373The expected number of records (73) was found in the data table.
25headerRowAttributeNamesinfo
Type:congruency
System:lter
On failure:info
Header row is displayed alongside attribute namesCompare the content of the data header row to the content of EML attribute names.No expectation, information only Customer should evaluate the findings
26dateFormatMatchesvalid
Type:congruency
System:lter
On failure:warn
Date format in metadata matches datadateTime/formatString in attribute metadata is from the preferred list, and the data matches. A non-match generates only a warn.Format string is preferred, and all data values match the format stringData values matched the specified formatString.Dates should be consistently formatted and match the formatString in metadata.
Entity Report
Entity Name: SMSCG_clam_EDI_2018_2021
Entity Identifier:
# Identifier Status Quality Check Name Description Expected Found Explanation Suggestion Reference
1entityNameLengthvalid
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 charactersentityName value is 100 characters or less24
2entityDescriptionPresentvalid
Type:metadata
System:lter
On failure:warn
An entity description is presentCheck for presence of an entity description.EML Best practices pp. 32-33, "...should have enough information for a user..."trueWith entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3numHeaderLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numHeaderLines' element is presentCheck for presence of the 'numHeaderLines' element.Document contains 'numHeaderLines' element.'numHeaderLines' element: 1
4numFooterLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numFooterLines' element is presentCheck for presence of the 'numFooterLines' element.Document contains 'numFooterLines' element.No 'numFooterLines' element foundIf data file contains footer lines, 'numFooterLines' must be specified.Add 'numFooterLines' element if needed.
5fieldDelimiterValidvalid
Type:metadata
System:knb
On failure:error
Field delimiter is a single characterField delimiters should be one character onlyA single character is expected,A valid fieldDelimiter value was foundhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6recordDelimiterPresentvalid
Type:metadata
System:knb
On failure:warn
Record delimiter is presentCheck 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\r\nA valid recordDelimiter value was foundhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7numberOfRecordsPresencevalid
Type:metadata
System:knb
On failure:warn
Is the numberOfRecords element present?Warn the user if the numberOfRecords check is not presentA number of records element is expected for this entitynumberOfRecords element foundThis is a valuable check that we have the correct table.
8entitySizePresencevalid
Type:metadata
System:knb
On failure:warn
Check for presence of an entity size elementLook 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 101089 and size unit specified as 'byte'.Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).Include an entity size in bytes Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
9integrityChecksumPresencevalid
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-1Check 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.truePASTA 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.
10dateTimeFormatStringvalid
Type:metadata
System:knb
On failure:warn
dateTime/formatString specified in metadata is from a preferred set of valuesCertain features of dateTime data formats are preferred, eg, ISO 8601, 4-digit years. This check looks at metadata to see if the dateTime format is in that preferred list.A formatString value that is a member of the preferred set is expected.YYYY-MM-DDThh:mm:ssZA preferred format string was found.Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
11attributeNamesUniquevalid
Type:metadata
System:knb
On failure:warn
Attribute names are uniqueChecks if attributeName values are unique in the table. Not required by EML.Unique attribute names.trueA good table does not have duplicate column names.EML Best Practices
12displayDownloadDatainfo
Type:data
System:knb
On failure:info
Display downloaded dataDisplay the first kilobyte of data that is downloadedUp to one kilobyte of data should be displayed
13urlReturnsDatavalid
Type:congruency
System:knb
On failure:error
URL returns dataChecks 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 metadatatruehttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
14onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: https://ezeml.edirepository.org/user-data/iep-6f022aeb59daaf04006d61b9f2d3a887/uploads/Suisun%20Marsh%20Salinity%20Control%20Gates/SMSCG_clam_EDI_2018_2021_corr.csv
15integrityChecksumvalid
Type:congruency
System:lter
On failure:error
Compare the metadata checksum for an entity to the checksum of the downloaded entityTwo possible responses: valid if checksums match; error if checksums do not match.c0e3356ce1540bbf5cf1bd4bade663e0c0e3356ce1540bbf5cf1bd4bade663e0Matching 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.
16entitySizeCongruencevalid
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.101089101089Examining the entity size is a method for checking that this is the correct entity.Check the entity size.
17databaseTableCreatedvalid
Type:metadata
System:knb
On failure:error
Database table createdStatus of creating a database tableA database table is expected to be generated from the EML attributes.A database table was generated from the attributes descriptionCREATE TABLE SMSCG_clam_EDI_2018_2021("Year" TEXT,"Month" TEXT,"Station" TEXT,"Station_alias" TEXT,"Date" TIMESTAMP,"North_decimal_degrees" FLOAT,"West_decimal_degrees" FLOAT,"Corbicula_AFDM_g_per_m2" FLOAT,"Corbicula_density_per_m2" FLOAT,"Corbicula_filtration_rate_m3_per_m2_per_day" FLOAT,"Corbicula_grazing_rate_m3_per_m2_per_day" FLOAT,"Potamocorbula_AFDM_g_per_m2" FLOAT,"Potamocorbula_density_per_m2" FLOAT,"Potamocorbula_filtration_rate_m3_per_m2_per_day" FLOAT,"Potamocorbula_grazing_rate_m3_per_m2_per_day" FLOAT,"Total_AFDM_g_per_m2" FLOAT,"Total_density_per_m2" FLOAT,"Total_filtration_rate_m3_per_m2_per_day" FLOAT,"Total_grazing_rate_m3_per_m2_per_day" FLOAT,"Corbicula_grazing_turnover_per_day" FLOAT,"Potamocorbula_grazing_turnover_per_day" FLOAT,"Total_grazing_turnover_per_day" FLOAT,"Depth_ft" FLOAT,"Depth_m" FLOAT,"Percent_Organic_Matter" FLOAT,"Percent_Clay" FLOAT,"Percent_Silt" FLOAT,"Percent_Mica" TEXT,"Percent_Fine_Sand" FLOAT,"Percent_Coarse_Sand" FLOAT,"Percent_Gravel" FLOAT,"Percent_Fines" FLOAT,"Water_temperature_C" FLOAT,"Specific_conductivity_uS_per_cm" FLOAT,"pH" FLOAT,"Chlorophyll_a_ug_per_L" FLOAT,"Turbidity_NTU" FLOAT,"Dissolved_oxygen_mg_per_L" FLOAT,"Sediment" TEXT,"Habitat" TEXT,"Habitat_type" TEXT,"Done_all_years" TEXT);
18examineRecordDelimitervalid
Type:congruency
System:knb
On failure:warn
Data are examined and possible record delimiters are displayedIf no record delimiter was specified, we assume that \r\n is the delimiter. Search the first row for other record delimiters and see if other delimiters are found.No other potential record delimiters expected in the first row.No other potential record delimiters were detected. A valid record delimiter was previously detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
19displayFirstInsertRowinfo
Type:data
System:knb
On failure:info
Display first insert rowDisplay the first row of data values to be inserted into the database tableThe first row of data values should be displayed
20onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: file:///home/pasta/local/data/edi.979.1/c169596f76bde5357fb3ad94734383b0
21tooFewFieldsvalid
Type:congruency
System:knb
On failure:error
Data does not have fewer fields than metadata attributesCompare number of fields specified in metadata to number of fields found in a data recordNo errors detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#dataFormat
22tooManyFieldsvalid
Type:congruency
System:knb
On failure:error
Data does not have more fields than metadata attributesCompare number of fields specified in metadata to number of fields found in a data recordNo errors detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#dataFormat
23dataLoadStatusvalid
Type:congruency
System:knb
On failure:warn
Data can be loaded into the databaseStatus of loading the data table into a databaseNo errors expected during data loading or data loading was not attempted for this data entityThe data table loaded successfully into a database
24numberOfRecordsvalid
Type:congruency
System:knb
On failure:warn
Number of records in metadata matches number of rows loadedCompare number of records specified in metadata to number of records found in data258258The expected number of records (258) was found in the data table.
25headerRowAttributeNamesinfo
Type:congruency
System:lter
On failure:info
Header row is displayed alongside attribute namesCompare the content of the data header row to the content of EML attribute names.No expectation, information only Customer should evaluate the findings
26dateFormatMatchesvalid
Type:congruency
System:lter
On failure:warn
Date format in metadata matches datadateTime/formatString in attribute metadata is from the preferred list, and the data matches. A non-match generates only a warn.Format string is preferred, and all data values match the format stringData values matched the specified formatString.Dates should be consistently formatted and match the formatString in metadata.
Entity Report
Entity Name: EDSM_2018-2021_SummerFall_DSM
Entity Identifier:
# Identifier Status Quality Check Name Description Expected Found Explanation Suggestion Reference
1entityNameLengthvalid
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 charactersentityName value is 100 characters or less29
2entityDescriptionPresentvalid
Type:metadata
System:lter
On failure:warn
An entity description is presentCheck for presence of an entity description.EML Best practices pp. 32-33, "...should have enough information for a user..."trueWith entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3numHeaderLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numHeaderLines' element is presentCheck for presence of the 'numHeaderLines' element.Document contains 'numHeaderLines' element.'numHeaderLines' element: 1
4numFooterLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numFooterLines' element is presentCheck for presence of the 'numFooterLines' element.Document contains 'numFooterLines' element.No 'numFooterLines' element foundIf data file contains footer lines, 'numFooterLines' must be specified.Add 'numFooterLines' element if needed.
5fieldDelimiterValidvalid
Type:metadata
System:knb
On failure:error
Field delimiter is a single characterField delimiters should be one character onlyA single character is expected,A valid fieldDelimiter value was foundhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6recordDelimiterPresentvalid
Type:metadata
System:knb
On failure:warn
Record delimiter is presentCheck 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\nA valid recordDelimiter value was foundhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7numberOfRecordsPresencevalid
Type:metadata
System:knb
On failure:warn
Is the numberOfRecords element present?Warn the user if the numberOfRecords check is not presentA number of records element is expected for this entitynumberOfRecords element foundThis is a valuable check that we have the correct table.
8entitySizePresencevalid
Type:metadata
System:knb
On failure:warn
Check for presence of an entity size elementLook 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 15344 and size unit specified as 'byte'.Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).Include an entity size in bytes Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
9integrityChecksumPresencevalid
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-1Check 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.truePASTA 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.
10attributeNamesUniquevalid
Type:metadata
System:knb
On failure:warn
Attribute names are uniqueChecks if attributeName values are unique in the table. Not required by EML.Unique attribute names.trueA good table does not have duplicate column names.EML Best Practices
11displayDownloadDatainfo
Type:data
System:knb
On failure:info
Display downloaded dataDisplay the first kilobyte of data that is downloadedUp to one kilobyte of data should be displayed
12urlReturnsDatavalid
Type:congruency
System:knb
On failure:error
URL returns dataChecks 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 metadatatruehttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
13onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: https://ezeml.edirepository.org/user-data/iep-6f022aeb59daaf04006d61b9f2d3a887/uploads/Suisun%20Marsh%20Salinity%20Control%20Gates/EDSM_2018-2021_SummerFall_DSM.csv
14integrityChecksumvalid
Type:congruency
System:lter
On failure:error
Compare the metadata checksum for an entity to the checksum of the downloaded entityTwo possible responses: valid if checksums match; error if checksums do not match.5d0a1b27895872178bcec630ca7e39985d0a1b27895872178bcec630ca7e3998Matching 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.
15entitySizeCongruencevalid
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.1534415344Examining the entity size is a method for checking that this is the correct entity.Check the entity size.
16databaseTableCreatedvalid
Type:metadata
System:knb
On failure:error
Database table createdStatus of creating a database tableA database table is expected to be generated from the EML attributes.A database table was generated from the attributes descriptionCREATE TABLE EDSM_2018_2021_SummerFall_DSM("Stratum" TEXT,"Week" FLOAT,"Month" TEXT,"Year" TEXT,"Tows" FLOAT,"Stations" FLOAT,"DSM" FLOAT,"DSMcpue" FLOAT);
17examineRecordDelimitervalid
Type:congruency
System:knb
On failure:warn
Data are examined and possible record delimiters are displayedIf no record delimiter was specified, we assume that \r\n is the delimiter. Search the first row for other record delimiters and see if other delimiters are found.No other potential record delimiters expected in the first row.No other potential record delimiters were detected. A valid record delimiter was previously detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
18displayFirstInsertRowinfo
Type:data
System:knb
On failure:info
Display first insert rowDisplay the first row of data values to be inserted into the database tableThe first row of data values should be displayedCache Slough LI, 27, 7, 2018, 25, 5, 0, 0
19onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: file:///home/pasta/local/data/edi.979.1/2908b7b77d7ddc8727cdf3905d636d00
20tooFewFieldsvalid
Type:congruency
System:knb
On failure:error
Data does not have fewer fields than metadata attributesCompare number of fields specified in metadata to number of fields found in a data recordNo errors detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#dataFormat
21tooManyFieldsvalid
Type:congruency
System:knb
On failure:error
Data does not have more fields than metadata attributesCompare number of fields specified in metadata to number of fields found in a data recordNo errors detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#dataFormat
22dataLoadStatusvalid
Type:congruency
System:knb
On failure:warn
Data can be loaded into the databaseStatus of loading the data table into a databaseNo errors expected during data loading or data loading was not attempted for this data entityThe data table loaded successfully into a database
23numberOfRecordsvalid
Type:congruency
System:knb
On failure:warn
Number of records in metadata matches number of rows loadedCompare number of records specified in metadata to number of records found in data406406The expected number of records (406) was found in the data table.
24headerRowAttributeNamesinfo
Type:congruency
System:lter
On failure:info
Header row is displayed alongside attribute namesCompare the content of the data header row to the content of EML attribute names.No expectation, information only Customer should evaluate the findings
25dateFormatMatchesvalid
Type:congruency
System:lter
On failure:warn
Date format in metadata matches datadateTime/formatString in attribute metadata is from the preferred list, and the data matches. A non-match generates only a warn.Format string is preferred, and all data values match the format stringData values matched the specified formatString.Dates should be consistently formatted and match the formatString in metadata.
Entity Report
Entity Name: ChangeLog
Entity Identifier:
# Identifier Status Quality Check Name Description Expected Found Explanation Suggestion Reference
1entityNameLengthvalid
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 charactersentityName value is 100 characters or less9
2entityDescriptionPresentvalid
Type:metadata
System:lter
On failure:warn
An entity description is presentCheck for presence of an entity description.EML Best practices pp. 32-33, "...should have enough information for a user..."trueWith entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3numHeaderLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numHeaderLines' element is presentCheck for presence of the 'numHeaderLines' element.Document contains 'numHeaderLines' element.No 'numHeaderLines' element foundIf data file contains header lines, 'numHeaderLines' must be specified.Add 'numHeaderLines' element if needed.
4numFooterLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numFooterLines' element is presentCheck for presence of the 'numFooterLines' element.Document contains 'numFooterLines' element.No 'numFooterLines' element foundIf data file contains footer lines, 'numFooterLines' must be specified.Add 'numFooterLines' element if needed.
5fieldDelimiterValidinfo
Type:metadata
System:knb
On failure:error
Field delimiter is a single characterField delimiters should be one character onlyA single character is expectednullA fieldDelimiter value is not checked for binary entities or entities with an externally defined formathttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6recordDelimiterPresentinfo
Type:metadata
System:knb
On failure:warn
Record delimiter is presentCheck 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#x0AnullA recordDelimiter value is not checked for binary entities or entities with an externally defined formathttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7entitySizePresencevalid
Type:metadata
System:knb
On failure:warn
Check for presence of an entity size elementLook 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 21927 and size unit specified as 'byte'.Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).Include an entity size in bytes Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8integrityChecksumPresencevalid
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-1Check 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.truePASTA 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.
9displayDownloadDatainfo
Type:data
System:knb
On failure:info
Display downloaded dataDisplay the first kilobyte of data that is downloadedUp to one kilobyte of data should be displayedCannot display NON-PLAIN TEXT DATA
10urlReturnsDatavalid
Type:congruency
System:knb
On failure:error
URL returns dataChecks 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 metadatatruehttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
11onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: https://ezeml.edirepository.org/user-data/iep-6f022aeb59daaf04006d61b9f2d3a887/uploads/Suisun%20Marsh%20Salinity%20Control%20Gates/ChangeLog.docx
12integrityChecksumvalid
Type:congruency
System:lter
On failure:error
Compare the metadata checksum for an entity to the checksum of the downloaded entityTwo possible responses: valid if checksums match; error if checksums do not match.e452abcd024f1bbd4a3044be816705cce452abcd024f1bbd4a3044be816705ccMatching 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.
13entitySizeCongruencevalid
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.2192721927Examining the entity size is a method for checking that this is the correct entity.Check the entity size.
Entity Report
Entity Name: SMSCG Related publications
Entity Identifier:
# Identifier Status Quality Check Name Description Expected Found Explanation Suggestion Reference
1entityNameLengthvalid
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 charactersentityName value is 100 characters or less26
2entityDescriptionPresentvalid
Type:metadata
System:lter
On failure:warn
An entity description is presentCheck for presence of an entity description.EML Best practices pp. 32-33, "...should have enough information for a user..."trueWith entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3numHeaderLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numHeaderLines' element is presentCheck for presence of the 'numHeaderLines' element.Document contains 'numHeaderLines' element.No 'numHeaderLines' element foundIf data file contains header lines, 'numHeaderLines' must be specified.Add 'numHeaderLines' element if needed.
4numFooterLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numFooterLines' element is presentCheck for presence of the 'numFooterLines' element.Document contains 'numFooterLines' element.No 'numFooterLines' element foundIf data file contains footer lines, 'numFooterLines' must be specified.Add 'numFooterLines' element if needed.
5fieldDelimiterValidinfo
Type:metadata
System:knb
On failure:error
Field delimiter is a single characterField delimiters should be one character onlyA single character is expectednullA fieldDelimiter value is not checked for binary entities or entities with an externally defined formathttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6recordDelimiterPresentinfo
Type:metadata
System:knb
On failure:warn
Record delimiter is presentCheck 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#x0AnullA recordDelimiter value is not checked for binary entities or entities with an externally defined formathttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7entitySizePresencevalid
Type:metadata
System:knb
On failure:warn
Check for presence of an entity size elementLook 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 102857 and size unit specified as 'byte'.Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).Include an entity size in bytes Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8integrityChecksumPresencevalid
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-1Check 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.truePASTA 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.
9displayDownloadDatainfo
Type:data
System:knb
On failure:info
Display downloaded dataDisplay the first kilobyte of data that is downloadedUp to one kilobyte of data should be displayedCannot display NON-PLAIN TEXT DATA
10urlReturnsDatavalid
Type:congruency
System:knb
On failure:error
URL returns dataChecks 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 metadatatruehttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
11onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: https://ezeml.edirepository.org/user-data/iep-6f022aeb59daaf04006d61b9f2d3a887/uploads/Suisun%20Marsh%20Salinity%20Control%20Gates/SMSCG%20Related%20publications.pdf
12integrityChecksumvalid
Type:congruency
System:lter
On failure:error
Compare the metadata checksum for an entity to the checksum of the downloaded entityTwo possible responses: valid if checksums match; error if checksums do not match.f112826d4c0923879640811f02097039f112826d4c0923879640811f02097039Matching 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.
13entitySizeCongruencevalid
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.102857102857Examining the entity size is a method for checking that this is the correct entity.Check the entity size.
Entity Report
Entity Name: SMSCG_MonitoringPlan_2021
Entity Identifier:
# Identifier Status Quality Check Name Description Expected Found Explanation Suggestion Reference
1entityNameLengthvalid
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 charactersentityName value is 100 characters or less25
2entityDescriptionPresentvalid
Type:metadata
System:lter
On failure:warn
An entity description is presentCheck for presence of an entity description.EML Best practices pp. 32-33, "...should have enough information for a user..."trueWith entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3numHeaderLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numHeaderLines' element is presentCheck for presence of the 'numHeaderLines' element.Document contains 'numHeaderLines' element.No 'numHeaderLines' element foundIf data file contains header lines, 'numHeaderLines' must be specified.Add 'numHeaderLines' element if needed.
4numFooterLinesPresentinfo
Type:metadata
System:knb
On failure:info
'numFooterLines' element is presentCheck for presence of the 'numFooterLines' element.Document contains 'numFooterLines' element.No 'numFooterLines' element foundIf data file contains footer lines, 'numFooterLines' must be specified.Add 'numFooterLines' element if needed.
5fieldDelimiterValidinfo
Type:metadata
System:knb
On failure:error
Field delimiter is a single characterField delimiters should be one character onlyA single character is expectednullA fieldDelimiter value is not checked for binary entities or entities with an externally defined formathttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6recordDelimiterPresentinfo
Type:metadata
System:knb
On failure:warn
Record delimiter is presentCheck 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#x0AnullA recordDelimiter value is not checked for binary entities or entities with an externally defined formathttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7entitySizePresencevalid
Type:metadata
System:knb
On failure:warn
Check for presence of an entity size elementLook 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 3425043 and size unit specified as 'byte'.Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).Include an entity size in bytes Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8integrityChecksumPresencevalid
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-1Check 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.truePASTA 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.
9displayDownloadDatainfo
Type:data
System:knb
On failure:info
Display downloaded dataDisplay the first kilobyte of data that is downloadedUp to one kilobyte of data should be displayedCannot display NON-PLAIN TEXT DATA
10urlReturnsDatavalid
Type:congruency
System:knb
On failure:error
URL returns dataChecks 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 metadatatruehttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
11onlineURLsvalid
Type:congruency
System:knb
On failure:error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: https://ezeml.edirepository.org/user-data/iep-6f022aeb59daaf04006d61b9f2d3a887/uploads/Suisun%20Marsh%20Salinity%20Control%20Gates/SMSCG_MonitoringPlan_2021.pdf
12integrityChecksumvalid
Type:congruency
System:lter
On failure:error
Compare the metadata checksum for an entity to the checksum of the downloaded entityTwo possible responses: valid if checksums match; error if checksums do not match.8ea269deb436b27b0b474433cb9391168ea269deb436b27b0b474433cb939116Matching 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.
13entitySizeCongruencevalid
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.34250433425043Examining the entity size is a method for checking that this is the correct entity.Check the entity size.