Check against LTER requirements for scope.identifier.revision
'scope.n.m', where 'n' and 'm' are integers and 'scope' is one of an allowed set of values
edi.829.3
2
emlVersion
valid
Type:
metadata
System:
lter
On failure:
error
EML version 2.1.0 or beyond
Check the EML document declaration for version 2.1.0 or higher
eml://ecoinformatics.org/eml-2.1.0 or higher
https://eml.ecoinformatics.org/eml-2.2.0
Validity of this quality report is dependent on this check being valid.
3
schemaValid
valid
Type:
metadata
System:
knb
On failure:
error
Document is schema-valid EML
Check document schema validity
schema-valid
Document validated for namespace: 'https://eml.ecoinformatics.org/eml-2.2.0'
Validity of this quality report is dependent on this check being valid.
4
parserValid
valid
Type:
metadata
System:
knb
On failure:
error
Document is EML parser-valid
Check document using the EML IDs and references parser
Validates with the EML IDs and references parser
EML IDs and references parser succeeded
Validity of this quality report is dependent on this check being valid.
5
schemaValidDereferenced
valid
Type:
metadata
System:
lter
On failure:
error
Dereferenced document is schema-valid EML
References are dereferenced, and the resulting file validated
schema-valid
Dereferenced document validated for namespace: 'https://eml.ecoinformatics.org/eml-2.2.0'
Validity of this quality report is dependent on this check being valid.
6
keywordPresent
valid
Type:
metadata
System:
lter
On failure:
warn
keyword element is present
Checks to see if at least one keyword is present
Presence of one or more keyword elements
10 'keyword' element(s) found
7
methodsElementPresent
valid
Type:
metadata
System:
lter
On failure:
warn
A 'methods' element is present
All datasets should contain a 'methods' element, at a minimum a link to a separate methods doc.
presence of 'methods' at one or more xpaths.
1 'methods' element(s) found
EML Best Practices, p. 28
8
coveragePresent
valid
Type:
metadata
System:
lter
On failure:
warn
coverage element is present
At least one coverage element should be present in a dataset.
At least one of geographicCoverage, taxonomicCoverage, or temporalCoverage is present in the EML.
1 'coverage' element(s) found
9
geographicCoveragePresent
info
Type:
metadata
System:
lter
On failure:
info
geographicCoverage is present
Check that geographicCoverage exists in EML at the dataset level, or at least one entity's level, or at least one attribute's level.
geographicCoverage at least at the dataset level.
34 'geographicCoverage' element(s) found
Many but not all datasets are appropriate to have spatial coverage.
If sampling EML is used within methods, does that obviate geographicCoverage? Or should those sites be repeated or referenced?
EML Best Practices v.2, p. 22-23. "One geographicCoverage element should be included, whose boundingCoordinates describe the extent of the data....Additional geographicCoverage elements may be entered at the dataset level if there are significant distances between study sites and it would be confusing if they were grouped into one bounding box." 6 decimal places.
10
taxonomicCoveragePresent
info
Type:
metadata
System:
lter
On failure:
info
taxonomicCoverage is present
Check that taxonomicCoverage exists in EML at the dataset level, or at least one entity's level, or at least one attribute's level.
taxonomicCoverage at least at the dataset level.
2 'taxonomicCoverage' element(s) found
Only when taxa are pertinent to the dataset will they have taxonomicCoverage.
Could search title, abstract, keywords for any taxonomic name (huge). Could search keywordType="taxonomic".
EML Best Practices v.2, p. 25
11
temporalCoveragePresent
info
Type:
metadata
System:
lter
On failure:
info
temporalCoverage is present
Check that temporalCoverage exists in EML at the dataset level, or at least one entity's level, or at least one attribute's level.
temporalCoverage at least at the dataset level.
1 'temporalCoverage' element(s) found
LTER wants to search datasets by time; the best place to search is the dataset level temporal coverage.
Most datasets have a temporal range.
EML Best Practices v.2, p. 24
12
pastaDoiAbsent
valid
Type:
metadata
System:
lter
On failure:
error
An alternateIdentifier with a DOI system attribute that looks like it is generated by PASTA should not be present
Reject the data package if it contains an alternateIdentifier DOI that looks like PASTA generated it.
No PASTA DOIs are expected to be found in the uploaded data package
No PASTA DOI alternateIdentifier elements found
PASTA DOI values might appear in an uploaded data package (by various mechanisms). PASTA will assign a DOI after the upload has completed successfully, so an initial one should not be there.
13
titleLength
valid
Type:
metadata
System:
lter
On failure:
warn
Dataset title length is at 5 least words.
If the title is shorter than 5 words, it might be insufficient. Title word count between 7 and 20 including prepositions and numbers.
Between 7 and 20 words
11 words found.
EML Best Practices, v.2, p. 13
14
fundingPresence
warn
Type:
metadata
System:
lter
On failure:
warn
check to see if funding element is present
Checks to see if the funding element is included.
the funding element is expected to be included
funding not found
Searches will want to display datasets by funder or grant id.
Include the funding source, please.
15
datasetAbstractLength
valid
Type:
metadata
System:
lter
On failure:
warn
Dataset abstract element is a minimum of 20 words
Check the length of a dataset abstract and warn if less than 20 words.
An abstract is 20 words or more.
260 words found.
EML Best Practices
16
duplicateEntityName
valid
Type:
metadata
System:
lter
On failure:
error
There are no duplicate entity names
Checks that content is not duplicated by other entityName elements in the document
entityName is not a duplicate within the document
No duplicates found
Data Manager requires a non-empty, non-duplicate entityName value for every entity
Declare a non-empty entityName and ensure that there are no duplicate entityName values in the document
Warn the user if the numberOfRecords check is not present
A number of records element is expected for this entity
numberOfRecords element found
This is a valuable check that we have the correct table.
8
entitySizePresence
valid
Type:
metadata
System:
knb
On failure:
warn
Check for presence of an entity size element
Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.
Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.
Found entity size element with value of 642625 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.
9
integrityChecksumPresence
valid
Type:
metadata
System:
lter
On failure:
warn
A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1
Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.
At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.
true
PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented
in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able
to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.
Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
10
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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-DD hh:mm:ss
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
11
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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.
YYYYMMDDThhmmssZ
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
12
attributeNamesUnique
valid
Type:
metadata
System:
knb
On failure:
warn
Attribute names are unique
Checks if attributeName values are unique in the table. Not required by EML.
Unique attribute names.
true
A good table does not have duplicate column names.
EML Best Practices
13
integrityChecksum
valid
Type:
congruency
System:
lter
On failure:
error
Compare the metadata checksum for an entity to the checksum of the downloaded entity
Two possible responses: valid if checksums match; error if checksums do not match.
6ba174718438be31e017d305252c8c75
6ba174718438be31e017d305252c8c75
Matching checksums will ensure data integrity during upload to the repository.
If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
14
entitySizeCongruence
valid
Type:
congruency
System:
knb
On failure:
error
Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.
Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.
642625
642625
Examining the entity size is a method for checking that this is the correct entity.
Check the entity size.
15
databaseTableCreated
valid
Type:
metadata
System:
knb
On failure:
error
Database table created
Status of creating a database table
A database table is expected to be generated from the EML attributes.
A database table was generated from the attributes description
Data are examined and possible record delimiters are displayed
If 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 detected
Warn the user if the numberOfRecords check is not present
A number of records element is expected for this entity
numberOfRecords element found
This is a valuable check that we have the correct table.
8
entitySizePresence
valid
Type:
metadata
System:
knb
On failure:
warn
Check for presence of an entity size element
Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.
Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.
Found entity size element with value of 785497 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.
9
integrityChecksumPresence
valid
Type:
metadata
System:
lter
On failure:
warn
A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1
Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.
At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.
true
PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented
in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able
to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.
Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
10
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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-DD hh:mm:ss
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
11
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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-DD hh:mm:ss
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
12
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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.
YYYYMMDDThhmmssZ
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
13
attributeNamesUnique
valid
Type:
metadata
System:
knb
On failure:
warn
Attribute names are unique
Checks if attributeName values are unique in the table. Not required by EML.
Unique attribute names.
true
A good table does not have duplicate column names.
EML Best Practices
14
integrityChecksum
valid
Type:
congruency
System:
lter
On failure:
error
Compare the metadata checksum for an entity to the checksum of the downloaded entity
Two possible responses: valid if checksums match; error if checksums do not match.
a4bfb49024698cc6fd8a5960b5b9b188
a4bfb49024698cc6fd8a5960b5b9b188
Matching checksums will ensure data integrity during upload to the repository.
If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
15
entitySizeCongruence
valid
Type:
congruency
System:
knb
On failure:
error
Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.
Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.
785497
785497
Examining the entity size is a method for checking that this is the correct entity.
Check the entity size.
16
databaseTableCreated
valid
Type:
metadata
System:
knb
On failure:
error
Database table created
Status of creating a database table
A database table is expected to be generated from the EML attributes.
A database table was generated from the attributes description
Data are examined and possible record delimiters are displayed
If 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 detected
Warn the user if the numberOfRecords check is not present
A number of records element is expected for this entity
numberOfRecords element found
This is a valuable check that we have the correct table.
8
entitySizePresence
valid
Type:
metadata
System:
knb
On failure:
warn
Check for presence of an entity size element
Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.
Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.
Found entity size element with value of 6065636 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.
9
integrityChecksumPresence
valid
Type:
metadata
System:
lter
On failure:
warn
A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1
Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.
At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.
true
PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented
in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able
to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.
Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
10
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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-DD hh:mm:ss
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
11
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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-DD
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
12
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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.
YYYYMMDDThhmmssZ
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
13
attributeNamesUnique
valid
Type:
metadata
System:
knb
On failure:
warn
Attribute names are unique
Checks if attributeName values are unique in the table. Not required by EML.
Unique attribute names.
true
A good table does not have duplicate column names.
EML Best Practices
14
integrityChecksum
valid
Type:
congruency
System:
lter
On failure:
error
Compare the metadata checksum for an entity to the checksum of the downloaded entity
Two possible responses: valid if checksums match; error if checksums do not match.
7f95ee1d268c8e03bb8606f238655524
7f95ee1d268c8e03bb8606f238655524
Matching checksums will ensure data integrity during upload to the repository.
If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
15
entitySizeCongruence
valid
Type:
congruency
System:
knb
On failure:
error
Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.
Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.
6065636
6065636
Examining the entity size is a method for checking that this is the correct entity.
Check the entity size.
16
databaseTableCreated
valid
Type:
metadata
System:
knb
On failure:
error
Database table created
Status of creating a database table
A database table is expected to be generated from the EML attributes.
A database table was generated from the attributes description
Display the first kilobyte of data that is downloaded
Up to one kilobyte of data should be displayed
Found for displayDownloadData check
"uid","domainID","siteID","namedLocation","collectDate","sampleID","sampleCode","sampleCondition","slideID","slideCode","laboratoryName","identifiedBy","qcTaxonomyStatus","identifiedDate","algalType","perBottleSampleVolume","subsamplePercent","algalParameter","algalParameterValue","algalParameterUnit","acceptedTaxonID","targetTaxaPresent","scientificName","morphospeciesID","division","class","order","family","genus","specificEpithet","infraspecificEpithet","scientificNameAuthorship","identificationQualifier","taxonRank","identificationReferences","remarks","testMethod","method","algalAnalysisMethod","dataQF","publicationDate","release"
"08de287d-2c22-4f52-8db4-e7de4beabe8b","D01","HOPB","HOPB.AOS.reach",2020-07-19 13:53:00,"HOPB.20200719.EPIPSAMMON.2.TAXONOMY","A00000156478","Condition OK",,,"Kociolek Laboratory at the University of Colorado Boulder","JPKociolek","original",2021-01-30,,60,16.7,"natural units",8,"count","NEONDREX48008","Y","Nitzschia dissipata (Kützing) Grunow",,"Chrysophyta","Bacillariophyc
18
urlReturnsData
valid
Type:
congruency
System:
knb
On failure:
error
URL returns data
Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.
Data are examined and possible record delimiters are displayed
If 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 detected
Warn the user if the numberOfRecords check is not present
A number of records element is expected for this entity
numberOfRecords element found
This is a valuable check that we have the correct table.
8
entitySizePresence
valid
Type:
metadata
System:
knb
On failure:
warn
Check for presence of an entity size element
Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.
Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.
Found entity size element with value of 315228 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.
9
integrityChecksumPresence
valid
Type:
metadata
System:
lter
On failure:
warn
A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1
Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.
At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.
true
PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented
in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able
to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.
Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
10
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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-DD hh:mm:ss
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
11
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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.
YYYYMMDDThhmmssZ
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
12
attributeNamesUnique
valid
Type:
metadata
System:
knb
On failure:
warn
Attribute names are unique
Checks if attributeName values are unique in the table. Not required by EML.
Unique attribute names.
true
A good table does not have duplicate column names.
EML Best Practices
13
integrityChecksum
valid
Type:
congruency
System:
lter
On failure:
error
Compare the metadata checksum for an entity to the checksum of the downloaded entity
Two possible responses: valid if checksums match; error if checksums do not match.
56c143a998f47de37440c9ff559c372b
56c143a998f47de37440c9ff559c372b
Matching checksums will ensure data integrity during upload to the repository.
If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
14
entitySizeCongruence
valid
Type:
congruency
System:
knb
On failure:
error
Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.
Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.
315228
315228
Examining the entity size is a method for checking that this is the correct entity.
Check the entity size.
15
databaseTableCreated
valid
Type:
metadata
System:
knb
On failure:
error
Database table created
Status of creating a database table
A database table is expected to be generated from the EML attributes.
A database table was generated from the attributes description
Display the first kilobyte of data that is downloaded
Up to one kilobyte of data should be displayed
Found for displayDownloadData check
"uid","domainID","siteID","namedLocation","decimalLatitude","decimalLongitude","coordinateUncertainty","geodeticDatum","elevation","elevationUncertainty","aquaticSiteType","collectDate","eventID","boutNumber","sampleID","sampleCode","geneticSampleID","geneticSampleCode","samplingProtocolVersion","samplingImpractical","biophysicalCriteria","habitatType","samplerType","sampleNumber","substratumSizeClass","benthicArea","ponarDepth","snagLength","snagDiameter","dnaSnagLength","dnaSnagDiameter","remarks","recordedBy","collectedBy","dataQF","publicationDate","release"
"1eac707b-83eb-4279-98f5-468c3f48a61c","D01","HOPB","HOPB.AOS.reach",42.471941,-72.329526,1000,"WGS84",203.4,1000,"stream",2021-04-12 15:12:00,"HOPB.20210412",1,"HOPB.20210412.SURBER.3","A00000151405","HOPB.20210412.SURBER.3.ARC","A00000151359","NEON.DOC.003046vE",,"OK - no known exceptions","riffle","surber",3,"cobble",0.093,,,,,,,"0000-0003-4958-6412","0000-0003-4958-6412",,"20211222T003543Z","PROVISIONAL"
"e3537be7-5035-444b-a215-382bfecfa378","D
17
urlReturnsData
valid
Type:
congruency
System:
knb
On failure:
error
URL returns data
Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.
Data are examined and possible record delimiters are displayed
If 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 detected
Warn the user if the numberOfRecords check is not present
A number of records element is expected for this entity
numberOfRecords element found
This is a valuable check that we have the correct table.
8
entitySizePresence
valid
Type:
metadata
System:
knb
On failure:
warn
Check for presence of an entity size element
Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.
Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.
Found entity size element with value of 9739079 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.
9
integrityChecksumPresence
valid
Type:
metadata
System:
lter
On failure:
warn
A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1
Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.
At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.
true
PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented
in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able
to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.
Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
10
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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-DD hh:mm:ss
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
11
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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-DD
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
12
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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.
YYYYMMDDThhmmssZ
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
13
attributeNamesUnique
valid
Type:
metadata
System:
knb
On failure:
warn
Attribute names are unique
Checks if attributeName values are unique in the table. Not required by EML.
Unique attribute names.
true
A good table does not have duplicate column names.
EML Best Practices
14
integrityChecksum
valid
Type:
congruency
System:
lter
On failure:
error
Compare the metadata checksum for an entity to the checksum of the downloaded entity
Two possible responses: valid if checksums match; error if checksums do not match.
58a71549b180d68eac06577e279c63e5
58a71549b180d68eac06577e279c63e5
Matching checksums will ensure data integrity during upload to the repository.
If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
15
entitySizeCongruence
valid
Type:
congruency
System:
knb
On failure:
error
Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.
Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.
9739079
9739079
Examining the entity size is a method for checking that this is the correct entity.
Check the entity size.
16
databaseTableCreated
valid
Type:
metadata
System:
knb
On failure:
error
Database table created
Status of creating a database table
A database table is expected to be generated from the EML attributes.
A database table was generated from the attributes description
Data are examined and possible record delimiters are displayed
If 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 detected
Warn the user if the numberOfRecords check is not present
A number of records element is expected for this entity
numberOfRecords element found
This is a valuable check that we have the correct table.
8
entitySizePresence
valid
Type:
metadata
System:
knb
On failure:
warn
Check for presence of an entity size element
Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.
Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.
Found entity size element with value of 24967 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.
9
integrityChecksumPresence
valid
Type:
metadata
System:
lter
On failure:
warn
A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1
Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.
At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.
true
PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented
in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able
to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.
Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
10
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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-DD hh:mm:ss
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
11
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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-DD hh:mm:ss
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
12
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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.
YYYYMMDDThhmmssZ
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
13
attributeNamesUnique
valid
Type:
metadata
System:
knb
On failure:
warn
Attribute names are unique
Checks if attributeName values are unique in the table. Not required by EML.
Unique attribute names.
true
A good table does not have duplicate column names.
EML Best Practices
14
integrityChecksum
valid
Type:
congruency
System:
lter
On failure:
error
Compare the metadata checksum for an entity to the checksum of the downloaded entity
Two possible responses: valid if checksums match; error if checksums do not match.
cf8ecbdc2810cbc0e8dd8c5f2ec13193
cf8ecbdc2810cbc0e8dd8c5f2ec13193
Matching checksums will ensure data integrity during upload to the repository.
If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
15
entitySizeCongruence
valid
Type:
congruency
System:
knb
On failure:
error
Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.
Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.
24967
24967
Examining the entity size is a method for checking that this is the correct entity.
Check the entity size.
16
databaseTableCreated
valid
Type:
metadata
System:
knb
On failure:
error
Database table created
Status of creating a database table
A database table is expected to be generated from the EML attributes.
A database table was generated from the attributes description
Display the first kilobyte of data that is downloaded
Up to one kilobyte of data should be displayed
Found for displayDownloadData check
"uid","domainID","siteID","namedLocation","decimalLatitude","decimalLongitude","coordinateUncertainty","additionalCoordUncertainty","geodeticDatum","elevation","elevationUncertainty","aquaticSiteType","startDate","collectDate","eventID","boutNumber","sampleID","sampleCode","samplingProtocolVersion","samplingImpractical","biophysicalCriteria","affectedByWind","samplerType","towsTrapsNumber","towsTrapsVolume","zooDepth1","zooDepth2","zooDepth3","remarks","recordedBy","collectedBy","dataQF","publicationDate","release"
"4602f4e7-6d91-4e6b-80f6-236b23707775","D03","BARC","BARC.AOS.buoy.c0",29.675982,-82.008414,10,10,"WGS84",27,10,"lake",2021-02-10 14:06:00,2021-02-10 14:06:00,"BARC.20210210",1,"BARC.20210210.TOWNET.2","A00000132212","NEON.DOC.001194vF",,"OK - no known exceptions","N","tow net",2,657,4.5,4.5,,,"0000-0003-1571-3196","0000-0001-6607-7236",,"20211221T211933Z","PROVISIONAL"
"b5458dbf-96a9-4d62-aa80-7f518de2cb81","D03","BARC","BARC.AOS.littoral2",29.674748,-82.008401,1.1,10,"WGS84",27.1,1,"lake",2021-
18
urlReturnsData
valid
Type:
congruency
System:
knb
On failure:
error
URL returns data
Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.
Data are examined and possible record delimiters are displayed
If 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 detected
Warn the user if the numberOfRecords check is not present
A number of records element is expected for this entity
numberOfRecords element found
This is a valuable check that we have the correct table.
8
entitySizePresence
valid
Type:
metadata
System:
knb
On failure:
warn
Check for presence of an entity size element
Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.
Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.
Found entity size element with value of 282883 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.
9
integrityChecksumPresence
valid
Type:
metadata
System:
lter
On failure:
warn
A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1
Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.
At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.
true
PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented
in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able
to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.
Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
10
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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-DD hh:mm:ss
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
11
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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-DD
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
12
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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.
YYYYMMDDThhmmssZ
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
13
attributeNamesUnique
valid
Type:
metadata
System:
knb
On failure:
warn
Attribute names are unique
Checks if attributeName values are unique in the table. Not required by EML.
Unique attribute names.
true
A good table does not have duplicate column names.
EML Best Practices
14
integrityChecksum
valid
Type:
congruency
System:
lter
On failure:
error
Compare the metadata checksum for an entity to the checksum of the downloaded entity
Two possible responses: valid if checksums match; error if checksums do not match.
16d4fbf69ad2860655546f81a848d6e7
16d4fbf69ad2860655546f81a848d6e7
Matching checksums will ensure data integrity during upload to the repository.
If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
15
entitySizeCongruence
valid
Type:
congruency
System:
knb
On failure:
error
Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.
Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.
282883
282883
Examining the entity size is a method for checking that this is the correct entity.
Check the entity size.
16
databaseTableCreated
valid
Type:
metadata
System:
knb
On failure:
error
Database table created
Status of creating a database table
A database table is expected to be generated from the EML attributes.
A database table was generated from the attributes description
Data are examined and possible record delimiters are displayed
If 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 detected
Warn the user if the numberOfRecords check is not present
A number of records element is expected for this entity
numberOfRecords element found
This is a valuable check that we have the correct table.
8
entitySizePresence
valid
Type:
metadata
System:
knb
On failure:
warn
Check for presence of an entity size element
Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.
Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.
Found entity size element with value of 24305091 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.
9
integrityChecksumPresence
valid
Type:
metadata
System:
lter
On failure:
warn
A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1
Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.
At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.
true
PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented
in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able
to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.
Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
10
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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:ssZ
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
11
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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:ssZ
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
12
dateTimeFormatString
valid
Type:
metadata
System:
knb
On failure:
warn
dateTime/formatString specified in metadata is from a preferred set of values
Certain 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.
YYYYMMDDThhmmssZ
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
13
attributeNamesUnique
valid
Type:
metadata
System:
knb
On failure:
warn
Attribute names are unique
Checks if attributeName values are unique in the table. Not required by EML.
Unique attribute names.
true
A good table does not have duplicate column names.
EML Best Practices
14
integrityChecksum
valid
Type:
congruency
System:
lter
On failure:
error
Compare the metadata checksum for an entity to the checksum of the downloaded entity
Two possible responses: valid if checksums match; error if checksums do not match.
ffec9fe9e9b9be6ba5b4402088a75e70
ffec9fe9e9b9be6ba5b4402088a75e70
Matching checksums will ensure data integrity during upload to the repository.
If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
15
entitySizeCongruence
valid
Type:
congruency
System:
knb
On failure:
error
Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.
Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.
24305091
24305091
Examining the entity size is a method for checking that this is the correct entity.
Check the entity size.
16
databaseTableCreated
valid
Type:
metadata
System:
knb
On failure:
error
Database table created
Status of creating a database table
A database table is expected to be generated from the EML attributes.
A database table was generated from the attributes description
Data are examined and possible record delimiters are displayed
If 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 detected
Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.
Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.
Found entity size element with value of 9754 and size unit specified as 'byte'.
Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).
Include an entity size in bytes
Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8
integrityChecksumPresence
valid
Type:
metadata
System:
lter
On failure:
warn
A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1
Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.
At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.
true
PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented
in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able
to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.
Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
9
integrityChecksum
valid
Type:
congruency
System:
lter
On failure:
error
Compare the metadata checksum for an entity to the checksum of the downloaded entity
Two possible responses: valid if checksums match; error if checksums do not match.
c6a7dd434a1d72b095fb9535bf1d2383
c6a7dd434a1d72b095fb9535bf1d2383
Matching checksums will ensure data integrity during upload to the repository.
If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
10
entitySizeCongruence
valid
Type:
congruency
System:
knb
On failure:
error
Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.
Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.
9754
9754
Examining the entity size is a method for checking that this is the correct entity.
Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.
Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.
Found entity size element with value of 7895 and size unit specified as 'byte'.
Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).
Include an entity size in bytes
Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8
integrityChecksumPresence
valid
Type:
metadata
System:
lter
On failure:
warn
A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1
Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.
At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.
true
PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented
in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able
to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.
Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
9
integrityChecksum
valid
Type:
congruency
System:
lter
On failure:
error
Compare the metadata checksum for an entity to the checksum of the downloaded entity
Two possible responses: valid if checksums match; error if checksums do not match.
2b3bd929a63c2774afb7465e84a4e8b4
2b3bd929a63c2774afb7465e84a4e8b4
Matching checksums will ensure data integrity during upload to the repository.
If the found integrity hash value does not match the expected integrity hash value, there may have been a loss of integrity in the data download. Check that the hash method and hash value documented in the metadata are the correct values.
10
entitySizeCongruence
valid
Type:
congruency
System:
knb
On failure:
error
Check that the entity size in the Level 0 metadata matches the one PASTA+ generates.
Compare raw file size of file to [entity]/physical/size element in metadata. Return error if not matching.
7895
7895
Examining the entity size is a method for checking that this is the correct entity.