Open Conal-Tuohy opened 5 years ago
A related problem is object 112121 which is a string bag which it claims is still in use, though clearly it is not. https://data.nma.gov.au/object/112121#
This looks like a data issue and ideally we would review all of the dates with this issue. I have managed to put together a list of records with production dates that need reviewing - there are around 100 of them.
In the meantime, yes I think the assumption about the production date is what should be used.
It also raises the issue around the other dates (associated dates), which I think you should leave as they are for now and we will also review these.
Hi Conal, speaking to Karen, we are going to review the problem dates - so hold off on doing anything until we have done that.
Following discussion with @f27wood, agreed to modify the interpretation of such dates for the purposes of searching only (i.e. the Solr search fields would be points in time, rather than date ranges stretching off into the indefinite future)
There is an issue with the production date fields as stored in Solr; they are assumed (sometimes incorrectly) to be date ranges which, if the end date is not specified, is understdood to mean a period which remains ongoing.
For instance, this object http://data.nma.gov.au/object/139881# (a postcard) has a Creation Activity that begins on 1937-02-06 and is still in progress today, i.e. the stored
temporal_date
value is[1937-02-06 TO *]
which is wrong.In some cases we have long-lasting events, but my feeling is that for production events, we should assume that unless the EMu record includes both an earliest and a latest date, that any "earliest date" given should be interpreted as the single point in time of the creation (i.e. that the creation is treated as instantaneous, rather than taking place within some period of time).
Thoughts?
The EMu source data is here:
root@nma-dev:/mnt/emu_data/full# xmllint --xpath "/*/*[irn='139881']" 2018-12-05_19-30_objects_86311_FULL.xml