- Article Type: Q&A
- Product: Rosetta
- Product Version: 3.2.2
Why a SIP get stuck in our Technical Analyst work bench, even though it was ingested properly by submission job?
The submission job purpose is to make the deposit. Once the SIP is created in Rosetta and there is a SIP id , from the submission job perspective, the deposit was successful. In that case the SIP folder name will include ~ at the beginning and the log of the submission job (under history) will indicate the SIP as successful.
It could be that the sip will later fall in the TA - as it may fall validation or any other reason, however that failure will NOT be indicated in the submission job. This status will be indicated in the SIP report , as this is the new ID that you can follow.
Category: Rosetta -
- Article last edited: 10/20/2014