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.1341.1
2
emlVersion
valid
Type:
metadata
System:
lter
On failure:
error
EML version 2.1.0 or beyond
Check the EML document declaration for version 2.1.0 or higher
eml://ecoinformatics.org/eml-2.1.0 or higher
https://eml.ecoinformatics.org/eml-2.2.0
Validity of this quality report is dependent on this check being valid.
3
schemaValid
valid
Type:
metadata
System:
knb
On failure:
error
Document is schema-valid EML
Check document schema validity
schema-valid
Document validated for namespace: 'https://eml.ecoinformatics.org/eml-2.2.0'
Validity of this quality report is dependent on this check being valid.
4
parserValid
valid
Type:
metadata
System:
knb
On failure:
error
Document is EML parser-valid
Check document using the EML IDs and references parser
Validates with the EML IDs and references parser
EML IDs and references parser succeeded
Validity of this quality report is dependent on this check being valid.
5
schemaValidDereferenced
valid
Type:
metadata
System:
lter
On failure:
error
Dereferenced document is schema-valid EML
References are dereferenced, and the resulting file validated
schema-valid
Dereferenced document validated for namespace: 'https://eml.ecoinformatics.org/eml-2.2.0'
Validity of this quality report is dependent on this check being valid.
6
keywordPresent
valid
Type:
metadata
System:
lter
On failure:
warn
keyword element is present
Checks to see if at least one keyword is present
Presence of one or more keyword elements
9 'keyword' element(s) found
7
methodsElementPresent
valid
Type:
metadata
System:
lter
On failure:
warn
A 'methods' element is present
All datasets should contain a 'methods' element, at a minimum a link to a separate methods doc.
presence of 'methods' at one or more xpaths.
1 'methods' element(s) found
EML Best Practices, p. 28
8
coveragePresent
valid
Type:
metadata
System:
lter
On failure:
warn
coverage element is present
At least one coverage element should be present in a dataset.
At least one of geographicCoverage, taxonomicCoverage, or temporalCoverage is present in the EML.
1 'coverage' element(s) found
9
geographicCoveragePresent
info
Type:
metadata
System:
lter
On failure:
info
geographicCoverage is present
Check that geographicCoverage exists in EML at the dataset level, or at least one entity's level, or at least one attribute's level.
geographicCoverage at least at the dataset level.
1 'geographicCoverage' element(s) found
Many but not all datasets are appropriate to have spatial coverage.
If sampling EML is used within methods, does that obviate geographicCoverage? Or should those sites be repeated or referenced?
EML Best Practices v.2, p. 22-23. "One geographicCoverage element should be included, whose boundingCoordinates describe the extent of the data....Additional geographicCoverage elements may be entered at the dataset level if there are significant distances between study sites and it would be confusing if they were grouped into one bounding box." 6 decimal places.
10
taxonomicCoveragePresent
info
Type:
metadata
System:
lter
On failure:
info
taxonomicCoverage is present
Check that taxonomicCoverage exists in EML at the dataset level, or at least one entity's level, or at least one attribute's level.
taxonomicCoverage at least at the dataset level.
0 'taxonomicCoverage' element(s) found
Only when taxa are pertinent to the dataset will they have taxonomicCoverage.
Could search title, abstract, keywords for any taxonomic name (huge). Could search keywordType="taxonomic".
EML Best Practices v.2, p. 25
11
temporalCoveragePresent
info
Type:
metadata
System:
lter
On failure:
info
temporalCoverage is present
Check that temporalCoverage exists in EML at the dataset level, or at least one entity's level, or at least one attribute's level.
temporalCoverage at least at the dataset level.
1 'temporalCoverage' element(s) found
LTER wants to search datasets by time; the best place to search is the dataset level temporal coverage.
Most datasets have a temporal range.
EML Best Practices v.2, p. 24
12
pastaDoiAbsent
valid
Type:
metadata
System:
lter
On failure:
error
An alternateIdentifier with a DOI system attribute that looks like it is generated by PASTA should not be present
Reject the data package if it contains an alternateIdentifier DOI that looks like PASTA generated it.
No PASTA DOIs are expected to be found in the uploaded data package
No PASTA DOI alternateIdentifier elements found
PASTA DOI values might appear in an uploaded data package (by various mechanisms). PASTA will assign a DOI after the upload has completed successfully, so an initial one should not be there.
13
titleLength
valid
Type:
metadata
System:
lter
On failure:
warn
Dataset title length is at 5 least words.
If the title is shorter than 5 words, it might be insufficient. Title word count between 7 and 20 including prepositions and numbers.
Between 7 and 20 words
14 words found.
EML Best Practices, v.2, p. 13
14
fundingPresence
valid
Type:
metadata
System:
lter
On failure:
warn
check to see if funding element is present
Checks to see if the funding element is included.
the funding element is expected to be included
National Science Foundation
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.
238 words found.
EML Best Practices
16
duplicateEntityName
valid
Type:
metadata
System:
lter
On failure:
error
There are no duplicate entity names
Checks that content is not duplicated by other entityName elements in the document
entityName is not a duplicate within the document
No duplicates found
Data Manager requires a non-empty, non-duplicate entityName value for every entity
Declare a non-empty entityName and ensure that there are no duplicate entityName values in the document
Entity Report
Entity Name:
phen_bm
Entity Identifier:
#
Identifier
Status
Quality Check
Name
Description
Expected
Found
Explanation
Suggestion
Reference
1
entityNameLength
valid
Type:
metadata
System:
knb
On failure:
warn
Length of entityName is not excessive (less than 100 char)
length of entity name is less than 100 characters
entityName value is 100 characters or less
7
2
entityDescriptionPresent
valid
Type:
metadata
System:
lter
On failure:
warn
An entity description is present
Check for presence of an entity description.
EML Best practices pp. 32-33, "...should have enough information for a user..."
true
With entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3
numHeaderLinesPresent
info
Type:
metadata
System:
knb
On failure:
info
'numHeaderLines' element is present
Check for presence of the 'numHeaderLines' element.
Document contains 'numHeaderLines' element.
'numHeaderLines' element: 1
4
numFooterLinesPresent
info
Type:
metadata
System:
knb
On failure:
info
'numFooterLines' element is present
Check for presence of the 'numFooterLines' element.
Document contains 'numFooterLines' element.
No 'numFooterLines' element found
If data file contains footer lines, 'numFooterLines' must be specified.
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 70307 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
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
11
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
12
displayDownloadData
info
Type:
data
System:
knb
On failure:
info
Display downloaded data
Display the first kilobyte of data that is downloaded
Succeeded in accessing URL: https://ezeml.edirepository.org/user-data/Ben_D._Scofield-88c6c63446b6810a103289fb51210da1/uploads/Coeur%20d'Alene%20Lake%20macrophyte%20phenology%20study/phen_bm.csv
15
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.
ae55595e056ff546ab9b9d97ba22c5d3
ae55595e056ff546ab9b9d97ba22c5d3
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.
16
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.
70307
70307
Examining the entity size is a method for checking that this is the correct entity.
Check the entity size.
17
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 22392200 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
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
11
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
12
displayDownloadData
info
Type:
data
System:
knb
On failure:
info
Display downloaded data
Display the first kilobyte of data that is downloaded
Succeeded in accessing URL: https://ezeml.edirepository.org/user-data/Ben_D._Scofield-88c6c63446b6810a103289fb51210da1/uploads/Coeur%20d'Alene%20Lake%20macrophyte%20phenology%20study/phen_bv_grid.csv
15
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.
e0de7a8fbce4807eced81beb4d0ee6cb
e0de7a8fbce4807eced81beb4d0ee6cb
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.
16
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.
22392200
22392200
Examining the entity size is a method for checking that this is the correct entity.
Check the entity size.
17
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 7253462 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
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
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
displayDownloadData
info
Type:
data
System:
knb
On failure:
info
Display downloaded data
Display the first kilobyte of data that is downloaded
Up to one kilobyte of data should be displayed
Found for displayDownloadData check
site,date,lon,lat,dep_m,rec,datetime_utc,son_filename
Black Lake,2017-06-13,-116.661636706421,47.4574331679114,2.352,10,2017-06-13T18:22:19Z,0afe43b3-0d9f-4f30-99d8-12c3387b1482
Black Lake,2017-06-13,-116.661636706421,47.4574392621929,2.329,20,2017-06-13T18:22:19Z,0afe43b3-0d9f-4f30-99d8-12c3387b1482
Black Lake,2017-06-13,-116.661645719794,47.4574392621929,2.341,30,2017-06-13T18:22:20Z,0afe43b3-0d9f-4f30-99d8-12c3387b1482
Black Lake,2017-06-13,-116.661645719794,47.4574392621929,2.29,40,2017-06-13T18:22:20Z,0afe43b3-0d9f-4f30-99d8-12c3387b1482
Black Lake,2017-06-13,-116.661645719794,47.4574453564738,2.236,50,2017-06-13T18:22:21Z,0afe43b3-0d9f-4f30-99d8-12c3387b1482
Black Lake,2017-06-13,-116.661645719794,47.4574453564738,2.239,60,2017-06-13T18:22:21Z,0afe43b3-0d9f-4f30-99d8-12c3387b1482
Black Lake,2017-06-13,-116.661645719794,47.4574514507539,2.24,70,2017-06-13T18:22:22Z,0afe43b3-0d9f-4f30-99d8-12c3387b1482
Black Lake,2017-06-13,-116.661654733167,47.4574575450333,2.235,80,2017-06-13T18:22:22Z,0afe43b3-0d9f-4f3
14
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.
Succeeded in accessing URL: https://ezeml.edirepository.org/user-data/Ben_D._Scofield-88c6c63446b6810a103289fb51210da1/uploads/Coeur%20d'Alene%20Lake%20macrophyte%20phenology%20study/phen_dep_path.csv
16
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.
2c5d2de164216b6b6312ec2b790f17cb
2c5d2de164216b6b6312ec2b790f17cb
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.
17
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.
7253462
7253462
Examining the entity size is a method for checking that this is the correct entity.
Check the entity size.
18
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 1167232 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
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
12
displayDownloadData
info
Type:
data
System:
knb
On failure:
info
Display downloaded data
Display the first kilobyte of data that is downloaded
Succeeded in accessing URL: https://ezeml.edirepository.org/user-data/Ben_D._Scofield-88c6c63446b6810a103289fb51210da1/uploads/Coeur%20d'Alene%20Lake%20macrophyte%20phenology%20study/phen_hobo_hr.csv
15
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.
7fe8d1cd31d2888fdce60243ce412aa5
7fe8d1cd31d2888fdce60243ce412aa5
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.
16
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.
1167232
1167232
Examining the entity size is a method for checking that this is the correct entity.
Check the entity size.
17
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 48253 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
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
11
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
12
displayDownloadData
info
Type:
data
System:
knb
On failure:
info
Display downloaded data
Display the first kilobyte of data that is downloaded
Up to one kilobyte of data should be displayed
Found for displayDownloadData check
site,date,meanT,minT,maxT,count,gdd
Black Lake,2017-04-27,9.691875,9.238,10.051,24,0
Black Lake,2017-04-28,9.642291666666667,8.965,10.149,24,0
Black Lake,2017-04-29,10.410499999999999,9.682,11.443,24,0
Black Lake,2017-04-30,11.189458333333334,10.98,11.394,24,0
Black Lake,2017-05-01,10.960833333333333,10.614,11.248,24,0
Black Lake,2017-05-02,10.704625,10.418,11.005,24,0
Black Lake,2017-05-03,10.944333333333333,10.565,11.734,24,0
Black Lake,2017-05-04,12.154291666666667,11.005,14.577,24,0
Black Lake,2017-05-05,12.952416666666666,11.005,15.151,24,0.0754999999999999
Black Lake,2017-05-06,9.472125,8.792,10.834,24,0.0754999999999999
Black Lake,2017-05-07,10.410958333333333,8.593,14.409,24,0.0754999999999999
Black Lake,2017-05-08,12.96625,11.759,14.29,24,0.0754999999999999
Black Lake,2017-05-09,13.421541666666666,11.904,14.433,24,0.0754999999999999
Black Lake,2017-05-10,14.122833333333334,11.565,15.247,24,0.19899999999999984
Black Lake,2017-05-11,15.292708333333334,13.738,16.392,24,0.8949999999999996
Black Lake,2017
13
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.
Succeeded in accessing URL: https://ezeml.edirepository.org/user-data/Ben_D._Scofield-88c6c63446b6810a103289fb51210da1/uploads/Coeur%20d'Alene%20Lake%20macrophyte%20phenology%20study/phen_hobo_day.csv
15
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.
0e552d17214af0db45d7054c4c98583b
0e552d17214af0db45d7054c4c98583b
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.
16
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.
48253
48253
Examining the entity size is a method for checking that this is the correct entity.
Check the entity size.
17
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 185856 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
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
12
displayDownloadData
info
Type:
data
System:
knb
On failure:
info
Display downloaded data
Display the first kilobyte of data that is downloaded
Up to one kilobyte of data should be displayed
Found for displayDownloadData check
site,datetime,dep_m,rnddep_m,temp_C,do_sat,do_mgL,pH,spcond_uScm,par_umolsm2,fluor_v,flag,intbat_v,filename
Black Lake,2017-04-26 12:09:23,0.41,0.5,10.19,106.9,11.02,7.64,74,310,0.1696,n,9.6,BlackLk042617.xlsx
Black Lake,2017-04-26 12:09:23,0.4,0.5,10.17,107.1,11.04,7.63,73,352,0.1694,n,9.4,BlackLk042617.xlsx
Black Lake,2017-04-26 12:09:25,0.4,0.5,10.17,107.1,11.04,7.63,73,352,0.1694,n,9.4,BlackLk042617.xlsx
Black Lake,2017-04-26 12:09:57,0.33,0.5,10.23,107.1,11.03,7.53,74,811,0.1317,n,9.4,BlackLk042617.xlsx
Black Lake,2017-04-26 12:09:58,0.33,0.5,10.23,107.1,11.03,7.53,74,811,0.1317,n,9.4,BlackLk042617.xlsx
Black Lake,2017-04-26 12:09:58,0.36,0.5,10.23,107.1,11.03,7.54,73,821,0.1294,n,9.4,BlackLk042617.xlsx
Black Lake,2017-04-26 12:10:57,1.01,1,10.17,106.9,11.02,7.51,73,129,0.179,n,9.4,BlackLk042617.xlsx
Black Lake,2017-04-26 12:10:59,1.01,1,10.18,106.9,11.02,7.51,73,128,0.1796,n,9.4,BlackLk042617.xlsx
Black Lake,2017-04-26 12:11:00,1.01,1,10.19,106.9,11.02,7.51,74,128,0.1796,n,9.4,BlackLk042617.xls
13
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.
Succeeded in accessing URL: https://ezeml.edirepository.org/user-data/Ben_D._Scofield-88c6c63446b6810a103289fb51210da1/uploads/Coeur%20d'Alene%20Lake%20macrophyte%20phenology%20study/phen_hydrolab.csv
15
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.
aef0f9d49155133ed477f360acb094d6
aef0f9d49155133ed477f360acb094d6
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.
16
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.
185856
185856
Examining the entity size is a method for checking that this is the correct entity.
Check the entity size.
17
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 33086 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
A preferred format string was found.
Modify the dateTime/formatString, selecting from among the preferred values one that best matches the data format
11
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
12
displayDownloadData
info
Type:
data
System:
knb
On failure:
info
Display downloaded data
Display the first kilobyte of data that is downloaded
Succeeded in accessing URL: https://ezeml.edirepository.org/user-data/Ben_D._Scofield-88c6c63446b6810a103289fb51210da1/uploads/Coeur%20d'Alene%20Lake%20macrophyte%20phenology%20study/phen_par.csv
15
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.
ddc9f3bf4f7a9d0e2c404fc5f796c24e
ddc9f3bf4f7a9d0e2c404fc5f796c24e
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.
16
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.
33086
33086
Examining the entity size is a method for checking that this is the correct entity.
Check the entity size.
17
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 50459 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
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
12
displayDownloadData
info
Type:
data
System:
knb
On failure:
info
Display downloaded data
Display the first kilobyte of data that is downloaded
Succeeded in accessing URL: https://ezeml.edirepository.org/user-data/Ben_D._Scofield-88c6c63446b6810a103289fb51210da1/uploads/Coeur%20d'Alene%20Lake%20macrophyte%20phenology%20study/phen_rake.csv
15
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.
8d1000a02a89626468eee305e4c5a2cd
8d1000a02a89626468eee305e4c5a2cd
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.
16
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.
50459
50459
Examining the entity size is a method for checking that this is the correct entity.
Check the entity size.
17
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 5712 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
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
12
displayDownloadData
info
Type:
data
System:
knb
On failure:
info
Display downloaded data
Display the first kilobyte of data that is downloaded
Up to one kilobyte of data should be displayed
Found for displayDownloadData check
siteid,site,datetime_utc,dep_m,note,globalid,lon,lat
15con1WQ,Chatcolet Lake,2017-05-18 21:02:00,3.1,GPS position was an estimate from map,{7D7F6830-79B7-4265-9DAF-29EA2AD4819E},-116.7366618,47.35884586
15con1WQ,Chatcolet Lake,2017-06-02 21:03:00,4,GPS position was an estimate from map,{8D0C6E66-207E-4D61-9D62-F74D01E05BF4},-116.7366663,47.35880355
15con1WQ,Chatcolet Lake,2017-06-14 19:00:00,4.35,Blue-ish green water color ,{781D126A-C058-4D09-AF3D-CC3C696D0CA3},-116.7367933,47.35882667
15con1WQ,Chatcolet Lake,2017-06-28 18:39:00,3.6,,{66F05F61-9F63-4E50-A364-9D50B885EC8F},-116.7365883,47.35882333
15con1WQ,Chatcolet Lake,2017-07-14 21:26:00,3.7,"Blue green water, small algae chunks in water",{12F2FC40-4C92-4A82-9AE6-8D60B0CEA052},-116.7366287,47.35864716
15con1WQ,Chatcolet Lake,2017-07-27 22:18:00,3.1,Chunky greenish algae bloom developing in shallow water near this site,{B16F61B0-9C98-4B8B-8933-8E062F6ECBB4},-116.7368617,47.35879
15con1WQ,Chatcolet Lake,2017-08-09 19:01:00,4.8,Water blue green with so
13
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.
Succeeded in accessing URL: https://ezeml.edirepository.org/user-data/Ben_D._Scofield-88c6c63446b6810a103289fb51210da1/uploads/Coeur%20d'Alene%20Lake%20macrophyte%20phenology%20study/phen_secchi.csv
15
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.
01a2976760690d180b01260be57e5aad
01a2976760690d180b01260be57e5aad
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.
16
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.
5712
5712
Examining the entity size is a method for checking that this is the correct entity.
Check the entity size.
17
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
Display the first row of data values to be inserted into the database table
The first row of data values should be displayed
15con1WQ, Chatcolet Lake, 2017-05-18 21:02:00, 3.1, GPS position was an estimate from map, {7D7F6830-79B7-4265-9DAF-29EA2AD4819E}, -116.7366618, 47.35884586
20
onlineURLs
valid
Type:
congruency
System:
knb
On failure:
error
Online URLs are live
Check that online URLs return something
true
true
Succeeded in accessing URL: file:///home/pasta/local/data/edi.1341.1/dfde561d38ccc7dc9a4cfff8a383dd6f
21
tooFewFields
valid
Type:
congruency
System:
knb
On failure:
error
Data does not have fewer fields than metadata attributes
Compare number of fields specified in metadata to number of fields found in a data record
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 1282 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
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
11
displayDownloadData
info
Type:
data
System:
knb
On failure:
info
Display downloaded data
Display the first kilobyte of data that is downloaded
Up to one kilobyte of data should be displayed
Found for displayDownloadData check
spp,fullname,note
Brasen,Brasenia schreberi,NA
Cerato,Ceratophyllum demersum,NA
Elatin,Elatine triandra,Species designation uncertain
Eleoch,Eleocharis parvula,NA
Elodea,Elodea canadensis,Likely includes some E. nuttallii
Equise,Equisetum parvula,NA
Filame,Filamentous algae,Cladophora often observed
Fontin,Fontinalis sp.,NA
Myriop,Myriophyllum spicatum,Due to hybridization of M. spicatum and M. sibiricum we cannot field identify milfoil past genus. Based on genetic ID by Ryan Thum (Montana State University) most milfoil is either M. spicatum or the M. spicatum x M. sibiricum hybrid
Najass,Najas sp.,NA
Nitell,Nitella sp.,Includes other charophytes e.g. Chara sp. but most often Nitella sp. is encountered
Pampli,Potamogeton amplifolius,NA
Pepihy,Potamogeton epihydrus,NA
Ppusil,Potamogeton pusillus,May include some P. foliosis
Pricha,Potamogeton richardsonii,NA
Probbi,Potamogeton robbinsii,NA
Pzoste,Potamogeton zosteriformis,NA
Ranunc,Ranunculus aquatilis,NA
Sagitt,Sagittaria spp.,Sagittaria sp. are difficult to
12
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.
Succeeded in accessing URL: https://ezeml.edirepository.org/user-data/Ben_D._Scofield-88c6c63446b6810a103289fb51210da1/uploads/Coeur%20d'Alene%20Lake%20macrophyte%20phenology%20study/phen_spp.csv
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.
c104acc729712f0202465056dbc848ea
c104acc729712f0202465056dbc848ea
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.
1282
1282
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