Opened 12 years ago

Closed 9 years ago

#18 closed defect (fixed)

timestamp for SASdata or SASentry

Reported by: prjemian Owned by: prjemian
Priority: major Version:
Keywords: timestamp Cc:


Daniel Franke notes today in an email:

I can't find a timestamp associated with a SASdata or SASentry?! Such a timestamp (collection begin/end or begin and exposure time) would simplify to compare SASentry/SASdata-sections over time (think of tests for radiation damage in biological samples on repeated exposure of the same sample). For now it's not clear to me in which order SASdata-blocks were obtained; the tag-order in XML is, as far as I know, not significant and SASentry/Run is not limited to sequential numbers.

Change History (4)

comment:1 Changed 12 years ago by prjemian

  • Status changed from new to assigned

I responded:

Provision for an optional time/date stamp on the SASdata is missing from the standard.  Unintentional omission.  We are gathering revisions for v1.1 and this is appropriate to add.  Perhaps as an optional attribute to the SASdata element.  Seems more common to retain exposure time than finish time.  May just be a matter of precision since exposure times can vary from minutes to milliseconds.

If one is concerned with the order of SASdata blocks, the only provision available at present is to use the SASdata/@name attribute to convey that information. 

comment:2 Changed 9 years ago by prjemian

implement as iso8601 standard

comment:3 Changed 9 years ago by prjemian

added as optional timestamp attribute of SASdata, format is XML dateTime (ISO8601 standard)

comment:4 Changed 9 years ago by prjemian

  • Resolution set to fixed
  • Status changed from assigned to closed

fixed in [231]

Note: See TracTickets for help on using tickets.