[Treebase-guts] [ treebase-Bugs-3033740 ] Some OAI records missing required datestamp element

[SourceForge.net <no...@so...>]

Bugs item #3033740, was opened at 2010-07-23 15:55
Message generated for change (Comment added) made by vgapeyev
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1126676&aid=3033740&group_id=248804

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: APIs
Group: None
>Status: Closed
Priority: 7
Private: No
Submitted By: Kevin S. Clarke (ksclarke)
Assigned to: Vladimir Gapeyev (vgapeyev)
Summary: Some OAI records missing required datestamp element

Initial Comment:
Some of the records coming out via OAI are missing a required datestamp element in their header.

For example: http://www.treebase.org/treebase-web/top/oai?verb=GetRecord&metadataPrefix=oai_dc&identifier=TB:s1236

These records have an empty <datestamp></datestamp> element, but this isn't acceptable according to the UTCdatetimeType defined in the schema.  The record, as a result, is not valid and may cause OAI ingesters to choke.

Thanks.

----------------------------------------------------------------------

>Comment By: Vladimir Gapeyev (vgapeyev)
Date: 2010-09-16 12:04

Message:
This problem was only in the production instance.  Newer versions, as
deployed on treebase-dev, return non-empty <datestamp>. 
FYI, the <datestamp> value comes from STUDY.LASTMODIFIEDDATE table field.
According to a comment in the source code, it is the date "the author last
changed the status field (i.e. from "in progress" to "ready")".
This field is nullable in the DB, so the element is not guaranteed to be
non-empty, although all records in treebase-dev do have a value there. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1126676&aid=3033740&group_id=248804