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.960.2
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
17 '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
11 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 1926050
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.
220 words found.
EML Best Practices
16
duplicateEntityName
valid
Type:
metadata
System:
lter
On failure:
error
There are no duplicate entity names
Checks that content is not duplicated by other entityName elements in the document
entityName is not a duplicate within the document
No duplicates found
Data Manager requires a non-empty, non-duplicate entityName value for every entity
Declare a non-empty entityName and ensure that there are no duplicate entityName values in the document
Warn the user if the numberOfRecords check is not present
A number of records element is expected for this entity
numberOfRecords element found
This is a valuable check that we have the correct table.
8
entitySizePresence
valid
Type:
metadata
System:
knb
On failure:
warn
Check for presence of an entity size element
Look for entity size element as a prep for checking congruence, and if not present, generate a warn. Note that to be most useful (i.e, to check congruence), entity size should contain the most precise measure of size, which is "byte" (the default unit); however, the presence or name of the entity size unit is NOT checked.
Entity size is present. If unit="byte" or unit is omitted (default = byte), then congruence can be checked.
Found entity size element with value of 3758658 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.
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
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.
'MMM DD-DD YYYY' 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
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.
'MMM DD' 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
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
13
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.
'MMM YYYY' 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
14
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.
'yyyy-mm-dd' is not in the set of preferred values.
The format string 'yyyy-mm-dd' differs only by case with preferred format string 'YYYY-MM-DD'.
Use 'YYYY-MM-DD' in place of 'yyyy-mm-dd'.
15
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
16
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
"Publication Type","Authors","Book Authors","Book Editors","Book Group Authors","Author Full Names","Book Author Full Names","Group Authors","Article Title","Source Title","Book Series Title","Book Series Subtitle","Language","Document Type","Conference Title","Conference Date","Conference Location","Conference Sponsor","Conference Host","Author Keywords","Keywords Plus","Abstract","Addresses","Affiliations","Reprint Addresses","Email Addresses","Researcher Ids","ORCIDs","Funding Orgs","Funding Text","Cited Reference Count","Times Cited, WoS Core","Times Cited, All Databases","180 Day Usage Count","Since 2013 Usage Count","Publisher","Publisher City","Publisher Address","ISSN","eISSN","ISBN","Journal Abbreviation","Journal ISO Abbreviation","Publication Date","Publication Year","Volume","Issue","Part Number","Supplement","Special Issue","Start Page","End Page","Article Number","DOI","Book DOI","Early Access Date","Number of Pages","WoS Categories","Web of Science Index","Research Areas","IDS Number","UT (Uniq
17
urlReturnsData
valid
Type:
congruency
System:
knb
On failure:
error
URL returns data
Checks whether a URL returns data. Unless the URL is specified to be function="information", the URL should return the resource for download.
Succeeded in accessing URL: https://portal-s.edirepository.org/nis/data/melofton-upload-2022-12-16-1671227556781/freshwater-forecasting-review-results.csv
19
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.
0a857e12c2742019aa4e8b3ddfa48bf9
0a857e12c2742019aa4e8b3ddfa48bf9
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.
20
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.
3758658
3758658
Examining the entity size is a method for checking that this is the correct entity.
Check the entity size.
21
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
Found for displayFirstInsertRow check
J, Dippold, DA; Aloysius, NR; Keitzer, SC; Yen, H; Arnold, JG; Daggupati, P; Fraker, ME; Martin, JF; Robertson, DM; Sowa, SP; Johnson, MVV; White, MJ; Ludsin, SA, NA, NA, NA, Dippold, David A.; Aloysius, Noel R.; Keitzer, Steven Conor; Yen, Haw; Arnold, Jeffrey G.; Daggupati, Prasad; Fraker, Michael E.; Martin, Jay F.; Robertson, Dale M.; Sowa, Scott P.; Johnson, Mari-Vaughn V.; White, Mike J.; Ludsin, Stuart A., NA, NA, Forecasting the combined effects of anticipated climate change and agricultural conservation practices on fish recruitment dynamics in Lake Erie, FRESHWATER BIOLOGY, NA, NA, English, Article, NA, NA, NA, NA, NA, climate warming; eutrophication; fisheries management; multiple stressors; percid, STIZOSTEDION-VITREUM-VITREUM; LAURENTIAN GREAT-LAKES; PERCH PERCA-FLAVESCENS; FRESH-WATER FISHES; EASTERN BERING-SEA; YELLOW PERCH; WHITE PERCH; RE-EUTROPHICATION; MORONE-AMERICANA; ENVIRONMENTAL-FACTORS, Many aquatic ecosystems are experiencing multiple anthropogenic stressors that threaten their ability to support ecologically and economically important fish species. Two of the most ubiquitous stressors are climate change and non-point source nutrient pollution. Agricultural conservation practices (ACPs, i.e. farming practices that reduce runoff, prevent erosion, and curb excessive nutrient loading) offer a potential means to mitigate the negative effects of non-point source pollution on fish populations. However, our understanding of how ACP implementation amidst a changing climate will affect fish production in large ecosystems that receive substantial upstream sediment and nutrient inputs remains incomplete. Towards this end, we explored how anticipated climate change and the implementation of realistic ACPs might alter the recruitment dynamics of three fish populations (native walleye Sander vitreus and yellow perch Perca flavescens and invasive white perch Morone americana) in the highly productive, dynamic west basin of Lake Erie. We projected future (2020-2065) recruitment under different combinations of anticipated climate change (n = 2 levels) and ACP implementation (n = 4 levels) in the western Lake Erie catchment using predictive biological models driven by forecasted winter severity, spring warming rate, and Maumee River total phosphorus loads that were generated from linked climate, catchment-hydrology, and agricultural-practice-simulation models. In general, our models projected reduced walleye and yellow perch recruitment whereas invasive white perch recruitment was projected to remain stable or increase relative to the recent past. Our modelling also suggests the potential for trade-offs, as ACP implementation was projected to reduce yellow perch recruitment with anticipated climate change. Overall, our study presents a useful modelling framework to forecast fish recruitment in Lake Erie and elsewhere, as well as offering projections and new avenues of research that could help resource management agencies and policy-makers develop adaptive and resilient management strategies in the face of anticipated climate and land-management change., [Dippold, David A.; Aloysius, Noel R.; Fraker, Michael E.; Ludsin, Stuart A.] Ohio State Univ, Aquat Ecol Lab, Dept Evolut Ecol & Organismal Biol, Columbus, OH 43210 USA; [Aloysius, Noel R.; Martin, Jay F.] Ohio State Univ, Dept Food Agr & Biol Engn, Columbus, OH 43210 USA; [Keitzer, Steven Conor] Tusculum Univ, Dept Nat Sci, Tusculum, TN USA; [Yen, Haw; Daggupati, Prasad] Texas A&M Univ, Blackland Res & Extens Ctr, College Stn, TX USA; [Arnold, Jeffrey G.; White, Mike J.] Agr Res Ctr, USDA, Temple, TX USA; [Robertson, Dale M.] US Geol Survey, Upper Midwest Water Sci Ctr, Middleton, WI USA; [Sowa, Scott P.] Michigan Field Off, Nat Conservancy, Lansing, MI USA; [Johnson, Mari-Vaughn V.] USDA, Resource Assessment Div, Nat Resources Conservat Serv, Temple, TX USA; [Aloysius, Noel R.] Univ Missouri, Coll Agr Food & Nat Resources, Columbia, MO USA; [Daggupati, Prasad] Univ Guelph, Sch Engn, Guelph, ON, Canada, NA, Ludsin, SA (corresponding author), Ohio State Univ, Aquat Ecol Lab, Dept Evolut Ecol & Organismal Biol, Columbus, OH 43210 USA., ludsin.1@osu.edu, Robertson, Dale/O-1913-2018, Robertson, Dale/0000-0001-6799-0596; Yen, Haw/0000-0002-5509-8792; Aloysius, Noel/0000-0002-9094-427X; Keitzer, Steven/0000-0002-8164-4099; Fraker, Michael/0000-0002-1813-706X; Sowa, Scott/0000-0002-5425-2591; Martin, Jay/0000-0002-1599-5931, Ohio State UniversityOhio State University; United States Department of Agriculture Conservation Effects Assessment Project [GRT00031346]; Great Lakes Fishery Commission [2016_LUD_44056]; Nature Conservancy [GRT00042416]; National Science Foundation Coupled Human and Natural Systems [GRT00022685], The Ohio State University; United States Department of Agriculture Conservation Effects Assessment Project, Grant/Award Number: GRT00031346; Great Lakes Fishery Commission, Grant/Award Number: 2016_LUD_44056; Nature Conservancy, Grant/Award Number: GRT00042416; National Science Foundation Coupled Human and Natural Systems, Grant/Award Number: GRT00022685, 140, 9, 9, 3, 33, WILEY, HOBOKEN, 111 RIVER ST, HOBOKEN 07030-5774, NJ USA, 0046-5070, 1365-2427, NA, FRESHWATER BIOL, Freshw. Biol., SEP, 2020, 65, 9, NA, NA, NA, 1487, 1508, NA, 10.1111/fwb.13515, NA, MAY 2020, 22, Ecology; Marine & Freshwater Biology, Science Citation Index Expanded (SCI-EXPANDED), Environmental Sciences & Ecology; Marine & Freshwater Biology, NB0DE, WOS:000531852000001, NA, hybrid, 2022-02-17, 1, y, yes; surface water, forecast, yes, no, process-based, no, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA, NA
24
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.
For attribute name "min_horizon_days", data value NA is not the expected data type of 'FLOAT': For input string: "NA"
25
headerRowAttributeNames
info
Type:
congruency
System:
lter
On failure:
info
Header row is displayed alongside attribute names
Compare the content of the data header row to the content of EML attribute names.
No expectation, information only
Found for headerRowAttributeNames check
*** HEADER ROWS ***
"Publication Type","Authors","Book Authors","Book Editors","Book Group Authors","Author Full Names","Book Author Full Names","Group Authors","Article Title","Source Title","Book Series Title","Book Series Subtitle","Language","Document Type","Conference Title","Conference Date","Conference Location","Conference Sponsor","Conference Host","Author Keywords","Keywords Plus","Abstract","Addresses","Affiliations","Reprint Addresses","Email Addresses","Researcher Ids","ORCIDs","Funding Orgs","Funding Text","Cited Reference Count","Times Cited, WoS Core","Times Cited, All Databases","180 Day Usage Count","Since 2013 Usage Count","Publisher","Publisher City","Publisher Address","ISSN","eISSN","ISBN","Journal Abbreviation","Journal ISO Abbreviation","Publication Date","Publication Year","Volume","Issue","Part Number","Supplement","Special Issue","Start Page","End Page","Article Number","DOI","Book DOI","Early Access Date","Number of Pages","WoS Categories","Web of Science Index","Research Areas","IDS Number","UT (Unique WOS ID)","Pubmed Id","Open Access Designations","Date of Export","result_num","title_screen","freshwater","forecast","uncertainty_present","nearterm","model_approach","hydrological","ecosystem","other_ecosystem","phys_chem_bio","forecast_vars","min_horizon_days","max_horizon_days","skill_metrics","model_comparison","simple_null_model","uncertainty_method","iterative","automated","archived","motivation","end_user","engagement"
*** ATTRIBUTE LIST ***
Publication Type,Authors,Book Authors,Book Editors,Book Group Authors,Author Full Names,Book Author Full Names,Group Authors,Article Title,Source Title,Book Series Title,Book Series Subtitle,Language,Document Type,Conference Title,Conference Date,Conference Location,Conference Sponsor,Conference Host,Author Keywords,Keywords Plus,Abstract,Addresses,Affiliations,Reprint Addresses,Email Addresses,Researcher Ids,ORCIDs,Funding Orgs,Funding Text,Cited Reference Count,Times Cited, WoS Core,Times Cited, All Databases,180 Day Usage Count,Since 2013 Usage Count,Publisher,Publisher City,Publisher Address,ISSN,eISSN,ISBN,Journal Abbreviation,Journal ISO Abbreviation,Publication Date,Publication Year,Volume,Issue,Part Number,Supplement,Special Issue,Start Page,End Page,Article Number,DOI,Book DOI,Early Access Date,Number of Pages,WoS Categories,Web of Science Index,Research Areas,IDS Number,UT (Unique WOS ID),Pubmed Id,Open Access Designations,Date of Export,result_num,title_screen,freshwater,forecast,uncertainty_present,nearterm,model_approach,hydrological,ecosystem,other_ecosystem,phys_chem_bio,forecast_vars,min_horizon_days,max_horizon_days,skill_metrics,model_comparison,simple_null_model,uncertainty_method,iterative,automated,archived,motivation,end_user,engagement
Customer should evaluate the findings
26
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.
'MMM DD-DD YYYY' 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.
27
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.960.2/3bdc7201f46157a0d6db5f0a9a8330cc
Entity Report
Entity Name:
Fig4_data.csv
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
13
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 10815 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.
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
"result_number","article_title","target_variables","title_screen"
1,"Forecasting the combined effects of anticipated climate change and agricultural conservation practices on fish recruitment dynamics in Lake Erie","fish","y"
2,"Projecting the effects of agricultural conservation practices on stream fish communities in a changing climate","fish","y"
4,"Comparing models using air and water temperature to forecast an aquatic invasive species response to climate change","zooplankton","y"
6,"A meta-modeling approach for hydrological forecasting under uncertainty: Application to groundwater nitrate response to climate change","nutrients","y"
8,"Forecasting water temperature in lakes and reservoirs using seasonal climate prediction","temperature","y"
17,"Predicting Lake Quality for the Next Generation: Impacts of Catchment Management and Climatic Factors in a Probabilistic Model Framework","phytoplankton,index","y"
20,NA,"amphibians",NA
21,"Short-term forecasting of cyanobacteria blooms in Yuqiao reservoir, China",
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://portal-s.edirepository.org/nis/data/melofton-upload-2022-12-16-1671227556781/Fig4_data.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.
e31e2fa0b317bc939c33def2213c1754
e31e2fa0b317bc939c33def2213c1754
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.
10815
10815
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
Display the first row of data values to be inserted into the database table
The first row of data values should be displayed
1, Forecasting the combined effects of anticipated climate change and agricultural conservation practices on fish recruitment dynamics in Lake Erie, fish, y
19
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.960.2/9cf7d6f16d5714f9252829717648bfd3
20
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
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 8197 and size unit specified as 'bytes'. Please note that a size element specified with a unit other than 'byte' will not be tested for congruence.
Examining the entity size is prep for checking congruence. Including the element is best practice, and if not present, a warn is generated. To be most useful, entity size should contain the most precise measure of size, which is "byte" (the default unit).
Include an entity size in bytes
Example success: knb-lter-sbc.3.12. Example of size in units other than byte: knb-lter-mcr.6.56.
8
integrityChecksumPresence
valid
Type:
metadata
System:
lter
On failure:
warn
A physical/authentication element is present and specifies a method attribute with a value of MD5 or SHA-1
Check for presence of a physical/authentication element containing a checksum or hash value for an integrity check (e.g. MD5, SHA-1). Warn if an entity does not have a physical/authentication element, or if none of the physical/authentication elements specify a method attribute with a value of MD5 or SHA-1.
At least one physical/authentication element with a method attribute specifying MD5 or SHA-1 and containing a checksum or hash value that can be used to perform an integrity check on the data.
true
PASTA will use this value to check the integrity of the data it downloads from your site. In addition, PASTA is planning to compare the contributor-supplied checksum/hash value documented
in the physical/authentication element to the checksum/hash value of this entity downloaded from previous revisions of this data package. If PASTA already has a copy of this entity, it will be able
to avoid an unnecessary download of the entity from your site, resulting in faster processing of the new data package revision when you update it in PASTA.
Add a physical/authentication element and store the entity checksum or hash value in it using a method such as MD5 or SHA-1.
9
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
10
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://portal-s.edirepository.org/nis/data/melofton-upload-2022-12-16-1671227556781/EDI_data_QAQC_and_formatting.R
12
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.
75c303dc42a68e084ee7f4b556a2ac6f
75c303dc42a68e084ee7f4b556a2ac6f
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.
13
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.
8197
8197
Examining the entity size is a method for checking that this is the correct entity.