You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Between 19:10 and 19:26 EST on 2021-04-14, I ran a batch of >1,000 rows through cspace-batch-import to create and transfer fcart Acquisition records into ba-staging.
All the acquisition records were created and transferred as expected.
However...
This was the XML for one of the rows transferred by cspace-batch-import during that time frame:
I am unable to duplicate the behavior that occurred during the batch ingest last night.
Spidey sense points toward collectionspace-mapper returning a truncated result when unable to get term lookup results from the CollectionSpace instance's API (due to scheduled restart or something?).
Need to test this and just have the record mapping fail if this is the case.
The text was updated successfully, but these errors were encountered:
Between 19:10 and 19:26 EST on 2021-04-14, I ran a batch of >1,000 rows through cspace-batch-import to create and transfer fcart Acquisition records into ba-staging.
All the acquisition records were created and transferred as expected.
However...
This was the XML for one of the rows transferred by cspace-batch-import during that time frame:
This is the XML for the same row, transferred by cspace-batch-import this morning:
I am unable to duplicate the behavior that occurred during the batch ingest last night.
Spidey sense points toward
collectionspace-mapper
returning a truncated result when unable to get term lookup results from the CollectionSpace instance's API (due to scheduled restart or something?).Need to test this and just have the record mapping fail if this is the case.
The text was updated successfully, but these errors were encountered: