[Esip-preserve] Provenance and Context Content Spreadsheet

[Siri Jodha Khalsa]

Rama and John,

Good work.  Some questions and comments:
1. I didn't see a mention of the data and metadata itself.  This archive 
package would be separate from the data?  The division between 
documentation and metadata is blurred, of course, e.g. production 
history is included in the table, but is in some cases saved as 
metadata. Some QA is metadata, some is in the product files. The spec 
needs to address how data and metadata are preserved.
2. Normalization of the entries is needed - there's lots of 
duplication/overlap, and some similar or identical items appear under 
different categories
3. Some descriptions refer to "project artifacts" - the reference should 
be to specific items in the table. Likewise, what are "developer's 
design documents"?
4. There needs to be a separate column for "alternate" sources for an 
item, rather than using the rationale column, which should eventually be 
populated for each item.
5.  Aren't items that refer to accessing the data, like NOAA item 36, 
irrelevant? The physical location of the data may change.
6. Error analysis under documentation belongs under Quality (and I think 
QA is too narrow of a term.  Should be just quality or quality 
measures). Validation belongs under Quality also, don't you think?
7. Why source code only for higher-level products?  Why not all source 
code involved in product generation?

Cheers,
SiriJodha

-- 
Siri-Jodha Singh KHALSA, Ph.D., SMIEEE
National Snow and Ice Data Center
University of Colorado
Boulder, CO 80309-0449 Phone: 1-303-492-1445 GV: 1-303-736-9976
http://cires.colorado.edu/~khalsa