2018 CEDEN Template Modification Requests
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
$
%
123
 
 
 
 
 
 
 
 
 
 
 
 
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
CEDEN Template Modification Requests
2
Please add comments (in support or in opposition to the change) in columns to the right. One commenter per cell. For example, if one person agrees that the appropriate CodeListName should be added, the first comment of support should be typed in cell E19. If another person also supports that change, the second commenter should type is cell F19.
3
4
5
Request No.
ItemChangeChange JustificationComment 1Comment 2Comment 3
6
1Notes_Information > Section on Grey with blue boldRemoveAs the station tab isn't in the data entry templates, this coding shouldn't be included for simplicity.agree
7
2Notes_Information > NewAdd link to the CV request template/link about CV requestshttp://www.ceden.org/vocabulary_request.shtmlagree
8
3All Templates > Locations > StationDetailVerByRemove or RenameNot StationDetailThis comment applies to rows 8-19. The Locations tab contains a mixture of StationDetail and Geometry information. The proposed changes will orient the template to the Geometry table. This will require all data checkers, loaders, and documentation to be updated. May want to consider waiting until CEDEN 2.0
9
4All Templates > Locations > StationDetailVerDateRemove or RenameNot StationDetail
10
5All Templates > Locations > StationDetailCommentsRemove or RenameNot StationDetail
11
6All Templates > Locations > VerificationByAdd or RenameIn DB, missing from template
12
7All Templates > Locations > VerificationDateAdd or RenameIn DB, missing from template
13
8All Templates > Locations > GeometryCommentsAdd or RenameIn DB, missing from template
14
9All Templates > Locations > ReconVerModeAddIn DB, missing from template
15
10All Templates > Locations > GPSFixAddIn DB, missing from template
16
11All Templates > Locations > GPSDeviceNameAddIn DB, missing from template. Data providers have indicated that they would like to provide it.
17
12All Templates > Locations > GPSAccuracyAddIn DB, missing from template
18
13All Templates > Locations > UnitGPSAccuracyAddIn DB, missing from template
19
14All Templates > Locations > Within10SecondsOfMapAddIn DB, missing from template
20
15Guidance > VariableCodesLookupAdd the appropriate CodeListNameagree
21
16Chemistry > ChemResults (Blank) > First two rows of Blank TemplateFixFirst two rows are formatted like header (bold/vertical) which can lead to incorrect formats, an inconvenience for the provider, and/or inaccurate results in checks.agree
22
17Chemistry > ChemResults (Blank) > AnalysisDateChange formatting to match example templateShows providers it is date + time field (likely fixed with change to first two rows)agree
23
18Chemistry > ChemResults (Blank) > PrepPreservationDateChange formatting to match example templateShows providers it is date + time field (likely fixed with change to first two rows)agree
24
19Chemistry > ChemResults (Blank) > DigestExtractDateChange formatting to match example templateShows providers it is date + time field, I think you could just take one row from the example template and paste formatting for the first bit of the blank template?agree
25
20Tissue > *Composite > SampleIDMove to the POE sectionIt's currently out of place and is leading providers to either not complete it or put in the wrong level of identifier. It is before TissueCollectionComments.agree
26
21Tissue > *Composite > LabReceiveDateReinstate this fieldIn DB, missing from templateThis change will require all data checkers, loaders, and documentation to be updated. Not sure it is worth the effort for the information contained. They are not required fields and the information does not affect the data quality.
27
22Tissue > *Composite > ReceivedByReinstate this fieldIn DB, missing from templateThis change will require all data checkers, loaders, and documentation to be updated. Not sure it is worth the effort for the information contained. They are not required fields and the information does not affect the data quality.
28
23Toxicity > ToxSummaryResults > ToxTestCommentsMoveCurrently out of place. It comes before the treatment information, which is part of ToxTestagree
29
24Toxicity > ToxSummaryResults > TIENarrativeMoveCurrently out of place. Belongs with ToxTest fields.agree
30
25Toxicity > ToxSummaryResults > TestQACodeMoveCurrently out of place. It belongs much earlier. Implies that different QACode values can be assigned to different endpoints, which is not true (for Summary). As is, it confuses users because it is out of place (it implies that that the code applies to end point, not entire test).agree
31
26Toxicity > ToxSummaryResults > ComplianceCodeMoveCurrently out of place. It belongs much earlier. Implies that different ComplianceCode values can be assigned to different endpoints, which is not true (for Summary). As is, it confuses users because it is out of place (it implies that that the code applies to end point, not entire test).agree
32
27Toxicity > ToxSummaryResults > ToxPointCommentsAddIn DB, missing from template, belongs around column AMProbably left out because so many tables with Comments fields that it was thought users would be confused which may lead to comments being populated at the inappropriate level: toxtest, ToxSumm, Toxreplicate etc
33
28Toxicity > Both > TestDurationChange to TestDurationCodeCurrent column name leaves abiguity between Name/CodeAgree,but should be changed to ToxTestDurCode to match the actual DB table name in ToxTestDurLookUp. All data checkers, loaders, and documentation will need to be updated.
34
29Toxicity > Both > TimePointChate to TimePointName/CodeCurrent column name leaves abiguity between Name/Code, guidance doesn't clarifyAgree with TimePointCode. All data checkers, loaders, and documentation will need to be updated.
35
30Toxicity > ToxReplicateResults > ToxTestCommentsMoveCurrently out of place. It comes before the treatment information, which is part of ToxTestagree
36
31Field > FieldResults > CollectionDeviceNameMoveCurrently out of place. Belongs with the FieldResult fields, is currently with the FieldCollection fields.makes senseagree
37
32Field > HabitatResults > CollectionDeviceNameMoveCurrently out of place. Belongs with the HabitatResult fields, is currently with the HabitatCollection fields.Makes senseagree
38
33Chem Checker > Duplicate entry in Results worksheet. The combination of columns A-C, F,H,J-M,O and U-Z must be unique for environmental samples within worksheet.Add Column N (CollectionDeviceName) to this checkCollectionDeviceName is part of the primary key, the check is incorrect. EventCode and ProtocolCode should be added as well.Agree. All data checkers will need to be updated.
39
34Chem Checker > LabBatch with multiple AnalysisDatesEither only check on a conversion of values to Date only, or RemoveAnalysisDate is a Date + Time field. We want to allow AnalysisDate to be different if labs are accurately reporting their results. Checker should only check for the same date, not including time so that this error isn't encountered as often. As is, providers are encouraged to strip out the time component so this warning isn't received.This check should be a warning - stripping out the time may lead to incorrect analysis dates/times being missed. Recommend leaving check and making it a warning in which case data providers can still submit the file
40
35Chem Checker > Missing BatchVerificationCode, a required field.Switch to warning, change messageOnly required for upload. A QA Officer for the project should be assigning this, not labs. This error leads to confusion if additional verfication is going to occur after submittal.SInce this field is required it must be populate with a default of NR - cannot change to a warning.
41
36Chem Checker > Missing Replicate, a required field.Fix template formatting or fix the checkerThe example records are formatted as numbers, but the rows below are formatted as text. If there is a combination, the text values are not recognized.Replicate should be formatted as a number (integer) in the template to match the DB requirement.
42
37Chem Checker > Missing MDL, a required field.Fix template formatting or fix the checkerThe example records are formatted as numbers, but the rows below are formatted as text. If there is a combination, the text values are not recognized.Would like to see text formatting recognizedMDL is a text field in the DB so the template format should be text.
43
38Chem Checker > Missing RL, a required field.Fix template formatting or fix the checkerThe example records are formatted as numbers, but the rows below are formatted as text. If there is a combination, the text values are not recognized.Would like to see text formatting recognizedRL is a text field in the DB so the template format should be text.
44
39Chem Checker > Missing CollectionDepth, a required field.Fix template formatting or fix the checkerThe example records are formatted as numbers, but the rows below are formatted as text. If there is a combination, the text values are not recognized.Would like to see text formatting recognizedCollectionDepth is a number field in the DB so the template should be a number field.
45
40Chem Checker >Did not expect LabReplicate to be 2.RemoveI think this is based off of SampleID. This shouldn't be a check. A lab replicate of a sample shouldn't have a different SampleID.This error isn't necessarily caused by SampleID issues. The point is correct, but the circumstances are more complicated.This check (CEDEN_C_239) is not based off SampleID or LabSampleID. It occurs when there is a LabReplicate of 2 with no associated original sample (LabReplicate = 1) based on Unique Constraint fields.
46
41TaxonomyAdd "Taxonomic authority"To allow harmonizing of the taxonomy as names change throughout time.Disagree. This field does not exist in the BenthicResults table. TaxonomicAuthority is in the OrganismLookUp table.
47
42TaxonomyAdd "ID Source"To allow harmonizing of the taxonomy as names change throughout time.Disagree. The Source field in the OrganismLookUp table identifies the agency that supplied the FinalID to the table.
48
43ChemistryAdd Percent RecoveryAdd Percent Recovery and require it through the checker for all MS, MSD, LCS, LCSD, CRM, CRMD sample types so that this value can be easily identified and used as a number, instead of trying to extract it from a comment field (LabResultsComments).I agree/support this changeAll data checkers, loaders, and documentation will need to be updated. All current CEDEN and SWAMP data will need to be updated to populate the fields accordingly. It is unclear if the commenter wants only the checker to make the field required or if the DB field should be required as well. If the latter, there will need to be a default value for non-QA samples. Suggest waiting till CEDEN 2.0Response to previous comment: Yes, it would require this retooling, but it seems worth it. As a default value for non-QA samples, -88 would work.
There are other calculated values - %D and RSD where would these be stored?
49
44ChemistryAdd Relative Percent DifferenceAdd Percent Recovery and require it through the checker for all MSD, LCSD, CRMD, and lab duplicate sample types so that this value can be easily identified and used as a number, instead of trying to extract it from a comment field (LabResultsComments).I agree/support this change, but would be okay if PR and RPD remained in the same column. I.e., one new column instead of two new columnsUsing two columns would make it text, which defeats the whole purpose of the suggestion.All data checkers, loaders, and documentation will need to be updated. All current CEDEN and SWAMP data will need to be updated to populate the fields accordingly. It is unclear if the commenter wants only the checker to make the field required or if the DB field should be required as well. If the latter, there will need to be a default value for non-QA samples. Suggest waiting till CEDEN 2.0Response to previous comment: Yes, it would require this retooling, but it seems worth it. As a default value for non-QA samples, -88 would work.
There are other calculated values - %D and RSD where would these be stored?
50
45ChemistryAdd an optional column for “EventType” or “WeatherCondition”Add an optional column for “EventType” or “WeatherCondition”, which will be used to indicate if the result of that row is for wet or dry condition. This column will help to distinguish between the data as related to wet or dry events. Column AP in the “ChemResults” tab could be used for this purpose. This addition is needed for completeness of the data especially for stormwater programs.ProjectCode can be used to distinguish 'wet' or 'dry' sampling events in a given year without requiring a design change and all associated updates for such a limited use case. A HabitatResult can also be used if one wants to link specific collections to a weather event/condition. Group sample was designed for this purpose but CEDEN does not use it to the extent it was intended for
51
46FieldAdd an optional column for “EventType” or “WeatherCondition”Add an optional column for EventType or WeatherCondition, which will be used to indicate if the result of that row is for wet or dry condition. This column will help to distinguish between the data as related to wet or dry events. Column AE in the “FieldResults” tab and column AA in the “HabitatResults” tab could be used for this purpose. This addition is needed for completeness of the data especially for stormwater programs.ProjectCode can be used to distinguish 'wet' or 'dry' sampling events in a given year without requiring a design change and all associated updates for such a limited use case. A HabitatResult can also be used if one wants to link specific collections to a weather event/condition.
52
47FieldAdd a required SampleID columnAdd a required SampleID column to link field data to chemistry and other data, if applicable, when sample collection and field measurements occur at the same site and time. Column AF in the FieldResults tab and column AB in the HabitatResults tab could be used for this purpose. The addition of a SampleID column is essential to link the field observation and data collection to other data, such as chemistry data, because field observation and sample collection are conducted concurrently for most monitoring programs.All data are linked by the Sample and Location unique constraint fields within these tables matching. Fields in the Collection tables (e.g., CollectionTime) can also be used to link data. SampleID is not required in other tables and is not necessary to add here.
53
48TaxonomyAdd an optional column for “EventType” or “WeatherCondition”Add an optional column for EventType or WeatherCondition, which will be used to indicate if the result of that row is for wet or dry condition. This column will help to distinguish between the data as related to wet or dry events. Column BC in the “BenthicResults” tab could be used for this purpose. The addition of an EventType column is needed for completeness of the data especially for stormwater programs.ProjectCode can be used to distinguish 'wet' or 'dry' sampling events in a given year without requiring a design change and all associated updates for such a limited use case. A HabitatResult can also be used if one wants to link specific collections to a weather event/condition. Group sample was designed for this purpose but CEDEN does not use it to the extent it was intended for
54
49TissueAdd a required SampleID column to “TISuperComposite” and “TIResults” tabs.Column M in TISuperComposite tab and column AC in TIResults tab could be used for this purpose. Currently, only the FishComposite and BivalveComposite tabs contain SampleID. There is no consistent identifier between all the tissue data tabs. The addition of a SampleID column provides an ID for each dataset and could be linked to other datasets.The consistent identifier is CompositeID which is on all the tabs; Supercomposite is a special circumstance where the actual link occurs in CompositeSourceID
55
50ToxicityAdd an optional column for EventType or WeatherCondition.This field will be used to indicate if the result of that row is for wet or dry condition. This column will help to distinguish between the data as related to wet or dry events. Column BD in the “ToxSummaryResults” tab and column AT in the ToxReplicateResults tab could be used for this purpose. The addition of an EventType column is needed for completeness of the data especially for stormwater programs.ProjectCode can be used to distinguish 'wet' or 'dry' sampling events in a given year without requiring a design change and all associated updates for such a limited use case. A HabitatResult can also be used if one wants to link specific collections to a weather event/condition. Group sample was designed for this purpose but CEDEN does not use it to the extent it was intended for
56
51BioassessmentAdd an optional column for EventType or WeatherCondition.This field will be used to indicate if the result of that row is for wet or dry condition. This column will help to distinguish between the data as related to wet or dry events. Column Hin the “Sample” tab, columnKin the “SampleHistory” tab, columnAEin theFieldResultstab, columnAAin theHabitatResultstab, columnBCin theBenthicResultstab, and columnAPin theChemResultstab could be used for this purpose.ProjectCode can be used to distinguish 'wet' or 'dry' sampling events in a given year without requiring a design change and all associated updates for such a limited use case. A HabitatResult can also be used if one wants to link specific collections to a weather event/condition. Group sample was designed for this purpose but CEDEN does not use it to the extent it was intended for
57
52BioassessmentAdd a required SampleID column to Sample, SampleHistory, FieldResults, and HabitatResults tabs.Column I in the Sample tab, column L in the SampleHistory tab, column AF in the FieldResults tab, and column AB in the HabitatResults tab could be used for this purpose. The addition of a SampleID column provides an ID for each dataset and could be linked to other datasets.All data are linked by the Sample and Location unique constraint fields within these tables matching. Fields in the Collection tables (e.g., CollectionTime) can also be used to link data. SampleID is not required in other tables and is not necessary to add here.
58
53ToxicityRequire both Percent Effect and Percent ControlThe sum of these two fields should equal 100. The inclusion of these fields will also overcome situations where a “-88” qualifier can get confused with an actual percent effect.disagree; I think we were advocating for PercentEffect to be required (is currently in the template) at the point of transition. We have always maintained that we should not have two fields reported that mean the same thing in case one produces an error but instead provide both in the export as a calculated field
59
54ToxicityRequire p Value or statistical resultsIt is needed to allow end users to check fhe integrity of the data.p value is not a field in the database. The fields CalValueType and CalculatedValue are used together to store this information.
60
55ToxicityRequire QA Control IDThis is the Lab ID for the Control sample used to calculate the test statistics. It is needed to allow end users to check fhe integrity of the data.agree
61
56ToxicityRequire QA Control MeanThis is the mean for the Control sample used to calculate the test statistics. It is needed to allow end users to check the integrity of the data.This information is being stored in the "MEAN" field which is required.There is no way to control whether a lab is going to report the labcontrol means as records in the summary tab of the template which is linked by QAControlID. Adding a new field QAControlMean would require a design change. Consider writing a check for it or wait until CEDEN 2.0
62
57ToxicityRequire QA CommentsIt is needed to allow end users to check the integrity of the data.this does not make sense to require or add a QAcomment field - there are other fields that are used to check data integrity.
63
58AllRemove SCCWRP and confirm correct linksIncreases the user-friendliness of templatesagree
64
59Vocab Request Template > ProgramNameAdd character limit in header commentIncreases the user-friendliness of templatesagree
65
60Vocab Request Template > ProjectNameAdd character limit in header commentIncreases the user-friendliness of templatesagree
66
61Vocab Request Template > ParentProjectNameAdd character limit in header commentIncreases the user-friendliness of templatesagree
67
62Vocab Request Template > StationNameAdd character limit in header commentIncreases the user-friendliness of templatesagree
68
63Vocab Request Template > ProtocolNameAdd character limit in header commentIncreases the user-friendliness of templatesagree
69
64Vocab Request Template > StationsOrder columns so required fields are togetherSometime waterbody type is not completed so the record can't be loaded and/or an additional back and forth is needed with the provideragree
70
65Vocab Request Template > FieldResEquipRemove notesDoesn't apply to CEDENagree
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...
 
 
 
Make Comments
Reference
 
 
Main menu