The Proai update cycle currently fails when it encounters a record with a setSpec like "1:a", but only the "1:a" set exists in the database (the inferred superset, "1" does not). This can occur if the set information for "1" is not provided by the OAIDriver at set update time.
When doing an update of set information in the database, Proai should go through all setSpecs and make sure that all possible inferred supersets exist. in the database. If they don't, it should add the appropriate entry to the rcSets table. The set name in this case can just be the setSpec string. When this occurs, a warning should also be logged noting the lack of the set info object for the inferred superset. (seeUpdater.java#updateSets(Connection))
This work can be done on the Proai trunk. When finished, the updated lib should be committed to the services/oaiprovider/trunk/lib.