View source

From ISFDB

You do not have permission to do that, for the following reasons:

• You do not have permission to edit pages in the Page namespace.
• The action you have requested is limited to users in one of the groups user, Write.

You can view and copy the source of this page:

==Schema Summary== +-------------+------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +-------------+------------+------+-----+---------+----------------+ | cleanup_id | int(11) | NO | PRI | NULL | auto_increment | | record_id | int(11) | YES | | NULL | | | report_type | int(11) | YES | MUL | NULL | | | resolved | tinyint(1) | YES | | NULL | | | record_id_2 | int(11) | YES | | NULL | | +-------------+------------+------+-----+---------+----------------+ ==Description== The cleanup table stores record IDs flagged by the nightly cleanup job. It is used by the "Cleanup report" menu and its numerous cleanup report. * '''cleanup_id''' - Unique record id for the cleanup table. * '''record_id''' - Record ID of the record that was flagged as "suspect" by the nightly cleanup job. Whether it refers to an author, title, publication, publisher, etc record is dependent on the report_type value (see below.) * '''report_type''' - Cleanup report number. * '''resolved''' - Flag indicating whether this record has been marked "resolved" and will be ignored by the nightly cleanup job in the future. The supported values are NULL if the record has not been resolved and 1 if it has been resolved. * '''record_id_2''' - A secondary record ID. Used by some cleanup reports that need to store 2 record IDS in order to identify the problem. For example, the report that looks for potentially duplicate author names needs to store the IDs of two authors.

Return to Schema:cleanup.