Opened 11 years ago
#1124 new defect
Unsafe update check in harvesters
| Reported by: | heikki | Owned by: | heikki |
|---|---|---|---|
| Priority: | minor | Milestone: | v2.8.0 |
| Component: | General | Version: | v2.8.0RC2 |
| Keywords: | harvesting iso19139 datestamp update | Cc: |
Description
Some of the harvester protocols (CSW, at least) use the dateStamp inside the harvested metadata to decide whether or not to update a metadata if one with the same UUID is already in the harvesting catalog.
This appears to be unsafe, as the dateStamp element in ISO19139 is not (necessarily) used as a 'last modification date'; it could be used as a 'creation date' as well, causing the metadata to never get updated.
See this email thread http://osgeo-org.1560.n6.nabble.com/Question-on-regarding-dateStamp-in-iso-19139-td5011273.html.
Propose to remove the check on dates, and just always update metadata if one with the same UUID is already present. This does not break anything, only makes things possibly a bit slower. While it may prevent problems.
If you have another opinion, please come forward.
Once the next version of ISO19139 is released, there are slots for different types of dates; then, we could use the loast-modification-date element to re-introduce this check for metadata where it has a value.
