We have a resource template that “forces” users who add new items of a given type to refer to another Omeka S item when filling the field
The following situation emerged:
- a number of items were created, and they referred to item “x” as provenance
- users realised they have not written correctly the name of “x”, so they update the name (actually, the title) of “x”. As expected, the new name appears in all items that have “x” as provenance on the related websites
- users proceed to add new items, and refer to “x” in provenance
All looks good, until people do search.
If they search for the updated name of “x” only the items created after the name change will appear. Even more surpisingly, if I search for the old name of “x” (nowhere to be visibly found in Omeka), all the items that include reference to “x” created before the name change will appear.
This happens both by searching in Omeka S backend, as well as on a site…
Again, reference to “x” appears with the updated and correct name in the website, in the backend, as well as when looking at the public APIs, and the old name is nowhere to be seen. But searching with the old name, shows all items that included reference to “x” before the name of “x” was changed.
Workaround: open all items that were created before the name change of “x” and that included “x” as provenance, and save them again without changing anything. They then appear when searching for the new name of “x” and do not appear any more when searching with the old name of “x”.
In this case it is just a few dozens items and is doable, but I suppose this is not the expected behaviour.