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
knb-lter-kbs.195.39
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
7 'keyword' element(s) found
7
methodsElementPresent
warn
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.
0 'methods' element(s) found
As a minimum, a reference to an external protocol should be given at the dataset level. However, detailed methods at this level are preferable. If further refinement is needed, methods can be defined for individual data entities or even individual attributes if necessary.
Since they are mostly for human consumption, one detailed description of all steps taken at the dataset level is frequently sufficient and more user friendly.
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
12 words found.
EML Best Practices, v.2, p. 13
14
datasetAbstractLength
warn
Type:
metadata
System:
lter
On failure:
warn
Dataset abstract element is a minimum of 20 words
Check the length of a dataset abstract and warn if less than 20 words.
An abstract is 20 words or more.
12 words found.
An abstract helps a user determine if the dataset is useful for a specific purpose. An abstract is usually a paragraph.
Add an abstract.
EML Best Practices
15
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:
Kellogg Biological Station LTER: LTER Weather Station - Data Formatted for Salus Model (KBS002-009)
Entity Identifier:
/datatables/143
#
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
99
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: 27
4
numFooterLinesPresent
info
Type:
metadata
System:
knb
On failure:
info
'numFooterLines' element is present
Check for presence of the 'numFooterLines' element.
Warn the user if the numberOfRecords check is not present
A number of records element is expected for this entity
numberOfRecords element not found
This is a valuable check that we have the correct table.
Add a numberOfRecords element and store the number of entity records
8
entitySizePresence
warn
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.
No entity size value was found.
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
warn
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.
No authentication element was found.
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
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
warn
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.
'DDD' is not in the set of preferred values.
In the current version of EML (2.1), the dateTime/formatString is interpreted as ISO-8601. This check is classified as a warn, so other formats are allowed. In the future (e.g., future version of EML), other formatStrings may be added to the preferred list.
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
Cannot display NON-PLAIN TEXT DATA
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.
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
1988, 1, , , , 0, , ,
19
dataLoadStatus
warn
Type:
congruency
System:
knb
On failure:
warn
Data can be loaded into the database
Status of loading the data table into a database
No errors expected during data loading or data loading was not attempted for this data entity
Error inserting data at row 1.
ERROR: cannot calculate day of year without year information
20
headerRowAttributeNames
info
Type:
congruency
System:
lter
On failure:
info
Header row is displayed alongside attribute names
Compare tne content of the data header row to the content of EML attribute names.
No expectation, information only
Found for headerRowAttributeNames check
*** HEADER ROWS ***
# LTER Weather Station - Data Formatted for Salus Model
#
# Original Data Source: https://lter.kbs.msu.edu/datatables/143
# The newest version of the data https://lter.kbs.msu.edu/datatables/143.csv
# Full EML Metadata: https://lter.kbs.msu.edu/datasets/195.eml
#
# These Data are copyrighted and use in a publication requires written permission
# as detailed in our Terms of use: https://lter.kbs.msu.edu/data/terms-of-use/
# Use of the data constitutes acceptance of the terms.
#
# VARIATE TABLE
# year observation year
# doy day of year
# solar_radiation megaJoulePerMeterSquared average solar radiation
# air_temp_max celsius maximum air temperature in C
# air_temp_min celsius minimum air temperature in C
# precipitation millimeter rainfall
# dew_point celsius dew point
# wind_run kilometer the distance wind would travel in a day
# par microEinsteinPerMeterSquaredPerSecond photosynthetically active radiation
#
#
# DATA TABLE CORRECTIONS AND COMMENTS
#
#
year,doy,solar_radiation,air_temp_max,air_temp_min,precipitation,dew_point,wind_run,par
#,,megaJoulePerMeterSquared,celsius,celsius,millimeter,celsius,kilometer,microEinsteinPerMeterSquaredPerSecond
*** ATTRIBUTE LIST ***
year,doy,solar_radiation,air_temp_max,air_temp_min,precipitation,dew_point,wind_run,par
Customer should evaluate the findings
21
dateFormatMatches
warn
Type:
congruency
System:
lter
On failure:
warn
Date format in metadata matches data
dateTime/formatString in attribute metadata is from the preferred list, and the data matches. A non-match generates only a warn.
Format string is preferred, and all data values match the format string
Not checked.
'DDD' is not a preferred format string and was not checked for congruency with the datetime values.
Dates should be consistently formatted and match the formatString in metadata.
22
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/knb-lter-kbs.195.39/5af5e05ba26781c8a823a8365091cb5c
Entity Report
Entity Name:
Kellogg Biological Station LTER: Soil Test data (KBS0136-007)
Entity Identifier:
/datatables/661
#
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
62
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: 34
4
numFooterLinesPresent
info
Type:
metadata
System:
knb
On failure:
info
'numFooterLines' element is present
Check for presence of the 'numFooterLines' element.
Warn the user if the numberOfRecords check is not present
A number of records element is expected for this entity
numberOfRecords element not found
This is a valuable check that we have the correct table.
Add a numberOfRecords element and store the number of entity records
8
entitySizePresence
warn
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.
No entity size value was found.
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
warn
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.
No authentication element was found.
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
Cannot display NON-PLAIN TEXT DATA
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.
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
No errors expected during data loading or data loading was not attempted for this data entity
The data table loaded successfully into a database
22
numberOfRecords
info
Type:
congruency
System:
knb
On failure:
warn
Number of records in metadata matches number of rows loaded
Compare number of records specified in metadata to number of records found in data
-1
753
The number of records found in the data table was: 753. There was no 'numberOfRecords' value specified in the EML.
23
headerRowAttributeNames
info
Type:
congruency
System:
lter
On failure:
info
Header row is displayed alongside attribute names
Compare tne content of the data header row to the content of EML attribute names.
No expectation, information only
Found for headerRowAttributeNames check
*** HEADER ROWS ***
# Soil Test data
#
# Original Data Source: https://lter.kbs.msu.edu/datatables/661
# The newest version of the data https://lter.kbs.msu.edu/datatables/661.csv
# Full EML Metadata: https://lter.kbs.msu.edu/datasets/195.eml
#
# These Data are copyrighted and use in a publication requires written permission
# as detailed in our Terms of use: https://lter.kbs.msu.edu/data/terms-of-use/
# Use of the data constitutes acceptance of the terms.
#
# VARIATE TABLE
# sample_date the date the sample is taken from the field
# treatment treatment
# replicate replicate block
# depth depth of the soil sample
# ph dimensionless measured pH
# cec milliEquivalentsPerHundredGram cation exchange capacity in meq/100g soil
# phosphorus milligramsPerKilogram Bray P1 phosphorus
# potassium milligramsPerKilogram potassium
# calcium milligramsPerKilogram calcium
# magnesium milligramsPerKilogram magnesium
# lime_index dimensionless lime index
# z_ppm milligramsPerKilogram zinc
# s_ppm milligramsPerKilogram sulphur
# b_ppm milligramsPerKilogram boron
# comment comment about the sample
# year the sample year
#
#
# DATA TABLE CORRECTIONS AND COMMENTS
#
#
sample_date,treatment,replicate,depth,ph,cec,phosphorus,potassium,calcium,magnesium,lime_index,z_ppm,s_ppm,b_ppm,comment,year
#,,,,dimensionless,milliEquivalentsPerHundredGram,milligramsPerKilogram,milligramsPerKilogram,milligramsPerKilogram,milligramsPerKilogram,dimensionless,milligramsPerKilogram,milligramsPerKilogram,milligramsPerKilogram,,
*** ATTRIBUTE LIST ***
sample_date,treatment,replicate,depth,ph,cec,phosphorus,potassium,calcium,magnesium,lime_index,z_ppm,s_ppm,b_ppm,comment,year
Customer should evaluate the findings
24
dateFormatMatches
valid
Type:
congruency
System:
lter
On failure:
warn
Date format in metadata matches data
dateTime/formatString in attribute metadata is from the preferred list, and the data matches. A non-match generates only a warn.
Format string is preferred, and all data values match the format string
Data values matched the specified formatString.
Dates should be consistently formatted and match the formatString in metadata.
Entity Report
Entity Name:
Kellogg Biological Station LTER: MCSE Activity Report for the Main plots (KBS036-001)
Entity Identifier:
/datatables/639
#
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
85
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: 26
4
numFooterLinesPresent
info
Type:
metadata
System:
knb
On failure:
info
'numFooterLines' element is present
Check for presence of the 'numFooterLines' element.
Warn the user if the numberOfRecords check is not present
A number of records element is expected for this entity
numberOfRecords element not found
This is a valuable check that we have the correct table.
Add a numberOfRecords element and store the number of entity records
8
entitySizePresence
warn
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.
No entity size value was found.
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
warn
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.
No authentication element was found.
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
Cannot display NON-PLAIN TEXT DATA
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.
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
Found for displayFirstInsertRow check
2020-07-30, T6, R2, T6R2, Roundup Power Max (glyphosate 48.7%), 2.34, Sprayed LTER T6 (MICRO PLOTS), and CE3 soybean plots with Roundup Powermax and AMS. AMS applied at 3.4 lbs/A, Roundup Powermax applied at 1 qt/A. Weather conditions at the beginning 10:37 a.m. partly cloudy, 75.3 degrees F, 4-5 mph north east wind, 65.9 % humidity. Conditions at the end 11:40 a.m., partly cloudy 75.4 degrees F, 5-6 mph north east wind, 67.4 % humidity., https://aglog.kbs.msu.edu/observations/4849
18
dataLoadStatus
warn
Type:
congruency
System:
knb
On failure:
warn
Data can be loaded into the database
Status of loading the data table into a database
No errors expected during data loading or data loading was not attempted for this data entity
Error inserting data at row 165.
There is a un-closed quote in data file
19
headerRowAttributeNames
info
Type:
congruency
System:
lter
On failure:
info
Header row is displayed alongside attribute names
Compare tne content of the data header row to the content of EML attribute names.
No expectation, information only
Found for headerRowAttributeNames check
*** HEADER ROWS ***
# MCSE Activity Report for the Main plots
#
# Original Data Source: https://lter.kbs.msu.edu/datatables/639
# The newest version of the data https://lter.kbs.msu.edu/datatables/639.csv
# Full EML Metadata: https://lter.kbs.msu.edu/datasets/195.eml
#
# These Data are copyrighted and use in a publication requires written permission
# as detailed in our Terms of use: https://lter.kbs.msu.edu/data/terms-of-use/
# Use of the data constitutes acceptance of the terms.
#
# VARIATE TABLE
# obs_date Observation Date
# treatment treatment identifier
# replicate replicate identifier
# plot plot identifier
# material Material applied if any
# rate_kg_ha kilogramsPerHectare rate of application if any
# comment a description of the activity or observation
# source the source url in the aglog of the observation
#
#
# DATA TABLE CORRECTIONS AND COMMENTS
#
#
obs_date,treatment,replicate,plot,material,rate_kg_ha,comment,source
#,,,,,kilogramsPerHectare,,
*** ATTRIBUTE LIST ***
obs_date,treatment,replicate,plot,material,rate_kg_ha,comment,source
Customer should evaluate the findings
20
dateFormatMatches
valid
Type:
congruency
System:
lter
On failure:
warn
Date format in metadata matches data
dateTime/formatString in attribute metadata is from the preferred list, and the data matches. A non-match generates only a warn.
Format string is preferred, and all data values match the format string
Data values matched the specified formatString.
Dates should be consistently formatted and match the formatString in metadata.
21
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/knb-lter-kbs.195.39/83a5c3f77aba6f69ee1061ce35186139
Entity Report
Entity Name:
Kellogg Biological Station LTER: Planting report for MCSE Main plots (KBS136-002)
Entity Identifier:
/datatables/640
#
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
81
2
entityDescriptionPresent
warn
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..."
false
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: 27
4
numFooterLinesPresent
info
Type:
metadata
System:
knb
On failure:
info
'numFooterLines' element is present
Check for presence of the 'numFooterLines' element.
Warn the user if the numberOfRecords check is not present
A number of records element is expected for this entity
numberOfRecords element not found
This is a valuable check that we have the correct table.
Add a numberOfRecords element and store the number of entity records
8
entitySizePresence
warn
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.
No entity size value was found.
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
warn
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.
No authentication element was found.
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
Cannot display NON-PLAIN TEXT DATA
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.
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
Found for displayFirstInsertRow check
2020-06-01, T4, R3, T4R3, Viking Organic Seed Corn Brand (O.84-95UP) Variety (A1025726), 32000, seeds, Planted corn in the LTER Main Site T4 plots, all replications in the order of (5, 3, 2, 4, 1 and 6). Equipment Used: JD 7330 tractor and JD 1730 planter. Brand and Variety Planted: Viking (brandO.84-95UP),Variety (A1025726), from Albert Lea Seed, (Certified Organic variety). This Variety has a relative maturity of 95 days. Planting Population: 32,000 seeds/A. Planting Depth: 1.75-2 inches. Row Spacing: 30 inches., https://aglog.kbs.msu.edu/observations/4797
18
dataLoadStatus
warn
Type:
congruency
System:
knb
On failure:
warn
Data can be loaded into the database
Status of loading the data table into a database
No errors expected during data loading or data loading was not attempted for this data entity
Error inserting data at row 7.
There is a un-closed quote in data file
19
headerRowAttributeNames
info
Type:
congruency
System:
lter
On failure:
info
Header row is displayed alongside attribute names
Compare tne content of the data header row to the content of EML attribute names.
No expectation, information only
Found for headerRowAttributeNames check
*** HEADER ROWS ***
# Planting report for MCSE Main plots
#
# Original Data Source: https://lter.kbs.msu.edu/datatables/640
# The newest version of the data https://lter.kbs.msu.edu/datatables/640.csv
# Full EML Metadata: https://lter.kbs.msu.edu/datasets/195.eml
#
# These Data are copyrighted and use in a publication requires written permission
# as detailed in our Terms of use: https://lter.kbs.msu.edu/data/terms-of-use/
# Use of the data constitutes acceptance of the terms.
#
# VARIATE TABLE
# obs_date the date the observation or activity happened
# treatment treatment identifier
# plot plot identifier
# replicate replicate identifier
# material seed or propagule planted
# rate the density of planting
# unit the unit of the planting rate
# comment a description of the planting event
# source the source url in the aglog
#
#
# DATA TABLE CORRECTIONS AND COMMENTS
#
#
obs_date,treatment,plot,replicate,material,rate,unit,comment,source
#,,,,,,,,
*** ATTRIBUTE LIST ***
obs_date,treatment,plot,replicate,material,rate,unit,comment,source
Customer should evaluate the findings
20
dateFormatMatches
valid
Type:
congruency
System:
lter
On failure:
warn
Date format in metadata matches data
dateTime/formatString in attribute metadata is from the preferred list, and the data matches. A non-match generates only a warn.
Format string is preferred, and all data values match the format string
Data values matched the specified formatString.
Dates should be consistently formatted and match the formatString in metadata.
21
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/knb-lter-kbs.195.39/25b68254b2e0ab5ce9f608b5507eb959
Entity Report
Entity Name:
Kellogg Biological Station LTER: Fertilizer Application Report for the Main Plots on the MCSE (KBS136-003)
Entity Identifier:
/datatables/641
#
Identifier
Status
Quality Check
Name
Description
Expected
Found
Explanation
Suggestion
Reference
1
entityNameLength
warn
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
106
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: 29
4
numFooterLinesPresent
info
Type:
metadata
System:
knb
On failure:
info
'numFooterLines' element is present
Check for presence of the 'numFooterLines' element.
Warn the user if the numberOfRecords check is not present
A number of records element is expected for this entity
numberOfRecords element not found
This is a valuable check that we have the correct table.
Add a numberOfRecords element and store the number of entity records
8
entitySizePresence
warn
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.
No entity size value was found.
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
warn
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.
No authentication element was found.
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
Cannot display NON-PLAIN TEXT DATA
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.
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
Found for displayFirstInsertRow check
2020-06-24, T1, R6, T1R6, 28% UAN (28-0-0), 281, 79, 0, 0, Fertilized LTER main site treatment T1 and T2 Alison's micro plots (plus nitrogen plots only). Applied 23.5 gallons of 28% liquid nitrogen. 28% liquid nitrogen fertilizer weighs 10.67 lbs/gallon. This equals 70 lbs of N/A. Set applicator up into a 4 row configuration using 5 knives. the middle 3 applied full rate and the outer 2 were half rate. Fertilizer was knifed 4-6 inches into the ground between the corn rows., http://aglog.kbs.msu.edu/observations/4828
18
dataLoadStatus
warn
Type:
congruency
System:
knb
On failure:
warn
Data can be loaded into the database
Status of loading the data table into a database
No errors expected during data loading or data loading was not attempted for this data entity
Error inserting data at row 13.
There is a un-closed quote in data file
19
headerRowAttributeNames
info
Type:
congruency
System:
lter
On failure:
info
Header row is displayed alongside attribute names
Compare tne content of the data header row to the content of EML attribute names.
No expectation, information only
Found for headerRowAttributeNames check
*** HEADER ROWS ***
# Fertilizer Application Report for the Main Plots on the MCSE
#
# Original Data Source: https://lter.kbs.msu.edu/datatables/641
# The newest version of the data https://lter.kbs.msu.edu/datatables/641.csv
# Full EML Metadata: https://lter.kbs.msu.edu/datasets/195.eml
#
# These Data are copyrighted and use in a publication requires written permission
# as detailed in our Terms of use: https://lter.kbs.msu.edu/data/terms-of-use/
# Use of the data constitutes acceptance of the terms.
#
# VARIATE TABLE
# obs_date the date the activity or observation occured
# treatment treatment identifier
# replicate replicate identifier
# plot plot identifier
# material material that was applied
# rate_kg_ha kilogramsPerHectare rate of material application
# n_rate_kg_ha kilogramsPerHectare application rate of N
# p_rate_kg_ha kilogramsPerHectare application rate of P
# k_rate_kg_ha kilogramsPerHectare application rate of K
# comment a description of the activity or observation
# source the source url of the observation in the aglog
#
#
# DATA TABLE CORRECTIONS AND COMMENTS
#!!! use wiht caution. If the aglog entries are not complete it won't be complete here either !!
#
obs_date,treatment,replicate,plot,material,rate_kg_ha,n_rate_kg_ha,p_rate_kg_ha,k_rate_kg_ha,comment,source
#,,,,,kilogramsPerHectare,kilogramsPerHectare,kilogramsPerHectare,kilogramsPerHectare,,
*** ATTRIBUTE LIST ***
obs_date,treatment,replicate,plot,material,rate_kg_ha,n_rate_kg_ha,p_rate_kg_ha,k_rate_kg_ha,comment,source
Customer should evaluate the findings
20
dateFormatMatches
valid
Type:
congruency
System:
lter
On failure:
warn
Date format in metadata matches data
dateTime/formatString in attribute metadata is from the preferred list, and the data matches. A non-match generates only a warn.
Format string is preferred, and all data values match the format string
Data values matched the specified formatString.
Dates should be consistently formatted and match the formatString in metadata.
21
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/knb-lter-kbs.195.39/4d9d661ed4d808bf19a2c998d8235611
Warn the user if the numberOfRecords check is not present
A number of records element is expected for this entity
numberOfRecords element not found
This is a valuable check that we have the correct table.
Add a numberOfRecords element and store the number of entity records
8
entitySizePresence
warn
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.
No entity size value was found.
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
warn
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.
No authentication element was found.
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
Cannot display NON-PLAIN TEXT DATA
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.
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
No errors expected during data loading or data loading was not attempted for this data entity
The data table loaded successfully into a database
22
numberOfRecords
info
Type:
congruency
System:
knb
On failure:
warn
Number of records in metadata matches number of rows loaded
Compare number of records specified in metadata to number of records found in data
-1
743
The number of records found in the data table was: 743. There was no 'numberOfRecords' value specified in the EML.
23
headerRowAttributeNames
info
Type:
congruency
System:
lter
On failure:
info
Header row is displayed alongside attribute names
Compare tne content of the data header row to the content of EML attribute names.
No expectation, information only
Found for headerRowAttributeNames check
*** HEADER ROWS ***
# Agronomic Yields - Annual Crops
#
# Original Data Source: https://lter.kbs.msu.edu/datatables/642
# The newest version of the data https://lter.kbs.msu.edu/datatables/642.csv
# Full EML Metadata: https://lter.kbs.msu.edu/datasets/195.eml
#
# These Data are copyrighted and use in a publication requires written permission
# as detailed in our Terms of use: https://lter.kbs.msu.edu/data/terms-of-use/
# Use of the data constitutes acceptance of the terms.
#
# VARIATE TABLE
# date harvest date
# treatment treatment identifier
# replicate replicate identifier
# crop Crop harvested
# yield_bu_a bushelsPerAcre agronomic yield in bushels/acre. Yields are reported at standard moistures, not dry weight.
# yield_kg_ha kilogramsPerHectare agronomic yield in kg per hectare. Yields are reported at standard moistures not dry weight.
#
#
# DATA TABLE CORRECTIONS AND COMMENTS
#<p>2003-12-18 Sven Bohm. From 2001 to present corn yield is based on 15% moisture rather than 15.5%</p><p>2004-1-13 Sven Bohm. Yield data from 2003 from treatments 3 and 4 were corrected for the presence of weed seeds, since there were more than the usual amount of weed seeds in the harvested grain</p>
#2012-12-27 Sven Bohm. Discovered that the 2011 kg/ha yield was mistakenly multiplied by 50 instead of 56. And 2005 kg/ha yields were different than the bu/acre yields, due to an unknown cause.
#2018-1-4 Sven Bohm. In 2017 we switched to reporting the harvest of the whole plot instead of just the east side
#2013-1-28 Sven Bohm. The 2011-11-15 T1R3 plot was mistakenly labeled T1T3.
#2013-2-1. Sven Bohm. It was discovered that the 2009 T3 yields were calculated with a 30 inch row spacing instead of 15 inches. This resulted in the reported yields to half of what they should have been. The mistake has been corrected and the updated numbers included in the dataset.
#2015-5-14 Sven Bohm. The yield in kg/ha was incorrectly reported for 2014. The numbers have been corrected.
#
date,treatment,replicate,crop,yield_bu_a,yield_kg_ha
#,,,,bushelsPerAcre,kilogramsPerHectare
*** ATTRIBUTE LIST ***
date,treatment,replicate,crop,yield_bu_a,yield_kg_ha
Customer should evaluate the findings
24
dateFormatMatches
valid
Type:
congruency
System:
lter
On failure:
warn
Date format in metadata matches data
dateTime/formatString in attribute metadata is from the preferred list, and the data matches. A non-match generates only a warn.
Format string is preferred, and all data values match the format string
Data values matched the specified formatString.
Dates should be consistently formatted and match the formatString in metadata.
Entity Report
Entity Name:
Kellogg Biological Station LTER: Plot Center Locations and Size (KBS136-006)
Entity Identifier:
/datatables/644
#
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
76
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: 26
4
numFooterLinesPresent
info
Type:
metadata
System:
knb
On failure:
info
'numFooterLines' element is present
Check for presence of the 'numFooterLines' element.
Warn the user if the numberOfRecords check is not present
A number of records element is expected for this entity
numberOfRecords element not found
This is a valuable check that we have the correct table.
Add a numberOfRecords element and store the number of entity records
8
entitySizePresence
warn
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.
No entity size value was found.
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
warn
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.
No authentication element was found.
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
Cannot display NON-PLAIN TEXT DATA
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.
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
No errors expected during data loading or data loading was not attempted for this data entity
The data table loaded successfully into a database
21
numberOfRecords
info
Type:
congruency
System:
knb
On failure:
warn
Number of records in metadata matches number of rows loaded
Compare number of records specified in metadata to number of records found in data
-1
40
The number of records found in the data table was: 40. There was no 'numberOfRecords' value specified in the EML.
22
headerRowAttributeNames
info
Type:
congruency
System:
lter
On failure:
info
Header row is displayed alongside attribute names
Compare tne content of the data header row to the content of EML attribute names.
No expectation, information only
Found for headerRowAttributeNames check
*** HEADER ROWS ***
# Plot Center Locations and Size
#
# Original Data Source: https://lter.kbs.msu.edu/datatables/644
# The newest version of the data https://lter.kbs.msu.edu/datatables/644.csv
# Full EML Metadata: https://lter.kbs.msu.edu/datasets/195.eml
#
# These Data are copyrighted and use in a publication requires written permission
# as detailed in our Terms of use: https://lter.kbs.msu.edu/data/terms-of-use/
# Use of the data constitutes acceptance of the terms.
#
# VARIATE TABLE
# longitude degrees latitude or longitude the longitude of the center of the plot
# latitude degrees latitude or longitude the latitude of the center of the plot
# altitude meter the altitude of the center of the plot
# experiment the name of the experiment
# treatment treatment identifier
# repliate replicate identifier
# landscape position the landscape position of the plot
# area_m2 squareMeter the area of the plot
#
#
# DATA TABLE CORRECTIONS AND COMMENTS
#
#
longitude,latitude,altitude,experiment,treatment,repliate,landscape position,area_m2
#degrees latitude or longitude,degrees latitude or longitude,meter,,,,,squareMeter
*** ATTRIBUTE LIST ***
longitude,latitude,altitude,experiment,treatment,repliate,landscape position,area_m2
Customer should evaluate the findings
23
dateFormatMatches
valid
Type:
congruency
System:
lter
On failure:
warn
Date format in metadata matches data
dateTime/formatString in attribute metadata is from the preferred list, and the data matches. A non-match generates only a warn.
Format string is preferred, and all data values match the format string
Data values matched the specified formatString.
Dates should be consistently formatted and match the formatString in metadata.