Interpret <status> element on GOKb TIPP
Description
Checklist
hideTestRail: Results
Activity
Felix Hemme November 15, 2019 at 10:27 AM
Hey @Owen Stephens: If the //TIPP/access@end is present & populated, then TIPP processed as normal 
tested with https://gokbt.gbv.de/gokb/resource/show/org.gokb.cred.TitleInstancePackagePlatform%3A1273556
Owen Stephens November 13, 2019 at 6:29 PM
@Felix Hemme @Benjamin Ahlborn
I've reported the problem with updates from GOKb being done correctly in https://folio-org.atlassian.net/browse/ERM-561#icft=ERM-561
As long as the accessStart/end dates are being set OK on first harvest, this issue can be passed
Felix Hemme November 13, 2019 at 2:09 PM
@Owen Stephens I can try again tomorrow and then let you know.
Owen Stephens November 13, 2019 at 2:05 PM
>If the //TIPP/access@end is present & populated, then TIPP processed as normal I've tested with https://gokbt.gbv.de/gokb/resource/show/org.gokb.cred.TitleInstancePackagePlatform%3A1273556. access_end_date in GOKbT: 2019-09-30. In Folio still 2019-08-08. This is the GOKbT lastUpdated date before I edited the access_end_date. Now lastUpdated is 2019-11-13. The change does not seem to pass or to be processed.
@Felix Hemme doing some testing locally, it looks like the problem might be the general update from GOKb to Folio, rather than the handling of Retired items with an accessEnd date. I'm doing some more investigation, but I think when the test system is refreshed tomorrow you'll see the accessEnd date come through without a problem. I'm going to do some more investigation and will log a bug once I've had a look
Owen Stephens November 13, 2019 at 11:41 AM
@Felix Hemme
> If the //TIPP/access@end is present & populated, then TIPP processed as normal
i.e. the TIPP should be added with the accessEnd date as specified in the incoming data
Details
Details
Components
Assignee
Reporter
Labels
Priority
TBD
In cases where a TIPP in GOKb, harvested by Folio, the value of the //TIPP/status element should be used to inform the updating of the equivalent PCI as follows:
If //TIPP/status == "Current" OR "Expected"
No special processing, the TIPP processed as normal
If //TIPP/status == "Retired"
If the //TIPP/access@end is present & populated, then TIPP processed as normal
If the //TIPP/access@end is not present/populated then set the relevant PCI accessEnd to the date from the //TIPP/lastUpdated element, and add entry to job log indicating that the PCI accessEnd date was guessed for that item in the harvest using "accessEnd date guessed for retired title <resource name> in <package name>"
If //TIPP/status == "Deleted"
Treat this as if the TIPP was absent from the feed - i.e. do not use the TIPP to create a package content item