Data Package Quality Report
PackageId: knb-lter-vcr.25.35
Report Date/Time: 2018-01-03T11:54:26
Dataset Report
# Identifier Status Quality Check Name Description Expected Found Explanation Suggestion Reference
1packageIdPattern
valid
 Type: metadata
 System: lter
 On Failure: error
packageId pattern matches "scope.identifier.revision"Check against LTER requirements for scope.identifier.revision'scope.n.m', where 'n' and 'm' are integers and 'scope' is one of an allowed set of valuesknb-lter-vcr.25.35
2emlVersion
valid
 Type: metadata
 System: lter
 On Failure: error
EML version 2.1.0 or beyondCheck the EML document declaration for version 2.1.0 or highereml://ecoinformatics.org/eml-2.1.0 or eml://ecoinformatics.org/eml-2.1.1eml://ecoinformatics.org/eml-2.1.0Validity of this quality report is dependent on this check being valid.
3schemaValid
valid
 Type: metadata
 System: knb
 On Failure: error
Document is schema-valid EMLCheck document schema validityschema-validDocument validated for namespace: 'eml://ecoinformatics.org/eml-2.1.0'Validity of this quality report is dependent on this check being valid.
4parserValid
valid
 Type: metadata
 System: knb
 On Failure: error
Document is EML parser-validCheck document using the EML IDs and references parserValidates with the EML IDs and references parserEML IDs and references parser succeededValidity of this quality report is dependent on this check being valid.
5schemaValidDereferenced
valid
 Type: metadata
 System: lter
 On Failure: error
Dereferenced document is schema-valid EMLReferences are dereferenced, and the resulting file validatedschema-validDereferenced document validated for namespace: 'eml://ecoinformatics.org/eml-2.1.0'Validity of this quality report is dependent on this check being valid.
6keywordPresent
valid
 Type: metadata
 System: lter
 On Failure: warn
keyword element is presentChecks to see if at least one keyword is presentPresence of one or more keyword elements9 'keyword' element(s) found
7methodsElementPresent
valid
 Type: metadata
 System: lter
 On Failure: warn
A 'methods' element is presentAll datasets should contain a 'methods' element, at a minimum a link to a separate methods doc.presence of 'methods' at one or more xpaths.9 'methods' element(s) foundEML Best Practices, p. 28
8coveragePresent
valid
 Type: metadata
 System: lter
 On Failure: warn
coverage element is presentAt least one coverage element should be present in a dataset.At least one of geographicCoverage, taxonomicCoverage, or temporalCoverage is present in the EML.1 'coverage' element(s) found
9geographicCoveragePresent
info
 Type: metadata
 System: lter
 On Failure: info
geographicCoverage is presentCheck that geographicCoverage exists in EML at the dataset level, or at least one entity's level, or at least one attribute's level.geographicCoverage at least at the dataset level.4 'geographicCoverage' element(s) foundMany but not all datasets are appropriate to have spatial coverage.If sampling EML is used within methods, does that obviate geographicCoverage? Or should those sites be repeated or referenced?EML Best Practices v.2, p. 22-23. "One geographicCoverage element should be included, whose boundingCoordinates describe the extent of the data....Additional geographicCoverage elements may be entered at the dataset level if there are significant distances between study sites and it would be confusing if they were grouped into one bounding box." 6 decimal places.
10taxonomicCoveragePresent
info
 Type: metadata
 System: lter
 On Failure: info
taxonomicCoverage is presentCheck that taxonomicCoverage exists in EML at the dataset level, or at least one entity's level, or at least one attribute's level.taxonomicCoverage at least at the dataset level.0 'taxonomicCoverage' element(s) foundOnly when taxa are pertinent to the dataset will they have taxonomicCoverage.Could search title, abstract, keywords for any taxonomic name (huge). Could search keywordType="taxonomic".EML Best Practices v.2, p. 25
11temporalCoveragePresent
info
 Type: metadata
 System: lter
 On Failure: info
temporalCoverage is presentCheck that temporalCoverage exists in EML at the dataset level, or at least one entity's level, or at least one attribute's level.temporalCoverage at least at the dataset level.1 'temporalCoverage' element(s) foundLTER wants to search datasets by time; the best place to search is the dataset level temporal coverage.Most datasets have a temporal range.EML Best Practices v.2, p. 24
12pastaDoiAbsent
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 presentReject the data package if it contains an alternateIdentifier DOI that looks like PASTA generated it.No PASTA DOIs are expected to be found in the uploaded data packageNo PASTA DOI alternateIdentifier elements foundPASTA DOI values might appear in an uploaded data package (by various mechanisms). PASTA will assign a DOI after the upload has completed successfully, so an initial one should not be there.
13titleLength
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 words10 words found.EML Best Practices, v.2, p. 13
14pubDatePresent
valid
 Type: metadata
 System: lter
 On Failure: warn
'pubDate' element is presentCheck for presence of the pubDate elementThe date that the dataset was submitted for publication in PASTA must be included. (The EML schema does not require this element, but when present, it does constrain its format to YYYY-MM-DD or just YYYY. Citation format uses only the YYYY portion even if a full date is entered.) 2017-12-26EML Best Practices v.2, p. 17
15datasetAbstractLength
valid
 Type: metadata
 System: lter
 On Failure: warn
Dataset abstract element is a minimum of 20 wordsCheck the length of a dataset abstract and warn if less than 20 words.An abstract is 20 words or more.56 words found.EML Best Practices
16duplicateEntityName
valid
 Type: metadata
 System: lter
 On Failure: error
There are no duplicate entity namesChecks that content is not duplicated by other entityName elements in the documententityName is not a duplicate within the documentNo duplicates foundData Manager requires a non-empty, non-duplicate entityName value for every entityDeclare a non-empty entityName and ensure that there are no duplicate entityName values in the document
Entity Report
Entity Name: VCR97018_1
Entity Identifier:
# Identifier Status Quality Check Name Description Expected Found Explanation Suggestion Reference
1entityNameLength
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 charactersentityName value is 100 characters or less10
2entityDescriptionPresent
valid
 Type: metadata
 System: lter
 On Failure: warn
An entity description is presentCheck for presence of an entity description.EML Best practices pp. 32-33, "...should have enough information for a user..."trueWith entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3numHeaderLinesPresent
info
 Type: metadata
 System: knb
 On Failure: info
'numHeaderLines' element is presentCheck for presence of the 'numHeaderLines' element.Document contains 'numHeaderLines' element.'numHeaderLines' element: 23
4numFooterLinesPresent
info
 Type: metadata
 System: knb
 On Failure: info
'numFooterLines' element is presentCheck for presence of the 'numFooterLines' element.Document contains 'numFooterLines' element.'numFooterLines' element: 0
5fieldDelimiterValid
valid
 Type: metadata
 System: knb
 On Failure: error
Field delimiter is a single characterField delimiters should be one character onlyA single character is expected,A valid fieldDelimiter value was foundhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6recordDelimiterPresent
valid
 Type: metadata
 System: knb
 On Failure: warn
Record delimiter is presentCheck presence of record delimiter. Check that the record delimiter is one of the suggested values.A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0A#x0AA valid recordDelimiter value was foundhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7numberOfRecordsPresence
warn
 Type: metadata
 System: knb
 On Failure: warn
Is the numberOfRecords element present?Warn the user if the numberOfRecords check is not presentA number of records element is expected for this entitynumberOfRecords element not foundThis is a valuable check that we have the correct table.Add a numberOfRecords element and store the number of entity records
8integrityChecksumPresence
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-1Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.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.
9attributeNamesUnique
valid
 Type: metadata
 System: knb
 On Failure: warn
Attribute names are uniqueChecks if attributeName values are unique in the table. Not required by EML.Unique attribute names.trueA good table does not have duplicate column names.EML Best Practices
10displayDownloadData
info
 Type: data
 System: knb
 On Failure: info
Display downloaded dataDisplay the first kilobyte of data that is downloadedUp to one kilobyte of data should be displayed #,"Porter, J.H., Krovetz,
11urlReturnsData
valid
 Type: congruency
 System: knb
 On Failure: error
URL returns dataChecks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.A data entity that matches the metadatatruehttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
12onlineURLs
valid
 Type: congruency
 System: knb
 On Failure: error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: http://www.vcrlter.virginia.edu/cgi-bin/fetchdataPASTA.cgi/1/VCR97018/whour_all_years.csv
13databaseTableCreated
valid
 Type: metadata
 System: knb
 On Failure: error
Database table createdStatus of creating a database tableA database table is expected to be generated from the EML attributes.A database table was generated from the attributes descriptionCREATE TABLE VCR97018_1("STATION" TEXT,"YEAR" INTEGER,"MONTH" INTEGER,"DAY" INTEGER,"TIME" INTEGER,"PPT" FLOAT,"AVG_T" FLOAT,"MIN_T" FLOAT,"MAX_T" FLOAT,"AVG_RH" FLOAT,"MIN_RH" FLOAT,"MAX_RH" FLOAT,"AVG_WS" FLOAT,"AVG_WANG" FLOAT,"STD_WANG" FLOAT,"RAD_SOL" FLOAT,"PAR" FLOAT,"SOIL_T" FLOAT);
14examineRecordDelimiter
valid
 Type: congruency
 System: knb
 On Failure: warn
Data are examined and possible record delimiters are displayedIf no record delimiter was specified, we assume that \r\n is the delimiter. Search the first row for other record delimiters and see if other delimiters are found.No other potential record delimiters expected in the first row.No other potential record delimiters were detected. A valid record delimiter was previously detectedhttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
15displayFirstInsertRow
info
 Type: data
 System: knb
 On Failure: info
Display first insert rowDisplay the first row of data values to be inserted into the database tableThe first row of data values should be displayedBRNV, ., ., ., ., 0, ., 0, ., 100, 0, 0, 0.000, 0, 0, ., 0, .
16dataLoadStatus
warn
 Type: congruency
 System: knb
 On Failure: warn
Data can be loaded into the databaseStatus of loading the data table into a databaseNo errors expected during data loading or data loading was not attempted for this data entityError inserting data at row 1.Data value '.' is NOT the expected data type of 'INTEGER'
17onlineURLs
valid
 Type: congruency
 System: knb
 On Failure: error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: file:///pasta/data1/knb-lter-vcr.25.35/32a020479d23312012444a5b4ff81658
Entity Report
Entity Name: VCR_LTER_Hourly_Weather.zip
Entity Identifier:
# Identifier Status Quality Check Name Description Expected Found Explanation Suggestion Reference
1entityNameLength
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 charactersentityName value is 100 characters or less27
2entityDescriptionPresent
valid
 Type: metadata
 System: lter
 On Failure: warn
An entity description is presentCheck for presence of an entity description.EML Best practices pp. 32-33, "...should have enough information for a user..."trueWith entityName sometimes serving as a file name rather than a title, it is important to be very descriptive here.
3numHeaderLinesPresent
info
 Type: metadata
 System: knb
 On Failure: info
'numHeaderLines' element is presentCheck for presence of the 'numHeaderLines' element.Document contains 'numHeaderLines' element.No 'numHeaderLines' element foundIf data file contains header lines, 'numHeaderLines' must be specified.Add 'numHeaderLines' element if needed.
4numFooterLinesPresent
info
 Type: metadata
 System: knb
 On Failure: info
'numFooterLines' element is presentCheck for presence of the 'numFooterLines' element.Document contains 'numFooterLines' element.No 'numFooterLines' element foundIf data file contains footer lines, 'numFooterLines' must be specified.Add 'numFooterLines' element if needed.
5fieldDelimiterValid
info
 Type: metadata
 System: knb
 On Failure: error
Field delimiter is a single characterField delimiters should be one character onlyA single character is expectednullA fieldDelimiter value is not checked for binary entities or entities with an externally defined formathttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#fieldDelimiter
6recordDelimiterPresent
info
 Type: metadata
 System: knb
 On Failure: warn
Record delimiter is presentCheck presence of record delimiter. Check that the record delimiter is one of the suggested values.A record delimiter from a list of suggested values: \n, \r, \r\n, #x0A, #x0D, #x0D#x0AnullA recordDelimiter value is not checked for binary entities or entities with an externally defined formathttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-physical.html#recordDelimiter
7integrityChecksumPresence
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-1Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.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.
8displayDownloadData
info
 Type: data
 System: knb
 On Failure: info
Display downloaded dataDisplay the first kilobyte of data that is downloadedUp to one kilobyte of data should be displayed*** BINARY DATA ***
9urlReturnsData
valid
 Type: congruency
 System: knb
 On Failure: error
URL returns dataChecks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.A data entity that matches the metadatatruehttp://knb.ecoinformatics.org/software/eml/eml-2.1.0/eml-resource.html#UrlType
10onlineURLs
valid
 Type: congruency
 System: knb
 On Failure: error
Online URLs are liveCheck that online URLs return somethingtruetrueSucceeded in accessing URL: http://www.vcrlter.virginia.edu/cgi-bin/fetchdataPASTA.cgi/2/VCR97018/VCR_LTER_Hourly_Weather.zip