Ignore:
Timestamp:
2017-08-18T19:28:42+12:00 (7 years ago)
Author:
ak19
Message:

I hope these are all the changes necessary on the runtime side of GS2 to get the OAI server validation working for GS2: instead of working out the earliest datetime stamp of the OAI repository by comparing the builddate in index/build.cfg of each OAI collection and selecting the earliest, the oai-inf.db is now storing the special earliesttimestamp record. The timestamp of this record represents its collection's earliest timestamp. And the earliest of these among all OAI collections is now the earliest datetime of the OAI repository.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • main/trunk/greenstone2/runtime-src/src/colservr/comtypes.h

    r31387 r31903  
    4848#endif
    4949
     50
     51const text_t OAI_EARLIESTTIMESTAMP_OID = "earliesttimestamp";
     52         // https://www.tutorialspoint.com/cplusplus/cpp_constants_literals.htm
    5053
    5154enum comerror_t {noError, authenticationFailure, protocolError,
     
    113116  text_tmap      dynamic_classifiers;
    114117  text_t         earliestDatestamp;   // For OAIserver validation. Time since linux Epoch, expressed as (long) integer value in string form
     118  // This field stored the builddate value from a collection's index/build.cfg file.
     119  // This field earliestDatestamp was used when oaiaction.calcEarliestDatestamp() needed to
     120  // determine the earliest timestamp of the repository, by selecting the earliestDatestamp among
     121  // all oai collections. Now it's no longer used by OAI, as that resorts to consulting oai-inf.db
     122  // of each collection, which has a collection's earliest timestamp stored, to work out the
     123  // earliest timestamp among all collections. But the build.cfg builddate stored in the
     124  // earliestDatestamp field may still be useful in future for some purpose, so leaving it alone.
     125 
    115126};
    116127
Note: See TracChangeset for help on using the changeset viewer.