Use the Content Status Panel to see if BiblioBoard's automated Processing Phase encountered any errors with your files. If any files had issues, you may use this panel to send them your Anthology back to the Processing Phase for a second try.
Failed Files
Files sometimes do not make it through the Processing Phase. The term "Failed" describes a technical process—BiblioLabs has not decided to reject your file! Sometimes there are technical issues with the files themselves, and sometimes our system is overloaded. Please be patient as we work to pass your files through to Enhancement. Please contact creatorsupport@biblioboard.com if a large number of files fail in your Anthology.
Reprocessing
| Warning |
|---|
You will be unable to make changes to a file until it exists the processing phase. |
Click the 
button to reprocess files that have failed. In most cases, the files will pass processing successfully on the second try. If the files fail again, our technical team can investigate why.
Keep in mind that it could take up to several hours for the failed files to reprocess. If you do not want to reprocess your files at this time, move on to the Review Quality Panel. You may return to the Review Quality Panel and reprocess the failed files at your convenience.
If your files continue to fail, please contact us at creatorsupport@biblioboard.com and we’ll help you work through the issuewhere each piece of content is within the curation process.
The "content status" column indicates if the content is still in processing, if it is awaiting Review Quality, if it is awaiting Describe, if it is awaiting Collections, if it is complete or if it has been removed by the curator.
Failed Files
If a piece of content is still processing after 48 hours, contact support by filling out a form via the feedback button on the far left of the screen. If any files show up as "failed" in the Content Status Panel, this means that the file cannot be used in Creator. This happens rarely, but if it does, you can contact creatorsupport@biblioboard.com to figure out why this has happened.