Check against LTER requirements for scope.identifier.revision
'knb-lter-abc.n.m', where 'abc' is an LTER site acronym and 'n' and 'm' are whole numbers
knb-lter-xyz.55.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 eml://ecoinformatics.org/eml-2.1.1
eml://ecoinformatics.org/eml-2.1.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: 'eml://ecoinformatics.org/eml-2.1.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: 'eml://ecoinformatics.org/eml-2.1.0'
Validity of this quality report is dependent on this check being valid.
6
keywordPresent
warn
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
0 'keyword' element(s) found
The LTER portal allows searches on keywords. This check is a precursor for checking on keywords from the controlled vocabulary.
Add at least one keyword.
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.
2 'methods' element(s) found
EML Best Practices, p. 28
8
coveragePresent
warn
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.
0 'coverage' element(s) found
9
geographicCoveragePresent
info
Type:
metadata
System:
lter
On failure:
info
geographicCoverage is present
Check that geographicCoverage exists in EML at the dataset level, or at least one entity's level, or at least one attribute's level.
geographicCoverage at least at the dataset level.
0 'geographicCoverage' element(s) found
Many but not all datasets are appropriate to have spatial coverage.
If sampling EML is used within methods, does that obviate geographicCoverage? Or should those sites be repeated or referenced?
EML Best Practices v.2, p. 22-23. "One geographicCoverage element should be included, whose boundingCoordinates describe the extent of the data....Additional geographicCoverage elements may be entered at the dataset level if there are significant distances between study sites and it would be confusing if they were grouped into one bounding box." 6 decimal places.
10
taxonomicCoveragePresent
info
Type:
metadata
System:
lter
On failure:
info
taxonomicCoverage is present
Check that taxonomicCoverage exists in EML at the dataset level, or at least one entity's level, or at least one attribute's level.
taxonomicCoverage at least at the dataset level.
0 'taxonomicCoverage' element(s) found
Only when taxa are pertinent to the dataset will they have taxonomicCoverage.
Could search title, abstract, keywords for any taxonomic name (huge). Could search keywordType="taxonomic".
EML Best Practices v.2, p. 25
11
temporalCoveragePresent
info
Type:
metadata
System:
lter
On failure:
info
temporalCoverage is present
Check that temporalCoverage exists in EML at the dataset level, or at least one entity's level, or at least one attribute's level.
temporalCoverage at least at the dataset level.
0 '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
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
5 words found.
EML Best Practices, v.2, p. 13
13
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.
0 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
14
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
Display the first kilobyte of data that is downloaded
Up to one kilobyte of data should be displayed
Found for displayDownloadData check
Blue Field,1998,4.5
Yellow Field,1998,3.45
Red Field,1998,6.75
Blue Field,1999,4.8
Yellow Field,1999,3.45
Red Field,1999,6.5
Blue Field,2000,4.52
Yellow Field,2000,3.48
Red Field,2000,7.5
Blue Field,2001,0.5
Yellow Field,2001,8.75
Red Field,2001,9.5
Blue Field,2002,14.5
Yellow Field,2002,13.45
Red Field,2002,16.5
Blue Field,2003,4.5
Yellow Field,2003,3.45
Red Field,2003,6.75
Blue Field,2004,4.5
Yellow Field,2004,3.45
Red Field,2004,6.75
Blue Field,2005,4.5
Yellow Field,2005,3.45
Red Field,2005,6.75
Blue Field,2006,4.5
Yellow Field,2006,3.45
Red Field,2006,6.75
Blue Field,2007,4.5
Yellow Field,2007,3.45
Red Field,2007,6.75
Blue Field,2008,4.5
Yellow Field,2008,3.45
Red Field,2008,6.75
Blue Field,2009,4.5
Yellow Field,2009,3.45
Red Field,2009,6.75
Blue Field,2010,4.5
Yellow Field,2010,3.45
Red Field,2010,6.75
Blue Field,2011,4.5
Yellow Field,2011,3.45
Red Field,2011,6.75
5
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