Follow up

[Peter McCartney]

Peter McCartney (peter.mccartney at asu.edu)
Center for Environmental Studies
Arizona State University
480-965-6791 

> -----Original Message-----
> From: Ken Ramsey [mailto:kramsey at jornada.nmsu.edu]
> Sent: Monday, September 09, 2002 11:21 AM
> To: peter.mccartney at asu.edu
> Subject: RE: Follow up
> 
> 
> Peter,
> 
> I have looked at the maintenance and change history. I have a 
> couple of
> questions for you:
> 
> 1. Does the ChangeScope hold either the ID, record number, or text
> string that identifies the actual record being changed?

Yes, in lieu of specifying parameters that work only to identify one record
using primary keys, i opted to accept any expression that defines the scope.
this allow you to identify scope by a record sequence number, range of
dates, etc. Its not machine parsable, but it would be flexible.


> 2. MaintenanceUpdateFrequency is the period of time that the 
> dataset is
> normally updated by?
yes...it has an enumeration domain that i took from the ISO spec - annual,
monthly, etc
 
> If the answers to the above questions are yes, then the only thing I
> would like to be able to do is add further comments 
> associated with any

So if i added <comment> as an optional string element?

> given change. For example, to explain the reason for the change. If I
> read the XMLspy correctly, all 3 elements under ChangeHistoryBase are
> required?
yes, but i would make comment optional.
> Ken
> 
> ----------------------------------------
> Ken Ramsey
> Data Manager
> Jornada Basin LTER Project
> New Mexico State University
> Wooton Hall, room 209
> Knox Street and Frenger
> Box 30003, MSC 3JER
> Las Cruces, NM 88003
> (505)646-7918 (office)
> (505)646-5665 (fax)
> keramsey at nmsu.edu
> 
> 
> >>> Peter McCartney <peter.mccartney at asu.edu> 09/09/02 10:41AM >>>
> Hi ken. are you able to view the cvs through the web interface?
> i added changes to the mainteneance element in dataset.xsd. I included
> the
> maintenance update frequency field from ISO which has several options
> for
> identifiying frequency (includeing none). I also simplified the change
> history to be simply text epxressoins of change scope, value changed
> and
> date. the detailed version wasnt working well for changes that have
> extensive scope (ie, change all area codes from 602 to 480)
> 
> 
> Peter McCartney (peter.mccartney at asu.edu)
> Center for Environmental Studies
> Arizona State University
> 480-965-6791 
> 
> > -----Original Message-----
> > From: Ken Ramsey [mailto:kramsey at jornada.nmsu.edu] 
> > Sent: Friday, September 06, 2002 4:15 PM
> > To: peter.mccartney at asu.edu 
> > Subject: Follow up
> > 
> > 
> > Peter,
> > 
> > I assume we will talk on Monday about the maintenance/change log
> > changes to EML, if necessary. It is after 5 PM here and I need to
> get
> > home. Thanks.
> > 
> > Ken
> > 
> > ----------------------------------------
> > Ken Ramsey
> > Data Manager
> > Jornada Basin LTER Project
> > New Mexico State University
> > Wooton Hall, room 209
> > Knox Street and Frenger
> > Box 30003, MSC 3JER
> > Las Cruces, NM 88003
> > (505)646-7918 (office)
> > (505)646-5665 (fax)
> > keramsey at nmsu.edu 
> > 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/eml-dev/attachments/20020909/6f977b03/attachment.htm