-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transferred items should trigger reindexing of the source instance #980
Comments
Possibly needs to be handled with a workflow change, so that the person who initiates the transfer updates both records. |
I looked into this a bit. There are tables in sul_mod_inventory_storage,
I then searched the mod-inventory-storage repo for audit_item and it looks like maybe the tables are related to keeping track of deletes. The API docs for inventory-move show holdings can be moved as well. I'm not sure what the use case for moving holdings to a different instance would be but it could probably happen. And this transferring thing makes me wonder about when stuff is transferred to SAL3, would Caiasoft update the old holdings or instance with a note too (if that's the workflow route we must go to solve this issue)? |
There are some kafka topics from inventory that I wonder if they might contain the info:
I moved item STA-12730460 (0186255d-dafa-5ed3-9a77-0d52a735edf2) from holdings record ah14193722_1 (c35bdf8b-7fbe-5907-92a3-f7ff51b381d9) to holdings record ah5680298_1 (17fd507f-93f9-5d10-8310-485f85ca914d) using the action "Move holdings/items to another instance" and looked at the kafka topics. There wasn't anything relevant in the instance or holdings-record topics but there was in item:
Maybe consuming this kafka topic might catch stuff? I look at this stuff by logging into one of the kafka pods in the k8s cluster and do |
Discussed at standup today with @ahafele the possibility that this could be a workflow thing, where the staff member adds a holdings note (or similar) to the instance that is losing its item. |
Jeanette transferred the SAL item from instance a1888067 to instance a2010714.
a2010714
was reindexed (because an item on the record had a recent updated timestamp), buta1888067
wasn't.How are we supposed to know to reindex a1888067?
The same issue may apply to deleted items and holdings:
The text was updated successfully, but these errors were encountered: