Summary: | biblio and biblio_metadata tables timestamp do not update when moving an item | ||
---|---|---|---|
Product: | Koha | Reporter: | Addie <addie> |
Component: | Database | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | arthur.suzuki, aspencatteam, mark |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Addie
2020-10-29 17:28:54 UTC
This would be very useful to our libraries. Without this working, there isn't a good way to track moving one item from a record to another record. - Bob Bennhoff I can understand the use case, but I feel like it would be giving wrong information somehow to update the timestamp on the record level without an actual change to the record. For example it would create extra updates over our API to the union catalog, where we don't transfer items, but only record changes. That probably would not be that many, but it might be worth seeing if we can figure out a different way to make the 'remove' of items known. How does Aspen Discovery get the record information from Koha, OAI-PMH? How does it deal with deleted items? Aspen Discovery is using an ODBC connection to the database to determine what records and items have changed by looking at the biblio timestamp, biblio_metadata timestamp, items timestamp. To determine which bibs and items have been deleted it looks at deleteditems and deletedbiblio. When an item has been moved to another bib, we can detect that it is changed, but we only know the new bib number, not the old bib number. So there is not an easy way to determine that the old bib record also needs to be updated to not include the item. Because items are part of the bib record, we feel it is appropriate to update the timestamp for the old bib record when the item is moved. If that turns out to not be appropriate, we would suggest creating another timestamp for when items within the biblio are created, or deleted so we can detect changes to the contents of the record. I think there is work underway to log biblio record merges, maybe we could also create a specific log entry for moving items? |