Discussion Forum: Thread 307861 |
|
|
| | Author: | atkk | Posted: | Aug 13, 2021 17:18 | Subject: | Instructions - combine | Viewed: | 72 times | Topic: | Catalog Requests | For: | Catalog Associate | Status: | Discarded | |
|
| Instructions for sets 41927, 41928, 41929 and 41930 should be combined into a
single listing since they are all identical.
|
|
| | | | | | |
| | | | Author: | randyf | Posted: | Aug 13, 2021 22:39 | Subject: | Re: Instructions - combine | Viewed: | 30 times | Topic: | Catalog Requests | |
|
| In Catalog Requests, atkk writes:
| Instructions for sets 41927, 41928, 41929 and 41930 should be combined into a
single listing since they are all identical.
|
This is not possible as the instructions entry for each set is directly linked
to the set entry for each set.
Cheers,
Randy
|
|
| | | | | | | | | |
| | | | | | Author: | atkk | Posted: | Aug 13, 2021 22:56 | Subject: | Re: Instructions - combine | Viewed: | 28 times | Topic: | Catalog Requests | |
|
| So how can this be addressed?
These 4 instructions are identical, but have different part numbers on Bricklink.
(and as was also mentioned for the minifig series instruction).
In Catalog Requests, randyf writes:
| In Catalog Requests, atkk writes:
| Instructions for sets 41927, 41928, 41929 and 41930 should be combined into a
single listing since they are all identical.
|
This is not possible as the instructions entry for each set is directly linked
to the set entry for each set.
Cheers,
Randy
|
|
|
| | | | | | | | | | | | | |
| | | | | | | | Author: | randyf | Posted: | Aug 13, 2021 23:09 | Subject: | Re: Instructions - combine | Viewed: | 21 times | Topic: | Catalog Requests | |
|
| In Catalog Requests, atkk writes:
| So how can this be addressed?
These 4 instructions are identical, but have different part numbers on Bricklink.
(and as was also mentioned for the minifig series instruction).
|
It can only be addressed by completely reprogramming the way the catalog database
functions in regards to instruction manuals. The chances of that happening anytime
in the foreseeable future is pretty close to nil.
|
|
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | Author: | hpoort | Posted: | Aug 14, 2021 02:27 | Subject: | Re: Instructions - combine | Viewed: | 26 times | Topic: | Catalog Requests | |
|
| In Catalog Requests, randyf writes:
| In Catalog Requests, atkk writes:
| So how can this be addressed?
These 4 instructions are identical, but have different part numbers on Bricklink.
(and as was also mentioned for the minifig series instruction).
|
It can only be addressed by completely reprogramming the way the catalog database
functions in regards to instruction manuals. The chances of that happening anytime
in the foreseeable future is pretty close to nil.
|
I was thinking to suggest (mis)using a relation type like "Same Stickers with
Different Catalog Entries" but even that won't work since it does not allow
links between instructions entries. Instructions are really the strange beast
among part/sets/gear/books/minifigures.
|
|
| | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | Author: | randyf | Posted: | Aug 14, 2021 04:50 | Subject: | Re: Instructions - combine | Viewed: | 24 times | Topic: | Catalog Requests | |
|
| In Catalog Requests, hpoort writes:
| In Catalog Requests, randyf writes:
| In Catalog Requests, atkk writes:
| So how can this be addressed?
These 4 instructions are identical, but have different part numbers on Bricklink.
(and as was also mentioned for the minifig series instruction).
|
It can only be addressed by completely reprogramming the way the catalog database
functions in regards to instruction manuals. The chances of that happening anytime
in the foreseeable future is pretty close to nil.
|
I was thinking to suggest (mis)using a relation type like "Same Stickers with
Different Catalog Entries" but even that won't work since it does not allow
links between instructions entries. Instructions are really the strange beast
among part/sets/gear/books/minifigures.
|
Instructions *and* boxes. They are both fundamentally associated with a set entry
and not their own items.
|
|
|
|
|
|
|