Dan made a change in February that should stop all items that contain "20thcentury" anywhere in their collection names from being added to the search engine at the end of the derive.
Of the roughly 1000 items we have in the 20thcentury collection, it seems about 50 are currently in the search engine. A handful of those bypassed Dan's change because they were derived before he made it. Most of the rest seem to have been added to the 20thcentury collection (via modify_xml.php) after being derived - i.e., after they were already in the search engine. In that case, noindex=true has to be explicitly specified, along with the collection, to get the item out of the search engine. I'll remind the relevant staff.
I'll set noindex=true for all 20thcentury items now in the search engine to give us a clean slate. If any more show up in the search engine after today, please post another comment on this bug report so we know there are more holes to plug.
Dan made a change in February that should stop all items that contain "20thcentury" anywhere in their collection names from being added to the search engine at the end of the derive.
Of the roughly 1000 items we have in the 20thcentury collection, it seems about 50 are currently in the search engine. A handful of those bypassed Dan's change because they were derived before he made it. Most of the rest seem to have been added to the 20thcentury collection (via modify_xml.php) after being derived - i.e., after they were already in the search engine. In that case, noindex=true has to be explicitly specified, along with the collection, to get the item out of the search engine. I'll remind the relevant staff.
I'll set noindex=true for all 20thcentury items now in the search engine to give us a clean slate. If any more show up in the search engine after today, please post another comment on this bug report so we know there are more holes to plug.