Ticket Information - ID: #374
| ID: | Category: | Severity | Reproducibility | Date Submitted | Updated By: |
|---|---|---|---|---|---|
| 0000374 | Feature Request | normal | N/A | 04/09/10 07:45AM | lozertuser |
|
|
| Summary: | Make a |
| Description: | This idea could be complementary to the suggestion I made in the comment section to http://gelbooru.com/tracker/index.php?page=tickets&s=view&id=369 To recap, I suggested to scrap the "child-parent" dependency system altogether, so that users would use the much more convenient pool system to group pics. But there's one case where a system similar to the "child-parent" dependency system would be quite helpful. Duplicates. So, what I'm suggesting: To create a "duplicate-original" dependency that would work in a similar way as the current "child-parent" dependency system. That is, instead of the current "Parent" field, we would have an "Original" field, which we could fill with the post number of the duplicate's original. Of course, if the pic is not a duplicate, the field would be left blank. That would leave this dependency system for duplicate spotting uses only, and encourage users to use the pool system for all other cases of pic grouping. |
| Additional Info: |
th8827 replied at 2010-04-13 22:38:31  |
| I'm not sure if this is very practical. We don't exactly look at every image in full size, so it might be overlooked, especially if it is an older image. Regualr users should just use the "Flag for deletion" button when they notice a double, and indicate what image it is a double of. |
lozertuser replied at 2010-05-09 03:55:16 |
| Exactly. I agree to having the parent/child relationships scrapped in favor of the more robust pooling system. |